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 preferences only, i.e.
using .adm files to set registry values, and "Registry policy processing" in
the GPO is "Not configured". We suppose that this policy only affect 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 2 out of 3 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", but the registry entries are not
changed by the GPO even it is the first-time logon. The remaining 1 machine
however works as in the WinXP case.
We do not suspect Win2K cannot perform what WinXP can, but we cannot locate
the problem. Please help.
And, Merry Christmas!
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 preferences only, i.e.
using .adm files to set registry values, and "Registry policy processing" in
the GPO is "Not configured". We suppose that this policy only affect 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 2 out of 3 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", but the registry entries are not
changed by the GPO even it is the first-time logon. The remaining 1 machine
however works as in the WinXP case.
We do not suspect Win2K cannot perform what WinXP can, but we cannot locate
the problem. Please help.
And, Merry Christmas!