Export VMs from Hyper-V with PowerShell

This morning I’m preparing to change my Windows Server 2012 RC to the RTM version. This server is only acting as a Hyper-v member server on my network so no big deal. My biggest challenge is that I wan to use the VMs that I have on this server again once I finish building the new one. I am performing a clean install so I need to export these VMs or fail them over. Since this is my test environment, I do not have a failover cluster.

For those of you who have manually performed a VM export in Hyper-V, you know that this is a time consuming process. I have 14 VMs with snapshots that need to be preserved. Since I am expecting this process to take some time, I wanted to have some type of visual indicator as to where I was in the export process. Here is the simple PowerShell one liner that I am using.

Get-VM | ForEach {Write-Host $_.Name;

Export-VM -Name $_.Name -Path S:\2012VMs}

This simple code does the following. First we gather all the VM objects from Hyper-V using the Get-VM cmdlet. We then pipe these objects into a ForEach statement that contains 2 different commands. The first simply displays the name of the VM that is being exported. The second performs that actual export.

That is it! I’m looking at my ISE and I am watch the names of each of the 14 VMs being displayed as they are being exported.

Comments

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

Jason Yoder, MCT

Search This Blog