admin

I have seen this happen a few times and i really hate how the checkpoint / snapshot feature works in Hyper-V. Basically it creates an “.avhd” file for each snapshot you create and using an “.xml” file keeps track of how they are stitched together. I had a customer that had a disk failure. and after rebuilding the host, i was lucky enough that the partition the VHD files lived on was intact. What really bothers me is the fact that you can’t simply import the virtual machine. The reason is quite silly: it was not exported. In order to get the vm back online you must use the Disk Editor and merge the files back into the root file one at a time. pretty lame microsoft.

Here is how you do it.

1) start by backing up the folder before you start

2) rename all the avhd files in the snapshot folder to vhd. (but first write down the modified date and time.

3) open the Disk editor in hyper-v manager and merge the most recent file to the parent

4) repeat this process until you have no more snapshots left.

For more reading on this subject, head on over to technet:

http://social.technet.microsoft.com/Forums/eu/winserverhyperv/thread/afff42b0-49ca-4542-9b22-e4f5a94230be

According to the WashingtonPost,

Amazon is announcing today that Netflix and Facebook will headline a cast of “several thousand” apps and games available for the Fire at launch, all of which have been tested by the company specifically for Fire compatibility.

read the full story here: http://www.theverge.com/2011/11/9/2549230/kindle-fire-apps-netflix-facebook-and-rhapsody-all-coming-next-week

The interesting part of this story is the rumor that Amazon will try to take out Netflix by offering streaming movies. Which , if it were true would make this announcement very odd.

I get asked this question alot and this is very simple. you can change the port by editing the registry, but what i usually do is create a separate registry entry to allow alternate ports to use to access my remote desktop. This is great for when i am on networks that block port 3389, but allow port 3390 and above. It goes without saying that if you are behind a firewall you will need additional configuration to allow access.

Reason for editing the registry to add the listener on the new port is the fact that you cannot add this using the GUI.

This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.

More >