Move AD & Exchange to new Server

[dreddnet]

I currently have 1 Windows 2000 server that runs AD, Exchange, Antivirus, and acts as the fileserver. I want to move the AD, and Exchange off to a new more robust server and keep the third-party apps and fileserver on the current server after a fresh install of it. How can I move my current AD and Exchange over to the new server, the server name will be different, but of course same domain name.

Hopefully I've explained in plain details what I am trying to do. There are only 10 users on this server, but I wanted to break the roles up onto two separate servers, but definately do not want to lose anything in the process.

Thanks for any help provided!

 

[TravisM]

If it's 10 users, I think the easiest thing to do would be to just take the box, set it off to the side and just rebuild everything from scratch. Put everyone's mail into a PST file, then copy it back up when the machine is back in place, or not.

You can always add the machine to the Domain, promote it to a domain controler, move all the GC and FMSO roles over to it and then tear the old machine down, but honestly with ten people you're going to have less headaches just bringing AD and exchange up from scratch and just one day dumping the old machine and adding all the current workstations to the new domain, copy their profiles over, etc.

Also, I wouldn't put exchange on a domain contoller unless ou absolutely have no way around it. You may want to consider having the DC host the file and print services and the other apps, and let exchange run all by itself over on the other box. Just something to think about.

 

[dreddnet]

Yea I thought about just totally rebuilding from scratch, but I really would like to learn how to do it the proper way too. So if possible I want to transfer the domain onto the new server and then take the old one down and rebuild the software aspect of it.

Why should exchange be on a separate PC? Should I run most of the apps from a member server and just have AD and file/print on the new main server?

 

[buddafish]

dreddnet,

1st, exchange consumes lots of resources and requires special anti-virus software. exchange is a complex product that deserves it's own server. domain controllers are ALWAYS busy doing things things that are not apparent to the user. They require alot of the server. Also, DC's are easier to secure if they are on thier own box...


anyway, build your new server, join it to the domain, give it a static IP address, then run DCPROMO. make it an additional domain controller for your current domain. reboot and it is now DC.

next, you will need to transfer all 5 FSMO roles to this server. this can be done from Active Directory Users and Computers --> right click and choose operation masters (3 of them), Active Directory Domains and Trusts (same right click deal) (1 role here) and finally if you have registered the Schema DLL (schmmgmt.dll)run the MMC and choose to add the Active Directory Schema. right click the schema and the same deal. in all these events you will choose your new server as the target.

make the new server a global catalog. Active Directory Sites and Services, expand your site, double click your server, right click NTDS settings, choose properties, check the check box for global catalog.

anyway, all this can happen if you just demote the first server after promoting the second, but that is not the "clean way". you may also need to get familar with NTDSUTIL.exe.

once done with all the above, run dcpromo on the old server and then just remove the object from AD.

best of luck

scottie

 

[buddafish]

forgot to add that you should check DNS that it was build correctly on the new server. if you are running Active Directory Integrated, then most often all is good.

WINS may also be required on your network.
DHCP database can be moved if it is on the old box.


scottie

 

[dreddnet]

Thank you for all the valuable information. I'll be sure to separate my Exchange Server from the domain controller.

But the current DC, I would like to totally wipe and reload it once I get the new server up. What would be the best method for me to protect my Exchange data until I get the server back and reinstalled?

 

[buddafish]

this would probably fall under the disaster recovery of an exchange server, if you are not able to bring yet another exchange server online to make a graceful transfer of the mailboxes, ect. by all means, you will need a full backup of the exchange information stores, ect.

post this question in the exchange 2000 forum.

scottie