fiza Posted May 21, 2015 Posted May 21, 2015 We need to move our user home drives, shared areas and profiles from our existing 2003 server to 2012 R2. We want to transfer all existing security and share permissions across. What is the easiest way to do this?
psydii Posted May 21, 2015 Posted May 21, 2015 (edited) Robocopy. Then recreate the shares. Then update all scripts and polices to secrecy the new location. Watch out for how offline files responds in this scenario. Create some test shares with content and move them first. Edited May 21, 2015 by psydii
fiza Posted May 21, 2015 Author Posted May 21, 2015 File Server Migration Toolkit I thought that wasn't compatible with 2012 R2 - - - Updated - - - Robocopy. Then recreate the shares. Then update all scripts and polices to secrecy the new location. Watch out for how offline files responds in this scenario. Create some test shares with content and move them first. Recreating the shares is what I want to avoid as we have loads, some embedded in others.
snagrat Posted May 21, 2015 Posted May 21, 2015 I use it all the time with little issue. Had some issues when moving from 2008 (non R2) 1
RobWilson-BBR Posted May 21, 2015 Posted May 21, 2015 Hi The easiest way to do it and best value is to use, Robocopy and then use RegEdit. If you go to the following key: SYSTEM\CurrentControlSet\Services\LanmanServer\Shares If you back this up on your old server and then install on the new one, you should see all your shares back. You need to do this after you have done the RoboCopy. RoboCopy instructions: https://technet.microsoft.com/en-GB/library/cc733145.aspx If you plan to run it over a few days, you should get all the files. From what I can remember, if you run a full copy day 1 and then day 2 and 3, do a incremental on any changes. You are more than likely to catch those users that ignore the "Please do not log on" messages! There is another way and that is to use DFS, but its a bit of effort to do this. Cheers Rob 2
ADMaster Posted May 21, 2015 Posted May 21, 2015 If you end up recreating the shares, set them up under a domain level DFS. This will make them easier to move in the future, and not effect offline files. 1
timbo343 Posted May 22, 2015 Posted May 22, 2015 I use Richcopy - it worked for what i wanted it to do and kept the security permissions. The only thing is, it doesn't keep top level folder permissions but keeps permissions on on all folders/files within the folder being copied.
fiza Posted May 22, 2015 Author Posted May 22, 2015 Hi The easiest way to do it and best value is to use, Robocopy and then use RegEdit. If you go to the following key: SYSTEM\CurrentControlSet\Services\LanmanServer\Shares If you back this up on your old server and then install on the new one, you should see all your shares back. You need to do this after you have done the RoboCopy. RoboCopy instructions: https://technet.microsoft.com/en-GB/library/cc733145.aspx If you plan to run it over a few days, you should get all the files. From what I can remember, if you run a full copy day 1 and then day 2 and 3, do a incremental on any changes. You are more than likely to catch those users that ignore the "Please do not log on" messages! There is another way and that is to use DFS, but its a bit of effort to do this. Cheers Rob Just looked at that registry entry. It has all the shares but also the current paths ie d:\users. On the new server do I have to ensure the shares are also moved to d:\users?
RobD Posted May 22, 2015 Posted May 22, 2015 I like RoboCop Robocopy which is just a pretty GUI for robocopy. Clicky 1
RobWilson-BBR Posted May 22, 2015 Posted May 22, 2015 Hi, You have to use the same path if you want to use the exported registry key, if not. You could just export it and edit in notepad with correct paths. Also, I tend to export these as a good reminder of where all the shares lead to. Rob 1
kennysarmy Posted May 22, 2015 Posted May 22, 2015 Just looked at that registry entry. It has all the shares but also the current paths ie d:\users. On the new server do I have to ensure the shares are also moved to d:\users? Notepad find and replace perhaps? 1
timbo343 Posted May 22, 2015 Posted May 22, 2015 When moving things over to a new file server have a think about using CNAMEs in DNS so that if something needs to be moved again you don't have to change the name of all the paths. We had set up things like \\FileServer1\... now we have a CNAME pointing to FileServer1 called FS-Students or whatever. In future all we need to do is change where the CNAME points to. We do this with most things around our place, i feel it makes for easier management of things. The only thing it doesnt work with is Printers, if you are sharing a printer, you have to use the server name opposed to the CNAME.
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