I have two Windows 2000 servers (both are domain controllers), one is a File/Print server, the second is an Exchange 200 server. I am looking at purchasing brand new servers running Windows 2003 server to replace the two 2000 servers. My question is, can I replace the servers by giving the new servers the same names as the old servers (i.e. name.domain.com)? WHat would be the best way to introduce the new servers to replace the old ones?

If it were me, I'd simply port the existing 2000 server's onto the new machines. You've already paid for those and this would save you $ over buying 2003 server. If your system's are working fine....why mess with them!? (ie: If it ain't broke, don't fix it!) You can do what you want to....but I'm not going to tell you how. I, and others, are here to help people, not train them. Most, if not all, the information you seek is freely available at microsoft's web site if you just go search it and read it.

To answer your question; yes they can have the same names, provided they are on two seperate networks that cannot talk to each other. The best way to introduce them is to completely build them out mirroring your existing 2000 structure. Then on go live day turn off the 2000 servers and connect the 2003 servers to your production network. Keep in mind that you will have to re-introduce all of the user accounts, machine accounts, Exchange accounts...yada, yada. Curt has some good points he mentioned. The only drawback is you need to stay up with the technology curve or you may find yourself unemployed one day and unable to find another job because you lack the certs or skills that some HR person put together. Most of the HR people don't even understand IT. <This is where I am now>

NOTE: Exchange 2000 will not run on Windows 2003! See http://support.microsoft.com/Default.aspx?kbid=321648 The best way would be to add the new servers to the current domain. Install and configure programs, set up your file shares, permissions, and all that, then make them DCs, GCs, and then transfer over the FSMO roles to one of them. Demote the 2000 servers to non-DC status then remove one from the domain, keeping the Exchange server running on a the now member server 2000 machine. This would be the least painful for the clients as well - they shouldn't feel a thing <G>. Peter (Alert me if you want a reply)

That would be the best way to do it alright...but still a lot more work than just sticking with 2000 server and porting your existing servers onto the new machines....cheaper too....you won't have to buy 2003 server.