client installation failed. MP is not compatible.

[curns]

Hi All,

 

Firstly, thanks for the guides they are a huge help.

 

I've just set up a new Windows Server 2012 server and installed SCCM 2012 SP1 with all roles except SQL. I've enabled the Software Update-Based Client Installation and it successfully installs on my test clients. Everything was going well until I noticed the client is failing to install on a lot of workstations. It seems to be workstations that have already got an older version of the client installed. The ccmsetup.log shows:

 

...

 

HTTP is selected for Client. The current state is 0. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

The MP name retrieved is 'sccm-server01.contoso.com' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>' ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

MP 'sccm-server01.contoso.com' is not compatible ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Retrieved 0 MP records from AD for site 'ABC' ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

FromAD: command line = SMSSITECODE=ABC ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Current AD forest name is contoso.com, domain name is contoso.com ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Domain joined client is in Intranet ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CMPInfoFromADCache requests are throttled for 01:00:00 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

SslState value: 255 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Detected sitecode 'ABC' from AD. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CCMHTTPPORT: 80 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CCMHTTPSPORT: 443 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CCMHTTPSSTATE: 255 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CCMHTTPSCERTNAME: ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

FSP: ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CCMCERTISSUERS: CN=CA-SERVER; DC=contoso; DC=com ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CCMFIRSTCERT: 1 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Looking for MPs from AD... ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CMPInfoFromADCache requests are throttled for 01:00:00 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

FromAD: command line = SMSSITECODE=ABC ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Current AD forest name is contoso.com, domain name is contoso.com ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Domain joined client is in Intranet ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CMPInfoFromADCache requests are throttled for 01:00:00 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Current directory 'C:\Windows\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

Failed to parse '"C:\Windows\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

A Fallback Status Point has not been specified. Message with STATEID='307' will not be sent. ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

CcmSetup failed with error code 0x80004005 ccmsetup 20/02/2013 9:35:31 PM 4732 (0x127C)

 

My guess is the old 2007 client is some how causing the issue. The bit I've highlighted orange seems to suggest that. We had a 2007 sccm server on another domain. The workstations were migrated to a new domain and thus why I am setting up a new 2012 server. I tried running ccmsetup /uninstall and then let windows update attempt to install the new version but the same error occurs.

 

Desperate for help!

 

Thanks,

Curns

 

[curns]

Hi Again,

 

I've tried ccmsetup /uninstall but it was not doing anything! So I ran the old ccmclean /all tool on the workstation. (I know it is not supported). The old client is now uninstalled. I renamed the softwareDistribution folder to .old and tried again. Getting the same error:

 

 

Current directory 'C:\Windows\SoftwareDistribution\Download\Install' is not a valid source location.

No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue.

ccmsetup.log:

==========[ ccmsetup started in process 4748 ]========== ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Running on platform X64 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Launch from folder C:\Windows\SoftwareDistribution\Download\Install\ ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CcmSetup version: 5.0.7804.1000 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Ccmsetup command line: "C:\Windows\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Local Machine is joined to an AD domain ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Current AD forest name is contoso.com, domain name is contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Domain joined client is in Intranet ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Begin checking Alternate Network Configuration ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Finished checking Alternate Network Configuration ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Adapter {A686B2C1-EEF1-421E-9A82-4C887789A921} is DHCP enabled. Checking quarantine status. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Current AD site of machine is Site1 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Attempting to query AD for assigned site code ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=175768123)(MSSMSRangedIPHigh>=175768123))(&(MSSMSRangedIPLow<=3232249857)(MSSMSRangedIPHigh>=3232249857))))' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.122.0.0)(mSSMSRoamingBoundaries=192.168.56.0)(mSSMSRoamingBoundaries=Site1)(mSSMSSiteCode=ABC)))' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSIsSiteCompatible : Verifying Site Compatibility for <ABC> ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Current AD forest name is contoso.com, domain name is contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Domain joined client is in Intranet ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'ABC' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=ABC))' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site 'ABC' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities> ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSIsSiteCompatible : Site <ABC> Version '5.00.7804.1000' is compatible. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

