InSearchOf
asked on
Migrate 2008 R2 fle server to 2016
I want to decommission a 2008R2 fileserver but would like to migrate the shares currently on it to a new 2016 server. Trying do it with the least amount of headache and downtime and maintain share and permission settings.
That is a fairly easy one...
First you need to recreate the drive structure on the new server, especially if it has multiple drive letters.
Use something like robocopy to sync file structure of the shares across.
You will want to do multiple syncs if the file server is in service.
On migration day you kill access to the file server (or at least tell users to stay off) and do a final sync.
On the existing Windows installation that contains the share names and permissions that you want to save, start Registry Editor (Regedt32.exe).From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares.Save or export the registry key.
On the new server,
Run Registry Editor (Regedt32.exe).
From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares.
Restore or import the registry key.
You can also name server the same as old one, and reuse IP address and none of your users shortcuts will stop working
First you need to recreate the drive structure on the new server, especially if it has multiple drive letters.
Use something like robocopy to sync file structure of the shares across.
You will want to do multiple syncs if the file server is in service.
On migration day you kill access to the file server (or at least tell users to stay off) and do a final sync.
On the existing Windows installation that contains the share names and permissions that you want to save, start Registry Editor (Regedt32.exe).From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares.Save or export the registry key.
- For Windows NT and Windows 2000, click Save Key on the Registry menu.
- For Windows Server 2003 and later, click Export on the File menu.
On the new server,
Run Registry Editor (Regedt32.exe).
From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares.
Restore or import the registry key.
- For Windows NT and Windows 2000, click Restore on the Registry menu.
- For Windows Server 2003, click Import on the File menu.
You can also name server the same as old one, and reuse IP address and none of your users shortcuts will stop working
Is the source a VM or physical? Is the destination VM or physical? If both source and destination are VMs, same hypervisor? Same back end storage? Least amount of headache and downtime depends on the setup you already have. If source and destination are VMs using same storage and you have DFS Namespace I can cut over in less than 10 minutes of downtime and maybe less than 1 hour or total work (most of which would be spent getting to know the environment).
Other options would involve copying or syncing data, and best options would depend on things like how much data, rate of change, speed of storage, and any times when the system is less busy.
Other options would involve copying or syncing data, and best options would depend on things like how much data, rate of change, speed of storage, and any times when the system is less busy.
ASKER
Scott will this work for 2008R2? You post mentions 2000 and 2003
The registry key is the same from NT through Windows 2019. The instructions are the same, with only slight variation for RegEdit UI between versions.
I used the same instructions to migrate a 2008R2 to 2016... I just copied/pasted the doc I had
I edited my post to say "2003 and later" for posterity
I edited my post to say "2003 and later" for posterity
Just use the Migration tools thats what they are for?
</P>
</P>
They also have longer downtime...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Can I use a backup instaed to restore the files?
You can try, but why not do it the way we outlined?
We know that works...
We know that works...
I have migrated file servers to Windows 2012 from Windows 2003.
I followed Scott Silva's method for a VM, moved the vmdk to new file server, renamed the server to be the old name as to maintain the clients connection and imported the reg key.
I followed Hello There's method to a physical server. I would have converted to physical to VM then move the vmdk file too. But , it was a small file sever and robocopy worked for me.
I followed Scott Silva's method for a VM, moved the vmdk to new file server, renamed the server to be the old name as to maintain the clients connection and imported the reg key.
I followed Hello There's method to a physical server. I would have converted to physical to VM then move the vmdk file too. But , it was a small file sever and robocopy worked for me.
Windows Server – Migrating Files / Folders / Shares / User Profiles
</P>