Active Directory

I am setting up a Windows 2003 Terminal Server.  I currently have a Windows 2000,  Active Directory and  roaming profile, environment with very little desktop restrictions.

My goal is to setup the terminal server for a legacy application, and allow users with their Active Directory credentials to login into the terminal server and access the application with an extremely restricted desktop environment.

I do not want the roaming profile to load on the terminal server, and would like to utilize policies to restrict the desktop, and not interfere with the users work pc when logging into the network.

Is this possible, and would you provide any documentation, links, or practical experience?  Thank you.
rpruittAsked:
Who is Participating?
 
Rob StoneConnect With a Mentor Commented:
Check this link for your second question:
http://www.thin-world.com/Q260370.htm
0
 
nader alkahtaniNetwork EngineerCommented:
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
Rob StoneCommented:
On TS you can create another profile (mandatory) and point to that.  In AD there is a TS tab with the profile location on that - that should do the trick.
0
 
Rob StoneCommented:
Here is a link to 2000 Server documentation.

TS is under Client Services > Terminal Services
http://www.microsoft.com/windows2000/en/server/help/
0
 
rpruittAuthor Commented:
Thank you,  Setting the TS tab with another profile worked and kept the two profiles separate.  Can I create a local policy that will NOT be applied to administrators, but apply to everyone else that logs into the terminal server, or do I have to use AD policies to manipulate the desktop?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.