After creating a new Remote DP with the “Add-CMDistributionPoint” PowerShell cmdlet Clients try downloading content from the first Server installed in the Hierarchy and not the new DP

I’ve created a new Remote Distribution Point (DP), using the Add-CMDistributionPoint PowerShell cmdlet introduced in Cumulative Update 1 (CU1), for ConfigMgr 2012 Service Pack 1 (SP1).

The DP was created successfully and I’ve been able to deploy content to it.

However, when Clients in the same location as the new DP attempt to download the content they trying to access the first Server installed in the Hierarchy and not the new DP created with PowerShell.

“Key not Found Exception” when running the Update-CMDistributionPoint –DeploymentTypeName cmdlet

When I run the Update-CMDistributionPoint –DeploymentTypeName cmdlet I get the following error message:

Key not Found Exception

Why does the Add-CMDistributionPoint cmdlet incorrectly set the value of the ServerRemoteName parameter to the name of the first installed Site Server?

I’m seeing an issue with the Add-CMDistributionPoint cmdlet incorrectly setting the value of the ServerRemoteName parameter to the name of the first installed Site Server. As a result my Clients are accessing content on the Site server instead of the intended Distribution Point server.

Why is the “refreshschedule” parameter not defined in the “NewByLimitName” parameter set when I run the “New-CMDeviceCollection” cmdlet?

I am trying to run the New-CMDeviceCollection cmdlet but when I do the refreshschedule parameter is not being defined in the NewByLimitName parameter set.

“The adapter cannot get property “GetType” for instance of SMS_ST_RecurInterval” error when the .GetType method is used for the object returned by the New-CMSchedule cmdlet

I am trying to use the .GetType method for the object returned by the New-CMSchedule cmdlet but it’s unsuccessful and I get the following error:

The adapter cannot get property “GetType” for instance of SMS_ST_RecurInterval

“The method or operation is not implemented” error when running the Clear-CMPxeDeployment cmdlet

When I run the Clear-CMPxeDeployment cmdlet I get the following error message:

The method or operation is not implemented

“Unable to cast object of type” error when running the New-CMDeviceCollection cmdlet together with the LimitingCollectionName option

I am trying to run the New-CMDeviceCollection cmdlet together with the LimitingCollectionName option.

However, this fails with the following error message:

Unable to cast object of type ‘Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlArrayItems’ to type’System.Management.ManagementBaseObject’.

Why does PowerShell quit unexpectedly when I run the “New-CMSiteSystemServer” cmdlet?

I am trying to run the ConfigMgr 2012 R2 New-CMSiteSystemServer cmdlet but PowerShell exits unexpectedly.

Why does the upgrade of a Shared Distribution Point fail when I use the “Start-CMDistributionPointUpgrade” PowerShell cmdlet?

I am trying to upgrade a shared Distribution Point (DP), to a ConfigMgr 2012 R2 DP using the
Start-CMDistributionPointUpgrade PowerShell cmdlet but it fails.

I’m seeing the following exception message:

Initiation of upgrade of BDP: server1.contoso.internal, failed.
Exception Type: System.Collections.Generic.KeyNotFoundException,Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.StartDistributionPointUpgradeCommand :: Exception Message: System.Collect
ions.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.StartDistributionPointUpgradeCommand.SetObjectProperties(IResultObject siteSystemObject, IResultObject distributionPointObject)
at Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.StartDistributionPointUpgradeCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord().

After creating a new SMP with the “Add-CMStateMigrationPoint” PowerShell cmdlet Clients try contacting the first Server installed in the Hierarchy and not the new SMP

I’ve created a new State Migration Point (SMP), using the Add-CMStateMigrationPoint PowerShell cmdlet introduced in Cumulative Update 1 (CU1), for ConfigMgr 2012 Service Pack 1 (SP1).

However, it doesn’t appear to have worked as if I look in the Smpisapi.log I see the following errors:

::SecureAccess(pszStorePath, m_sAccessAccount, dwAccess, bGrantAccess), HRESULT=80070043 (e:\nts_sccm_release\sms\server\smp\isapi\smprequesthandler.cpp,941)

AddACE to store with access account failed for directory \\SMPSTOREM_28C49E47$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473

hr, HRESULT=80070043 (e:\nts_sccm_release\sms\server\smp\isapi\smprequesthandler.cpp,2311)

Revoke access failed for directory \\SMPSTOREM_28C49E47$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473

StatusRequest::UpdateStatus failed with errorcode (0x80070043)