I have a project to migrate all of the files from a Windows 2008 R2 Standard Server (64-bit) to a new Windows 2012 R2 Standard Server (64-bit). Since we have so many Active Directory "Group Policies" and "Home Directories" tied to the original File Server name "FileServer1" I think it would be best eventually rename the new file server name to be "FileServer1" as well.
I wanted to discuss my plan the experts and see if anyone has any other suggestions regarding how to go about this project? The last time I did something like this was about 4 years ago and I am not certain if there are any better utilities for me to use.
1. I plan to have a full backup Friday night and I will ask the user to not logon until that file Server's backup is finsihed.
2. After the backups (VEEAM Backup & Replication) I can begin the copy process from "FileServer1" to "FileServer2".
a. I plan to use the RoboCopy GUI ( http://www.thewindowsclub.com/whats-new-in-windows-7-robocopy
) for this copy process.
3. FileServer1 has all relevant files on its B: Drive (don't ask why 'B', it was not my idea). Inside this B: drive there are several shared folders and subfolders.
a. The Source path will the fileServer1's B: Drive.
b. The Destination server (FileServer2) will have E: Drive.
c. The Destination path will be the fileServer2's E: Drive ( I will map a drive from FileServer1 to this destination location).
4. Ideally, I would like to maintain the current folder structure and its security permissions.
a. There will be some files that are already encrypted, and I want to copy them over as well.
b. I will use the web page: http://burpee.smccme.edu/studenthowtos/robocopy.htm
shows the copy options.
c. I hope that this version of Robocopy will work with Windows 2008 R2 and Windows 2012 r2 servers.
d. If it will not are there any other alternatives to this version of Robocopy?
5. I think I will need to manually create the shared folders.
a. I will need to verify all of the security permissions anyway; hence, I can setup the folder permissions at the same time.
b. Then test the access with my user account and several test user accounts that have different security rights.
c. I will need to verify the functionality of the security permissions.
6. Then when the files and folder shares and security settings are verified I will rename the original FileServer1 to something else.
a. Then change the IP address on the original FileServer1.
b. Then power off the original fileServer1.
c. Verify the static Windows DNS settings are as they should be.
7. Then rename the destination server to be "FileServer1" and then change the IP address as well.
a. Verify that the DNS entries are as they should be.
b. I hope this will satisfy the group policies and home directories and mapped drives with DNS and Active Directory.
8. Then test everything out.
a. Verify the functionality of the network and fix whatever may need fixing.
b. The exit strategy will be to rename the servers as they were before and try again at a later time.
c. Or use the backups to restore the original server back.