After reading through some other posts, etc. I went back and looked at some
of my previous steps I took in trying to correct my problems. In early
December, I had downloaded the WMIDiag tool from Microsoft. I had tried to
address some of the issues from running that tool. Well, I ran it again and
I think it is pointing me in the direction I need to go. Here are some of
the results, I think this is really the crux of my issues. There are 6
warnings that some WMI DCOM components registration are missing from the
following EXE/DLLs:
C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL
(\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL
(\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL
(\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL
(\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL
(\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL
(\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
WMI System components are not properly registered as COM objects, which
could make WMI to fail depending on the operation requested.
In addition there are 5 similar instances of the following (I won't include
all, you can get the idea though):
DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation
Permissions): ........................... MODIFIED.
!! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
** - REMOVED ACE:
** ACEType: &h0
** ACCESS_ALLOWED_ACE_TYPE
** ACEFlags: &h0
** ACEMask: &h1
** DCOM_RIGHT_EXECUTE
The REMOVED ACE was part of the DEFAULT setup for the trustee.
** Removing default security will cause some operations to fail!
** It is possible to fix this issue by editing the security descriptor
and adding the ACE.
** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
!! ERROR: Overall DCOM security status:
...................................................... ERROR!
That last line says it all really. So, it appears that I can run the
DCOMCNFG.exe and edit it to fix the 5 "ACE" errors and I can attempt to
re-register the other components using "REGSVR32.EXE <Filename.DLL>" (I know
I have tried this several times previously with these two DLLs and with not
much success). So my actual questions are:
1) Do I need to remove the incorrect DLL registry entries for the
"mis-registered" components (the bigger log file says there is an incorrect
root provided).
2) What exactly does "ACE" mean? And how did these "trustees" get removed?
I would not have removed them (knowingly anyway).
3) I am fairly adept and comfortable with editing the registry and running
the configuration components, but this seems fairly tedious and lengthy - is
there a more simple and elegant solution? If not, I will set aside a block
of time and just coffee up and power through.
4) Is this actually going to fix my problem? I have been down this path
previously and thought I had fixed it before. (I really shouldn't be doing
these things so late at night I guess)
Anyway, I hope this detail helps in deciphering my problem. I really do
appreciate the time and input anybody my have to help me. I realize that my
initial post lacked specific detail and I wasn't very polite. I apologize.
Thank you!
