You aren’t alone. I figured out this morning it is related to the integration components and that they are not at the same level as the server.  Months ago I create a new VM. After creating it I sys-prepped my machine and used the sys-prepped drive as part of my templates in the VMM library. Since creating the template my server got updated and so did the integration components. Because of this, when I went to go use the template I got heart beat errors because the VM and Host are not at the same level.

Lesson learned? Well, make sure that you always have the same integration components installed. Want to learn from my Hyper-V mishaps? Check out the Virtual Machine Manager & Hyper-V section of my blog.

You might be surprised that the Virtual Machine Manager Configuration Analyzer will spit this message out if you aren’t logged in as a domain admin when you run the tool!

Log off and log back on as a domain admin and you won’t have to worry about this issue anymore!

Hope this helps someone else.

I have partitioned the Machine’s drive into a smaller system drive and  much larger data drive that will house the VMM library data. I also make sure that the server has at least 2GB of ram. If you don’t the install will squawk at you but allow you to still install things. I also wanted to tell you I am installing this on a DC. Microsoft doesn’t like you installing this on a DC especially if you are wanting a self service portal. You’ve been warned.

You are going to need to download and install a few pieces of software (don’t run them just yet):

1. Microsoft Baseline Configuration Analyzer (this is needed by the SCVMM Configuration Analyzer)
2. System Center Virtual Machine Manager 2008, 2008 R2, and 2008 R2 SP1 Configuration Analyzer

Install IIS on the server

Open Server Manager and right click Roles. Click “Add Roles”.

Make sure IIS is checked off. Click Next.

Ensure that these additional IIS items are all checked off and hit Next and Install:

• Static Content
• Default Document
• Directory Browsing
• HTTP Errors
• ASP.NET
• .NET Extensibility
• ISAPI Extensions
• ISAPI Filters
• Request Filtering
• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility

You should restart your machine since you just installed a feature. Once you have done this your machine should validate and everything should go very smoothly. To validate your machine run the VMM configuration Analyzer. This should now be in your start menu since you installed it in the previous steps.

If you followed my instructions you should see something like this:

Run setup on the VMM Disk

The install is easy. When it asks where to install the files I switched it from C: to E:

When it asks about SQL server I am just going to us SQL Express.

Specify a Share. Again I am moving things to E:

The rest of the install I just selected the defaults. Once it is finished updating I recommend that you run the machine through Windows Update and make sure everything is all patched and up to date.

You will most likely want to install the VMM Administrator Console. You can do this by running it off the setup program of VMM.

The install of the VMM Administrator Console is very simple. It’s your typical Next, Next, Next install. It will ask where you want to install it and what ports you want it to run on. I told it to install to the E: and I kept the ports the set to the default numbers.

Hope this helped you get VMM up and running a bit faster.

Ensure that no application on machine host.domain.tld listens for HTTP traffic on TCP port 443 during the conversion. Ensure that no application on host.domain.tld machine listens for HTTP traffic on TCP port 443 during the conversion. Alternatively use registry key HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\P2VBITSTcpPort on the VMM server to change the P2V transfer port number and add the necessary firewall rule for TCP port 443 on machine tbcdc03. Alternatively use registry key HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\P2VBITSTcpPort on the VMM server to change the transfer P2V portnumber and add the necessary firewall rule for TCP port 443 on machine.

1. Open Regedit on SCVMM server.
2. Go to –> HKLM \Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
3. Create a new DWORD (32) entry with the name: P2VBITSTcpPort
4. Give it a port value of say: 441 instead of default of 443.
5. Restart the VMM server to apply the setting.

I have seen this documented in a couple of places now – but I also see a number of people still wondering why this is happening and how to stop it, so I thought I would post it here too.  When you first add a Hyper-V host to SCVMM 2008 you may see a warning icon displayed with the message "Needs Attention" and "Virtualization service version status is not up-to-date".  To get rid of this alert there are three updates that need to be applied to the Hyper-V server:

• KB950050: This is the RTM update for Hyper-V
• KB956589:  This is an update to Hyper-V specifically for SCVMM compatibility
• KB956774: This is an update to the Background Intelligent Transfer Service (BITS) client in Windows Server 2008

Once you have these three updates installed everything should come up green.