G
Guest
We used a W2K3 server for a domain controller and are planning to join all
the Win2K professional workstations to the domain. Before this, some WinXP
machines are already joined to this domain.
One of the GPOs for the WinXP machines is concerning IE preferences only,
i.e. using .adm files to set registry values of IE, such as zone levels, IE
title string etc., and "Registry policy processing" in the GPO is "Not
configured". We suppose that this policy only affects the client settings
once (only when the user profile is newly created). This works on WinXP.
We then copy the policy for Win2K. We find that 3 out of 4 testing machines
do not have the expected result. The failure is that, the GPO has applied as
we can see from using the tool "GPResult", and also "ntuser.pol" in
%allusersprofile% and %userprofile%, but the most (not all, but almost all)
registry entries are not changed by the GPO even it is the first-time logon.
The remaining 1 machine however seems work as in the WinXP case.
We think that it is the problem solely for IE6 with Win2K, as the problem
vanishes if IE5.5 SP2 is used. Please help.
the Win2K professional workstations to the domain. Before this, some WinXP
machines are already joined to this domain.
One of the GPOs for the WinXP machines is concerning IE preferences only,
i.e. using .adm files to set registry values of IE, such as zone levels, IE
title string etc., and "Registry policy processing" in the GPO is "Not
configured". We suppose that this policy only affects the client settings
once (only when the user profile is newly created). This works on WinXP.
We then copy the policy for Win2K. We find that 3 out of 4 testing machines
do not have the expected result. The failure is that, the GPO has applied as
we can see from using the tool "GPResult", and also "ntuser.pol" in
%allusersprofile% and %userprofile%, but the most (not all, but almost all)
registry entries are not changed by the GPO even it is the first-time logon.
The remaining 1 machine however seems work as in the WinXP case.
We think that it is the problem solely for IE6 with Win2K, as the problem
vanishes if IE5.5 SP2 is used. Please help.