J
Jason Hammer
We are in the process of moving our student lab computers from Windows
2000 Professional to Windows XP Professional. In the past, we have
used group policies running on a Windows 2000 server to restrict
access to Run, My Network Places, etc.
As we create new policies for an OU in our Windows 2003 domain running
with Windows 2003 native functionality, we find that the policies are
applied properly to any users who are freshly created within the OU,
but do no apply at all to pre-existing users who are moved into the OU
or to newly created users in the default Users container.
When the functional level of the Windows 2003 domain was raised from
mixed mode to Windows 2003 native, we did not move existing users into
an OU as recommended by the appropriate MS white paper on upgrading
the domain.
Does anyone have any suggestions on how to correct this problem? With
hundreds of returning students and the need to lock down our
configurations, this is a major obstacle we need to overcome.
Thanks in advance for any thoughts.
2000 Professional to Windows XP Professional. In the past, we have
used group policies running on a Windows 2000 server to restrict
access to Run, My Network Places, etc.
As we create new policies for an OU in our Windows 2003 domain running
with Windows 2003 native functionality, we find that the policies are
applied properly to any users who are freshly created within the OU,
but do no apply at all to pre-existing users who are moved into the OU
or to newly created users in the default Users container.
When the functional level of the Windows 2003 domain was raised from
mixed mode to Windows 2003 native, we did not move existing users into
an OU as recommended by the appropriate MS white paper on upgrading
the domain.
Does anyone have any suggestions on how to correct this problem? With
hundreds of returning students and the need to lock down our
configurations, this is a major obstacle we need to overcome.
Thanks in advance for any thoughts.