This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 23%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Some clients fail to be installed，I can't find any method to solve it, please help me, think you!
SCCM client installation failed, a total of about 1800 devices were identified, after nearly two months, only about 520 device clients were successfully installed.
Two methods of pushing the client through SCCM console and group policy delivery were tried.
This was the mathod group policy delivery.
This are my Site Status.
Server version :WinServer2016
SQL Server version: SQL Server2016
Configuration manager version: 2303
This is the ClientLocation.log
This is LocationServices.log
Anything in ccmsetup.log?
I found the log on the computer that failed to install, please help me analyze it. Thank you very much!
Hello,
Have you tried the client Push installation from the console? Refer to my following blog post:
On your failed machines, does the GPO applied correctly? Can you see the ccmsetup folder under %WINDIR% ? What does ccmsetup.log says?
Regards,
Youssef Saad | Blog: https://youssef-saad.blogspot.com/ | LinkedIn
At the first time, I have pushed the installation from the console, but it still failed. And the second time, I tired push inatallation from the group policy and half of the machines still failed
. nAnd ow there is a new problem. Last week, I deleted the long-unused machines in the AD, and also deleted and reloaded the client identified in SCCM. Before deletion, about 500 devices were identified, and after re-identification, only about 400 devices were identified. After two weeks of loading, there are now around 500 units. I would like to ask why does it take so long to recognize the devices that have successfully installed the client. And if my earlier question had anything to do with that?
There are no ccm logs on the computer without the client installed.
Hi,
Thank you for posting in Microsoft Q&A forum.
1,Please check the ccm.log in the server logs to see if the server received the request from the client and if the ccmsetup.exe service was able to successfully run on the targeted client machine. For more troubleshooting steps, please refer to:
Troubleshooting SCCM ..Part I (Client Push Installation )
2,Please copy the client agent install files from the site server to destination computer and manually install the client agent to have a try. Refer to:
How to Manually Install SCCM Client Agent
Thanks for your time. Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I have tried to manually install the client agent, but it took two installs before it was successful.
Hi,
Thanks for your reply. Do you mean if we manually install the client agent, it will aways be successful at the second time? If yes, is there any difference in the logs between the two installations?
Best regards,
Simon
Hello,
I want to ask another question, what is a non-client system? What is a client system? Such as the bottom two pictures. If the non-client system means that the client is not installed successfully, but the client is not installed successfully why some computers can recognize the IP address of the client and the assigned site. Is this related to the fact that some of my computer clients have been installed unsuccessfully?
Look forward to hearing from you!
Hi,
Thank you for posting in Microsoft Q&A forum.
A non-client system in SCCM means a device where SCCM client is not installed or installed unsuccessfully. The IP address and assigned site of non-client systems are collection via AD when they are discovered. In my lab, it is shown like yours:
Thanks for your time. Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi,
Thank you very much! Through your answer I understand the difference between client system and non-client system.
I found the log on the computer that failed to install, clould you help me analyze it.?
Hi,
Thank you for posting in Microsoft Q&A forum.
The error code 0x8004100e means "Invalid namespace" and 0x80072ee2 means "The operation timed out".
1,Please check your boundaries and boundary groups configurations, and associate your MPs and DPs to the boundary groups. Make sure the client can communicate with the MPs and DPs.
For more detailed troubleshooting steps, please refer to the helpful article:
Troubleshooting SCCM ..Part I (Client Push Installation )
Thanks for your time. Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello,
I want to ask another question, some computers recognize the site code, but the client still shows No, what caused this situation？（as shown in the image below）
Best regards,
Simon
Hello, I want to ask another question, some computers recognize the site code, but the client still shows No, what caused this situation？（as shown in the image below） Best regards, Simon
You should start the troubleshooting from the client installation log (ccmsetup.log).
If you are pushing client remotely, take a look of ccm.log.
Regards,
Youssef Saad | Blog: https://youssef-saad.blogspot.com/ | LinkedIn
I found it
Based on the logs, the client cannot reach the MP.
Double check the health of your ConfigMgr components from the console Monitoring > System Status > Site Status & Component Status.
If there is any firewall, make sure that your clients can communicate with your MP within 80 & 443 ports.
Regards,
Youssef Saad | Blog: https://youssef-saad.blogspot.com/ | LinkedIn