WMI Health assistance for XP Workstations - DCOM/WMI

[Guest Robert Orr]

Team,

I work for a fairly large organization which is experience various

problems. We have been trying to implement various Client Server Applications

with limited success. I have spoken with Microsoft Support to have our SMS

server Upgraded to Service Pack 3. As where our Server side upgrade to

Service Pack 3 was successful the client upgrade has been only partial

upgraded. Secondly our local Workstation imaging department is using Ghost

not WDS or RIS. Therefore every new computer put on the network is different

then the last bringing all the problems with it. To make matter more

complicated Security applications are applied to some of these systems

locking them down. As we have identified little by little each problem and

how to fix each problem we are still having problems on some of are

workstation. After speaking with Microsoft Support for multiple days on the

phone and Device Lock Support they have both pointed out that we either have

a RPC problem with the workstations connecting to the network or which is

very much more likely a Local Workstation WMI problem. Our local In House

Programmer mentioned that about a 1/3 of our machines on our network have WMI

heatlh problems. Aka this is a major problem. I have exprience with Batch

startup Scripts but maintaning WMI health on local workstations is beyond my

capability as a Systems Engineer. Does anyone out there have any good

information for us that Basic WMI workstation health and also Assist with

Disecting this WMIDiag which has been run on one of our problematic machines.

Thank you all for any Assitance can supply. We suspect that DCOM is suspected

to be the culperate but through all of our time investigating these issues we

still haven't gotten to the fix. Is SMS Client DCOM or WMI somehow related?

If so why are some of our SMS clients not able to be pushed to our clients.

Regaurdless of the resolve if you guys can help me learn a little bit more on

how to interpret this Diag output and how to go about fixing WMI workstation

health then I think that will put us where we need to be. I have tried using

the WMIRepair.bat which is listed below but the WMI diag still shows errors.

 

--------------------------------- WMI Repair

 

@echo on

color 1a

cd /d c:\temp

if not exist %windir%\system32\wbem goto TryInstall

cd /d %windir%\system32\wbem

net stop winmgmt /Yes

winmgmt /kill

if exist Rep_bak rd Rep_bak /s /q

rename Repository Rep_bak

for %%i in (*.dll) do RegSvr32 -s %%i

for %%i in (*.exe) do call :FixSrv %%i

for %%i in (*.mof,*.mfl) do Mofcomp %%i

net start winmgmt

goto End

 

:FixSrv

if /I (%1) == (wbemcntl.exe) goto SkipSrv

if /I (%1) == (wbemtest.exe) goto SkipSrv

if /I (%1) == (mofcomp.exe) goto SkipSrv

%1 /RegServer

 

:SkipSrv

goto End

 

:TryInstall

if not exist wmicore.exe goto End

wmicore /s

net start winmgmt

:End

 

 

 

 

22439 11:52:19 (0) ** WMIDiag v2.0 started on Friday, July 17, 2009 at 11:50.

22440 11:52:19 (0) **

22441 11:52:19 (0) ** Copyright