ConfigMgr client not working
The article you have in the link is talking about the SMS 2003 client. What is your problem?Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund
April 27th, 2012 8:52am
Yeah Clara,
Pllease describe your problem,
or check the KB that would be help you,
http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspxSharad Singh | My blogs: SharadTech | Twitter:
@MrLucknowWale |
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2012 1:55pm
I have come across a few clients which the ccm client has stopped working.
When investigating I came across this article http://support.microsoft.com/kb/922362 where it states "Make sure that the type of the
Path entry is REG_EXPAND_SZ and not REG_SZ" The machines in question have a path environment variable of REG_SZ. I am a bit dubious on changing a PC's registry, bit it is appearing on a couple of machines so far - Is it safe to change
to an expandable string value as described in the Microsoft article? And also, if I DON'T change it, will this prevent the PC from ever being managed correctly by ConfigMgr? Has anyone come across this before?
Thanks,
CJ
April 27th, 2012 2:38pm
Sorry for the delay:
%SystemRoot%\System32\Wbem was not listed in environment path variables in Registry. I have added this. (I also see now that that article is for sms 2003 clients, thanks and I have not changed it from REG_SZ to REG_EXPAND_SZ)
Ran a wmirepair through SCCM Client Center.
Stopped and restarted ccmexec service.
But afterward, it restarts but then shuts down (ccmexec.log) :
Starting CCMEXEC service... 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Running on machine BGMIDDT05869 as user SYSTEM. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
ERROR!! WBEM not found in the system path. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Successfully added WBEM to the process environment variable PATH. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Initializing COM. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Registering for logging change notifications. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Setting default logging component for process. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Setting service status to RUNNING. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Checking configuration. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Successfully Created Thread for CheckConfiguration. Waiting for Configuration to Complete 27/04/2012 14:39:42
CcmExec 344 (0x0158)
Failed to open to WMI namespace '\\.\root\ccm' (8004100a) 27/04/2012 14:39:42 CCMEXEC 364 (0x016C)
Failed to connect to CCM namespace 27/04/2012 14:39:42 CCMEXEC 364 (0x016C)
Starting phase 0 initialization. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Initializing performance counters. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Initializing thread pool. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Initializing task engine. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Initializing system task processor. 27/04/2012 14:39:42 CcmExec 344
(0x0158)
Registering for Network Change Events. 27/04/2012 14:39:42 CcmExec
344 (0x0158)
Creating global objects. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
SystemRequiredSeconds registry value is not set. 27/04/2012 14:39:42 CcmExec
344 (0x0158)
Entering Certificate Maintenance 27/04/2012 14:39:42 CcmExec 344
(0x0158)
Client SSL is disabled. Setting state to 0x0. 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Certificate (0xa4818) is Exportable 27/04/2012 14:39:42 CcmExec 344 (0x0158)
Failed to open to WMI namespace '\\.\root\ccm' (8004100a) 27/04/2012 14:39:43 CcmExec 344 (0x0158)
CCMDoCertificateMaintenance() failed (0x8004100a). 27/04/2012 14:39:43 CcmExec 344 (0x0158)
Failed to open to WMI namespace '\\.\root\CCM\Events' (8004100a) 27/04/2012 14:39:43 CcmExec 344 (0x0158)
CCMDoCertificateMaintenance() raised CCM_ServiceHost_CertificateOperationsFailure status event. 27/04/2012 14:39:43 CcmExec
344 (0x0158)
Loading service settings. 27/04/2012 14:39:43 CcmExec 344
(0x0158)
Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8004100a) 27/04/2012 14:39:43 CcmExec 344
(0x0158)
Error loading service settings. Code 0x8004100a 27/04/2012 14:39:43 CcmExec
344 (0x0158)
Phase 0 initialization failed (0x8004100a). 27/04/2012 14:39:43 CcmExec 344
(0x0158)
Service initialization failed (0x8004100a). 27/04/2012 14:39:43 CcmExec
344 (0x0158)
Shutting down CCMEXEC... 27/04/2012 14:39:43 CcmExec 344 (0x0158)
UninitCommandExec failed (0x800401fb). 27/04/2012 14:39:43 CcmExec 344 (0x0158)
Waiting up to 2 seconds for active tasks to complete... 27/04/2012 14:39:43 CcmExec 344 (0x0158)
Finished shutting down CCMEXEC. 27/04/2012 14:39:43 CcmExec 344 (0x0158)
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 8:53am
Did you restart the computer after adding the path variable? If the restart doesn't solve it, repair or reinstall the ConfigMgr client.
I encountered this once, but can't remember if a restart, a repair, or both was required to fix the client.
Nicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile
May 5th, 2012 9:21am
Yes the machine had rebooted & still getting the same. I've now repaired the client via client push, I'll monitor it and see what happens over the next day. I'm still unsure as to why I am finding some clients (which were working fine)
now do not have the %SystemRoot%\System32\Wbem listed as an environment path variable. I had thought Group Policies to be a culprit but am assured there are no policies in place that would override this... I have a few clients like this, so I'll perform the
same steps and see where that gets me.
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 9:44am
Let us know.
In my case, it was missing because someone intentionally removed it. No clue why they would do that though.Nicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile
May 5th, 2012 10:50am
I would double check your path variables also.
The reg value should be REG_EXPAND_SZ cause %SYSTEMROOT% get taken literal and not as a variable if it's set to REG_SZ.
if you did
c:\windows\System32\Wbem that would work as a REG_SZ ,
%SystemRoot%\System32\Wbem would have need to be REG_EXPAND_SZ
Check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
there should be a registry entry called windir and it should be REG_EXPAND_SZ %SYSTEMROOT%
Make sure PATH is REG_EXPAND_SZ and %SystemRoot%\System32\Wbem is part of the PATH enviorment
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%SystemRoot%\System32\Windows System Resource Manager\bin;;%systemroot%\idmu\common;
This is a example PATH statement for a typical windows 7 machine path variable.
Not sure this will help but good luck reguardless
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 11:49am
An update on the re-installation. Again this has not worked. I am still getting the above errors in ccmsetup.log and service shutdown..
Joseph, I have taken your suggestion and edited the Path variable from %systemroot%\system32\WBEM to c:\windows\system32\wbem (as it is currently set as REG_SZ)
Again, I will monitor and post back if successful.
May 6th, 2012 6:21am
A repair through Client Push installation and reboot does not work. Same again. So as a next step, I have uninstalled the client completely and re-installed. I'm going to wait toward the end of today/ tomorrow
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2012 6:51am