The specified server is not a Configuration Manager Site Server is a common error in the Configuration Manager Service Manager of Microsoft Endpoint Configuration Manager (known as SCCM). It immediately appears when you attempt to open Configuration Manager Service Manager, to view the Component Status of one of the components, like SMS_CERTIFICATE_MANAGER or SMS_WSUS_SYNC_MANAGER.
Cause of The specified server is not a Configuration Manager Site Server
The few people reporting this error mention that have upgraded the operating system from Windows Server 2012 to 2019. This is an necessary upgrade, because Windows Server 2012 will soon be unsupported by Microsoft. This means no security updates will be released from that moment on.
I’m not aware of problems when upgrading from WS 2016 to 2019. But if you do, please let me know in the comments section below!
Solution for The specified server is not a Configuration Manager Site Server
Credits should go to user Motoralizer, posting the solution in this topic. He found out it’s required to recompile cmprov.mof with the mofcomp tool. This turned out to be the easiest fix for error The specified server is not a Configuration Manager Site Server:
- Logon to the Site Server
- Open an elevated command prompt
- Navigate to your SCCM application folder. Usually %programfiles%\Microsoft Configuration Manager\cd.latest\SMSSETUP\BIN\X64. The C-drive is default, but many organizations install applications on a separate drive.
- Enter the following command to compile cmprov.mof with the mofcomp tool: mofcomp .\cmprov.mof
This will re-create missing classes. The execution of this command should take less than a second
- Close the ConfigMgr console, re-open it and try to Configuration Manager Service Manager. It should successfully connect.
More info about Configuration Manager Service Manager
The Configuration Manager Service Manager is very useful to start or stop one particular component or thread as part of troubleshooting. In fact, it allows you to manage components the same way that you manage services in Windows. The following actions apply to Configuration Manager components:
In addition, you can also configure the log location per component, as well as the maximum log size
To open and view component statuses in Microsoft Endpoint Configuration Manager, do the following:
- In the Configuration Manager console, go to the Monitoring workspace, expand System Status
- Select the Component Status node.
- In the Component group of the ribbon, select Start, and then choose Configuration Manager Service Manager.
To modify the location or log size, right click the Component and choose Logging.
For further analyses, this is the command of the moftool and stdout, in order to fix The specified server is not a Configuration Manager Site Server:
PS D:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\BIN\X64> mofcomp .\cmprov.mof
Microsoft (R) MOF Compiler Version 10.0.17763.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: .\cmprov.mof
MOF file has been successfully parsed
Storing data in the repository…
WARNING: File .\cmprov.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
PS D:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\BIN\X64>
Leave a comment!
If this article did not help you solve your problem, please leave a comment! This website is visited thousands of times a day. There is a good chance that I or someone else has an answer to your question.
In addition, if you have a better solution for this problem, please leave a comment too! It may help me improve this article, as well as you may help other users facing this issue.