Group Policy script extension caused error

Very Good Point!

In fact, I would recommend using a VM of a device that has never had any
policies applied.

#1 - Policies will be applied as you edit them and then undone when you
finish editing the policy.
By using a VM instead of your own machine, you eliminate the possibility
that some policy does not get undone for any reason.

#2 - The GPO will be based on the GPO you create and edit on the PC.
The Windows Group Policy editor will pull in the GPT.ini that currently
exists on your PC when creating the GPO which may include unneeded GPO
Extensions.
By using a "Clean" PC, this will help avoid that issue.



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


"kfreise" <kfreise@no-mx.forums.novell.com> wrote in message
news:kfreise.40o3cq@no-mx.forums.novell.com...
>
> My guess is that creating the policies on a device that was upgraded
> from Zen7 to Zen10 had something to do with this.
>
> On a fresh Zen10 device I created a policy and only 1 pair of GUIDs
> existed in the GPT.ini file.
>
>
> --
> kfreise
> ------------------------------------------------------------------------
> kfreise's Profile: http://forums.novell.com/members/kfreise.html
> View this thread: Group Policy script extension caused error
>