• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Server 2008 R2, need to replicate all settings to a new server.

Compman55

Golden Member
Bottom line is, within group policy, I cannot remember all the settings I have altered. I am getting a new server and would like to replicate all the settings an also keep the same name. So it is DC01.home.local. I know I can set it to DC02.home.local and let the settings replicate but I do not want 2 servers sucking electricity.
 
I'm assuming by the name of the servers, these are domain controllers at home and you're wanting to copy domain policies, etc? It is easy -- bring up the new server as a DC02, DCPROMO it, and transfer all the FSMO roles to it. Next, go over to DC01, DCPROMO it back to a member server, and then remove it from the domain and shut it down.
 
He's suggesting that you make your existing server a Virtual Machine by doing a Physical-to-Virtual (P2V) migration.
 
I'm assuming by the name of the servers, these are domain controllers at home and you're wanting to copy domain policies, etc? It is easy -- bring up the new server as a DC02, DCPROMO it, and transfer all the FSMO roles to it. Next, go over to DC01, DCPROMO it back to a member server, and then remove it from the domain and shut it down.

This is the industry standard way of doing it. If you really care about the name you can rename it after you remove the old server from the network, I always give the new server a new name though to easily identify outdated documentation that still has the old server name on it (and thus needs to be updated!).
 
I wonder if it's really policies he's worried about in a home environment. More likely things like network shares and ACLs.
 
Lastly what should I do with the folder redirection policy? The physical drive will no longer be the same on the new server. Will be much bigger.... Will I need to maunally edit the GPO to reflect the new area that the folder redirection will be taking place?

When I did this in a practice VM, I broke the folder redirection and could not get it back.
 
Lastly what should I do with the folder redirection policy? The physical drive will no longer be the same on the new server. Will be much bigger.... Will I need to maunally edit the GPO to reflect the new area that the folder redirection will be taking place?

When I did this in a practice VM, I broke the folder redirection and could not get it back.

How are you doing folder redirection now?

If you're redirecting to the user's home directory, then you would need to go into the properties of the user accounts in ADUC, go to the Profile tab, and change the path that you connect the Home folder to.

Otherwise, you should be able to assign a new location through the GPO if you're not using Home Directories.
 
Setting the location thru a tab under the user properties (not sure as I am not in front of it), then made a seperate GPO for the offline files syncronization every (x) amount of seconds. I do this so I can run each computer in offline mode, and have it sync the folders. This way in offline mode I don;t feel the pain of the slow gigabit network. It can sync later.
 
Back
Top