See all of the top support solutions for our most common issues here
I had an interesting case the other day and since I didn’t see it documented anywhere I thought I’d mention it here in case anyone else runs into it. What can happen is that when you try to install the Configuration Manager 2007 agent on a workgroup machine when connected over Internet, which does not have access to the Active Directory, the agent installation may fail with the following error:
Action start 21:42:22: CcmValidateInternetConfigurations. [21:42:22] The 'CCMHOSTNAME' is passed as msi parameter and the value is 'sccm2007.scs.in'. [21:42:22] Client Internet MP Host Name is 'sccm2007.scs.in'. [21:42:22] The msi parameter 'CCMHTTPSSTATE' is missing . [21:42:22] Providing MSI parameter 'CCMHOSTNAME' means client is IBCM enabled. [21:42:22] Client must be in Native mode while it is IBCM enabled. [21:42:22] @@ERR:26001 MSI (s) (A0!BC) [21:42:22:523]: Product: Configuration Manager Client -- Error 26001. The Management Point (MP) must be in Native mode when client is internet enabled.
Error 26001. The Management Point (MP) must be in Native mode when client is internet enabled.
MSI: Action 21:42:22: CcmValidateInternetConfigurations. Setting Security Configurations ccmsetup 6/30/2009 9:42:22 PM 1772 (0x06EC) MSI: The Management Point (MP) must be in Native mode when client is internet enabled. ccmsetup 6/30/2009 9:42:22 PM 1772 (0x06EC) Installation failed with error code 1603 ccmsetup 6/30/2009 9:42:23 PM 1772 (0x06EC) Next retry in 120 minute(s)... ccmsetup 6/30/2009 9:42:24 PM 1772 (0x06EC)
For some reason it seemed that specifying the /native switch was not kicking off. We next tried including the CCMHTTPSSTATE=1 property in the command line, so the command line looked like this:
ccmsetup.exe /source: C:\ccmclient /native: CCMALWAYSINF=1 SMSMP=sccm2007.scs.in SMSSITECODE=CEN DNSSUFFIX=scs.in CCMHOSTNAME=sccm2007.scs.in ccmhttpsstate=1
Only after we included the CCMHTTPSSTATE=1 property did the installation succeed.
Hope this helps,
Adnan Ezzi | System Center Support Engineer
I know this is quite a while on this post, however I'd like to thank you for this post......This is the only place I have seen mention about the ccmhttpsstate=1 property. I was wondering why my client always wanted to use http instead of https even though I specified native mode.
I dont see this CCMHTTPSSTATE switch in the client installation properties article in TechNet.
Also how did the client install without having SiteSigning cert in command linewhen it is in Internet?