Deleting a SysvolPolicy dangerous?

[Sandy]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Hey everyone, good day,

I'm posting my problem in a different way, as it seems that no one has a clue about how to 'fix' the problem, or has
seen this before. Maybe this question has a simpler answer...

Background: Native 2000 enterprise, SP4 on all servers, all XP SP1 clients. Two 2003 Member Servers. Group Policy
is functioning normally.

Question: if, when I access Group Policy from any of the DCs, I get a warning about a particular numbered policy
(XXXXX-XXXXX-XXXXX-XXXX)\Adm\inetres.adm on line 158, error 51, unexpected keyword, etc.
and, although the number of the policy may be different on each DC, the path and line and error and message are the same, is it SAFE to simply delete the policy number from within the Winnt\Sysvol\Policies\(policy number)?

I am not getting any such error if I administer GP from my XP, SP1 client machine with the adminpak.msi.

I'm looking forward to upgrading to 2003 across the board this summer, and I'd like to do it with no nagging
warnings to follow me.

Anyone a Sysvol\Policies\ or .adm guru who knows the implications of deleting the policy from the file system as
a last resort?

Thanks for any help,
Sandy

 

[boomstick]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Will it let you rename it? Maybe you could just put a .old at the end and
see if it makes your domain caugh up a hairball. : )

That way, you could always rename it back to what it was.

Just a thought...

Jared


"Sandy" <shacker@nhvweb.net> wrote in message
news:AACB46B8-4B59-425A-9EE3-8F06B232000F@microsoft.com...
> Hey everyone, good day,
>
> I'm posting my problem in a different way, as it seems that no one has a
clue about how to 'fix' the problem, or has
> seen this before. Maybe this question has a simpler answer...
>
> Background: Native 2000 enterprise, SP4 on all servers, all XP SP1
clients. Two 2003 Member Servers. Group Policy
> is functioning normally.
>
> Question: if, when I access Group Policy from any of the DCs, I get a
warning about a particular numbered policy
> (XXXXX-XXXXX-XXXXX-XXXX)\Adm\inetres.adm on line 158, error 51, unexpected
keyword, etc.
> and, although the number of the policy may be different on each DC, the
path and line and error and message are the same, is it SAFE to simply
delete the policy number from within the Winnt\Sysvol\Policies\(policy
number)?
>
> I am not getting any such error if I administer GP from my XP, SP1 client
machine with the adminpak.msi.
>
> I'm looking forward to upgrading to 2003 across the board this summer, and
I'd like to do it with no nagging
> warnings to follow me.
>
> Anyone a Sysvol\Policies\ or .adm guru who knows the implications of
deleting the policy from the file system as
> a last resort?
>
> Thanks for any help,
> Sandy
>
>

 

[Sandy]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Hey Jared,
thanks, that's a fairly simple thing I could do. Just for any one else's info, I found on another forum totally
unrelated to Microsoft, someone with a very similar problem.
Windows 2000 does not seem to understand the keywords 'Supported' or 'Explain' in .adm templates which
are introduces into .adm files when
you copy the templates from XP (which is actually a valid operation and documented in Micosoft 'how to' papers).

Someone suggested edited out the words 2000 doesn't understand.
I'll try it, but I think upgraded to 2003 is the only way to get rid of this seemingly harmless yet extremely
annoying warning.

I'm really disappointed that there is a complete lack of recognition of this problem on the Microsoft sights.
It's obviously happening to many people who are interoperating XP with 2000 and updated the templates to handle
the GP differences.

Anyone at Microsoft reading this thread or what? There's a problem with 2000 accepting the copied templates from XP!

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Hello Sandy,

