Forum Discussion
Problems after upgrading SCCM from 1910 to 2002
michaelgibson I had same issue, it resolved after adding https to MP parmater, eg., SMSMP=httpS://<ServerName> SMSSITECODE=<sitecode> /mp:httpS://<sitecode>
I'm seeing the same thing on a few of our clients during the client upgrade (both Windows 10 and server). This has happened using our internal MP and removing the client fully and pointing them to our CMG which has a valid GoDaddy certificate on and both have exactly the same issue.
I've worked around this issue after trying lots of different things including client removal/clean/cert/registry deletion etc. with no luck. Because we have a CMG I mentioned I also tried the token install which failed with exactly the same error but the following got the client to install against our internal MP:
1. Uninstall client
2. Try installing client with the token command line (will fail)
3. Uninstall client again. This takes ages as if you watch the ccmsetup.log you can see it cycling through trying to connect multiple times before it finally tries to remove it
4. Run the old SCCM ccmclean utility
5. Delete SMS certs from the store
6. Install the client using local files
There will probably be other combinations that get this to work more efficiently (may not need the local files) but I just needed to get these couple of servers fixed.
Who knows what MS have done to break ccmsetup but I hope they fix it soon.
michaelgibson I had same issue, it resolved after adding https to MP parmater, eg., SMSMP=httpS://<ServerName> SMSSITECODE=<sitecode> /mp:httpS://<sitecode>
Where do you change the code to https? I go into the MP properties and don't find anywhere where I can change the httpS in the sitecode. Please assist.