Fix SCCM Upgrade resulting in MP issue. If you have trouble with your Management Point after the SCCM upgrade (updated with detailed steps and info regarding WSUS)
Fix – SCCM Upgrade resulting in MP issue
How to fix MP issues after the SCCM upgrade.
- Stop SCCM services (i.e. SMS_EXECUTIVE, SMS_SERVER_LOCATOR_POINT, etc)
- Remove SMS Management, Software Updates and Reporting Point roles
- Uninstall WSUS 3.0 SP2 (don’t remove updates, logs, and WSUS database)
- Remove the Windows Process Activation Service feature (it will remove IIS)
- Reboot server
- Stop SCCM services
- Reinstall IIS, required IIS role services by SCCM, and required features (BITS Server Extensions and Remote Differential Compression)
- Reboot
- Reinstall WSUS 3.0 SP2
- Reboot
- You might need to repair or reinstall the WebDAV extensions for IIS
- Reinstall SCCM Management, Reporting, and Software Updates Point roles.
- I checked mpMSI.log and MPSetup.log and a reboot was required
- Optional: if your boot images are not updated, reassign your Task Sequences to use the new ones and inject the right drivers into them.
NOTE: If your SCCM site is in Native mode you need to remember to configure your SSL certificate for the IIS SSL bindings (HTTPS for whatever port you are using).
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
Resources
SCCM ConfigMgr MP Deinstallation failed Client Registration Issues ConfigMgr