Hello!

I'm having problems in SCCM client installation to computers. Here's the scenario:

SCCM server: Windows Server 2012 R2 + SCCM 2012 R2

Clients: Windows XP SP3 + Windows 7 ~160 computers.

When I try client push installation from SCCM console, I can deploy SCCM client to ~50 computers successfully (this includes both Windows XP & Windows 7 computers). Clients do not have firewall installed or set ON, or access to internet. Server has firewall, but everything should be opened for successful client installation (those ~50 computers prove that everything should be ok). When I check ccm.log from SCCM server, I get roughly 50 error messages for different computers (including again both Windows XP and 7 operating system):

---> Unable to connect to WMI on remote machine "computername", error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 23.1.2015 6:39:53 8796 (0x225C)

These ~50 WMI problem computers reply to ping and shares can be mapped. RPC works also. All computers are discovered by using same discovery method: Active Directory System Discovery under same OU from AD. Also every computer belongs to same SCCM site and are in same network. I am very confused about this situation. I've checked few WMI problem computers WMI function. WMI works fine. Oh and also the account which is used for client push installation belongs to computers local administrators group.

Any ideas about this situation? Is the WMI corrupted in about 50 computers (I'm talking about xp & 7 windows and old and new computers)? I really can't figure this one out. Any help would be greatly appreciated.

Hi,

What if you install the client manually on one of the computers does it work then? The error translates to "The RPC server is unavailable." so it sounds like an issue with firewall anyway.

I normally use this great startup script instead of client push that Jason has written it is great and adds a lot of features as well like, patch and so on. http://blog.configmgrftw.com/configmgr-client-startup-script/

Regards,
Jrgen

+1 on the Start up script.  When I had these issues on onesie twosies I would just rebuild WMI.

Stop windows mgmt instrumental service then delete the folder  c:\windows\system32\wbem\repository

That would resolve those issues.

 Is the WMI corrupted in about 50 computers

No. As Jorgen pointed out, this is an unreachability issue. It is possible that the WMI needs to be repaired, but you should not jump to that conclusion.

Have you checked if you can connect to WMI locally?

Also note that it could be something different on each and every system.

Hello again and sorry for delay! I've been trying to pinpoint the problem, but alas have not yet succeeded.

When I try manually install SCCM client everything seems to go OK. I copied whole client folder from SCCM server (to client computer) and tried to run it using admin account. I can see that event viewer starts ccmsetup.exe, but after that nothing, after trying to reboot nothing and after waiting couple of hours STILL nothing. This happened on few computers and 1 computer was successful in installing SCCM client, but I can't really say was it because of manual install or something else.

I also tried using group policy to install automatically SCCM client to computers, but it doesn't seem to do its job very well. I've managed to add few clients now and then to SCCM, but after experimenting with so many things can't really say what works and what doesn't.

Deleting and rebuilding WMI is not an option since it can brake some programs and in my job environment that is not an option so I can't try that. As I said in my earlier post WMI seems to be working OK (at least when looking from services and trying wbemtest), so I don't know anymore if that is the main problem.

I really can't understand, even manual installation doesn't seem to work. Startup script is in .vbs and I'm not too comfortable to be running something on every computer which I'm responsible for unless I know exactly what that script is doing.

You're now describing separate issues. The first you described was during push and occurred well before ccmsetup would have been executed on the target system. The second happened during ccmsetup.

For the first, have you tried to connect remotely to WMI on the target systems?

For the second, you will have to examine ccmsetup.log and possible client.msi.log.

You're now describing separate issues. The first you described was during push and occurred well before ccmsetup would have been executed on the target system. The second happened during ccmsetup.

For the first, have you tried to connect remotely to WMI on the target systems?

For the second, you will have to examine ccmsetup.log and possible client.ms

Ultimately, you've got lots of different problems here so don't treat them as all the same thing. Also, you do know that XP is no longer supported, correct?

You should go through the following KB for additional help -- kinowing what exactly happens in the process will help you isolate where the issues lie: https://support.microsoft.com/kb/925282

I've been trying to figure out some kind of red string which would connect all - or most - of these problems. Seems like there is not one. In the end I've left without any good ideas and I have to walk to the computer and do some searching. It is time consuming, but what need to be done needs to be done. Luckily there isn't so much faulty computers left..

Yes I know XP isn't no longer supported :) We are trying to update our computers, but can't really do it over one night, so we update computers in little groups to Windows 7. Thanks for that article, I'll check it right away..