<div>
Terminal Services is not recommended on a Domain Controller by Microsoft. &nbsp;TS Clients must be given log on locally rights to the box. &nbsp;Also, a buggy application could bring the DC to it's knees. &nbsp;I have just been facing this exact issue at one of my remote sites. &nbsp;<br />
<br />

</div>


Terminal Services is not recommended on a Domain Controller by Microsoft.  TS Clients must be given log on locally rights to the box.  Also, a buggy application could bring the DC to it's knees.  I have just been facing this exact issue at one of my remote sites.  



<div>
<div class="content wysiwyg-content">
I would like to know what should be taken into consideration when implementing a Terminal Server on a Domain Controller. &nbsp;I would like to know if this is not recommended and if there are any security issues I should be aware of. &nbsp;If anyone has had any experience with this, please shoot your info my way! &nbsp;Thanks EE!<br />
<br />
Larz
</div>
</div>


I would like to know what should be taken into consideration when implementing a Terminal Server on a Domain Controller.  I would like to know if this is not recommended and if there are any security issues I should be aware of.  If anyone has had any experience with this, please shoot your info my way!  Thanks EE!

Larz

Terminal Server on a Domain Controller???

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).