Everyone knows that it’s better to prevent problems from happening than to try and deal with things after they go wrong. That’s why it’s important to make sure you configure your default Hyper-V storage locations appropriately before you start creating new virtual machines on a Hyper-V host or importing existing virtual machines onto the host. Ben Armstrong, a Program Manager on the Hyper-V team at Microsoft, indicates in his “Virtual PC Guy Blog” that one of the top support-call generators for Hyper-V is when customers run out of space on their host. This is because the default locations for storing virtual hard disks and virtual machine configuration files is the system drive on the host, and if this drive becomes filled up, the host can fail to function. Because of the problems that can arise if these default location remains unchanged, some changes were made to the Add Roles And Features Wizard to ensure that customers think about the potential impact of this issue when they are installing the Hyper-V role. For more information, see Ben’s post at http://blogs.msdn.com/b/virtual_pc_guy/archive/2012/06/19/default-hyper-v-storage-paths-in-windows-server-2012.aspx.
Mitch Tulloch is a nine-time recipient of the Microsoft Most Valuable Professional (MVP) award and a widely recognized expert on Windows administration, deployment and virtualization. For more information see http://www.mtit.com. This tip was excerpted from his latest book Training Guide: Installing and Configuring Windows Server 2012 from Microsoft Press.