Client tried to load kb3202796 on SCCM 1606 and it got stuck extracting the files. Client then decided to try loading 1610 and 1702 in quick succession, which both failed pre-req checks for disk space.
Now all upgrade options are grayed out, and cmupdate log show no useful info as this happened 10 months ago.
I've tried running the upgrade install directly from the cmupdate folders, but I get the error :
8/24/2018 9:37:35 AM: ConfigMgrSetupWizard Information: 1 : Setup detected an existing SCCM installation. Currently installed version is 8412
8/24/2018 9:37:35 AM: ConfigMgrSetupWizard Information: 1 : Phase is 000001C7
8/24/2018 9:37:37 AM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
8/24/2018 9:37:37 AM: ConfigMgrSetupWizard Information: 1 : A build other than R2SP1 is detected. Upgrade is blocked
8/24/2018 9:37:47 AM: ConfigMgrSetupWizard Verbose: 1 : Exiting SetupWPF.exe.
8/24/2018 9:38:42 AM: ConfigMgrSetupWizard Information: 1 : Setup detected an existing SCCM installation. Currently installed version is 8412
8/24/2018 9:38:42 AM: ConfigMgrSetupWizard Information: 1 : Phase is 000001C7
8/24/2018 9:38:45 AM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
8/24/2018 9:38:45 AM: ConfigMgrSetupWizard Information: 1 : CD_LATEST is not used. Recovery is blocked
8/24/2018 9:38:45 AM: ConfigMgrSetupWizard Information: 1 : A build other than SP1, R2, or R2SP1 is detected. Upgrade is blocked
: and the upgrade option is unavailable.
Can (and should) I run the CMUPDATERESET tool from one of the EasySetupPayload folders? Is there something else I should be looking at / doing that I am missing?
