Upgrading SCCM to 1706 Woes

Everyone thought upgrading would be easy right?

🚨🚨 IMPORTANT NOTICE🚨🚨
🦄 We moved to our brand new blog at MEM.Zone 🦄
🚨🚨 IMPORTANT NOTICE🚨🚨

16.08.2017 — Microsoft has updated the Package :)

Refresh of Update 1706 for System Center Configuration Manager (Current Branch)

https://support.microsoft.com/en-us/help/4039380/update-for-system-center-configuration-manager-version-1706-first-wave

This week (01–04.08.2017)we planned to upgrade our SCCM Test Environment to 1706. No more Production Updates without validation, especially after the issues we had upgrading to 1702 :D.

Issues encountered:

• Package Download would not complete
• Prerequisites check would not start
• Installation option grayed out

Workaround:
After trying everything from deleting package from disk, deleting Database References, using CM Update Reset Tool from the 1706 package with reported “success”, the only thing that saved the day in the end was:

• Copy SCCM_Install_Folder\EasySetupPayload\b7700d5c-d16f-40da-bb0d-a8c5a90822b9\SMSSETUP\TOOLS\CMUpdateReset\cmupdateReset.exe to a different Location.
• Run cmupdateReset.exe with following parameters:

Site_Database_FQDN = Your Site Database FQDN
SCCM_Database = Your SCCM Database Name
Update_Package_Name = Problem SCCM Update Package ID (In this case: b7700d5c-d16f-40da-bb0d-a8c5a90822b9)
FORCE = Without the force parameter even though the reset tool reported reported “success”, we could not move to installation phase

cmupdateReset.exe -S Site_Database_FQDN -D SCCM_Database -P Update_Package_Name -FORCE

In the end it’s always fun spending a couple of days of troubleshooting SCCM Upgrades :)

Please use Github for 🐛 reporting and feature requests 🌈