• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 320
  • Last Modified:

DC 2008 R 2 Enterprise replacement

I have a dc 2008 R 2 , which was built and installed , we have the whole network up and running with DNS and DHCP , we found out that the server is to slow , and the ram is no longer available , so we bought a new Server ...
I need to know the safest way to replace teh box with our new one ...

1 do i do a system state backup , then toss the old box and replace with new and restore .. ??
2 do i bring it into the network and add it to the domain and move the fismo roles ??

Only problem with that is all my settings like DNS and so forth , i do have a secondary DC but its not working a 100% due to DNS issues and DHCP .. Otherwise it has everything else ...

Please help
1 Solution
Mike KlineCommented:
You go with number 2.  You bring up the new server and then promote that to be a DC/Global Catalog/DNS server then make sure clients are pointing to the new box for DNS and you can also transfer the FSMO roles.

...definitely always have at least two DCs in all networks.


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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now