I have come to realise that there are quite a few computers (400 odd) in our estate that are failing the SCCM client install (through with the following errors appearing in the ccmsetup.log
MSI: Setup was unable to create the WMI namespace CCM
The error code is 80041002
Installation failed with error code 1603
I need a script to remotely recompile .mof files on all the 400 odd computers which would help resolve the above WMI issues.
I am hoping resolving the above issue would enable successfull SCCM client installation through client push
lunes, 18 de junio de 2012 10:21
- Cambiado Moiz Rassiwala[MSFT]Microsoft employee lunes, 18 de junio de 2012 20:34 (From:Configuration Manager 2007 General)
Todas las respuestas
Prior to you rebuilding WMI on a machine,have a test performed.You can follow the below mentioned link to do the basic testing
Once the basic testing is done and if you find WMI to be corrupted,This should help you rebuild WMI on that machine
net stop winmgmt
if exist %windir%\system32\wbem\repository.old rmdir /s /q repository.old
rename %windir%\system32\wbem\repository repository.old
for /f %%s in (' dir /b *.dll' ) do regsvr32 /s %s
net start winmgmt
Let me know if this helps.
lunes, 18 de junio de 2012 10:29
Also check this ConfigMgr 2007 WMI related article - http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspxlunes, 18 de junio de 2012 10:53
Check & confirm whether the issue is with WMI.
I feel we can use psexec to copy & execute the WMI Repair script on the list of machines. But, before performing any script as such on list of machines is at high risk and I advise you to check in the test lab befor performing it.
Here below is the WMI Repair commands list for windows xp, copy it and make it as a batch file and use the psexec command to run it on all the list of machines.
net stop winmgmt /y
sc config winmgmt start= disabled
ren Repository OldRep
sc config winmgmt start= auto
net start winmgm /y
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServerlunes, 18 de junio de 2012 10:53
Please don't start off with a destructive repair of WMU by deleteing the repository. This can create alot of problems. If this is XP then do a stop of WMI and then repair WMI
rundll32 wbemupgd, UpgradeRepository
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.comlunes, 18 de junio de 2012 13:13
you can go with this post to fix wmi automatically ... http://eskonr.com/2012/01/how-to-fix-wmi-issues-automatically/
You can comment the deletion of repository folder rather deleting it.lunes, 18 de junio de 2012 13:22