creosote Posted September 13, 2013 Posted September 13, 2013 So I have found plenty of scenarios with regards to moving to a new server, but not sure one exactly like mine. I am not a server guru by any means, as this question may attest to. Basically, we are moving campuses and want to ditch the old hardware and switch to a new server (still running Server 2008). Currently, we use it for AD, GP, DHCP, DNS, and Print Management. BUT we only want to transfer the AD. The situation on the new campus is still a bit muddled in the sense we have to integrate with another network, so it is likely the DHCP and DNS setups will be totally different. I initially thought it would be easy enough to backup the AD and restore it to the new server, but after reading maybe not. The options I think we have are: 1. Do a backup and restore of the AD. I am already confused, though, by the terminology I am running into (system states, authoritative restores, subtrees, leaf objects, command line directions, etc). Definitely not as simple as I would have imagined. 2. Somehow connect the new server to the old network and do a dcpromo, etc. so it replicates the AD. Will it only replicate the AD (not DNS, etc.) if I have not installed those services on the new server? 3. Manually re-create the AD. Not a huge deal, the only downside I see is users having to reset passwords on the new campus (I assume there is no way to export current passwords from the current server). Any thoughts? Help is much appreciated.
ADMaster Posted September 14, 2013 Posted September 14, 2013 If the new campus will be the same domain I’d go the dc promo route. Dhcp will not replicate Dns will replicate if it is an AD integrated zone; which it should be. Join the new server to the current setup Dc promo so it begins replicating Transfer FSMO roles to new server Dc promo the old server to demote it as a DC However I recommend at least two DC’s if you can manage it. Perhaps skip demoting the old server and only transfer a few FSMO roles so they share the load. Good luck
twin--turbo Posted September 14, 2013 Posted September 14, 2013 If the new campus will be the same domain I’d go the dc promo route. Dhcp will not replicate Dns will replicate if it is an AD integrated zone; which it should be. Join the new server to the current setup Dc promo so it begins replicating Transfer FSMO roles to new server Dc promo the old server to demote it as a DC However I recommend at least two DC’s if you can manage it. Perhaps skip demoting the old server and only transfer a few FSMO roles so they share the load. Good luck You could always virtualise the old machine, and remove the roles that are not needed. Otherwise adding the new one as a DC is the way to go. Rob
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now