Skip to main content

Expanding the Boot Volume of a Windows Server 2008 Virtual Machine


Expanding the Boot Volume

To demonstrate how this works, I installed Windows Server 2008 as a virtual machine inside VMware ESXi 4.0. During the creation of the VM the boot partition size was set at 20 GB, which in Windows Server 2008 might just be a bit to small.



To expand it, we need to expand the virtual disk first. This is a simple process, all it needs is a couple of mouse clicks and you're set.

In the vSphere Client, right click the virtual machine and select Edit Settings



Next, you need to find the virtual disk and edit it's size from 20 GB to 30 GB, or any other size you might want, click OK and let it weave it's magic.



The disk should now be expanded, but Windows Server 2008 still doesn't recognize the new available space. This is where the Disk Manager enters the picture.

Navigate the Start Menu and find Server Manager. Find the Storage node, expand it and select Disk Management





Right click Disk Management and use either Refresh or Rescan Disks, both should work just fine. When the refresh is finished, you should see the newly added extra 10 GB as unallocated space on the disk you expanded. In our case it's Disk 0, as thats the only virtual disk that is attached to this particular server.



Right click the c:\ volume, and select Extend Volume and the "Extend Volume Wizard" should appear. This is pretty straight forward, but click next and you will be presented with a the tool that allows the volume expansion.



By default, the wizard will select all available space in the Selected column, but you can tweak those settings if you like. When you have done a selection you're comfortable with, click Next and a summary screen will appear outlining the changes you have made. If you are satisfied with your choices, click Finish, if not select Back and redo your settings.

Lean back and see that your boot drive has been extended to 30GB instead of 20GB, all without any downtime or interruption of service at all.





Note that if this was a physical machine, and not a virtual one, it would be a bit harder to accomplish. It would require that you have available, unpartitioned space, on the physical boot drive. Normally that's not the case and you would still need third party tools to be able to repartition your boot drive to free up some space that you could expand your boot volume with.
Summary

The Windows Server 2008 Disk Manager allows you to easily expand a boot volume, given that you have available unpartitioned space available to it. This great feature add-on in Windows Server 2008 might just prove invaluable to you down the line, especially in virtualized environments. The “Extend” feature only works when there is unallocated space available directly adjacent to the boot partition. That is too say, you cannot extend the system partition by shrinking others partition, you have to delete the partitions.

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...