transfer a domain controller to new hardware

[danrhodes]

You have to manually setup DNS and DHCP.

[Gardinho]

It's designed to be easy.

 

 

Install Server 2008 R2 on new platform.

Install DNS, DHCP (if required) etc

Run DCPROMO to make it a domain controller

Ensure DNS is replicating correctly and DHCP now points to new server for services.

Transfer the FSMO roles

Ensure FSMO info is being correctly registered on new server and in AD

Wait a day (AD being the fickle beast it is at times)

Check again

Run DCPROMO on the old DC to demote it **This bit is very important, don't just remove it or else borkage will occur**

Make coffee and sit back in the knowlege of a job jobbed.

 

Hi mate,

 

Thanks for your help with this. I have another query:

 

When I install DNS & DHCP before I promote it, do I configure it with identical settings to the old server? Do I need to remove DNS and DHCP on the old server at this point so that there is no conflicts?

 

 

 

Many thanks,

Edited May 25, 2010 by Gardinho

[danrhodes]

Some usefull docs to look over - DHCP: Dynamic Host Configuration Protocol (DHCP)

 

D

Edited May 25, 2010 by danrhodes

[CHR1S]

If your adding it as a member server first and your existing DNS is linked to AD then it will populate the new DNS for you once its installed as a role on the new server.

[Gardinho]

What a great help this has been.

 

One final question! Does anyone know an effective method to copy (or move) the data to the new server, retaining shares, acls and ntfs permissions?

 

Many thanks in advance.

[glennda]

What a great help this has been.

 

One final question! Does anyone know an effective method to copy (or move) the data to the new server, retaining shares, acls and ntfs permissions?

 

Many thanks in advance.

 

I tend to use Ntbackup to backup the data i need then restore to the new server. but there are other methods out there. robocopy, edumove at the end of the day its down to personal preference.

[danrhodes]

What a great help this has been.

 

One final question! Does anyone know an effective method to copy (or move) the data to the new server, retaining shares, acls and ntfs permissions?

 

Many thanks in advance.

 

Consider using RoboCopy it will copy it quickly and preserve the ACL, it cannot preserve the shares but for this consider using rmtshare!

 

Robocopy

Rmtshare - File and Printer shares

 

D

[CHR1S]

See my earlier post about a DFS.

[Gardinho]

Hi guys,

 

I'm back to bug you all again!

 

What do you do with the antivirus console? We use Sophos Enterprise Console. If I install the console on the new server, the clients will still be pointing to the old server name. Is it just a case of redeploying the antivirus to the client PCs?

 

Finally, will I be able to keep the same IP address as the old server? I'm pretty sure that I will be OK to, but I didn't know if changing the address after replicating DNS, DHCP and Active directory if this would cause a problem.

 

I have ran this once in my test environment, and the instructions provided by danrhodes were perfect.

 

With regards to moving the shares and acl's, I think I'm just going to use it as an opportunity to restructure the folders and make sure everything is controlled with NTFS permissions.

 

Many thanks,

[danrhodes]

Correct, it is just a case of re-deploying sophos through the newly installed console.

 

Also you can keep the old IP and not have issues as this will be handled by DNS / DHCP, just make sure the other server is off the network before you change the address over. Also it may be worth manually changing the DNS entries to your new server name afterwards so you dont get any dns resolving issues on your clients.

 

D

[ind1ekid]

You will need to run both the adprep /forestprep and adprep /domainprep commands before you add the new 2k8 server. These commands will need to be run on the domain controller on your network that contains the scheme operations master FSMO Role, probably your old server, as they will extend the schema to support the 2008 server.

 

D

 

Could you clarify, when you say "add", do you mean it has to be done before it is added as a member server? or before you run dcpromo to add it as a domain controller? I presume the latter?

 

Im planning on doing this at some point soon, so I'm forging a kind of guide together through all your guys posts/links etc.

 

Cheers

[danrhodes]

Correct, It's probably better to do it before you add the server as a DC to prepare the forest and domain for the new 2k8 server.

[ind1ekid]

Thanks for that, I thought that would be the case

[danrhodes]

NP good luck ;-)

[edutech4schools]

Just running through the process in my head and wondered during the new OS install at the network setup page do I point DNS to the original server that is running DNS? or as this is going to become the new DNS server at some stage point it at it's self.

 

