Deleted GPO Applying to Workstations

[Chris Smith]

Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2

In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it may still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy Modeling
Wizard shows the correct GPO settings though.

I can connect to both DC's with the gpmc and the correct GPO's are in place
and the deleted GPO's are completely gone.

I have run "netdiag /v /l" and I see no strange errors. I have checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of infrastructure
network problems.

Any ideas?

[samir shah]

That Policy must have been created in the parent domain itself and must have
been applied from there

Try checking the parent server.

Samir Shah

Post by Chris Smith
Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2
In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it may still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy Modeling
Wizard shows the correct GPO settings though.
I can connect to both DC's with the gpmc and the correct GPO's are in place
and the deleted GPO's are completely gone.
I have run "netdiag /v /l" and I see no strange errors. I have checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of
infrastructure
network problems.
Any ideas?
--
CSS

...

[Chris Smith]

The GPO was created in the specific child domain only and applied from there.
All parent GPO's are separate and specific.

It was created and deleted from the child domain only.
--
CSS

Post by samir shah
That Policy must have been created in the parent domain itself and must have
been applied from there
Try checking the parent server.
Samir Shah

Post by Chris Smith
Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2
In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it may still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy Modeling
Wizard shows the correct GPO settings though.
I can connect to both DC's with the gpmc and the correct GPO's are in place
and the deleted GPO's are completely gone.
I have run "netdiag /v /l" and I see no strange errors. I have checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of infrastructure
network problems.
Any ideas?
--
CSS

...

[Robert Kettel]

I guess, your Policy was a machine policy that modified the registry
(registry tatooing), not only temporarly by setting new values or new keys?
To remove them you would need a "reverse" policy that removes the keys again.
Is that a possible explanation?
--
Robert Kettel

Post by Chris Smith
The GPO was created in the specific child domain only and applied from there.
All parent GPO's are separate and specific.
It was created and deleted from the child domain only.
--
CSS

Post by samir shah
That Policy must have been created in the parent domain itself and must have
been applied from there
Try checking the parent server.
Samir Shah

Post by Chris Smith
Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2
In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it may still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy Modeling
Wizard shows the correct GPO settings though.
I can connect to both DC's with the gpmc and the correct GPO's are in place
and the deleted GPO's are completely gone.
I have run "netdiag /v /l" and I see no strange errors. I have checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of infrastructure
network problems.
Any ideas?
--
CSS

...

[w.sky]

I just wanted to say that our organization is also having the same problem
with a deleted GPO still applying, and we would be interested to know if /
when Chris finds a solution.

Post by Robert Kettel
I guess, your Policy was a machine policy that modified the registry
(registry tatooing), not only temporarly by setting new values or new keys?
To remove them you would need a "reverse" policy that removes the keys again.
Is that a possible explanation?
--
Robert Kettel

Post by Chris Smith
The GPO was created in the specific child domain only and applied from there.
All parent GPO's are separate and specific.
It was created and deleted from the child domain only.
--
CSS

Post by samir shah
That Policy must have been created in the parent domain itself and must have
been applied from there
Try checking the parent server.
Samir Shah

Post by Chris Smith
Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2
In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it may still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy Modeling
Wizard shows the correct GPO settings though.
I can connect to both DC's with the gpmc and the correct GPO's are in place
and the deleted GPO's are completely gone.
I have run "netdiag /v /l" and I see no strange errors. I have checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of infrastructure
network problems.
Any ideas?
--
CSS

...

[Darren Mar-Elia]

I have a freeware tool, called cleanregpol, that is designed to remove
policies and preferences from a given computer or user. Check out the
freeware section on this page for the download:
www.sdmsoftware.com/products.php

If you try it, let me know how you get on with it.

Thanks

Darren
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
http://www.gpoguy.com -- The Windows Group Policy Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related

Speed Group Policy Troubleshooting with the NEW GPHealth Reporter tool at
http://www.sdmsoftware.com/products.php

Post by w.sky
I just wanted to say that our organization is also having the same problem
with a deleted GPO still applying, and we would be interested to know if /
when Chris finds a solution.

Post by Robert Kettel
I guess, your Policy was a machine policy that modified the registry
(registry tatooing), not only temporarly by setting new values or new keys?
To remove them you would need a "reverse" policy that removes the keys again.
Is that a possible explanation?
--
Robert Kettel

Post by Chris Smith
The GPO was created in the specific child domain only and applied from there.
All parent GPO's are separate and specific.
It was created and deleted from the child domain only.
--
CSS

Post by samir shah
That Policy must have been created in the parent domain itself and must have
been applied from there
Try checking the parent server.
Samir Shah

Post by Chris Smith
Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2
In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it
may
still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy Modeling
Wizard shows the correct GPO settings though.
I can connect to both DC's with the gpmc and the correct GPO's are
in
place
and the deleted GPO's are completely gone.
I have run "netdiag /v /l" and I see no strange errors. I have checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of infrastructure
network problems.
Any ideas?
--
CSS

...

[Chris Smith]

Wonderful! I was curious if this was an option... to clean out GPO data in
the registry. I'll give it a try. Perhaps this will be exactly what we (w.sky
and myself) need.

Thanks.
--
CSS

Post by Darren Mar-Elia
I have a freeware tool, called cleanregpol, that is designed to remove
policies and preferences from a given computer or user. Check out the
www.sdmsoftware.com/products.php
If you try it, let me know how you get on with it.
Thanks
Darren
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related
Speed Group Policy Troubleshooting with the NEW GPHealth Reporter tool at
http://www.sdmsoftware.com/products.php

Post by w.sky
I just wanted to say that our organization is also having the same problem
with a deleted GPO still applying, and we would be interested to know if /
when Chris finds a solution.

Post by Robert Kettel
I guess, your Policy was a machine policy that modified the registry
(registry tatooing), not only temporarly by setting new values or new keys?
To remove them you would need a "reverse" policy that removes the keys again.
Is that a possible explanation?
--
Robert Kettel

Post by Chris Smith
The GPO was created in the specific child domain only and applied from there.
All parent GPO's are separate and specific.
It was created and deleted from the child domain only.
--
CSS

Post by samir shah
That Policy must have been created in the parent domain itself and must have
been applied from there
Try checking the parent server.
Samir Shah

Post by Chris Smith
Windows 2003 parent domain/forest (2003 mode)
Windows 2003 child domain (2003 mode)
Each child domain has two DC's
Workstations are Windows XP SP2
In the child domain in question, group policy is not applying accurately.
For instance, if I delete a GPO completely (not just the link) it
may
still
apply to workstations the next day... even if I "gpupdate /force" on the
workstations and reboot. The Group Policy Results Wizard is showing
me (in
gpmc.msc) that GPO's I deleted are still applying. The Group Policy
Modeling
Wizard shows the correct GPO settings though.
I can connect to both DC's with the gpmc and the correct GPO's are
in
place
and the deleted GPO's are completely gone.
I have run "netdiag /v /l" and I see no strange errors. I have
checked the
event logs on the DC's without applicable errors and I rebooted both
yesterday. The domain seems healthy. There are no symptoms of
infrastructure
network problems.
Any ideas?
--
CSS

...