Hi Team,

I have installed SCCM 2012 in my lab (Hyper V). Installation was successful. But now I am unable to push client installation on windows 7 client. Discovery method is working fine, system is getting discovered. When I use "Install Client" option, client is not getting installed. If I see the log, it says unable to contact (System Name) admin$ share but I have tried to access it via \\hostname/IP address\admin$, it is working fine. If I see the task manager in windows 7 client, ccmsetup.exe is not running. Ping is working fine from server to client and vice versa. Access to UNC path is also working fine on both sides. 

Please help someone as I am stuck here from last couple of days and cannot continue to next topic. Let me know if someone needs further information.

Thanks

Jatinder Pal

Here's the details for troubleshooting client push

http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-i-client-push-installation.aspx

Hi Paul,

Thanks for this link however I did see this link but this seems to be for SCCM 2007, will the troubleshooting client installation be same for SCCM 2012

Thanks

JPS

Since you've validated network connectivity and that the shares are accessible, the next thing is to validate that you have 1) configured a Client Push Account for the site and 2) that the Client Push Account has local administrator rights on the target device.

I hope that helps,

Nash

Yes, the above link was converted to a KB and is 99% valid for 2012.

Hi Nash,

I have validated that Client Push Account for the site is configured and the Client Push Account has local administrator rights on the target device. I am able to successfully connect to client server admin$ share and vice versa. Below is the ccm.log errors that I am getting:

======>Begin Processing request: "2097152001", machine name: "SCCMCLIENT5" SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
Execute query exec [sp_IsMPAvailable] N'GTC' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Attempting to connect to administrative share '\\SCCMCLIENT5\admin$' using account 'HJE\Administrator' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account HJE\Administrator (0000052e) SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Attempting to connect to administrative share '\\SCCMCLIENT5\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Failed to connect to \\SCCMCLIENT5\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> ERROR: Failed to connect to the \\SCCMCLIENT5\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Attempting to connect to administrative share '\\SCCMCLIENT5.hje.com\admin$' using account 'HJE\Administrator' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account HJE\Administrator (0000052e) SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Attempting to connect to administrative share '\\SCCMCLIENT5.hje.com\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Failed to connect to \\SCCMCLIENT5.hje.com\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> ERROR: Failed to connect to the \\SCCMCLIENT5.hje.com\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Attempting to connect to administrative share '\\SCCMCLIENT5\admin$' using account 'HJE\Administrator' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account HJE\Administrator (0000052e) SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Attempting to connect to administrative share '\\SCCMCLIENT5\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> Failed to connect to \\SCCMCLIENT5\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> ERROR: Failed to connect to the \\SCCMCLIENT5\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
---> ERROR: Unable to access target machine for request: "2097152001", machine name: "SCCMCLIENT5",  access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
Execute query exec [sp_CP_SetLastErrorCode] 2097152001, 5 SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
Stored request "2097152001", machine name "SCCMCLIENT5", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152001, 2 SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
Execute query exec [sp_CP_SetLatest] 2097152001, N'05/29/2015 09:09:53', 10 SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)
<======End request: "2097152001", machine name: "SCCMCLIENT5". SMS_CLIENT_CONFIG_MANAGER 5/29/2015 2:39:53 PM 2840 (0x0B18)

Please let me know if anything further required. 

 I am able to successfully connect to client server admin$ share and vice versa.

... using 'HJE\Administrator' ?

(0000052e) indicates the following error:

 "Logon failure: unknown user name or bad password."

Check your client push account settings

hje is the domain in my lab hje.com

That's not what Torsten is asking. He's asking if you tried to get to the admin$ share using the hje\Administrator account? You getting to that share with your account proves the share is available but it doesn't mean the client push process can because it's using the hje\Administrator account which means you need to try using that account to properly simulate what's going on.

As Paul pointed out though, the error code explicitly tells you what the problem is.

Thanks Paul, apologize as I am new to SCCM. I mentioned the administrator account in client push settings but I did not enter the account password and share path, when I entered that, the error is gone.

Now the different error is showing. Below is the error for ccm.log in SCCM server:

unable to connect to wmi root\ccm on remote machine "machine name", error = 0x8004100e

I can see ccmsetup.exe running on client machine in task manager and ccm folder is also created. below is the error for ccmsetup.log in client machine:

failed to get dp locations as the expected version from mp "fqdn", error = 0x87

Thanks Jason to clear this, however now that error is gone however I am getting the different error as mentioned above to Paul.

Nt all errors are fatal or unexpected.

"unable to connect to wmi root\ccm on remote machine "machine name", error = 0x8004100e"

The root\ccm namespace doesn't exist until the client agent is actually installed thus this failure simply means the client isn't installed yet and is the push processes way of checking for an existing client agent so this is perfectly normal on a client system that doesn't have the agent yet.

