Shrinking VMs

I need soma assistance with shrinking existing VMs. It seems it is the containers that hold all the VM components that is not able to be shrunk due to data blocks that can't be moved. For example: I have a Windows 7 VM that is 300 GB in size but there is actually 187 GB of free space on the virtual HDD. The HyperV host is a Windows Server 2012 RS and I use the HYper-V Manager. Most of the oversized VM were created from cloning one of the original existing machines. Any thoughts?
DevilDoc325Asked:
Who is Participating?
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.

becraigCommented:
Shrinking a virtual hard disk

As expected, when you shrink a virtual hard disk, the virtual hard disk capacity is decreased. However, there is a limit to amount of disk space that can be adjusted when you shrink a virtual hard disk. That limit is defined by the size of the volume that is currently in use by the virtual machine. The Hyper-V Manager user interface shows the minimum disk size available for shrinking a virtual hard disk.

If you want to shrink the size of the virtual hard disk below the size of the currently used volume within the virtual machine, you must first use Disk Manager in the operating system of the virtual machine to shrink the volume. After that is complete, you can reduce the size of the virtual hard disk.

Instructions on shrinking the disk in the OS:
http://technet.microsoft.com/en-us/library/cc731894.aspx
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
another method, is to create a new virtual disk of the correct (shrunk size).

and then use a Cloning tool (e.g. clonezilla) to clone the partition from disk to disk, and then remove the original disk.
0

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
DevilDoc325Author Commented:
Thanks Andrew and becraig. I will be working on this and I will let you know my results.
0
DevilDoc325Author Commented:
Both solution would work and I appreciate the guidance. I am using WDS on a Server 2012 R2 to create and deploy the correctly sized images and simplify future deployments.  I am creating a new base image and basically cloning old systems.
0
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.

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.