I inherited a Windows Server 2003 R2 virtual machine that was previously running under a failing Windows Virtual Server 2005. Both the C: and D: VHDs were within a few hundred megs of being full.
I created a new Hyper-V-based VM to port the old one to and edited the VHDs prior to using them by expanding them both by 10Gigs.
The integration services install & HAL upgrade went fine but when I boot the VM, both drives were still showing as almost full still.
A quick look with Disk Management shows that they both have an extra 10Gigs of unallocated space tacked onto them.
I'm thinking an easy fix would be to simply down the Win2k3 R2 VM and attach its VHDs to another Win2k8 R2 VM running on the same Hyper-V server and use its disk management tools to extend the partitions to cover the extra 10Gigs added onto them.
Will Win2k8 R2 try to tack any additional "stuff" (drive signatures or the like) onto the VHDs that would prevent the Win2k3 R2 VM from functioning? I'd hate to purchase a 3rd party partitioning utility if I can do things with stuff already in-house.