Tag Archive for 'Server 2008 R2'

Suspend Hyper-V VMs with PowerShell

I have one Hyper-V R2 server that fights with me on occasion. The VMs are responsive and I can RDP into them. The server itself is sometimes responsive, and I can RDP into it, but it fails to connect to Hyper-V manager. A reboot usually clears up the problem, but I hate to reboot the host machine with VMs still running.

I have noticed, however, that I can still access Hyper-V through the PowerShell API. As the VMs on this machine aren’t critical, I can suspend the VMs using the API. Then I can reboot the host machine, and start the VMs back up again using Hyper-V manager.

Continue reading ‘Suspend Hyper-V VMs with PowerShell’

Windows 7 Theme on Server 2008 R2

Sometimes you get tired of looking at a server desktop. So, here is a way to spice up Server 2008 R2 and make it look like Windows 7.

Continue reading ‘Windows 7 Theme on Server 2008 R2′

Hyper-V Double Import Error

The type of work I do relies heavily on passing Hyper-V VMs around. When I send a VM to someone, I usually export a copy onto an external Hard Drive. In a perfect world, the VM would get copied off of the external drive to the local machine before being imported, but that sometimes doesn’t always happen. One user imported the VM while it was still on the external drive. Granted the VM would still work, it would probably be considerably slower due to running off of USB. They ran into problems on their host machine, so they decided to swap it out for another host machine. They shutdown the VM, and deleted it from Hyper-V. Then they plugged in the external drive into a new machine, and tried to import the VM again. This time they received an error:

Hyper-V Import Error Message

Hyper-V Import Error Message

Hyper-V Manager

A server error occurred while attempting to import the virtual machine.

Import failed.

Import failed. Unable to find virtual machine import files under location ‘D:\vm-export\test-import\’. You can import a virtual machine only if you used Hyper-V to create and export it.

Hyper-V doesn’t allow you to import VMs multiple times. In order to import the VM again, they would have needed to export the VM beforehand in order to prepare it for being imported on the second machine. The export process basically, cleans up the file structure of the VM and creates a config.xml file similar to the following:

<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<configuration>
  <SnapShotDataRoot type="string"></SnapShotDataRoot>
  <ExternalDataRoot type="string"></ExternalDataRoot>
  <vhd>
    <source type="string">D:\VMs\test-import\test-import.vhd</source>
    <target type="string"></target>
  </vhd>
  <VmStateCopied type="bool">true</VmStateCopied>
</configuration>

Upon importing the VM, Hyper-V looks for and then removes the config.xml file. If it can’t find that file, you will get an error message.

Now, if you have received this message, there is no need to panic. There are still ways to recover your VHD files. If your VM had 0 snapshots it is actually very easy to bring the VM back online. Dig around through the VM’s folder structure and locate its VHD file. That is the virtual hard disk that your VM uses to store all of its information.

If you have a VM with snapshots, the process will be a little different. Essentially, you will need to use the “Edit Disk” feature in Hyper-V to merge the AVHD disks into 1 VHD file, and then create a new Virtual Machine using that VHD file. There is a good guide located http://www.networkfoo.org/server-infrastructure/recovering-your-virtual-machine-how-manually-merge-hyper-v-snapshots-back-one- that can help you merge your AVHDs back into a single VHD file.

Once you have a single VHD file, in Hyper-V, create a new Virtual Machine. Give it a name and location, and fill out all the other important information it asks. Then once you get to the “Connect Virtual Hard Disk” screen, select “Use an existing virtual hard disk” and then browse and select the VHD file you found from above. Finish creating the VM and turn it on. The VM should work just as it did before.

Server 2008 R2 Hyper-V / Intel I7 – Blue Screen of Death

I was building out a new demonstration laptop. The laptop would be running VMs on Server 2008 R2 Hyper-V. Since the VMs we needed to run were rather large, we picked up a rather powerful laptop to support them.

  • Server 2008 R2 Enterprise
  • Intel i7-720 QM
  • 8GB RAM
  • 640 GB HD

The build went fine. It was simple, enabling Virtualization in the BIOS, installing the OS, adding Hyper-V role, importing a few VMs. Everything went smoothly.

I started a Virtual Machine to make a few tweaks before going home for the weekend. When I came in on Monday morning. I found a wonderful screen telling me there was an unexpected shutdown. Awesome. Thanks Monday…

I checked the Event Viewer and found out that it had been restarting every few hours all weekend.

Continue reading ‘Server 2008 R2 Hyper-V / Intel I7 – Blue Screen of Death’

No Remote Desktop License Servers Available

A client we were working with was having issues connecting to one of their servers. When trying to RDP to a Server 2008 R2 machine, they kept receiving this error message:

No Remote  Desktop License Servers Available

No Remote Desktop License Servers Available

The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.

Please contact the server administrator.

According to Microsoft’s Website, RDS and the License Server works like the following:

Continue reading ‘No Remote Desktop License Servers Available’