EDIT

Ok the bit that is confussing me is from the following quote found on the first page

 

Install Server 2008 R2 on new platform.

Install DNS, DHCP (if required) etc

Run DCPROMO to make it a domain controller

Ensure DNS is replicating correctly and DHCP now points to new server for services.

Transfer the FSMO roles

Ensure FSMO info is being correctly registered on new server and in AD

Wait a day (AD being the fickle beast it is at times)

Check again

Run DCPROMO on the old DC to demote it **This bit is very important, don't just remove it or else borkage will occur**

Make coffee and sit back in the knowlege of a job jobbed.

 

On the second line down it says

Install DNS, DHCP (if required) etc

 

Do these (DNS, DHCP) get installed and setup as though no other server is on the network, basically how I would setup a server for the first time or do they need to take into account the old server and point at them? If its to ignor the old server does this not cause issues with having two servers issuing DNS/DHCP at the same time?

Edited May 29, 2010 by edutech4schools

[djones]

Install Server 2008 R2 on new hardware.

Change name to whatever is appropriate.

Setup static IP and existing gateway IP and then point DNS at original DC to verify that Internet/Network connection functions correctly.

If not done already, adprep /forestprep and /domainprep etc on original server

Join new server to existing domain and after reboot, confirm that everything still works as expected.

Run DCPROMO to make it a domain controller - this will install AD & DNS as well IIRC and begin to replicate existing AD & DNS.

Now change the new server's DNS settings to point, first to itself and then to the original DC.

Ensure DNS is replicating correctly.

Backup/export existing DHCP database/settings and migrate manually to new DHCP install on new DC.

Transfer the FSMO roles.

Ensure FSMO info is being correctly registered on new server and in AD.

Wait a day (AD being the fickle beast it is at times)

Check again

Run DCPROMO on the old DC to demote it.

 

That's how I've just done it anyway - only I haven't demoted the old server yet as I'm not sure how best to test that I've transfered everything - switch off old server and see if anything/one complains, if nothing obvious...switch back on and demote properly??

Edited May 29, 2010 by djones

[edutech4schools]

Thanks for the step by step. I'll have a play and update this post if I find anything that may help.

[edutech4schools]

Run DCPROMO to make it a domain controller - this will install AD & DNS as well IIRC and begin to replicate existing AD & DNS.

 

I have just done the above line but DNS has not installed. is this correct and should I just install it or does this suggest a problem?

[danrhodes]

No you will have to install DNS from the server roles. See Install a DNS server in Windows Server 2008 - Windows Server - Techguide

 

D

[teejay]

Install Server 2008 R2 on new hardware.

 

That's how I've just done it anyway - only I haven't demoted the old server yet as I'm not sure how best to test that I've transfered everything - switch off old server and see if anything/one complains, if nothing obvious...switch back on and demote properly??

 

Erm yeah, I had a muppet moment over half term as I forgot to change the dns settings on a bunch of servers with static IP and then removed the DNS service from our old servers

[edutech4schools]

ok this is my check list for 2003 to 2003 migration. Take into account the old server runs everything like Sims, FMS, home folders, DHCP, curric software..........

 

Check Network – Support tools

Backup old server

Setup Raid

Install OS

Setup OS (Updates)

adprep domainprep (if needed)

Join Domain

DCPROMO

Install DNS (should be populated by old server)

Transfer the FSMO roles

Point new server LAN settings at itself for DNS

Test from client computer

 

 

Firstly at what point should I enable DHCP on the new server? I was thinking after 'Transfer the FSMO roles'.

 

I am also planning on leaving Sims, FMS running on the old server while I move other docs and software over. Will this process leave me with a working Sims server?

 

EDIT

Should I run dcpromo on the old server to demote while sims is on the old server?

 

Anything look wrong with my list

Edited June 16, 2010 by edutech4schools

[edutech4schools]

Would somebody be able to reply to the above post. It would be handy for me to have this info before I begin the transfer. Thanks

[edutech4schools]

To add to the two posts above at what point does the netlogon/sysvol info get moved to the new server?

[ChrisH]

Netlogon/Sysvol will be replicated across during normal replication. I would run DCPROMO on the old server after you have moved SIMS. It shouldn't make a difference but you know what SIMS is like . Do dhcp last.

[edutech4schools]

Thanks