Disk2VHD

I'm trying to create a VHD of my exchange 2003 to move it to another location and virtualize the server to be able to migrate to 2010. However, I just learned that Disk2VHD has a 127GB file size limit.

My data partition is 200GB+ in size.  Are there any other alternatives that an allow me to save a VHD larger than 127gb and import into Hyper-V?
Anthony H.Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

matrix8086Commented:
Download the last version of Disk2vhd which allows you to convert a physical hdd to a vhdx file format. Vhdx has a much greater limit of file size

Maybe this link will help you more
https://technet.microsoft.com/en-us/library/ee656415.aspx

Best regards
Anthony H.Author Commented:
That's the website where I saw this:

"Note: Virtual PC supports a maximum virtual disk size of 127GB. If you create a VHD from a larger disk it will not be accessible from a Virtual PC VM."
matrix8086Commented:
Sorry, wrong link, try this one:

http://hyperv.veeam.com/how-to-convert-physical-machine-hyper-v-virtual-machine-disk2vhd/

where is written:

NOTE: VHDX is a new disk format that was introduced in Windows Server 2012. Compared to traditional VHD, VHDX has several improvements, including a special internal log to reduce the chances of data corruption, a bigger capacity (up to 64 TB) and other great features. I recommend using VHDX whenever possible.

I hope you have Hyper-V on Windows Server 2012 ...
SolarWinds® Network Configuration Manager (NCM)

SolarWinds® Network Configuration Manager brings structure and peace of mind to configuration management. Bulk config deployment, automatic backups, change detection, vulnerability assessments, and config change templates reduce the time needed for repetitive tasks.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you are wanting to create a P2V or V2V of a server, use the supported and free method, by the recent introduction of the new tool Microsoft Virtual Machine Converter 3 from Microsoft.

Please see my EE Articles, Step by Step tutorial instructions with screenshots.

HOW TO:  P2V, V2V for FREE to Hyper-V -  Microsoft Virtual Machine Converter 3.1

HOW TO: Convert a physical server or virtual server (P2V/V2V) to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1
Lee W, MVPTechnology and Business Process AdvisorCommented:
First, VirtualPC has a 127 GB limit - not Disk2VHD.  And NOT Hyper-V.

That said. I agree with Andrew Hancock - it's unwise to use an unsupported method to perform P2V conversion.
matrix8086Commented:
I think TotalTech2020 has Windows 2003 Server, so Microsoft Virtual Machine Converter cannot be used.

Why are you saying that Disk2VHD is an unsupported method? Is on the Microsoft's tech site. And I used it a few days ago with great success. I don't talk from Google Search, I am talking from my live experiences :)

Best regards!
Lee W, MVPTechnology and Business Process AdvisorCommented:
Just because it works MOST of the time (in my experience) doesn't make it supported.  To be clear, a SUPPORTED method is one that you can get technical support for - it has been tested extensively enough by MS (or whatever the vendor is) to confirm that it works or that it doesn't under certain conditions.  No professional should ever use an unsupported method of anything in a production environment unless it's absolutely necessary.  And even then alternatives which may not be what you originally wanted to do would be the wise choice.
Anthony H.Author Commented:
Andrew: Not Found
The page you're looking for cannot be found

:(
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Anthony H.Author Commented:
Then it is NOT an option, right?
Anthony H.Author Commented:
so back to Disk2VHD?  or this
http://www.symantec.com/system-recovery-server-edition/system-requirements/

Open in new window

matrix8086Commented:
Totaltech2020: let me explain how I just converted windows server 2003 R2 from physical to virtual. First of all I have made a full backup of the host. Then With Disk2vhd I have created the vhdx files, transfered them to the hyper-v host. Shutdown the physical host. Create a new machine in Hyper-v and select the vhdx file to use as virtual hdd. Attach other vhdx files (in case of more physical hdds). Start the new machine

It may be the case that network adapter will not be reconized. No problem: install Integrated services and install Legacy driver. In that case you will receive an error that it is an unused NIC with the same IP. No problem: it is a procedure to remove hidden devices (search on Google) !

Nothing could goes wrong! In case of some failure you can anytime to start the old physical host. I made all above, outside the working hours, remote, from my home.

Good luck!
Anthony H.Author Commented:
thanks Matrix - for some reason Disk2VHD is not seeing my partitions/OS drives.  I'm running a full backup via shadowprotect and going to restart it to see if I can get Disk2VHD to see the partitions. If not, i'll use Symantec System Recovery to create the image.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You could always do this the long way round, and P2V using VMware Converter. (but you'll need an older version) because latest version dropped support for 2003.

Once you have the VMware VM, then convert using V2V Starwind Convertor.
Anthony H.Author Commented:
Andrew - Coverter 6.0 (latest version?) does support windows 2003.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Converter 6.0 supports the same version as 5.5.3, despite many requests to VMware, because of Windows 2003 End of Life and Support, they've not added it. They've also now removed Windows XP from 6.0 as well.

Windows Server 2003 R2 SP2 (32-bit and 64-bit) is supported, you didn't mention if you were using R2 ?

Note the R2.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony H.Author Commented:
I was able to use the VMWare converter and Star2wind to convert it to VHDx.  
I liked the Disk2VHD idea, but I could never get it to create it due to HD space issues. Thank you guys.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.