We had to perform a fresh install of Windows Server 2003 Standard on our primary domain controller on our network due to suspected security breach. The OS is now installed on a different hard drive. There is another domain controller on our network also running integrated DNS and possessing a copy of the global catalog. The problem is all 5 FSMO roles were on the primary domain controller which is now offline. How can we bring this server back into the AD network? Same hardware, same ip address, same name. The secondary domain controller shows all operations masters as offline. Should I setup the DNS Server first, and then run dcpromo, or just run dcpromo? In particular, when I am configuring the services, should I set it up as an new server in an existing DNS domain/Active Directory, or should I "pretend" that I'm setting up the DNS domain/Active Directory domain for the first time? I'm not sure what the next step here is in order to bring back the FSMO roles on the original server, & as far as I know, I cannot seize the FSMO roles if the primary is offline. I don't want to risk rebooting the primary back to the original OS install and plugging it into the network. Thanks in advance.

You can follow this guide (http://support.microsoft.com/default.aspx/kb/255504) which lets you seize (not transfer) the FSMO-roles. In this case all the roles will be on your secondary DC until your first one is completely setup as a DC again. When it is you can transfer the roles back to that one if you prefer it that way (it really doesn't matter which one they're on, and you could even split them on different DC's, but that's a different story.)Best regards Joachim Nsslander IT-Expert, Knowledge Factory (http://www.knowledgefactory.se) MVP Cluster Member of Microsoft Extended Experts Team (MEET) Blog: http://www.nullsession.com