<div>
<div class="content wysiwyg-content">
Greetings,<br />
<br />
We are running a Windows 2003 SBS domain with about 50 users. &nbsp;We now have a requirement to add a new AD user that will not have access to any of the normal Domain based file shares as all other authenticated users. &nbsp;This new AD user will log onto our Windows 2008 R2 Terminal Server in order to launch a specific application.<br />
<br />
How can we restrict this user so the account is restricted from accessing anything except for the application they need to run on the Terminal Server?<br />
<br />
Thanks in advance -<br />
<br />
Dan
</div>
</div>


Greetings,

We are running a Windows 2003 SBS domain with about 50 users.  We now have a requirement to add a new AD user that will not have access to any of the normal Domain based file shares as all other authenticated users.  This new AD user will log onto our Windows 2008 R2 Terminal Server in order to launch a specific application.

How can we restrict this user so the account is restricted from accessing anything except for the application they need to run on the Terminal Server?

Thanks in advance -

Dan

Using Group Policy to restrict Authenticated User Access on Domain

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.