For 0x87d00215, have you defined your boundaries and boundary groups properly?

Yes Jason, I have created the boundary and that boundary is also part of boundary group. The client IP address is also in the range of boundary.

I ran the command wbemtest and if I click on Connect, it shows root\cimv2. I tried \\'hostname'\root\cimv2 and click on Connect, after that nothing happens, not sure if this means it is connecting successfully if there is no error while clicking on Connect.

Let me know what further information you require. 

I also want to confirm this, as I mentioned ccm.log error on server and ccmsetup.log error on client. Both are different. Initially which log file should I use to troubleshoot, server or client log file?

Also would want to add that I am able to open IIS site using http//:'FQDN' on IE in SCCM server.

Thanks

If there's no error after pressing connect from wbemtest, then yes it connected successfully. That really has almost nothing to do with client push though.

Here's a pretty detailed end-to-end walk-through of client push:

https://support.microsoft.com/en-us/kb/925282

Jason, I think I found the failure related to below error on client:

failed to get dp locations as the expected version from mp "fqdn", error = 0x87d00215

when I try to connect to below namespace using wbemtest, I get below error:

 

I haven't read the full thread, but you should remove the "." after MicrosoftIISv2

Also, that namespace will only exist on systems hosting IIS which still has nothing to do with client push as DP location is done by sending a query to the MP and does not use WMI directly.

Please read through the KB I linked above.

Also, please post the entire, relevant, and unedited snippet of ccmsetup.log showing the issue.

Torsten, sorry this is by mistake I mention (.) in it however without (.), it is showing same error. I will post the complete log file of ccmsetup.log as told by Jason.

Is your client installation successful? Can you see Software Center and configmanager in conrol panel?

Check C:\windows\ccm\logs

• Edited by Ashribad Rout 4 hours 22 minutes ago

Is your client installation successful? Can you see Software Center and configmanager in conrol panel?

Check C:\windows\ccm\logs

• Edited by Ashribad Rout Wednesday, June 03, 2015 3:24 AM

Hi Jason,

Sorry for delay, however please find the below log from ccmsetup.log file on client computer:

==========[ ccmsetup started in process 1860 ]========== ccmsetup 6/6/2015 3:19:18 AM 2708 (0x0A94)
Running on platform X64 ccmsetup 6/6/2015 3:19:19 AM 2708 (0x0A94)
Launch from folder C:\Windows\ccmsetup\ ccmsetup 6/6/2015 3:19:19 AM 2708 (0x0A94)
CcmSetup version: 5.0.7958.1000 ccmsetup 6/6/2015 3:19:19 AM 2708 (0x0A94)
In ServiceMain ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
Running on 'Microsoft Windows 7 Ultimate ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required. ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
SslState value: 224 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
CCMHTTPPORT:    80 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
CCMHTTPSPORT:    443 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
CCMHTTPSSTATE:    224 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
CCMHTTPSCERTNAME:     ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
FSP:    DC1 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
CCMFIRSTCERT:    1 ccmsetup 6/6/2015 3:19:19 AM 1512 (0x05E8)
Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
Retry time:       10 minute(s) ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
MSI properties:    INSTALL="ALL" SMSSITECODE="HJE" FSP="DC1" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
Source List: ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
                  \\dc1.jps.com\SMSClient ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
                  \\DC1.JPS.COM\SMSClient ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
MPs: ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
                  dc1.jps.com ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
