Article ID: 2891764 - View products that this article applies to.
When you use the Add-CMStateMigrationPoint Windows PowerShell cmdlet that was introduced in Cumulative Update 1 for System Center 2012 Configuration Manager Service Pack 1 to create a new State Migration Point (SMP), an incorrect ServerRemoteName value is set. Additionally, you receive the following error message in the Smpisapi.log file:
::SecureAccess(pszStorePath, m_sAccessAccount, dwAccess, bGrantAccess), HRESULT=80070043 (e:\nts_sccm_release\sms\server\smp\isapi\smprequesthandler.cpp,941) smpisapi
AddACE to store with access account failed for directory \\SMPSTOREM_28C49E47$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi
hr, HRESULT=80070043 (e:\nts_sccm_release\sms\server\smp\isapi\smprequesthandler.cpp,2311) smpisapi
Revoke access failed for directory \\SMPSTOREM_28C49E47$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi
StatusRequest::UpdateStatus failed with errorcode (0x80070043) smpisapi
This issue occurs because the Add-CMStateMigrationPoint PowerShell cmdlet incorrectly sets the ServerRemoteName property for the state migration point to the fully qualified domain name (FQDN) of the first server in the hierarchy. Therefore, the client selects the best state migration point by locality (same IP subnet, same Active Directory site, and so on) but then uses the wrong FQDN to communicate with the state migration point.
To resolve this issue, use a Windows PowerShell script that resembles the script that is used for the distribution point. For example, use the following script:
Article ID: 2891764 - Last Review: October 21, 2013 - Revision: 3.0