Skip to main content

Configuring VM Storage in Hyper-V

The Default location for storing Hyper-V Virtual Machine files is:

 

.vhd: C:\Users\Public\Public Documents\Hyper-V\virtual hard disks

 

Configuration files: C:\Program Files\Microsoft\Windows\Hyper-V

 

It is OK to leave them there in a test environment, but in practice, you will want to move them to different physical drives simply for the sake of better performance. Here are a few considerations.

 

  • Move them off the partition that holds the host’s operating system
  • Move them off the disk that is used by the parent for paging.
  • If using multiple VMs on the same server, distribute the VM files across as many disks as possible.
  • If stored on a SAN, ensure reliability and performance will meet expectations.
  • Make sure the location will not only have enough space for data, but also snapshots.
  • Restrict access to the storage locations to only those who need to copy and paste files in that location.
  • If on a failover cluster, store the files on the shared disk.

 

To change the default location of the stored files, open Hyper-V Manager:

 

Click Hyper-V Settings in the Actions pane.

 

The first two columns on the left are the default storage locations. Changing these will change the storage location of all future VM files.

 

clip_image002

 

You can also specify the location of the data files when you create a new VM.

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the