![]() ![]() If working remotely you will need to maintain access at least to the Hyper-V host throughout entire process.If SBS is an OEM version it is a licensing violation to install on different hardware or virtualize, the activation will probably fail, and if it does Microsoft will not assist. Note: The process will require re-activation of the SBS license. I have posted the steps that worked flawlessly for me on a test server, trail run, and final move. I am not suggesting the following is the best method, or even a good method, but perhaps it will be of some help to those attempting the same task. Though disk2vhd has worked well for me with other operating systems in the past, for some reason the HAL in this case caused problems. ![]() The first run on a test machine using a single disk worked well but did require several ‘tweaks’, and then when I added the data drives, which may have been unrelated, I ran into many problems, especially when I tried installing the Integration Services components. I first Googled the task and found many suggestions which based on the various articles and instinct, using Microsoft’s disk2vhd was the simplest solution. I have done SBS conversions to VMware hosts in the past with with little or no problem, but converting to Hyper-V, my preference, was a little more involved. I recently needed to virtualize an SBS 2003, that is to say convert it from a physical machine to a virtual machine on a Hyper-V host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |