WMI Health assistance for XP Workstations - DCOM/WMI


R

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 (c) Microsoft Corporation. All rights
reserved - January 2007.
22442 11:52:19 (0) **
22443 11:52:19 (0) ** This script is not supported under any Microsoft
standard support program or service.
22444 11:52:19 (0) ** The script is provided AS IS without warranty of any
kind. Microsoft further disclaims all
22445 11:52:19 (0) ** implied warranties including, without limitation, any
implied warranties of merchantability
22446 11:52:19 (0) ** or of fitness for a particular purpose. The entire
risk arising out of the use or performance
22447 11:52:19 (0) ** of the scripts and documentation remains with you. In
no event shall Microsoft, its authors,
22448 11:52:19 (0) ** or anyone else involved in the creation, production,
or delivery of the script be liable for
22449 11:52:19 (0) ** any damages whatsoever (including, without limitation,
damages for loss of business profits,
22450 11:52:19 (0) ** business interruption, loss of business information,
or other pecuniary loss) arising out of
22451 11:52:19 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
22452 11:52:19 (0) ** of the possibility of such damages.
22453 11:52:19 (0) **
22454 11:52:19 (0) **
22455 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22456 11:52:19 (0) ** -----------------------------------------------------
WMI REPORT: BEGIN ----------------------------------------------------------
22457 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22458 11:52:19 (0) **
22459 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22460 11:52:19 (0) ** Windows XP - No service pack - 32-bit (2600) - User
'JTFB\SCAB7' on computer 'G27-5282'.
22461 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22462 11:52:19 (0) ** Environment:
......................................................................................................... OK..
22463 11:52:19 (0) ** System drive:
........................................................................................................ C: (Disk #0 Partition #0).
22464 11:52:19 (0) ** Drive type:
.......................................................................................................... IDE (ST3250310AS).
22465 11:52:19 (0) ** There are no missing WMI system files:
............................................................................... OK.
22466 11:52:19 (0) ** There are no missing WMI repository files:
........................................................................... OK.
22467 11:52:19 (0) ** WMI repository state:
................................................................................................ N/A.
22468 11:52:19 (0) ** BEFORE running WMIDiag:
22469 11:52:19 (0) ** The WMI repository has a size of:
.................................................................................... 22 MB.
22470 11:52:19 (0) ** - Disk free space on 'C:':
........................................................................................... 221822 MB.
22471 11:52:19 (0) ** - INDEX.BTR, 1810432 bytes,
7/17/2009 10:50:51 AM
22472 11:52:19 (0) ** - INDEX.MAP, 964 bytes,
7/17/2009 10:50:51 AM
22473 11:52:19 (0) ** - OBJECTS.DATA, 21561344 bytes,
7/17/2009 10:50:51 AM
22474 11:52:19 (0) ** - OBJECTS.MAP, 10624 bytes,
7/17/2009 10:50:51 AM
22475 11:52:19 (0) ** AFTER running WMIDiag:
22476 11:52:19 (0) ** The WMI repository has a size of:
.................................................................................... 22 MB.
22477 11:52:19 (0) ** - Disk free space on 'C:':
........................................................................................... 221820 MB.
22478 11:52:19 (0) ** - INDEX.BTR, 1810432 bytes,
7/17/2009 10:50:51 AM
22479 11:52:19 (0) ** - INDEX.MAP, 964 bytes,
7/17/2009 10:50:51 AM
22480 11:52:19 (0) ** - OBJECTS.DATA, 21561344 bytes,
7/17/2009 10:50:51 AM
22481 11:52:19 (0) ** - OBJECTS.MAP, 10624 bytes,
7/17/2009 10:50:51 AM
22482 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22483 11:52:19 (0) ** Windows Firewall:
.................................................................................................... NOT INSTALLED.
22484 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22485 11:52:19 (0) ** DCOM Status:
......................................................................................................... OK.
22486 11:52:19 (0) ** WMI registry setup:
.................................................................................................. OK.
22487 11:52:19 (0) ** INFO: WMI service has dependents:
.................................................................................... 1 SERVICE(S)!
22488 11:52:19 (0) ** - Exchange Management Service (MSEXCHANGEMGMT,
StartMode='Automatic')
22489 11:52:19 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
22490 11:52:19 (0) ** Note: If the service is marked with (*), it means
that the service/application uses WMI but
22491 11:52:19 (0) ** there is no hard dependency on WMI. However,
if the WMI service is stopped,
22492 11:52:19 (0) ** this can prevent the service/application to
work as expected.
22493 11:52:19 (0) **
22494 11:52:19 (0) ** RPCSS service:
....................................................................................................... OK (Already started).
22495 11:52:19 (0) ** WINMGMT service:
..................................................................................................... OK (Already started).
22496 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22497 11:52:19 (0) ** WMI service DCOM setup:
.............................................................................................. OK.
22498 11:52:19 (2) !! WARNING: WMI DCOM components registration is missing
for the following EXE/DLLs: .................................... 6 WARNING(S)!
22499 11:52:19 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL
(\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
22500 11:52:19 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL
(\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
22501 11:52:19 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL
(\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
22502 11:52:19 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL
(\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
22503 11:52:19 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL
(\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
22504 11:52:19 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL
(\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
22505 11:52:19 (0) ** => WMI System components are not properly registered
as COM objects, which could make WMI to
22506 11:52:19 (0) ** fail depending on the operation requested.
22507 11:52:19 (0) ** => For a .DLL, you can correct the DCOM configuration
by executing the 'REGSVR32.EXE <Filename.DLL>' command.
22508 11:52:19 (0) **
22509 11:52:19 (0) ** WMI ProgID registrations:
............................................................................................ OK.
22510 11:52:19 (0) ** WMI provider DCOM registrations:
..................................................................................... OK.
22511 11:52:19 (0) ** WMI provider CIM registrations:
...................................................................................... OK.
22512 11:52:19 (0) ** WMI provider CLSIDs:
................................................................................................. OK.
22513 11:52:19 (0) ** WMI providers EXE/DLL availability:
.................................................................................. OK.
22514 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22515 11:52:19 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment'
(Launch & Activation Permissions): ........................... MODIFIED.
22516 11:52:19 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has
been REMOVED!
22517 11:52:19 (0) ** - REMOVED ACE:
22518 11:52:19 (0) ** ACEType: &h0
22519 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22520 11:52:19 (0) ** ACEFlags: &h0
22521 11:52:19 (0) ** ACEMask: &h1
22522 11:52:19 (0) ** DCOM_RIGHT_EXECUTE
22523 11:52:19 (0) **
22524 11:52:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
22525 11:52:19 (0) ** Removing default security will cause some
operations to fail!
22526 11:52:19 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
22527 11:52:19 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
22528 11:52:19 (0) **
22529 11:52:19 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment'
(Launch & Activation Permissions): ........................... MODIFIED.
22530 11:52:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has
been REMOVED!
22531 11:52:19 (0) ** - REMOVED ACE:
22532 11:52:19 (0) ** ACEType: &h0
22533 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22534 11:52:19 (0) ** ACEFlags: &h0
22535 11:52:19 (0) ** ACEMask: &h1
22536 11:52:19 (0) ** DCOM_RIGHT_EXECUTE
22537 11:52:19 (0) **
22538 11:52:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
22539 11:52:19 (0) ** Removing default security will cause some
operations to fail!
22540 11:52:19 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
22541 11:52:19 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
22542 11:52:19 (0) **
22543 11:52:19 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment'
(Launch & Activation Permissions): ........................... MODIFIED.
22544 11:52:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been
REMOVED!
22545 11:52:19 (0) ** - REMOVED ACE:
22546 11:52:19 (0) ** ACEType: &h0
22547 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22548 11:52:19 (0) ** ACEFlags: &h0
22549 11:52:19 (0) ** ACEMask: &h1
22550 11:52:19 (0) ** DCOM_RIGHT_EXECUTE
22551 11:52:19 (0) **
22552 11:52:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
22553 11:52:19 (0) ** Removing default security will cause some
operations to fail!
22554 11:52:19 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
22555 11:52:19 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
22556 11:52:19 (0) **
22557 11:52:19 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL':
......................................................................
MODIFIED.
22558 11:52:19 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE'
DOES NOT match corresponding expected trustee rights (Actual->Default)
22559 11:52:19 (0) ** - ACTUAL ACE:
22560 11:52:19 (0) ** ACEType: &h0
22561 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22562 11:52:19 (0) ** ACEFlags: &h2
22563 11:52:19 (0) ** CONTAINER_INHERIT_ACE
22564 11:52:19 (0) ** ACEMask: &h1
22565 11:52:19 (0) ** WBEM_ENABLE
22566 11:52:19 (0) ** - EXPECTED ACE:
22567 11:52:19 (0) ** ACEType: &h0
22568 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22569 11:52:19 (0) ** ACEFlags: &h12
22570 11:52:19 (0) ** CONTAINER_INHERIT_ACE
22571 11:52:19 (0) ** INHERITED_ACE
22572 11:52:19 (0) ** ACEMask: &h13
22573 11:52:19 (0) ** WBEM_ENABLE
22574 11:52:19 (0) ** WBEM_METHOD_EXECUTE
22575 11:52:19 (0) ** WBEM_WRITE_PROVIDER
22576 11:52:19 (0) **
22577 11:52:19 (0) ** => The actual ACE has the right(s) '&h12
WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
22578 11:52:19 (0) ** This will cause some operations to fail!
22579 11:52:19 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the removed right.
22580 11:52:19 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
22581 11:52:19 (0) ** Note: WMIDiag has no specific knowledge of this WMI
namespace.
22582 11:52:19 (0) ** The security diagnostic is based on the WMI
namespace expected defaults.
22583 11:52:19 (0) ** A specific WMI application can always require a
security setup different
22584 11:52:19 (0) ** than the WMI security defaults.
22585 11:52:19 (0) **
22586 11:52:19 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL':
......................................................................
MODIFIED.
22587 11:52:19 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE'
DOES NOT match corresponding expected trustee rights (Actual->Default)
22588 11:52:19 (0) ** - ACTUAL ACE:
22589 11:52:19 (0) ** ACEType: &h0
22590 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22591 11:52:19 (0) ** ACEFlags: &h2
22592 11:52:19 (0) ** CONTAINER_INHERIT_ACE
22593 11:52:19 (0) ** ACEMask: &h1
22594 11:52:19 (0) ** WBEM_ENABLE
22595 11:52:19 (0) ** - EXPECTED ACE:
22596 11:52:19 (0) ** ACEType: &h0
22597 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22598 11:52:19 (0) ** ACEFlags: &h12
22599 11:52:19 (0) ** CONTAINER_INHERIT_ACE
22600 11:52:19 (0) ** INHERITED_ACE
22601 11:52:19 (0) ** ACEMask: &h13
22602 11:52:19 (0) ** WBEM_ENABLE
22603 11:52:19 (0) ** WBEM_METHOD_EXECUTE
22604 11:52:19 (0) ** WBEM_WRITE_PROVIDER
22605 11:52:19 (0) **
22606 11:52:19 (0) ** => The actual ACE has the right(s) '&h12
WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
22607 11:52:19 (0) ** This will cause some operations to fail!
22608 11:52:19 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the removed right.
22609 11:52:19 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
22610 11:52:19 (0) ** Note: WMIDiag has no specific knowledge of this WMI
namespace.
22611 11:52:19 (0) ** The security diagnostic is based on the WMI
namespace expected defaults.
22612 11:52:19 (0) ** A specific WMI application can always require a
security setup different
22613 11:52:19 (0) ** than the WMI security defaults.
22614 11:52:19 (0) **
22615 11:52:19 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL':
......................................................................
MODIFIED.
22616 11:52:19 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
22617 11:52:19 (0) ** - REMOVED ACE:
22618 11:52:19 (0) ** ACEType: &h0
22619 11:52:19 (0) ** ACCESS_ALLOWED_ACE_TYPE
22620 11:52:19 (0) ** ACEFlags: &h12
22621 11:52:19 (0) ** CONTAINER_INHERIT_ACE
22622 11:52:19 (0) ** INHERITED_ACE
22623 11:52:19 (0) ** ACEMask: &h13
22624 11:52:19 (0) ** WBEM_ENABLE
22625 11:52:19 (0) ** WBEM_METHOD_EXECUTE
22626 11:52:19 (0) ** WBEM_WRITE_PROVIDER
22627 11:52:19 (0) **
22628 11:52:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for
the trustee.
22629 11:52:19 (0) ** Removing default security will cause some
operations to fail!
22630 11:52:19 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
22631 11:52:19 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
22632 11:52:19 (0) ** Note: WMIDiag has no specific knowledge of this WMI
namespace.
22633 11:52:19 (0) ** The security diagnostic is based on the WMI
namespace expected defaults.
22634 11:52:19 (0) ** A specific WMI application can always require a
security setup different
22635 11:52:19 (0) ** than the WMI security defaults.
22636 11:52:19 (0) **
22637 11:52:19 (0) **
22638 11:52:19 (0) ** DCOM security warning(s) detected:
................................................................................... 0.
22639 11:52:19 (0) ** DCOM security error(s) detected:
..................................................................................... 3.
22640 11:52:19 (0) ** WMI security warning(s) detected:
.................................................................................... 0.
22641 11:52:19 (0) ** WMI security error(s) detected:
...................................................................................... 3.
22642 11:52:19 (0) **
22643 11:52:19 (1) !! ERROR: Overall DCOM security status:
................................................................................. ERROR!
22644 11:52:19 (1) !! ERROR: Overall WMI security status:
.................................................................................. ERROR!
22645 11:52:19 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------------------------------------
22646 11:52:19 (0) ** INFO: WMI permanent SUBSCRIPTION(S):
................................................................................. 2.
22647 11:52:19 (0) ** - ROOT/SUBSCRIPTION,
MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario
Control".
22648 11:52:19 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE
TargetInstance ISA 'MSFT_UCScenario''
22649 11:52:19 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM
Event Log Consumer".
22650 11:52:19 (0) ** 'select * from MSFT_SCMEventLogEvent'
22651 11:52:19 (0) **
22652 11:52:19 (0) ** WMI TIMER instruction(s):
............................................................................................ NONE.
22653 11:52:19 (0) ** WMI ADAP status:
..................................................................................................... OK.
22654 11:52:19 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY:
..................................................................... 1
NAMESPACE(S)!
22655 11:52:19 (0) ** - ROOT/SERVICEMODEL.
22656 11:52:19 (0) ** => When remotely connecting, the namespace(s) listed
require(s) the WMI client to
22657 11:52:19 (0) ** use an encrypted connection by specifying the
PACKET PRIVACY authentication level.
22658 11:52:19 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
22659 11:52:19 (0) ** i.e. 'WMIC.EXE /NODE:"G27-5282"
/AUTHLEVEL:pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
22660 11:52:19 (0) **
22661 11:52:19 (0) ** WMI MONIKER CONNECTIONS:
............................................................................................. OK.
22662 11:52:19 (0) ** WMI CONNECTIONS:
..................................................................................................... OK.
22663 11:52:19 (0) ** WMI GET operations:
.................................................................................................. OK.
22664 11:52:19 (0) ** WMI MOF representations:
............................................................................................. OK.
22665 11:52:19 (0) ** WMI QUALIFIER access operations:
..................................................................................... OK.
22666 11:52:19 (0) ** WMI ENUMERATION operations:
.......................................................................................... OK.
22667 11:52:19 (0) ** WMI EXECQUERY operations:
............................................................................................ OK.
22668 11:52:19 (0) ** WMI GET VALUE operations:
............................................................................................ OK.
22669 11:52:19 (0) ** WMI WRITE operations:
................................................................................................ NOT TESTED.
22670 11:52:19 (0) ** WMI PUT operations:
.................................................................................................. NOT TESTED.
22671 11:52:19 (0) ** WMI DELETE operations:
............................................................................................... NOT TESTED.
22672 11:52:19 (0) ** WMI static instances retrieved:
...................................................................................... 2658.
22673 11:52:19 (0) ** WMI dynamic instances retrieved:
..................................................................................... 0.
22674 11:52:19 (0) ** WMI instance request cancellations (to limit
performance impact): ................................................... 0.
22675 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22676 11:52:19 (0) ** # of Event Log events BEFORE WMIDiag execution since
the last 20 day(s):
22677 11:52:19 (0) ** DCOM:
.............................................................................................................. 4.
22678 11:52:19 (0) ** WINMGMT:
........................................................................................................... 10.
22679 11:52:19 (0) ** WMIADAPTER:
........................................................................................................ 0.
22680 11:52:19 (0) ** => Verify the WMIDiag LOG at line #21947 for more
details.
22681 11:52:19 (0) **
22682 11:52:19 (0) ** # of additional Event Log events AFTER WMIDiag
execution:
22683 11:52:19 (0) ** DCOM:
.............................................................................................................. 0.
22684 11:52:19 (0) ** WINMGMT:
........................................................................................................... 0.
22685 11:52:19 (0) ** WMIADAPTER:
........................................................................................................ 0.
22686 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22687 11:52:19 (0) ** WMI Registry key setup:
.............................................................................................. OK.
22688 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22689 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22690 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22691 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22692 11:52:19 (0) **
22693 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22694 11:52:19 (0) ** ------------------------------------------------------
WMI REPORT: END -----------------------------------------------------------
22695 11:52:19 (0) **
----------------------------------------------------------------------------------------------------------------------------------
22696 11:52:19 (0) **
22697 11:52:19 (0) ** ERROR: WMIDiag detected issues that could prevent WMI
to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\SCAB7\LOCAL
SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_G27-5282_2009.07.17_11.50.18.LOG'
for details.
22698 11:52:19 (0) **
22699 11:52:19 (0) ** WMIDiag v2.0 ended on Friday, July 17, 2009 at 11:52
(W:77 E:23 S:1).
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top