LSGetAssignedSiteFromAD : Trying to Assign to the Site <ABC> ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Got site code 'ABC' from AD. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=ABC))' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>63</SecurityModeMask><SecurityModeMaskEx>63</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=CA-SERVER; DC=contoso; DC=com</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>30820305308201EDA0030201020210150E25BC7002F1A54A175086DAB426CC300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303231313232323933305A180F32313133303131393232323933305A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009E00430F06414C5D35833448E88136BD66B9CFF2438D8356CCFFF23420507D697780208315A13E5CDDB5240AC4EF49A7AC72DBCB4E465166297DD61618AF9032F0B4B6D776D8E4FE2B44E7B55EEC3506AB04E056ED45DE1ED1B0AFB476412228E7325B54E51054FDD2DE64C866F4EF78332D2218B7C2EE2B03CCEE5A0E3B7BBCB16EC0A9717F77C65394925DA42CE1BA24760F5808E1C9DDAFAE97DE3AB87852F743B54F5D7253D869C4BEFCAB63F85BA83D0BA6B6825166C97CC115758CFECCFB20286E364F15255E868E727C9878BA9E9FBB1D72FD8C1A2A6719D97EF813F989E7D80FC3029664C28CB4F7A9B210B0DB6F53BC2E885A5CC7652685DC9FB9930203010001A34D304B30330603551D11042C302A82287072642D7065722D7363636D30312E617061632E62697263686D616E67726F75702E636F6D2E617530140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100011B194CC1C20055DF958EC1AD5695D48791FACF786842AFC2219D434D0A0D6AD39B896B208E72D3DF9AB3159015BD2C3CCC4B82FD89D7FD9E16D0802E51D7EE7C35840629395F416EDF2FAFB8449780D73F083D269F1034CAC20BDF738A60A098D0463D271CADC3ED039CFAB59DED80497BE9D66F74074F395E712D59FC84E16ED147A00D73C7051CD05641592EB44BCE9408EBCF897FF287ABDECA7965FFA926FA9E71F3D9A47E2DCD1F50576397CDED204B722FF43E78BAC212200CE74E611FAC6F7E5B0E889DE4639224A0C274C00E47BFCB62ECE7C77CAEFB611653E8FCAC61E2FBBCBB84F72813BA4CF4D6AE50F82A0EA7D876FADE0939765A52EA90CD</SiteSigningCert></SecurityConfiguration><RootSiteCode>ABC</RootSiteCode><CCM> <CommandLine>SMSSITECODE=ABC</CommandLine> </CCM><FSP> <FSPServer>sccm-server01.contoso.com</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState" Value="63" /></Capabilities><Domain Value="contoso.com" /><Forest Value="contoso.com" /></ClientOperationalSettings>' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

HTTP is selected for Client. The current state is 0. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

The MP name retrieved is 'sccm-server01.contoso.com' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

MP 'sccm-server01.contoso.com' is not compatible ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Retrieved 0 MP records from AD for site 'ABC' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

FromAD: FSP = sccm-server01.contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

FromAD: command line = SMSSITECODE=ABC ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Current AD forest name is contoso.com, domain name is contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Domain joined client is in Intranet ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

SslState value: 255 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Detected sitecode 'ABC' from AD. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CCMHTTPPORT: 80 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CCMHTTPSPORT: 443 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CCMHTTPSSTATE: 255 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CCMHTTPSCERTNAME: ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

FSP: sccm-server01.contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CCMCERTISSUERS: CN=CA-SERVER; DC=contoso; DC=com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CCMFIRSTCERT: 1 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Looking for MPs from AD... ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

FromAD: FSP = sccm-server01.contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

FromAD: command line = SMSSITECODE=ABC ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Current AD forest name is contoso.com, domain name is contoso.com ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Domain joined client is in Intranet ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Current directory 'C:\Windows\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Failed to parse '"C:\Windows\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Sending Fallback Status Point message to 'sccm-server01.contoso.com', STATEID='100'. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Params to send FSP message '5.0.7804.1000 Deployment ' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

