P
pt
I just had a weird problem. I have been trying to get a laptop setup
so that I can have several configurations of security settings,
computer name, workgroup, network connections, etc. I was trying to
use the "Hardware Profiles" feature to accomplish this (doesn't
work-Windows just can't do what I need). A secret side benefit of
adding or renaming the hardware profiles is that the Computer
Management plugin (compmgmt.msc) stopped working! It took me a while
to track this down. The System Log had this to say about it:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service WinMgmt with arguments "" in order to
run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
This gave me a hint, which didn't sink in for a day or two. I finally
wised up and checked the Windows Management Instrumentation service
(via services.msc). It wasn't running and wouldn't start. Checking
the WMI service's Properties/Log On, I found that the WMI service (and
WMI Driver Extensions) had not been enabled for my new profiles.
Enabling it allowed compmgmt.msc to run.
One other service (an ATI keybd handler) was also not running.
Another hint was to look at the service list for anything set as
"Startup Type Automatic" but not started.
so that I can have several configurations of security settings,
computer name, workgroup, network connections, etc. I was trying to
use the "Hardware Profiles" feature to accomplish this (doesn't
work-Windows just can't do what I need). A secret side benefit of
adding or renaming the hardware profiles is that the Computer
Management plugin (compmgmt.msc) stopped working! It took me a while
to track this down. The System Log had this to say about it:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service WinMgmt with arguments "" in order to
run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
This gave me a hint, which didn't sink in for a day or two. I finally
wised up and checked the Windows Management Instrumentation service
(via services.msc). It wasn't running and wouldn't start. Checking
the WMI service's Properties/Log On, I found that the WMI service (and
WMI Driver Extensions) had not been enabled for my new profiles.
Enabling it allowed compmgmt.msc to run.
One other service (an ATI keybd handler) was also not running.
Another hint was to look at the service list for anything set as
"Startup Type Automatic" but not started.