Kamlesh-
I'm not sure I understand what you're saying about "Not
Configured". If I check "Automatically Detect configuration settings" in IE
Maintenance policy, then that box is checked for all users that process the
policy. If you uncheck that box, the box is unchecked for the user the next time
they process the policy. What behavior are you trying to
achieve?
Darren
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kamlesh Parmar
Sent: Wednesday, November 02, 2005 9:33 AM
To: [email protected]
Subject: [ActiveDir] GP version mismatch between DS & SYSVOL
Which once configured, can't be made "not - configured" as you can do with other settings.
This values are either disable or enable, there is no option like "not configured"
I have two or three such policies, and I want to get rid of these settings, without recreating the GPO.
so I thought I would go directly in SYSVOL folder of this policies and delete the appropriate settings and UP the version number in gpt.ini so that it replicates.
But, since I have not used standard group policy editor, the version in Active Directory remains old.
Now it gives error in monitoring tools saying version mismatch between DS & SYSVOL.
So,
1) Is there better way to handle these sticky settings? other than recreating GPO.
2) Can I change the version in DS using adsiedit.msc to reflect the same as SYSVOL? will it have any effect on GP application?
--
Kamlesh
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Fortune and Love befriend the bold"
~~~~~~~~~~~~~~~~~~~~~~~~~~~
