<div>
<div class="content wysiwyg-content">
Hey guys,<br />
<br />
We have a terminal server (2003) that someone built years ago and at the time it was on a different domain. Currently users access the server using local accounts, but it is messing up their access to AD based file permissions on the file servers in the correct domain. <br />
<br />
I'd like to join it the proper domain, but i'm worried if this would break anything?
</div>
</div>


Hey guys,

We have a terminal server (2003) that someone built years ago and at the time it was on a different domain. Currently users access the server using local accounts, but it is messing up their access to AD based file permissions on the file servers in the correct domain. 

I'd like to join it the proper domain, but i'm worried if this would break anything?

Terminal Server 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 Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.