I believe I may know the cause of this. In the Windows XP Service Pack 2
Release Candidate 1 version of inetres.adm an error was introduced (wheerby
the Supported tag was not surrounded by the appropriate #if / #endif tags,
to ensure that it was not interpreted by Windows 2000 workstations). This
issue did not exist in the Beta version of XP SP2 and has been resolved post
RC1 (so it you won't see it in subsequent releases).

My guess is that someone in your environment opened a GPO from a machine
running XP SP2 RC1, which resulted in the errant inetres.adm being send to
Sysvol (due to the timestampt comparison), which will subsequently be used
by all other users attempting to edit or view that GPO. Please let me know
if this is a potential explanation for your environment.

Thanks.
--

Mark Williams
Program Manager, Group Policy
Microsoft. http://www.microsoft.com/technet/grouppolicy
This posting is provided "AS IS" with no warranties, and confers no rights.


"Sandy" <shacker@nhvweb.net> wrote in message
news:248C2E89-5E24-4891-AD79-235712FAAF57@microsoft.com...
> Hey Jared,
> thanks, that's a fairly simple thing I could do. Just for any one else's
> info, I found on another forum totally
> unrelated to Microsoft, someone with a very similar problem.
> Windows 2000 does not seem to understand the keywords 'Supported' or
> 'Explain' in .adm templates which
> are introduces into .adm files when
> you copy the templates from XP (which is actually a valid operation and
> documented in Micosoft 'how to' papers).
>
> Someone suggested edited out the words 2000 doesn't understand.
> I'll try it, but I think upgraded to 2003 is the only way to get rid of
> this seemingly harmless yet extremely
> annoying warning.
>
> I'm really disappointed that there is a complete lack of recognition of
> this problem on the Microsoft sights.
> It's obviously happening to many people who are interoperating XP with
> 2000 and updated the templates to handle
> the GP differences.
>
> Anyone at Microsoft reading this thread or what? There's a problem with
> 2000 accepting the copied templates from XP!

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

I have the same errors that I get twice any time I try to access Admin
templates under GPO. I have win2k DCs with mixed clients 2kPro & XP. I
think Mark William description was right on the money. Yes I edited my
GPO from XP machine with SP2. Does any one have the solution to this
problem?

Any help is appreciate it.

Sam





"Sandy" <shacker@nhvweb.net> wrote in message news:<AACB46B8-4B59-425A-9EE3-8F06B232000F@microsoft.com>...
> Hey everyone, good day,
>
> I'm posting my problem in a different way, as it seems that no one has a clue about how to 'fix' the problem, or has
> seen this before. Maybe this question has a simpler answer...
>
> Background: Native 2000 enterprise, SP4 on all servers, all XP SP1 clients. Two 2003 Member Servers. Group Policy
> is functioning normally.
>
> Question: if, when I access Group Policy from any of the DCs, I get a warning about a particular numbered policy
> (XXXXX-XXXXX-XXXXX-XXXX)\Adm\inetres.adm on line 158, error 51, unexpected keyword, etc.
> and, although the number of the policy may be different on each DC, the path and line and error and message are the same, is it SAFE to simply delete the policy number from within the Winnt\Sysvol\Policies\(policy number)?
>
> I am not getting any such error if I administer GP from my XP, SP1 client machine with the adminpak.msi.
>
> I'm looking forward to upgrading to 2003 across the board this summer, and I'd like to do it with no nagging
> warnings to follow me.
>
> Anyone a Sysvol\Policies\ or .adm guru who knows the implications of deleting the policy from the file system as
> a last resort?
>
> Thanks for any help,
> Sandy

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

I also have the error, and I did load XP SP2 RC1 and Group Policy
management tool. Any fixes?

koukousam@hotmail.com (kokousam) wrote in message news:<f0265ad6.0404271151.34a980cf@posting.google.com>...
> I have the same errors that I get twice any time I try to access Admin
> templates under GPO. I have win2k DCs with mixed clients 2kPro & XP. I
> think Mark William description was right on the money. Yes I edited my
> GPO from XP machine with SP2. Does any one have the solution to this
> problem?
>
> Any help is appreciate it.
>
> Sam
>
>
>
>