Unable to open Configuration Manager Service Manager - "The specified server is not a Configuration Manager site server"

Question

Unable to open Configuration Manager Service Manager - "The specified server is not a Configuration Manager site server"

BrandonM 71

I am having an issue opening the Configuration Manager Service Manager. It is returning the error "The specified server is not a Configuration Manager site server". Let me provide some background.

I recently upgraded the operating system on my only two Endpoint Manager servers from Windows Server 2012 R2 to Server 2019. I followed this Microsoft documentation for the upgrade: https://learn.microsoft.com/en-us/mem/configmgr/core/servers/manage/upgrade-on-premises-infrastructure. The OS upgrade itself went fine, however it left negative effects to the MEM system. Long story short, I was able to get all effected roles up and running correctly, but I still have some lingering issues. The one I am dealing with now is trying to access the "Configuration Manager Service Manager" from MEM console, Monitoring\System Status\Site Status > Start > Configuration Manager Service Manager. I have tried opening it remotely and from the Site Server itself, but it is returning this "The specified server is not a Configuration Manager site server" message. All site components seem to be healthy, so I do not see any obvious issues.

The only suggestion I could find on an internet search was to make sure the \siteServer\SMS_siteCode file share was up and available, which I verified it is. Is there a log file I can look at to troubleshoot? Any suggestions appreciated.

Accepted answer

1 additional answer

Your answer

Answer 1

Amandayou-MSFT 11,156

Hi @BrandonM ,

This problem could be solved after running the installation file from the backup file and reinstall the site server.

This is the step required to clean up the existing server
Clean an existing server for site server recovery only
Delete SMS registry keys: HKLM\Software\Microsoft\SMS
Delete any registry entries starting with SMS from HKLM\System\CurrentControlSet\Services.
For example:
SMS_DISCOVERY_DATA_MANAGER
SMS_EXECUTIVE
SMS_INBOX_MONITOR
SMS_INVENTORY_DATA_LOADER
SMS_LAN_SENDER
SMS_MP_FILE_DISPATCH_MANAGER
SMS_SCHEDULER
SMS_SITE_BACKUP
SMS_SITE_COMPONENT_MANAGER
SMS_SITE_SQL_BACKUP
SMS_SITE_VSS_WRITER
SMS_SOFTWARE_METERING_PROCESSOR
SMS_STATE_SYSTEM
SMS_STATUS_MANAGER
SMS_WSUS_SYNC_MANAGER
SMSvcHost 3.0.0.0
SMSvcHost 4.0.0.0
Uninstall the Configuration Manager console
Restart the server
Confirm that all of the above registry keys are deleted.

Here is the link about similar post, please refer to it.
Note: Non-Microsoft link, just for the reference.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.

BrandonM 71 Reputation points

2021-12-16T13:58:50.91+00:00

I don't understand these instructions. What is meant by "running the installation file from the backup file and reinstall site server" and "clean an existing server for site server recovery only"? This is a production site server. Wouldn't reinstalling the site server take down all of SCCM?
Jason Sandys 31,406 Reputation points Microsoft Employee Moderator

2021-12-16T15:47:35.593+00:00

Please don't do this. That's simply the first post from the thread linked to by @Amandayou-MSFT and would basically be starting over and is not what you want or need. There is another solution proposed in that thread though (it's not obvious but there is a link near the bottom of the reply: https://www.windows-noob.com/forums/topic/21157-%E5%B0%86sccm2002%E6%9C%8D%E5%8A%A1%E5%99%A8windows2012r2%E5%8D%87%E7%BA%A7%E5%88%B0server2019%E4%B9%8B%E5%90%8E%EF%BC%8C%E6%8C%87%E5%AE%9A%E7%9A%84%E6%9C%8D%E5%8A%A1%E5%99%A8%E4%B8%8D%E6%98%AFconfiguration-manager%E7%AB%99%E7%82%B9%E6%9C%8D%E5%8A%A1%E5%99%A8/).

If that doesn't work, a support case is probably in order although you could also use something like procmon to watch the activity on the site server to see if there's anything being denied.
BrandonM 71 Reputation points

2021-12-16T15:53:28.583+00:00

Thank you for the heads-up on the comment near the bottom! It worked! I rebuilt the repository using mofcomp.exe G:\Microsoft Configuration Manager\cd.latest\SMSSETUP\BIN\X64\cmprov.mof and it fixed it.
Jason Sandys 31,406 Reputation points Microsoft Employee Moderator

2021-12-16T15:54:36.1+00:00

Glad to hear.

Answer 2

Jason Sandys 31,406 Microsoft Employee Moderator

From memory, this component makes heavy use of the remote registry service to perform its work.

Have you made sure this service is running on the primary site server?

Did you perform a site reset after upgrading the OS in-place?

BrandonM 71 Reputation points

2021-12-15T19:35:04.58+00:00

Verified Remote Registry is Automatic and running. Also successfully tested remote registry query. Yes, I did site reset after the upgrade.

Share via

Unable to open Configuration Manager Service Manager - "The specified server is not a Configuration Manager site server"

1 additional answer

Your answer