Reinstalling a Management Point on a Secondary Site
By William Bracken
Published October 30, 2014
Estimated Reading Time: 3 minutes

Have a corrupt Management Point on a System Center Configuration Manager 2012 Secondary Site Server?  If so, you are likely seeing the following error in the SMS_MP_CONTROL_MANAGER component status:

 

MP could not write out CCM settings to WMI.  Possible cause: MP didn’t get installed properly.

wmierror

I experienced this issue when the Hyper-V server hosting the Secondary Site suffered a power failure.  Given a Management Point Role is a requirement for a Secondary Site,  simply removing the role and re-adding it is not an option.  What to do?  Rebuild the Secondary Site server?  Well that would likely get you the result you are looking for, however there is a much quicker way to at least attempt a repair of your MP before you do that!
 
The following steps allow you to effectively trick you server into re-installing the MP role, and let’s be honest, who doesn’t like to trick their server?

What’s the trick?  Pretty simply actually, modify the client connection type from HTTP to HTTPS (or vice versa), and the back again.  Ok, so maybe trick isn’t really the right word as this is expected behavior for SCCM, but it does sound more dramatic.

 

In the scenario below, the corrupt MP is configured for HTTP client connections.  Navigate to the properties of the Management Point and select HTTPS, then click OK.  This will trigger a re-install of the MP Role.

https

After several minutes you will likely see a new error in the SMS_MP_CONTROL_MANAGER component status:

 
Site Component Manager failed to install this component, because Secure Socket Layer (SSL) is not configured properly on the Internet Information Server.
 

Given this was an HTTP MP, IIS has not been configured for SSL so this error is to be expected and can be ignored as it is only a temporary measure.

https_error

Go back to the properties of your Management Point and flip it BACK to HTTP, then click OK.  This once again triggers a re-install of the MP Role:

http

The result is a successfully re-installed Management Point that is no longer reporting errors.

httpsuccess

As you can see this is a much quicker and simplified process to re-installing a Management Point role on a Secondary Site server.  This not guaranteed to work in every scenario of course.  The success rate is determined by the overall health state the server is in.  In my humble opinion however, this is certainly worth a few minutes of your time attempting this prior to the much more lengthy process of re-installing the Secondary Site server altogether!

Post Tags: Management Point
Article By William Bracken
Partner – Model Technology Solutions William is an experienced and results-driven IT geek who is passionate about the “automation of things,” with an extensive background in systems management, advanced OS deployment automation, and overall infrastructure automation. He has more than 19 years of experience in IT, and has designed and implemented management solutions that have dramatically reduced support costs and ultimately brought consistent and well managed operating environments to organizations across the US.

Related Posts

Paying high cyber-insurance premiums?

Prove you’re cyber-ready and reduce your premiums through our NIST-based cybersecurity assessment. Then make the most of your assessment results through monthly consulting sessions with our vCISO Director of Cybersecurity.

Learn More