You find a computer that is not getting client. You ping it and it responses. You try to go to the adminshare of the computer like this \computeradmin$ and you get this:
The CCM.log file is looking like this for the client push:
======>Begin Processing request: "XJ7MRG1P", machine name: "MACHINE"
—> Trying each entry in the SMS Client Remote Installation account list
—> Attempting to connect to administrative share ‘MACHINE.Domain.localadmin$’ using machine account.
—> Failed to get token for current process (5)
—> ERROR: Failed to connect to the MACHINEadmin$ share using account ‘Machine Account’
—> Attempting to connect to administrative share ‘192.168.212.162admin$’ using ‘Machine Account’
—> Connected to administrative share on machine 192.168.212.162 using ‘Machine Account ‘
—> Attempting to make IPC connection to share 192.168.212.162IPC$
—> Searching for SMSClientInstall.* under ‘192.168.212.162admin$’
CWmi::Connect(): ConnectServer(Namespace) failed. – 0x800706ba
—> Unable to connect to WMI on remote machine "MACHINE", error = 0x800706ba.
—> Deleting SMS Client Install Lock File ‘192.168.212.162admin$SMSClientInstall.S01’
Stored request "MACHINE_Domain_Local.Domain", machine name "MACHINE", in queue "Retry".
<======End request: "MACHINE_Domain_Local.Domain", machine name: "MACHINE".
A normal person would now say. It is WMI that is the issue here. But it is not. The clients WMI is working fine. How could I know this? Keep reading…
If I convert 0x800706ba to decimal using the command: " Set /a c=0x06ba "
I get 1722. If I ask windows what this means using: " net helpmsg 1722 "
I get the following respons: "THE RPC SERVER IS UNAVAILABLE"
OK. Let’s investigate. I can ping it, but not map it. Target account name usually means that the name is directing you to the wrong IP. The first I would check would be DNS. If you find the machine in DNS and you also see that another machine is having the same IP then there is your answer. Set up scavenging immediately. In my case this was the issue:
Here you see that 3 computers is having the same IP. It is no wonder why SCCM can’t push clients to all machines. When it resolves the machine there are also 2 others having the same record.
However if this is not the case, then I would start psexec against the IP of the machine and start cmd. Then I would type hostname to see what the computers real name is. In almost every case you will see that this is another machine then you believe it is.
Okay then, back to the WMI issue. As you see SCCM is trying to connect to MACHINE.Domain.local and is receiving 192.168.212.162. The computer is answering, but it is not MACHINE that is answering. It is Machine1. And therefore we get the RPC Server unavailable message from WMI, because we are trying to connect to the wrong machine with a different name.
In order to really clean things up I would also check the machine account in active directory and look at the lastlogontimestamp attribute. It could be that this machine object should be deleted. But the most important lesson to be learned here is that DNS should always be kept nice and tidy.
Anyways, Happy Client Pushing