Converting Physical SBS2011 to Hyper-v with Disk2vhd Utility

Hi,

From this website/link:
https://lhdinger.wordpress.com/2011/12/12/converting-physical-sbs-to-hyper-v-with-disk2vhd-utility/ I discovered that VHDX file (created by Disk2vhd Utility program) for SBS2011 OS partition can't be bigger than 127GB. Otherwise it may not work at all.

Since I was not successful in migrating physical SBS2011 to a VM in Hyer-V server, I wonder if it was because my VHDX file was bigger than 127GB. In my case, files and folders along with active directory moved over just fine when I started a SBS2011 VM, but client Outlook failed to connect to Exchange Server 2010 even though all exchange server services were running in SERVICES.msc.

 I like to know from experts who have migrated a physical SBS2011 to a VM in Hyer-V server if such a limit exists.

Thanks.
LVL 1
sgleeAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
 
Tom CieslikIT EngineerCommented:
You can't use P2V software to convert domain controller.
There is a problem with security token in active directory and administrator password.
0
 
RoninCommented:
I wouldn't be P2V-ing SBS server, which is possible. I would migrate of the services from it. Exchange, SQL, etc different machines.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
sgleeAuthor Commented:
"You can't use P2V software to convert domain controller." --> There are many articles where people converted a physical SBS2011 to Virtual Machine in Hyper V server. Some used Disk2VHD, Some used Windwos Server Backup. Some used Double-Take software. But people have done it.

"I wouldn't be P2V-ing SBS server, which is possible. I would migrate of the services from it. Exchange, SQL, etc different machines." --> I can't separate Exchange, SQL ... etc. I have either bring it as it is or build another SBS2011 from the scratch and create users, folder permissions, import PST into user mailboxes .. etc.
0
 
sgleeAuthor Commented:
But I am only curious if you have heard about this 127GB limitation in VHDX file for SBS OS partition.
0
 
RoninCommented:
127GB was limitation in previous versions of Hyper-V, Virtual Server or PC.
Maybe the utility outdated?
Usually such limitation are listed in the software documentation.
Or you can use a different, newer tool.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
There is no 127 GB limit to a VHDX - the VHDX limit is 64TB.  The VHD limit is 2TB.

The only issue with > 127 GB VHDs is when used with Virtual PC.  You are using Hyper-V, a completely different type of hypervisor.  That is not your problem.

I would ask Tom to post a link (at Microsoft.com) that explains the "problem with security token in active directory and administrator password."  I've not heard of it nor have any seen any issues suggesting I've experienced it or seen others experience it over the years.  Indeed, Microsoft has blogs on P2Ving domain controllers - here's one: https://blogs.technet.microsoft.com/askds/2010/06/10/how-to-virtualize-active-directory-domain-controllers-part-1/

That said, Disk2VHD is NOT the preferred method of P2V.  Use the Microsoft Virtual Machine Converter (MVMC).  I *HAVE* used Disk2VHD for P2V in the past and not had any issues, but you generally get a better experience from MVMC and there has been some debate that Disk2VHD is not a supported method; MVMC is definitely supported.

As for your issues connecting to Exchange, odds are it's a firewall/IP/networking issue.  You need to troubleshoot that.
0
 
sgleeAuthor Commented:
@Lee,

 " I HAVE used Disk2VHD for P2V in the past and not had any issues, but you generally get a better experience from MVMC"  --> Have you migrated a standalone SBS2011 into a VM in HyperV?
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
I've migrated OLDER SBS systems - SBS 2008 and other non-SBS 2008 R2 systems.
0
 
sgleeAuthor Commented:
@Lee & @Andrew,

 I have tried both Disk2VHD  and Microsoft Virtual Machine Converter 3.1 for testing.
Here was my experience:

(1) Disk2VHD : First time, I did not shut down Exchange Server related services (before running Disk2VHD program) which was my bad. Second time, I did shut down Exchange. However end result was the same. I also ran Disk2VHD on  several workstation PCs. I put all these VHDX files on new HyperV server and turned them on. Every virtual machine PC had no problem logging on to SBS2011/VM (DHCP was giving out IP addresses) and mapped drives worked fine. However Outlook client could not detect exchange server. What I have not tried on workstation VM PCs was to create a new Outlook Profile. The change/adjustment that I had to make on SBS2011 VM was to populate static IP address.
(2) MVMC was a completely different animal. I ran into so many issues/errors in even filling out the information about source and destination, let alone seeing a new VM created as a result. It was so complicated and a nightmare.

So I am considering 3rd option "Windows Server Backup route".
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
 
sgleeAuthor Commented:
@Andrew
Thanks for the article. Do you happen to have another version that is geared towards to Hyper V?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It works with EVERYTHING! substitue the word VMware with Microsoft Hyper-V!

Backup your server to an image, BOOT Recovery Media in Hyper-V VM, and Restore!

Job Done! That's how easy it is...
0
 
Tom CieslikIT EngineerCommented:
Windows Backup is OK, bot not Disk2VHDX,,,many users reported problem about DC functionality after conversion using this software
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
(1) ... However Outlook client could not detect exchange server. What I have not tried on workstation VM PCs was to create a new Outlook Profile. The change/adjustment that I had to make on SBS2011 VM was to populate static IP address.
This doesn't tell me much.  What testing have you done to get this working?  Are there event log errors?  The Network adapter changes when you switch hardware (which is what you're doing) and you could have entered a different firewall profile which blocks Exchange.  "It won't connect so I'm starting over" isn't a good procedure in my opinion.
(2) MVMC was a completely different animal. I ran into so many issues/errors in even filling out the information about source and destination, let alone seeing a new VM created as a result. It was so complicated and a nightmare.
Don't know what issues or errors, but if you are, there could be other things going on with the server that needs correcting.
0
 
RoninCommented:
Points for the contribution and explanation of the approaches.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.