Hello all,
We have a W2K advanced member server as part of an NT4 domain, the W2K server is running terminal services in application mode. All users have mandatory profiles, policies are applied according to group membership, each user receives a locked down desktop. There are at least 3 types of user that will run different types of applications on the W2K terminal server. There are no plans to move to W2K domain controller.
Question is: What is the best practice for applying a locked down W2K terminal services desktop when accessing the terminal server through the terminal services client running on NT workstation within an NT domain. Do I have to create local profiles on the W2K server?? How would a policy be applied to the server whilst still allowing admin access??
Any help appreciated.
We have a W2K advanced member server as part of an NT4 domain, the W2K server is running terminal services in application mode. All users have mandatory profiles, policies are applied according to group membership, each user receives a locked down desktop. There are at least 3 types of user that will run different types of applications on the W2K terminal server. There are no plans to move to W2K domain controller.
Question is: What is the best practice for applying a locked down W2K terminal services desktop when accessing the terminal server through the terminal services client running on NT workstation within an NT domain. Do I have to create local profiles on the W2K server?? How would a policy be applied to the server whilst still allowing admin access??
Any help appreciated.
