RE: WMI Errors Clean install of SMS 2003

You might want to see if there is an issue with DCOM permissions. Look at the
first Q&A in the Windows Server 2003 SP1 section of
http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq02.mspx

"Skye Sands" wrote:

Could someone please give me some insight on this? I am trying to find out
if anyone else has tried running the WMIDiag.vbs tool on a clean installation
of SMS and if they recieved an Error Report or WIM Functioning Normally.

Please help,

Schuyler<Skye>

"Skye Sands" wrote:


I am attmpting to install SMS 2003 SP2 on Windows Server 2003 SP2. I just
did a FRESH install of Windows Server 2003, loaded SP2 for Windows Server
2003. After running critical updates, I reboot and then ran the WMIDiag.vbs,
and it returned that WMI is Operating Properly.

I than loaded SMS SP2, let it sit over night, checked Status and logs and
all seemed to be working properly.

I than ran the WMIDiag again. It reported numerous probelms with Security
issues in the WMI Control, stating that the Defaults have changed and it may
hinder WMI from functioning normally.

Besides those, the first warnings I recieved reference directly to SMS and
CCM. Here is the part of the report I am concerned with:

In a fresh install is this normal reaction? Why is WMI having problems?
What would cause this on a totally fresh installation? Is this a major
concern and how can I resolve it? I appreciate any assistance that I may
obtain.

Thanks,

Skye

-------------------------------------------------------------------------------------------------------------------------

29801 09:24:55 (2) !! WARNING: WMI provider DCOM registrations missing for
the following provider(s): ..................................... 2 WARNING(S)!

29802 09:24:55 (0) ** - ROOT/CIMV2/SMS, SMS_CIMV2
({********-E1EC-11D2-846E-************}) (i.e. WMI Class 'SMS_Processor')

29803 09:24:55 (0) ** Provider DLL: 'C:\WINDOWS\SYSTEM32\CCM\SMSPROC.DLL'

29804 09:24:55 (0) ** - ROOT/CIMV2/SMS, SMS_CIMLD
({********-2801-11D3-88DA-************}) (i.e. WMI Class 'SMS_LogicalDisk')

29805 09:24:55 (0) ** Provider DLL: 'C:\WINDOWS\SYSTEM32\CCM\SMSCCMLD.DLL'

29806 09:24:55 (0) ** => This is an issue because there are still some WMI
classes referencing this list of providers

29807 09:24:55 (0) ** while the DCOM registration is wrong or missing.
This can be due to:

29808 09:24:55 (0) ** - a de-installation of the software.

29809 09:24:55 (0) ** - a deletion of some registry key data.

29810 09:24:55 (0) ** - a registry corruption.

29811 09:24:55 (0) ** => You can correct the DCOM configuration by:

29812 09:24:55 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>'
command.

29813 09:24:55 (0) ** Note: You can build a list of classes in relation
with their WMI provider and MOF file with WMIDiag.

29814 09:24:55 (0) ** (This list can be built on a similar and
working WMI Windows installation)

29815 09:24:55 (0) ** The following command line must be used:

29816 09:24:55 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'

29817 09:24:55 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from
'C:\WINDOWS\SYSTEM32\WBEM\'

29818 09:24:55 (0) ** may not solve the problem as the DLL
supporting the WMI class(es)

29819 09:24:55 (0) ** can be located in a different folder.

29820 09:24:55 (0) ** You must refer to the class name to determine
the software delivering the related DLL.

29821 09:24:55 (0) ** => If the software has been de-installed
intentionally, then this information must be

29822 09:24:55 (0) ** removed from the WMI repository. You can use the
'WMIC.EXE' command to remove

29823 09:24:55 (0) ** the provider registration data.

29824 09:24:55 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\CIMV2\SMS path
__Win32Provider Where Name='SMS_CIMP' DELETE'

29825 09:24:55 (0) ** => If the namespace was ENTIRELY dedicated to the
intentionally de-installed software,

29826 09:24:55 (0) ** the namespace and ALL its content can be ENTIRELY
deleted.

29827 09:24:55 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\CIMV2 path
__NAMESPACE Where Name='SMS' DELETE'

29828 09:24:55 (0) ** - Re-installing the software.

29829 09:24:55 (0) **

.

Relevant Pages

  • WMI Errors Clean install of SMS 2003
    ... did a FRESH install of Windows Server 2003, loaded SP2 for Windows Server ... and it returned that WMI is Operating Properly. ...
    (microsoft.public.sms.setup)
  • RE: WMI Errors Clean install of SMS 2003
    ... of SMS and if they recieved an Error Report or WIM Functioning Normally. ... did a FRESH install of Windows Server 2003, ... and it returned that WMI is Operating Properly. ...
    (microsoft.public.sms.setup)
  • Re: Remotely accessing WMI information without using a Local Administr
    ... We are trying to get access to WMI information on a Windows Server 2003 ... domain user is added to the local administrator group. ... to the local administrators group. ...
    (microsoft.public.windows.server.general)
  • Re: .NET code errors on WIN 2003 Server
    ... It is also a fresh install of Windows Server 2003 SP2 with nothing else ... smaller files download without problem but larger files ...
    (microsoft.public.dotnet.general)
  • WMI Access Denied on Domain Controller
    ... After promoting my Windows Server 2003 server to a domain ... controller I can no longer access WMI Processor or WMI ... Prior to the promotion WMI worked. ... CWbemProviderGlue::Release, count is (approx) 2 ...
    (microsoft.public.windows.server.migration)