I have a physical SBS2011 server and need to move it to new Hyper-V environment. I have attempted two migration methods (1) Disk2Vhd (2) Restoring Windows Server backup to virtual machine via image restore.
But so far, each method has its own challenges. In other words, none of these worked out seamlessly so far in test environment.
Therefore I am considering the following.
(1) Do a complete Installation of SBS2011 as a virtual machine.
(2) On new SBS VM, create users and share folders from the scratch based on what we have on production server. Set permissions and match IP address and domain name .. etc. I will keep this VM separately from existing network.
(3) Do a complete Windows Server backup of production SBS2011 on network share (this might be faster that backing up on an external USB hard drive in terms of backup & restore time).
(4) Export exchange mailboxes into PST files using single Exchange shell command (unless you believe that it is better to create PST from outlook on each user’s outlook from accuracy standpoint).
(5) Disjoin all workstations from production SBS server and disconnect SBS server from the network.
(6) Connect Hyper-V server and new SBS VM to the network.
(7) Restore files and folders from the server backup stored on the network share.
(8) Using Exchange shell command, import PST files into corresponding mailboxes. (or I could import PST into Outlook on each workstation PC. There are only 20 PCs)
(9) Set permissions on folders on new SBS.
(10) Join workstation PCs to the new domain.
(11) Copy old user profile (C:\users\old_username_folder\*.*) into newly created profile folder (C:\users\new_username_folder\*.*) on each PC.
(12) add local & network Printers.
That’s is all I can think for now. If I am missing something or if there is an easier way to restore mailboxes or set folder permissions as I restore from the windows server backup, I would appreciate your suggestions.
Even though I know creating new SBS is going to be more time-consuming than two other methods that I tried, one thing that is good about this method is that I can start a fresh new SBS server without any errors in Event viewer. In current production server, there are a ton of error messages both in an application and system section of event viewer and I will not have time to troubleshoot these errors although they do not seem to create any problems in day-to-day operation.