Migrating Server 2003 AD DC to New box with Server 2008 and need to keep all things the same

Here's my situation...

I have an old machine, we'll call "Server". It is a File Server, SQL Server, Active Directory Domain Controller, and DNS Server.

I purchased a new server a couple of years ago, named it "Server2" (same name as old box, but number 2 added), installed Windows Server 2003, and made it a second AD DC.

I now need to basically discontinue use of the old server, and make the new server named "Server". I've also decided to try and install Windows Server 2008 or 2012 on this new box.

I think the problem, or complication, is that it's a domain controller and I know it's not as simple as turning off "Server" and renaming "Server2" to "Server", but all of my shares, roaming profiles, and programs that use the SQL data all use the name "Server", so i believe it's a necessary evil.

As it stands, I am currently running a nightly robocopy of the files and permissions, so I'm thinking that just re-creating the shares from old to new should be simple...but are there any tools?

What's the best way to get the old box offline, get the new box online, and make it invisible to the end users? I'd rather spend all of a day setting up the server, migrating there, etc, as opposed to touching every machine or making some crazy group policies or scripts to change all the clients.
Who is Participating?
it_saigeConnect With a Mentor DeveloperCommented:
FSMigrate is a utility that Microsoft has for doing File Server Share and/or File migrations.  As for renaming the DC.  It can be done, it's just not usually the preferred solution.

Will SzymkowskiSenior Solution ArchitectCommented:
I would not be installing anything on a domain controller other than DNS/GC/DHCP. Installing SQL/FileShare etc is not a good practice especially because a domain controller has enhanced security on it.

You also have a complexity with SQL being on the box. I do not believe you can rename a SQL server without breaking databases (could be wrong not a SQL expert).

I would recommend having your DC without having any other roles install other then the ones i have listed above. Make sure that your other DC (secondary) is functioning properly and move the FSMO roles over to it before demoting the current one.

You will then need to point DNS to the new DC once you have demoted the old one.

jeffh2345Author Commented:
Thanks for both comments, and I realize it's not the best way to do it, but I just don't have 3 or 4 servers to do all the jobs. I'm having to make due with what I've got. It's worked on the old server for about 10 years, so now I have to migrate it all to the new one.
Will SzymkowskiSenior Solution ArchitectCommented:
That is understandable if it is not in the budget. However, if you ever encounter issues it is going to be that much harder to correct and in most cases it will not be supported.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.