Pkafkas
asked on
How to setup DFS and is my plan for deployment correct?
Hello,
I am in the process of plannig a Windows 2008 R2 File Server Migration to Windows 2012 R2 File Server. I was going to use robocopy to move the files over to a new Server; but, in a previous case other experts suggested to use a Distributed File System (DFS) server instead ( https://www.experts-exchange.com/questions/28984124/File-Server-Migration-Questions-and-advice.html ).
I like the idea of using DFS and that should be a good plan for a smoother transition regarding future file Server migrations. I will be working with an IT consultant that has done this before and he has some really good ideas. The consultant's ideas sound logical and should work; but, I want to be as prepared as possible when it is deployment time.
Allow me to outline the objectives and then our plan. I then look forward to hearing feedback from the group regarding the design of plan.
1. Clearly document the current file Shares and Security permission on the 2008 R2 File Server folders.
2. Clearly document what program are installed on the file Server.
a. AntiVirus programs.
b. Etc.
3. Create a new Windows 2012 R2 Virtual Server (OS Drive only).
a. We do not have a SAN at this workplace.
b. The new 2012 R2 Virtual Server will be on the same ESXi Host and Datastore as the 2008 R2 File Server.
3. Plan a maintenance window to un-install any applications on the 2008 R2 File Server.
a. Then restart the file server and then power that same 2008 R2 Server off.
b. power off the new 2012 R2 DFS / File server as well.
4. During the same maintenance window detach the Data Drive from the 2008 R2 File Server.
a. Begin to download a copy of that Data Drive from the 2008 R2 File Server to a PC (with enough storage space).
b. Then upload and atatch the same data drive to the new Windows 2012 R2 File Server/DFS Server.
5. Create a DNS alias for the 2008 R2 file Server name to point to the new 2012 R2 File Server' DNS name.
a. Power on the 2012 R2 File Server ad verify all of the data is there.
6. At this point I will need to re-set the security permissions; but, the folder share's I believe should still be there.
a. Does point 6 sound correct? I have never done this before.
7. Then install the required applications for the new File Server.
a. The test everything out.
b. Eventually delete the old file Server from disk; but, the user's will still be using the older file server DNS name for mapped drives.
I would appreciate feedback and thoughts regarding this File Server migration.
I am in the process of plannig a Windows 2008 R2 File Server Migration to Windows 2012 R2 File Server. I was going to use robocopy to move the files over to a new Server; but, in a previous case other experts suggested to use a Distributed File System (DFS) server instead ( https://www.experts-exchange.com/questions/28984124/File-Server-Migration-Questions-and-advice.html ).
I like the idea of using DFS and that should be a good plan for a smoother transition regarding future file Server migrations. I will be working with an IT consultant that has done this before and he has some really good ideas. The consultant's ideas sound logical and should work; but, I want to be as prepared as possible when it is deployment time.
Allow me to outline the objectives and then our plan. I then look forward to hearing feedback from the group regarding the design of plan.
1. Clearly document the current file Shares and Security permission on the 2008 R2 File Server folders.
2. Clearly document what program are installed on the file Server.
a. AntiVirus programs.
b. Etc.
3. Create a new Windows 2012 R2 Virtual Server (OS Drive only).
a. We do not have a SAN at this workplace.
b. The new 2012 R2 Virtual Server will be on the same ESXi Host and Datastore as the 2008 R2 File Server.
3. Plan a maintenance window to un-install any applications on the 2008 R2 File Server.
a. Then restart the file server and then power that same 2008 R2 Server off.
b. power off the new 2012 R2 DFS / File server as well.
4. During the same maintenance window detach the Data Drive from the 2008 R2 File Server.
a. Begin to download a copy of that Data Drive from the 2008 R2 File Server to a PC (with enough storage space).
b. Then upload and atatch the same data drive to the new Windows 2012 R2 File Server/DFS Server.
5. Create a DNS alias for the 2008 R2 file Server name to point to the new 2012 R2 File Server' DNS name.
a. Power on the 2012 R2 File Server ad verify all of the data is there.
6. At this point I will need to re-set the security permissions; but, the folder share's I believe should still be there.
a. Does point 6 sound correct? I have never done this before.
7. Then install the required applications for the new File Server.
a. The test everything out.
b. Eventually delete the old file Server from disk; but, the user's will still be using the older file server DNS name for mapped drives.
I would appreciate feedback and thoughts regarding this File Server migration.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just so we are both on the same page. i am not planning on using robocopy at all. I was originally thinking of using robocopy; but, other experts suggested I should use DFS instead. With that said, it sounds as if this process will be simpler than I thought regarding the security permissions.
According to your notes, if I use the same driver letter on the new server and attach the drive from the old server to the new Windows 2012 r2 server (with VMware) then both the Windows Shared permissions and the NTFS security permissions should be the same.
Since we will only have 1 active file server in production then there is no reason for the DFS Server and the File Server not be the on the same virtual server. I am still confused about the DNS alias for the old server.
We have many group policies that reference the old file server (Terminal Server profiles, logon scripts, etc.). if we can still use the original file server DNS name; but, simply re-direct all inquiries to the new file server (I thought an Alias record would do this). Then if an Alias record would work we can keep the original server name forever and simply change the where the DNS alias would point to, when we need to update future servers.
Does anyone else have any experience wit this type of project?