State message with TopicType 800 and TopicId {1006FF85-C847-495B-80B1-DAC117FA53C7} has been sent to the FSP FSPStateMessage 21/02/2013 12:00:54 PM 2028 (0x07EC)

Sending Fallback Status Point message to 'sccm-server01.contoso.com', STATEID='307'. ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

Params to send FSP message '5.0.7804.1000 Deployment "C:\Windows\SoftwareDistribution\Download\Install\ccmsetup.exe" ' ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

State message with TopicType 800 and TopicId {82D8AF65-E9AD-462A-9C76-0DB73E41BD2A} has been sent to the FSP FSPStateMessage 21/02/2013 12:00:54 PM 2028 (0x07EC)

CcmSetup failed with error code 0x80004005 ccmsetup 21/02/2013 12:00:54 PM 2028 (0x07EC)

I don't understand why it is not working. It works fine on newly built machines which have never had the client installed before.

Thanks,

curns.

[curns]

Just thought I would update this thread in case anyone else reads this. I think the issue is related to using https and it seems the windows update method was trying to use http for some reason. The log shows:

 

HTTP is selected for Client. The current state is 0

 

I was able to manually install the client by running the command: C:\Windows\SoftwareDistribution\Download\Install>ccmsetup /usePKICert /mp:HTTPS://sccm-server01 SMSSITECODE=ABC

 

I the end, I enabled the client push installation method and it successfully deployed to all my workstations (after applying a group policy to open file & print and WMI ports for windows firewall, see http://technet.microsoft.com/en-us/library/bb694088.aspx)

 

Curns.

[hollisorama]

Just thought I would update this thread in case anyone else reads this. I think the issue is related to using https and it seems the windows update method was trying to use http for some reason. The log shows:

 

HTTP is selected for Client. The current state is 0

 

I was able to manually install the client by running the command: C:\Windows\SoftwareDistribution\Download\Install>ccmsetup /usePKICert /mp:HTTPS://sccm-server01 SMSSITECODE=ABC

 

I the end, I enabled the client push installation method and it successfully deployed to all my workstations (after applying a group policy to open file & print and WMI ports for windows firewall, see http://technet.microsoft.com/en-us/library/bb694088.aspx)

 

Curns.

 

I'm getting the same "HTTP is selected for Client. The current state is 0" when using the Software update Point based isntallation, but it is only happening on clients that are in a remote location accross a WAN over our MPLS network. Clients here at my location, select HTTPS. I'm not sure why.

 

Once the isntallation selects HTTP, it's lights out for the install beecause none of my MPs are enabled for HTTP. Just to check, I changed one MP to HTTP and the installation was successful.

 

Client push installation works just fine and HTTPS and certificates are selected appropriately. I'm not sure why it has this behavior.

 

I'm looking into assigning the client installation properties via Group Policy, but I don't know if the Software Update Based installation will pay attention to those parameters. We'll see.

[hollisorama]

Alright. Problem solved. The message "HTTP is selected for Client. The current state is 0" is because we have clients that are on ConfigMgr 2007 and the site is in mixed mode. All clients have the registry key HKLM\SOFTWARE\Microsoft\CCM\Httpsstate set to 0. Clients need to have this value set to 63 for a ConfigMgr 2012 site set only for PKI to be able to install the client via a SUP. This does not affect Client Push installation methods. It is an aparent bug that has been reported to Microsoft.

 

See the thread http://social.technet.microsoft.com/Forums/en-US/67d85763-f787-4a8f-99c4-0ffa1a392829/client-install-via-wsus-fails?prof=required and look for the post near the bottom that says "Issues with GPO/WSUS SCCM 2012 (CM12) (HTTPS/PKI/Native) Client Installation/Upgrade from SCCM 2007 (CM07) (HTTP Mixed Mode) Client"

 

The fix is to use group policy preference (Computer Configuration) to set the key to 63 and scope it to clients that you are migrating to ConfigMgr 2012. I made this setting part of my GPO I'm using for SUP client deployment.