Migrating DNS and other roles

[tvanduzee]

Hello

Im still pretty new at all this, but here is my question.

I am getting 2 new Gen 8 servers in our organization; to replace 2 gen 5 proliants.

Right now, One server (server 2008 r2) acts as my DC and a file server and the other is an app server (RDP TS).

One of my new servers, I would like to setup as just the file server. Right now, this server also handles replication via VPN to another server in another city.

I would like to wipe/reload my existing DC which handles all Domain roles (DNS, Accounts etc) with no exchange or sql. So I will want to migrate the dns etc to my new server until the old server is reloaded. How is this done? I will likely keep the same IP for the DC to prevent having to change the DNS server entries on all other servers and firewall appliances. But my file server IP will of course change. Also, the name of the DC will likely change.

Open to all suggestions.. as this is a learning opportunity for my present position as "THE" IT guy here.

Thanks you so much
Terry

 

[xSauronx]

what you do is add a new dc to the domain, it will sync DNS settings, AD accounts, sites, users, etc.

then you get over your want and change DNS on the other servers, devices (and your DHCP scopes) to use the new server. you *can* change the ip of the new one after you decom and power down the old one, but unless you have a shitload of devices to change it on im not sure id want to bother. Since you dont have experience at this i definitely wouldnt suggest you actually change the ip of the new DC once the old one is down. (there is some maintenance to do after you change the IP)

then you make the new server the FSMO role holder

then you properly decom the original DC to take it out of the domain, then you can format and do what you want with it.

i would suggest getting a consultant involved if this is your first migration. adding/removing a DC is not typically a big deal or drawn out process, but if you dont have experience and knowledge about this already you are going to be in a bad place if something goes wrong. Surely there is a managed services vendor in your area who could get you a quote and help this process along.

 

[tvanduzee]

Thank you for the quick reply.
Yes, I do have someone I could call in. Because this is and will be my responsibility, it is important that I learn each aspect of it and would like to go through each part of the process so that I will not have to rely on a consultant for maintaining the different roles.

The reason for my post is simply to learn "what" has to be done so that I can research the details about each process.

Thank you so much for your reply.

Terry

 

[SecurityTheatre]

Thank you for the quick reply.
Yes, I do have someone I could call in. Because this is and will be my responsibility, it is important that I learn each aspect of it and would like to go through each part of the process so that I will not have to rely on a consultant for maintaining the different roles.

The reason for my post is simply to learn "what" has to be done so that I can research the details about each process.

Thank you so much for your reply.

Terry

Yep, build the new server as a secondary domain controller and get it all sync'd properly- accounts and DNS will replicate to the new one.

Then you can promote the secondary to primary and you can decommission the old one for wiping.

Later, you can re-IP as necessary.

 

[tvanduzee]

Thank you.. Will give it a shot (after reading a bit of course).