PENDING Unable to install the client on machines

[Marcos Marciano]

Good afternoon,
We have implemented SCCM in our environment, we are having difficulty installing the client on some machines in our AD of 280 machines, 50 were not installed, what could it be?

 

[Garth]

Good afternoon,
We have implemented SCCM in our environment, we are having difficulty installing the client on some machines in our AD of 280 machines, 50 were not installed, what could it be?

Review the logs for problems. But likely it is a boundary issue.

 

[Marcos Marciano]

Review the logs for problems. But likely it is a boundary issue.

So, in the logs the return is code 0. Are you referring to this limit in terms of the number of machines?

 

[Garth]

So, in the logs the return is code 0. Are you referring to this limit in terms of the number of machines?

if the setup exit code is 0 then this is likely a boundaries issue. Are you only using IP Ranges for boundaries? What make you think the client is not installed?

 

[Marcos Marciano]

Below is the printout of the cliet installation.

 

[Garth]

Below is the printout of the cliet installation.
View attachment 6089

Of what little you displayed of the log file, it looks prefect and the client is installed.

 

[Marcos Marciano]

These notebooks are not identifying the client, is there anything I can do?

 

[Garth]

These notebooks are not identifying the client, is there anything I can do?
View attachment 6097

This likely means that you are not using only IP Ranges for boundaries. Go fix your boundaries.

 

[Prajwal Desai]

What I am guessing is that the clients are installed, but they aren't reporting back to the management point because they don't have information. If you log in to one of the Windows devices, you may find the client installed, but when you open the configuration manager item from CP, you will find only two items. As @Garth mentioned, check your boundaries and use the IP address ranges because they work in all situations.

 

[Marcos Marciano]

What I am guessing is that the clients are installed, but they aren't reporting back to the management point because they don't have information. If you log in to one of the Windows devices, you may find the client installed, but when you open the configuration manager item from CP, you will find only two items. As @Garth mentioned, check your boundaries and use the IP address ranges because they work in all situations.

Where can I see that the client is installed?

 

[Garth]

Where can I see that the client is installed?

In the control panel on the device or within the install directory on the device.

 

[Marcos Marciano]

Can you help me with this error?

 

[Prajwal Desai]

Check this - https://forums.prajwaldesai.com/threads/failed-to-connect-to-admin-using-machine-account-67.1099/

 

[Marcos Marciano]

Well, I managed to solve the previous error, but then I got this erro:

 

[Harshit Pandey]

I think you have a DNS issue or some network issues.

 

[MJ-Tech]

Manually uninstall the CCMclient.exe on one of your testing devices and reboot the computer. Later, attempt to install using the following format: ccmsetup.exe SMSSITECODE=<SITE CODE> SMSMP=<SCCM SERVER> FSP=<SCCM SERVER> DNSSUFFIX=<Domain name> /mp:<SCCM MGMTSERVER> /ForceInstall. Run all cycles manually under Control Panel -> Configuration Manager. Wait for a few minutes and check the status.