Where to look for obsolete MP data

Question

I've recently migrated to a new site, and so far everything is working well, with one exception. Lately I've had a number of clients reporting an error when they try to run Software Center. In troubleshooting this I keep coming across an entry in locationservices which points to the old MP. The entry text is "Retrieved MP <OldMP Name> from Registry". The funny thing Is I have searched the registry for this server name and the only entries I can find are related to the Admin Console. We have no GPO's that are specifying the site, and as far as I can tell MP discovery through AD\DNS is working fine. Does anyone know what registry key this message refers to or what may be setting it?

Answer 1

Hi, @John Bigg
Here is a User Voice about the same issue for your reference:
https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/34820848-i-have-a-suggestion-for-the-smsslp-parameter-and-r

And a similar thread in TechNet forum:
https://social.technet.microsoft.com/Forums/en-US/d77ff560-cfe1-403a-b0b7-b849d358b1f5/quotsmsslpquot-registry-key-shows-old-sccm-server-name?forum=configmanagerdeployment

Answer 2

Hi, @John Bigg
Thank you for posting in Microsoft Q&A forum.
Have you configured the boundaries and boundary groups correctly after migration?
And could you get some more information from ClientLocation.log?

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi @AllenLiu-MSFT
The clients are all in the proper boundaries; all of them can download and install software from the DP's. I also removed the boundaries from the old site just as a precaution. The only area that there may have been an issue was the old site objects were still in the System Management container, but I've removed those now, and the entries still appear in the Locationservices log. One thing that is different about the suspect machines is that they also have an entry in the Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM key called SMSSLP and that entry does point to the old site server. This is a throwback to our old site. I've tried uninstalling and reinstalling the client, but that key persists. The SMSSLP property is not part of our current client install properties.

The ClientLocation log contains repeated entries showing the client is in the correct site:

Getting Assigned site
Assigned Site is XXX (Our primary site code)

Current Assigned Management Point is <FQDN of our current MP> with Version 9040 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>

Answer 4

Further to this, I've found where the SMSSLP key comes from, it appears in the ccmsetup log as an msi property when the client auto-upgrades:

MSI properties: CCMCERTID="<CERTID>" CCMCERTSTORE="MY" CCMFIRSTCERT="1" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMPKICERTOPTIONS="1" DNSSUFFIX="OURDOMAIN" FSP="OURFSP" INSTALL="ALL" MANAGEDINSTALLER="0" RESETKEYINFORMATION="TRUE" SMSCACHESIZE="5120" SMSMP="CORRECT MP" SMSMPLIST="CORRECT MP" SMSSITECODE="XXX" SMSSLP="OUR OLD SITE SERVER FQDN" smsmplist="CORRECT MP"

There is also an entry showing it is using the old site server as an MP:

Lookup MP: <FQDN of old site server>

Unfortunately I cant locate where these msi properties are coming from, I know the SMSSLP role has been incorporated into the MP role, so it isn't anywhere in our current site settings, and hasn't been for a long time.

Answer 5

Hi, @John Bigg
How about manually add the SMSSLP properties with the "CORRECT MP" in Client Push Installation Properties and reinstall the client?