<div>
Thanks. This is what is needed. The new domain is in a different forrest.
</div>


Thanks. This is what is needed. The new domain is in a different forrest.

<div>
<div class="content wysiwyg-content">
We've moved some of our servers to a new AD tree but have a trust relationship with our old one. Most servers, and our SCOM server, exist on the old AD. &nbsp;I'm trying to install the agent on one of our servers which moved, and while it says it is installing, it never completes. (I'm using the console to discover the server in question, and have tried various IDs.)<br />
<br />
Any thoughts/guidence from someone who has had a similar situation? &nbsp;
</div>
</div>


We've moved some of our servers to a new AD tree but have a trust relationship with our old one. Most servers, and our SCOM server, exist on the old AD.  I'm trying to install the agent on one of our servers which moved, and while it says it is installing, it never completes. (I'm using the console to discover the server in question, and have tried various IDs.)

Any thoughts/guidence from someone who has had a similar situation?  

Installing SCOM agent to server in trusted 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

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.