> Does the GPT.ini file get generated on the workstation based on what
> policies are currently on the Workstation plus the cumulation of the
> zenworks policy.
> OR does it simply just download and copy the GPT.ini file from the
> server and over the policies on the workstation.
It works like this:
If there are Group Policies on the workstation prior to the install of the
ZfDAgent, the install will move those to
\system32\GroupPolicy.WMOriginal2
and then they will be cumulative applied every time the policy is applied.
So, if there for example is a corrupt gpt.ini on the WS prior to the
install, this will affect the "final" gpt.ini.
It's best not to have any Local Policies configured on a WS prior to the
ZfDAgent install if you want full control from ZfD.
Furthermore, if you have both User- and WS Policy Packages with GPOs
configured, the final gpt.ini is also created from the cumulative content of
those, plus that you could have at least three levels of GPO Policy Packages
of both the WS- and User kind (container, group, object), which would make a
total sum of seven possible gpt.ini-files that the final gpt.ini could be
created from.
I always edit the gpt.ini-files so that they only contain the extensions
that fits with the GPO they belong to, although I think this should not
really be necessary.
Useful links:
http://technet.microsoft.com/en-us/l.../cc779745.aspx
http://support.microsoft.com/kb/216357
http://support.microsoft.com/kb/271135
Regards
Rolf Lidvall
Swedish Radio (Ltd)
Re: Corrupt gpt.ini
Threaded Mode
