PENDING Client Agent CcmSetup failed with error code 0x80004005

[Lexmc]

New install of SCCM 2012 R2. I can push client to Servers with no issues, but when I push to clients I get an error CcmSetup failed with error code 0x80004005

Here is the log

==========[ ccmsetup started in process 10792 ]========== ccmsetup 6/28/2018 2:11:37 PM 13776 (0x35D0)
Launch from folder C:\windows\ccmsetup\ ccmsetup 6/28/2018 2:11:37 PM 13776 (0x35D0)
CcmSetup version: 5.0.8239.1001 ccmsetup 6/28/2018 2:11:37 PM 13776 (0x35D0)
In ServiceMain ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Running on 'Microsoft Windows 10 Enterprise' (10.0.16299). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Ccmsetup command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
SslState value: 224 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
CCMHTTPPORT: 80 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
CCMHTTPSPORT: 443 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
CCMHTTPSSTATE: 224 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
CCMHTTPSCERTNAME: ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
FSP: ***SCPS01.***.COM ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
CCMFIRSTCERT: 1 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Config file: C:\windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Retry time: 10 minute(s) ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
MSI log file: C:\windows\ccmsetup\Logs\client.msi.log ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
MSI properties: INSTALL="ALL" MP="***SCPS01.***.COM" SMSSITECODE="***" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" FSP="***SCPS01.***.COM" CCMFIRSTCERT="1" ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Source List: ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
\\***SCPS01.***.COM\SMSClient ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
\\***SCPS01.***.COM\SMSClient ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
MPs: ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
***SCPS01.***.COM ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
MapNLMCostDataToCCMCost() returning Cost 0x1 ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
No version of the client is currently detected. ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 6/28/2018 2:11:37 PM 3180 (0x0C6C)
Updated security on object C:\windows\ccmsetup\. ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Params to send '5.0.8239.1001 Deployment Error: ' ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Sending Fallback Status Point message to '***SCPS01.***.COM', STATEID='100'. ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
<ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" Platform="2"/></ClientDeploymentMessage> ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
State message with TopicType 800 and TopicId {BDC31BBE-641E-43E7-8D86-1BEF8C8A030F} has been sent to the FSP FSPStateMessage 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Running as user "SYSTEM" ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Params to send '5.0.8239.1001 Deployment Error: 0x87d00264, ' ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
Sending Fallback Status Point message to '***SCPS01.***.COM', STATEID='328'. ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
<ClientDeploymentMessage ErrorCode="-2016411036"><Client Baseline="1" Platform="2"/></ClientDeploymentMessage> ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C)
State message with TopicType 800 and TopicId {95F448B7-FCB2-4851-B763-0D5494FD8C13} has been sent to the FSP FSPStateMessage 6/28/2018 2:12:12 PM 3180 (0x0C6C)
CcmSetup failed with error code 0x80004005 ccmsetup 6/28/2018 2:12:12 PM 13776 (0x35D0)

Digging into the issue I found that there was no share for \\***SCPS01.***.COM\SMSClient. I created this share and assigned to correct permission but no change.

I am able to access the other shares from the computer in question.

When I push I see it drop 3 files and create 2 folders (logs and Cache).
Anyone have any thoughts?

Thanks
Lex

 

[Prajwal Desai]

CcmSetup failed with error code 0x80004005 ccmsetup 6/28/2018 2:12:12 PM 13776 (0x35D0)

Digging into the issue I found that there was no share for \\***SCPS01.***.COM\SMSClient. I created this share and assigned to correct permission but no change.

You should not create any folder and assign permissions. Does installing the client agent manually on client computer works ?.

 

[Lexmc]

The Client doesn't install even is run manually. I have tried in on 3 systems now and all have the same issue. They are all running windows 10. I did see a thread about intune maybe causing an issue but no one posted a fix. or work around.

 

[Prajwal Desai]

I did see a thread about intune maybe causing an issue but no one posted a fix. or work around.

Have you configured an account that can install configmgr client agent ?. Check this post -https://prajwaldesai.com/install-configuration-manager-clients-using-client-push/

 

[Lexmc]

Yes. The account I setup has domain admin and can push to the server. I have confirmed the account has local admin rights.

 

[Prajwal Desai]

As per your log file, i see "Running as user "SYSTEM" ccmsetup 6/28/2018 2:12:12 PM 3180 (0x0C6C) ". I also want you to check other things such as firewall, WMI and ensure you have configured all things correctly. https://prajwaldesai.com/configuring-firewall-settings-for-configuration-manager-2012-r2/

 

[Lexmc]

I have confirmed the firewall and WMI GPO exist and that the local computer has received the policies.

I get the same results when I try and manually install the client even with elevated rights