No version of the client is currently detected. ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 6/6/2015 3:19:20 AM 1512 (0x05E8)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 6/6/2015 3:19:21 AM 1512 (0x05E8)
Sending Fallback Status Point message to 'DC1', STATEID='100'. ccmsetup 6/6/2015 3:19:21 AM 1512 (0x05E8)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 6/6/2015 3:19:21 AM 1512 (0x05E8)
Params to send FSP message '5.0.7958.1000 Deployment ' ccmsetup 6/6/2015 3:19:21 AM 1512 (0x05E8)
sending with winhttp failed; 80072efd FSPStateMessage 6/6/2015 3:19:22 AM 1512 (0x05E8)
Running as user "SYSTEM" ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Detected 41835 MB free disk space on system drive. ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Checking Write Filter Status. ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=HJE))' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202E8308201D0A0030201020210625EB12FB19AD7AB434C5B7B94CE5D5C300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3135303230353035353533315A180F32313135303131333035353533315A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100B9BA256B16822BE68304487DCDADC8C9E21BD9AD2A4E7DB5F101BFFEF7D269649485E55285D8FB778188F0902BF2DA18B3E5A4EE66DAEB5B24260C8E45730A4E513DB69A963C7B9A0772D791644640D97A2C9C8F5D53941B05C0782D96B7D6867E26294B72C3996334D95A973AA06E3D05377C04DAAB15F0BB8B5832360C0830F538E67BD0BB7783964D212F29070A0BA9D4DEDC80B37B47125E4D221143750B9B67038381837C1E5A65BF7D36F3C03F1139BA498A1D7945366D86EAEDEB91FD0A182088FF4746D49A2168012D67C619FBF73C3583D17639920258AA81623BF817D4E2A6E35247F3DC06F7A4184A973D8F55A90019F3C11FF279B650AFEF96490203010001A330302E30160603551D11040F300D820B6463312E6A70732E636F6D30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B050003820101003D748B1D32E154788D5A39EBA5CAEDB835C98498D62B5E529014AC1509D48193E2EDAED278BD495162BC0086F7CD92472BBF4C2E95A9E99AE70AF8C0FB967DA7D7AA5EA139130F1544ED293EF134C2A0AD4E208FED5097168A990A707EC35094B58E7066F5281B6DC799507841A73F857FCCB19E380CE74108C665159DD0F396D0F92E2251464D179E4A5691B94FF33A44E3439A0500B9BBBF3A89E3E2078188C8007E2D82187B6D3DD26624F3AD1A37BC377ADADF5A5BC87A5CAFCDBD472295E024E79D3F8351DF036594F3F046F054DC6D3CDC86857E7924A98DA43D6E94C28D6EF3CC0EDEC7905CC273660E9A9B5A914B1A8B6117590F5992E1EE3DEF29BE</SiteSigningCert></SecurityConfiguration><RootSiteCode>HJE</RootSiteCode><CCM> <CommandLine>SMSSITECODE=HJE FSP=dc1</CommandLine> </CCM><FSP> <FSPServer>dc1.jps.com</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="jps.com" /><Forest Value="jps.com" /></ClientOperationalSettings>' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
The MP name retrieved is 'dc1.jps.com' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
MP 'dc1.jps.com' is compatible ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Retrieved 1 MP records from AD for site 'HJE' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Retrived site version '5.00.7958.1000' from AD for site 'HJE' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
SiteCode:         HJE ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
SiteVersion:      5.00.7958.1000 ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Only one MP dc1.jps.com is specified. Use it. ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Searching for DP locations from MP(s)... ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Current AD site of machine is Default-First-Site-Name LocationServices 6/6/2015 3:19:23 AM 1512 (0x05E8)
Local Machine is joined to an AD domain LocationServices 6/6/2015 3:19:23 AM 1512 (0x05E8)
Current AD forest name is jps.com, domain name is jps.com LocationServices 6/6/2015 3:19:23 AM 1512 (0x05E8)
DhcpGetOriginalSubnetMask entry point is supported. LocationServices 6/6/2015 3:19:23 AM 1512 (0x05E8)
Begin checking Alternate Network Configuration LocationServices 6/6/2015 3:19:23 AM 1512 (0x05E8)
Finished checking Alternate Network Configuration LocationServices 6/6/2015 3:19:23 AM 1512 (0x05E8)
Sending message body '<ContentLocationRequest SchemaVersion="1.00">
  <AssignedSite SiteCode="HJE"/>
  <ClientPackage/>
  <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
    <ADSite Name="Default-First-Site-Name"/>
    <Forest Name="jps.com"/>
    <Domain Name="jps.com"/>
    <IPAddresses>
<IPAddress SubnetAddress="10.0.0.0" Address="10.0.0.102"/>
    </IPAddresses>
  </ClientLocationInfo>
</ContentLocationRequest>
' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
Sending message header '<Msg SchemaVersion="1.1"><ID>{07FB8010-C179-417E-AFB6-8B0E6796E972}</ID><SourceHost>SCCMCLIENT2</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:SCCMCLIENT2:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>dc1.jps.com</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-06-05T21:49:23Z</SentTime><Body Type="ByteRange" Offset="0" Length="1096"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
CCM_POST 'HTTP://dc1.jps.com/ccm_system/request' ccmsetup 6/6/2015 3:19:23 AM 1512 (0x05E8)
GetDPLocations failed with error 0x80072efd ccmsetup 6/6/2015 3:19:24 AM 1512 (0x05E8)
Failed to get DP locations as the expected version from MP 'dc1.jps.com'. Error 0x80072efd ccmsetup 6/6/2015 3:19:24 AM 1512 (0x05E8)
Sending Fallback Status Point message to 'DC1', STATEID='101'. ccmsetup 6/6/2015 3:19:24 AM 1512 (0x05E8)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 6/6/2015 3:19:24 AM 1512 (0x05E8)
Params to send FSP message '5.0.7958.1000 Deployment ' ccmsetup 6/6/2015 3:19:24 AM 1512 (0x05E8)
sending with winhttp failed; 80072efd FSPStateMessage 6/6/2015 3:19:25 AM 1512 (0x05E8)
Next retry in 10 minute(s)... ccmsetup 6/6/2015 3:19:25 AM 1512 (0x05E8)

Let me know if anything further required or what step should I follow now.