Reinstalling a Management Point on a Secondary Site

I recently ran into an issue where one of my SCCM 2012 SP1 (Cu3) secondary sites that is hosted on a Hyper-V server had a corrupt management point after a power failure in the facility.

The SMS_MP_CONTROL_MANAGER showed the following errors when the site server came back online:

wmierror

Since this site system is a Secondary Site I could not simply remove the role and re-add it (A management point is a requirement for a Secondary Site).  I decided to try the following before delving into reinstalling the Secondary Site.

This is an HTTP based Management Point so I first flipped it to HTTPS, which triggers a reinstall of the MP:

https

As you might expect, this results in a failure since IIS is not configured to support SSL.  This is fine as it is only a temporary measure.

https_error

I then flipped it BACK to HTTP, which once again triggers a reinstall of the MP:

http

My Management Point is now successfully reinstalled and no longer reporting errors.

httpsuccess

Quick and painless!  🙂

Disclaimer: I have no idea if this is a “supported” process from Microsoft so you should research your issue thoroughly and contact MS Support if needed.

Gotcha to be aware for SCCM 2012 Management Points

A new blog post was released by Muhammad Adil on TechNet regarding a support case that was escalated to him about SCCM 2012 MP’s that work for a brief period before throwing errors like this in the mpcontrol.log:

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER

If you use Group Policy to control the CCMEXEC service you will want to read this article. 😉
http://blogs.technet.com/b/configurationmgr/archive/2013/09/04/support-tip-configmgr-2012-management-point-fails-with-a-500-error-after-working-fine-for-a-short-period-of-time.aspx

Some great additional information about troubleshooting 500 errors can be found here:
http://jasonwrutherford.wordpress.com/2013/08/14/management-point-problems/