I recently asked a question about cloning a failing Windows 2008 R2 server onto new, identical hardware, and was given the good advice not to attempt to clone it since it's a domain controller. Now that I've identified the correct method to remove the server, I need some advice on how to best conduct the migration. I need to migrate the following:
Approximately 300 user "home" folders.
Multiple shares with complex security assignments.
All FSMO roles (This was the fist DC, and has all of the primary roles)
Multiple Access database with the UNC path of the server hard coded.
I'm hoping to avoid recreating all the shares and security along with manually identifying and modifying all the user account home folder assignment.
Is there a migration tool available that works reliably? Can it be tested before rolling the dice in a production environment?
Out of everything I listed, DHCP is the only role I'm comfortable moving (done it several times previously). DNS has caused me some hangups in the past. I've had to transfer the FSMO roles before but don't recall the exact procedure. I assume that I can copy the shares from one server to the other and retain the security settings. It would be wonderful if there is a way to filter the active directory user accounts with a home folder on the server to be replaced and then update every account with a new home path of "\\NEWSERVERNAME\USER\%USERNAME%" and be done. The Access databases could be all manually altered, but it would be so much easier if I could just leave a DNS alias to the old server name. I assume there is no way possible to retain the old server name after migration?
Any advice would be greatly appreciated!