Forum Discussion

PaulKlerkx's avatar
PaulKlerkx
Iron Contributor
Jun 21, 2020

MECM client over CMG

Hi, I have recently upgraded from MECM 1910 to 2002.  the client is deploying ok to intranet based devices, but no devices on CMG are getting the new client.   Where do I go to troubleshoot this? ...
cloud-attached management
Anandkumar's avatar
Anandkumar
Copper Contributor
Aug 15, 2020

PaulKlerkx you can use standalone SCCM client package to upgrade the Client version. Use the following SCCM client installation parameter 

 

"C:\windows\ccmsetup\ccmsetup.exe" /nocrlcheck /mp:https://cmg.cloudapp.net/CCM_Proxy_MutualAuth/6257556037928694 CCMHTTPSSTATE=31 CCMHOSTNAME=CMG.CLOUDAPP.NET/CCM_Proxy_MutualAuth/62057556037928694 SMSSiteCode=PS1 AADTENANTID=5004305e-6764-4e6b-b9a4-c4d5ccfd1524 AADCLIENTAPPID=3C6a28b2-9d0a-484d-8553-7cb0d4897512 

PaulKlerkx's avatar
PaulKlerkx
Iron Contributor
Aug 16, 2020

Anandkumar Thanks for that info,  I'll try to take a look tomorrow.  

 

One thing I thought of, since I configured CMG, I haven't modified the Client Push installation properties for our site.  Should I have?  We currently only have the SMSSITECODE property in there.  (could this be the reason for the CMG client install failures??)

 

 

*************************************************************************

I had quick look at the command line you posted

 

"CCMHTTPSSTATE=31" - the documentation doesn't seem to mention this.  I have looked at the logs of an internal machine and it has  CCMHTTPSSTATE="1472" , any idea what the different numbers equate to or what the purpose of the property is?  the only google results I can find don't have much information on it.  

https://docs.microsoft.com/en-us/mem/configmgr/core/clients/deploy/about-client-installation-properties

https://docs.microsoft.com/en-us/mem/configmgr/core/clients/deploy/deploy-clients-cmg-azure