Restrictions in Terminal Services

**Eclipse2003** · 11-14-2005, 03:07 PM

I am going to be installing and using Terminal Services on a Server running Windows 2003 Server and clients will be using XP Pro. What is the best and easiest way to not allow the users to be able to access anything besides the programs they will be using such as Office and their software they use for their practice. I do not want them to be able to access Shut down or any other things that could cause problems or changes on the server. Thanks for the help.

**w00t** · 11-20-2005, 03:49 AM

Just make a ghetto user account (example: user, or :jobtitle:) and modify the properties so they are restricted in that account.

Why would you not want them to be able to access shutdown for that node?

**Eclipse2003** · 11-20-2005, 07:15 AM

If I understand TS right, wouldn't a shutdown, shutdown the server? Because aren't they technically using remote desktop to log into the server?

**Squashman** · 11-20-2005, 03:57 PM

Set a local policy for who can shutdown the system.

**Eclipse2003** · 11-28-2005, 09:34 AM

I am kind of new to this, how do I exactly do that on a Server 2003 machine?

**Squashman** · 11-28-2005, 02:55 PM

If you are a Windows Server admin, I suggest you read thru every policy setting you can make locally and thru the domain.

**Eclipse2003** · 12-06-2005, 10:07 AM

Thanks alot for the help Squashman. I looked through most of the different restrictions I can setup and have played with them some. I appreciate the help.

11-14-2005, 03:07 PM	#1 (permalink)
Eclipse2003 TSF Enthusiast Join Date: Apr 2005 Location: Ohio Posts: 1,156 OS: XP	Restrictions in Terminal Services I am going to be installing and using Terminal Services on a Server running Windows 2003 Server and clients will be using XP Pro. What is the best and easiest way to not allow the users to be able to access anything besides the programs they will be using such as Office and their software they use for their practice. I do not want them to be able to access Shut down or any other things that could cause problems or changes on the server. Thanks for the help.

11-20-2005, 03:49 AM	#2 (permalink)
w00t Chex mix and Cream soda! Join Date: Jun 2004 Location: Oahu Posts: 596 OS: Slackware 11.1, Fedora Core 3, K12LTSP, Suse ES 9, Windows 2000sp4, Mac OSX, Knoppix, Mephis	Just make a ghetto user account (example: user, or :jobtitle:) and modify the properties so they are restricted in that account. Why would you not want them to be able to access shutdown for that node? __________________ Elvis didn't die he just went open source w00tb0t, because you can't make tea with potatoes

11-20-2005, 07:15 AM	#3 (permalink)
Eclipse2003 TSF Enthusiast Join Date: Apr 2005 Location: Ohio Posts: 1,156 OS: XP	If I understand TS right, wouldn't a shutdown, shutdown the server? Because aren't they technically using remote desktop to log into the server?

11-20-2005, 03:57 PM	#4 (permalink)
Squashman Tech, Networking Forums Join Date: Apr 2005 Location: 1265 Lombardi Ave. Posts: 1,142 OS: All of the above	Set a local policy for who can shutdown the system.

11-28-2005, 09:34 AM	#5 (permalink)
Eclipse2003 TSF Enthusiast Join Date: Apr 2005 Location: Ohio Posts: 1,156 OS: XP	I am kind of new to this, how do I exactly do that on a Server 2003 machine?

12-06-2005, 10:07 AM	#7 (permalink)
Eclipse2003 TSF Enthusiast Join Date: Apr 2005 Location: Ohio Posts: 1,156 OS: XP	Thanks alot for the help Squashman. I looked through most of the different restrictions I can setup and have played with them some. I appreciate the help.