<div>
Well, since the new server is already a Domain Controller(clean install), and DNS is AD integrated, and there are no shares or printers to move, that doesn't look too bad! &nbsp;I'll transfer the FSMO roles and make the new DC a global catalog. &nbsp;Thanks.
</div>


Well, since the new server is already a Domain Controller(clean install), and DNS is AD integrated, and there are no shares or printers to move, that doesn't look too bad!  I'll transfer the FSMO roles and make the new DC a global catalog.  Thanks.

<div>
<div class="content wysiwyg-content">
I'm planning on retiring our old DC which is currently running Windows Server 2003 on out-dated proprietary hardware. &nbsp;It is our main DC that was originally upgraded from NT. &nbsp;I have another DC on modern hardware running Windows Server 2003 as well.<br />
<br />
Before I retire the DC, I seem to remember that I should do the following:<br />
<br />
-Move Global Catalog<br />
-Transfer FSMO Roles<br />
<br />
Is this correct? &nbsp;Anything else? &nbsp;Any tips on performing the above?<br />
<br />
Thanks!
</div>
</div>


I'm planning on retiring our old DC which is currently running Windows Server 2003 on out-dated proprietary hardware.  It is our main DC that was originally upgraded from NT.  I have another DC on modern hardware running Windows Server 2003 as well.

Before I retire the DC, I seem to remember that I should do the following:

-Move Global Catalog
-Transfer FSMO Roles

Is this correct?  Anything else?  Any tips on performing the above?

Thanks!

Retiring old DC - need to move master catalog?

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