FIX: Site assignments do not work in a System Center 2012 Configuration Manager site environment


Consider the following scenario:
  • You have a Microsoft System Center 2012 Configuration Manager site environment. 
  • You import a third-party root certification authority (CA) certificate by using the Configuration Manager console. 
  • There is an ampersand (&) or other nonalphanumeric character in the CertificateIssuers string.
In this scenario, site assignments may not work.

Note If you remove the nonalphanumeric character from the CertificateIssuers string, site assignments work as expected.

When this problem occurs, an entry that resembles one of the following is logged in the the LocationServices.log file:
  • Example 1

    LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'ABC'
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=ABC))'
    parentElement, HRESULT=80004005
    LSGetCapabilitiesAndADMembershipFromCliOpSettings(sCliOpSetting, sCapabilities, sNull, sNull), HRESULT=80004005
    LSGetSiteVersionFromAD : Failed to retrieve version for the site 'ABC' (0x80004005)
    LSIsSiteCompatible : Failed to get Site Version from all directories
    sSMSAssignedSite.length(), HRESULT=80004005
  • Example 2

    Refreshing security settings over AD
    ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=ABC))'
    true == doc.LoadFromString(sOperationalXML), HRESULT=87d00217
    Failed to refresh security settings over AD with error 0x87d00217.
Additionally, when you click Find Site in the Configuration Manager Console, an entry that resembles the following is logged in the MP_Location.log file:
  • Example 1
    MP_GetSiteInfo (CCB) MP_LocationManager datetime 9128 (0x23A8)
    CHandleLocationRequest::CreateReply failed with error (8000ffff). MP_LocationManager datetime 9128 (0x23A8)
    MP LM: Message discarded MP_LocationManager datetime 9128 (0x23A8)


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must have Cumulative Update 1 for System Center 2012 Configuration Manager Service Pack 1 installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Note We recommend that you close Configuration Manager Administration Console before you install this hotfix package.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.