Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, May 27, 2016 8:37 PM
Hi,
I have a 2012R2 server congigured as AD, DNS, DHCP, IIS and a second 2012R2 server running the 2012R2 SCCM and 2014 SQL.
I followed Gerry Hampson's blog and several youtube video and I cannot install the Client when I push it from my SCCM.
Checking the ccm.log I see Unable to connect to WMI (root\ccm) on remote machine "CONCORDSCCL01", error = 0x8004100e.
Checking the ccmsetup.log file on my Win7 client I get Failed to get client version for sending state messages. Error 0x8004100e.
I am not able to paste the enire log file as it contains links and my account wasn't verified yet.
Any help is appreciated.
Thanks a lot!
All replies (9)
Friday, May 27, 2016 10:10 PM | 1 vote
Log files are about more than just finding error messages and codes. You need to read and follow them in context.
The first message above is not fatal (and thus not an/your issue) -- you can see this because the log continues to show activity for that system after the message.
The second message is the result of other issues encountered during setup. These should be shown above this error message in the log.
Jason | http://blog.configmgrftw.com | @jasonsandys
Sunday, May 29, 2016 1:50 AM
can you share the ccmsetup.log and the ccm.log on OneDrive or other service so that we can review the logs? as Jason said, logs need to be read in context and having the entire log helps with that.
jeff
Monday, May 30, 2016 8:12 AM
Dear Sir,
Don't know which blog you are referring, please check below for client deployment:
Prerequisites for Windows Client Deployment in Configuration Manager:
https://technet.microsoft.com/en-sg/library/gg682042.aspx
ConfigMgr Client Installation Troubleshooting Check List:
Troubleshooting SCCM ..Part I (Client Push Installation )
Best regards
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com
Wednesday, June 1, 2016 1:23 PM
Thanks for your replies! I am so new to SCCM and your help is so valuable to me.
Here are my log files
Monday, June 6, 2016 4:14 AM
It looks like your management point is configured to use HTTPS. Do you have certificates set up for the clients?
CCM_POST 'HTTPS://CONCORDSCCM01.CONCORD.TEST/ccm_system/request'
Begin searching client certificates based on Certificate Issuers
Completed searching client certificates based on Certificate Issuers
Begin to select client certificate
The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'.
There are no certificates in the 'MY' store.
GetSSLCertificateContext failed with error 0x87d00280
GetHttpRequestObjects failed for verb: 'CCM_POST', url: 'HTTPS://CONCORDSCCM01.CONCORD.TEST/ccm_system/request'
GetDPLocations failed with error 0x87d00280
Failed to get DP locations as the expected version from MP 'HTTPS://CONCORDSCCM01.CONCORD.TEST'. Error 0x87d00280
Failed to find DP locations from MP 'HTTPS://CONCORDSCCM01.CONCORD.TEST' with error 0x87d00280, status code 200. Check next MP.
Wednesday, June 8, 2016 3:15 PM
Hi Nick2095. I think you are right. I don't think I setup any certificates for the client. I am going to look into it.
Thanks for pointing that out.
Wednesday, June 8, 2016 10:57 PM
I followed this article for creating my Client Certificates and I still cannot push the SCCM client. Any help is more than appreciated. Maybe I am not following the proper guide.
The client push was on 08/06/2016 at 6.30PM
Thanks
Wednesday, June 8, 2016 11:10 PM
You're still getting the SSL issues. Are you sure the certificates were installed properly? It is much easier if your management point is set to HTTP.
GetSSLCertificateContext failed with error 0x87d00280
Thursday, June 9, 2016 11:47 PM
Did you create certificates for your servers as well?
C:\Windows\CCM\Logs\ClientIDManagerStartup.log will point you in the right direction for certificate issues. Using SSL communication is much more complex to set up than HTTP if you aren't quite familiar with ConfigMgr. This guide is helpful - https://blogs.technet.microsoft.com/configmgrdogs/2015/01/21/configmgr-2012-r2-certificate-requirements-and-https-configuration/
You could narrow down the issue by changing your management point and distribution points to use HTTP.