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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog