Migrating File Shares to a New Server

I recently needed to perform a physical to virtual migration (P2V) of  a file server.  I tried using my P2V software to accomplish this, but the virtual server would not boot after migration.  So the question became what do you do when its time to upgrade to a new file server or want to migrate to a virtual server without expensive P2V software.  I have used this method in the past when upgrading a physical file server and it served me well for this process as well.

If your file server is on a domain and all you need are the files, shares, and permissions this can be accomplished rather easily. This process should of course be performed during a scheduled downtime or maintenance windows and the new server needs to be configured with the same drive letters and file paths as the old server.  First, simply backup your files and restore them to the corresponding drive(s) on the new server.  I like to start this process a day or two before the actual migration.  I perform a full image backup of the shares and restore it to the new server ahead of time and follow up with a differential backup and restore at the time of migration. This reduces the time required to complete the migration dramatically.  When performing your backups, include file permissions and disk quotas where applicable.

Next you export two registry keys from the old server and import them into the new server. (This process can be done prior to migration as well as long as no new shares or permissions will be adjusted prior to migration). These keys are SYSTEM\CurrentControlSet\Services\LanmanServer\Shares and SYSTEM\CurrentControlSet\Services\LanmanServer\Shares\Security (more information here). 

LanmanServer\Shares Registry Key

Reboot the new server and voila your shares are up and running on the new server.

Finally during your scheduled maintenance window, shutdown the old server.  Then rename and readdress the new server to use the old servers information and you are done.  Alternatively if the the new server needs to have a different name and/or IP address, update your log in scripts to point to the new server.