Networks

Ask something
Question Locked

Replacing a Windows 2003 server

0 helpful
8 replies

by charliedennis

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
In the next couple of months I will be replacing my 2003 server with a new box. I want everything that is on the old box to be on the new one...active directory, files, programs, etc. Does anyone know of some helpful material on the web that deals with this?

8 replies

by drummerb0y

But in my opinion there are two main ways to do this. The 1st would be to image (Ghost, Acronis, etc.) your old server, apply the image to the new Server and attempt to remedy the driver issues that are bound to happen.
Pros: If it works, you get an exact copy of your current server (minus drivers for the new hardware).
Cons: You could quite possibly have too many driver conflicts, and the new server would never boot properly. Software that might depend on hardware IDs (network apps that register based on network card MAC address for example) would stop working.

The 2nd option would be an 'in-place' migration. Install your new server's software manually until it matches. For files, just copy 'em over. And for Active Directory, you join the new server to the domain, make it another domain controller in the domain. Ensure that all AD information is replicating smoothly, then demote the old server.
Pros: Users can access the existing server for the majority of your transition time. All driver conflicts will be resolved on the new server before you move data.
Cons: The new server will not 100% match the old one. It will need a different name, IP address (at least until the old one leaves the domain), apps won't be setup exactly the same way (unless you have documentation).

If you try the 1st option, make sure to leave the old server powered off so it doesn't conflict with it's mirror self on the network.

Don't take my advice as law, by any means. There are too many 'what-ifs' here to make something go wrong. Obviously, make sure you have good, verified backups of everything before you start, and good luck!

by bart777

Getting the apps configured on the new server would be far easier than dealing with hardware driver issues that may not pop up for weeks when the users are in full production.

One thing to make sure of is that when you promote the second server you move teh 5 FSMO roles. If you forget to do this and also make the server a Global catalog server you will have major issues down the road.

The phased migration to the new server is the best route to take.

For the shared files use a program like Beyond Compare to get them moved. And the drive mapping is easy enough to change in your logon script.

Good luck

by charliedennis

Not trying to sound like I don't appreciate your suggestions (because I do!!), but many of the things you stated were what I had in mind...especially putting the new server on the network under a different ip address and name. Then, application by application and file by file, start installing and copying things over. Then, after I see that everything is working ok, removing the old server (physically) from the network and then change the name and ip address on the new server to the ip address and name that was on the old server. One question I did have, and I guess I'll be showing my ignorance, but I've seen on more than one instance where, if you promote a server to a domain controller on a domain that already has a domain controller, all items in the active directory will be replicated (copied?) to the new domain contoller. Is my presumption on this correct? Also, if this 'is' correct, what is the purpose of Microsoft's Active Directory Migration Tool? Again, I'd like to express just how grateful I really am for your suggestions!

by bart777

When you promote the new server it will, in fact, have all of the AD data replicated to it. Just remember to make this new server a Global Catalog server and move the FSMO roles before you demote and remove the old server.

ADMT is used when you want to migrate from one domain to another. It's a great tool if you want to do things like change your domian name but not needed for a simple DCPROMO.

Good Luck, and don't eat too much Turkey. :)

by charliedennis

Thanks...again for the help! I was wondering, though, were you able to find your help in one place on this subject or from researching various places?

Charlie

by bart777

Most of what I was telling you comes from doing that process many times.

Also from cleaning up after someone else forgot to do thingss like transfer the FSMO roles.

I suppose that over the years it would be a broad search but I've done this process more times than I can remember.

Best of luck.

by drummerb0y

We learn most of this stuff through trial and error. However, my company did actually send me through the MCSE courses (which were taught onsite luckily), so I got some hands-on lab training into these scenarios. But it REALLY helps to have your own lab, if your company or government contract can afford it. Having a lab that mirrors what the operational sites have is INVALUABLE to hashing these problems out ahead of time.

This discussion is closed to new replies.