[gptalk] Re: WMI Not Working on all domain systems.
- From: "Nelson, Jamie R" <Jamie.Nelson@xxxxxxxxxxxxxxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Fri, 11 Jan 2008 14:14:17 -0600
Good to hear. J
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Piet Slaghekke
Sent: Friday, January 11, 2008 2:07 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Not Working on all domain systems.
Ok I found the problem. It had to do with security rights on my GPO's
When I went through each GPO's settings in GPMC some of the GPO's said
that their security settings did not coincide with those Sysvol. It
asked me to correct this is by clicking "OK" After gpupdate /force I
was able to use my WMI again!!
Thanks for the help! I am glad this issue is finally solved.
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Nelson, Jamie R
Sent: Friday, January 11, 2008 2:20 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Not Working on all domain systems.
I doubt it is the .adm templates. They shouldn't have anything to do
with WMI. The workstation doesn't really even care about them when it
processes GP. They merely only serve as a roadmap for whenever you are
editing a policy.
Since machines only exhibit the issue after being added to the domain
(not mention the fact that servers aren't affected), create a blocked
inheritance OU and pre-stage a computer account there before joining it
to the domain (also make sure you don't have any policies enforced at a
higher level). If they don't have an issue with that then you have a
policy somewhere that is causing some kind of corruption. If I had to
guess I would say something you've turned on in security policy may be
causing the issue.
To determine which policy is the problem child, link each GPO back one
at a time to the blocked inheritance OU until the issue occurs again.
You also might consider turning on verbose GP logging to pinpoint the
issue even further.
Regards,
Jamie Nelson
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Piet Slaghekke
Sent: Friday, January 11, 2008 12:35 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Not Working on all domain systems.
thanks Jamie!
I have looked at some of this. Though I have a hunch that there is
something wrong with my domain wide adm template. Since the machines
start showing wmi problems only when they are joined to a domain and I
the domain wide adm template had been corrupted and repaired.
I am thinking of creating a new GPO with a default ADM template an then
adding the settings from my current GPO adm template to see if this
helps.
do all think this might work?
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Nelson, Jamie R
Sent: Thursday, January 10, 2008 6:08 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Not Working on all domain systems.
Try going through the steps on the following article "WMI Isn't
Working!"
http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx
Regards,
Jamie Nelson
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Piet Slaghekke
Sent: Thursday, January 10, 2008 3:21 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Not Working on all domain systems.
Does anyone have an idea what this could be?
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Piet Slaghekke
Sent: Saturday, January 05, 2008 4:51 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] WMI Not Working on all domain systems.
Hello everyone,
Happy New year!
I posted about this issue a while back and still have not found a
resolution. I do have some more info about the issue:
WMI is not working on any of my domain computers
When I go to the advanced tab on my network connection properties I get
the following message:
"Windows cannot display the properties of this connection. The Windows
Management Instrumentation (WMI) information might be corrupted..."
I am not able to get any system information on any of my domain systems
except for my servers. This issue occurs when ever I add a system to
my domain.
I think this problem emerged when I repaired a corrupted Admin template
on my default domain GPO.
I believe somehow a GPO is causing this issue on my systems but am not
able to determine what needs to be corrected.
has anyone had a similar issue and found a resolution to this?
________________________________
This e-mail may contain identifiable health information that is subject
to protection under state and federal law. This information is intended
to be for the use of the individual named above. If you are not the
intended recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited and may be
punishable by law. If you have received this electronic transmission in
error, please notify us immediately by electronic mail (reply).
________________________________
This e-mail may contain identifiable health information that is subject
to protection under state and federal law. This information is intended
to be for the use of the individual named above. If you are not the
intended recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited and may be
punishable by law. If you have received this electronic transmission in
error, please notify us immediately by electronic mail (reply).
**********************************************************************
This e-mail may contain identifiable health information that is subject to
protection under state and federal law. This information is intended to be for
the use of the individual named above. If you are not the intended recipient,
be aware that any disclosure, copying, distribution or use of the contents of
this information is prohibited and may be punishable by law. If you have
received this electronic transmission in error, please notify us immediately by
electronic mail (reply).
Other related posts:
