Hi,
We are moving from 2007 to 2012 Sp1 via SUP method. The new 2012 SP1 environment is fully secured via PKI. A manual client install works fine with everything being discovered automatically and certificates being created and used. If we
push via SUP the client upgrade fails, the management points are discovered but are then shown in ccmsetup.log as being imcompatible...
The MP name retrieved is 'xxx' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>' ccmsetup 13/05/2013 14:14:45 4556 (0x11CC)
MP 'xxx' is not compatible ccmsetup 13/05/2013 14:14:45 4556 (0x11CC)
The MP name retrieved is 'xxx' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>' ccmsetup 13/05/2013 14:14:45 4556 (0x11CC)
MP 'xxx' is not compatible ccmsetup 13/05/2013 14:14:45 4556 (0x11CC)
Retrieved 0 MP records from AD for site 'AP1' ccmsetup 13/05/2013 14:14:45 4556 (0x11CC)
I have found that if I change the key (64-bit OS):
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\HttpsState
from 0 to 1 the installation will work correctly.
Is there a neater way to enforce ccmsetup.exe to use this via the adm? I've tried ccmsetup.exe CCMHTTPSSTATE=1 but this does not work, I also tried CCMHTTPSSTATE=480 as this number appears in the logs when it does work but this also fails.
Thanks