Supporting Virtual Machine Manager in the Enterprise

P2V fails with Error 2910 (0x80070005) Access Denied

2010-11-12T20:52:05Z

Symptom

When using Microsoft System Center Virtual Machine Manager 2008 to perform a Physical-to-Virtual conversion (P2V), the following error message appears during the Scan System phase.

Error (2910)
VMM does not have appropriate permissions to access the resource on the %server.
Access is denied (0x80070005)

Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.
Additional Information: The Source computer is the machine intended to be virtualized in the P2V conversion.

Cause

This failure is typically caused by either of the following conditions:

• The credentials provided during the P2V wizard is not a member of the local ‘Administrators’ group on the Source computer.

• The Source computer does not allow remote WMI calls to the CIMV2 namespace for the credentials entered during the P2V wizard.

Resolution

To resolve the problem, follow these steps:

1. Make sure that the account used during the P2V wizard is a member of the local ‘Administrators’ group on the Source computer. Note Pay particular attention to this if the SCVMM server and Source computer are in different domains.

2. During the Scan System phase of the P2V conversion, SCVMM makes WMI calls to the CIMV2 namespace on the Source computer to pull basic system information. If these WMI calls fail, then the P2V conversion will also fail. To verify WMI connectivity to the CIMV2 namespace on the Source computer, perform the following actions from the SCVMM server:

a. Click Start , point to Run and type " WBEMtest" (without the quotes) in the Open box and click OK . This will open the WBEMtest window.

b. Click Connect in the upper right hand corner.

c. Now, connect to the CIMV2 namespace on the Source computer.

Example: \\Source\ROOT\CIMV2

Note Be sure to use the name of your Source computer.

d. Then click Connect to complete the connection. This should connect without any errors displayed.

e. Just to confirm access to a sample object, select Open Class and type Win32_PhysicalMemory

f. You should see objects populate in the Object Editor window. The actual content returned is not as important as the fact that a remote connection to the CIMV2 namespace was established.

3. Open wmimgmt.msc and verify connectivity to the Local computer and also check the 'Remote Enable' permissions.

a. Click Start , point to Run and type wmimgmt.msc and click OK . This will open the WMI Control (Local).

b. Right click on the WMI Control (Local) node and select Properties .

c. Select the Security tab, highlight Root and then open security by clicking the Security button in the lower right.

d. Select "Remote Enable" permission for Everyone or the specific user account that you want to grant this permission to.

e. This action does not require a reboot.

4. Open dcomcnfg and verify that DCOM is running and also check the 'Remote Activation' permission.

a. Click Start , point to Run and type dcomcnfg and click OK . This will open the Component Services snap-in.|

b. Expand Component Service , then Computers , then My Computer . If My Computer has a red down arrow mark, it means that the service is not running. It will need to be started.

c. Right click on My Computer and select Properties and select the COM Security tab.

d. Click Edit Limits under the Launch and Activation Permissions section.

e. For the Everyone user give the "Remote Activation" permission or add the specific user account that you want to grant this permission to.

Note The following error message may occur if the appropriate WMI permission is not granted to the user:
Access Denied" with Error Code: 0x80041003

5. This problem can also occur if the OLE registry key is missing or has the incorrect value on the Source computer.

a. Start Registry Editor.

b. Locate the following path:
HKLM\SOFTWARE\Microsoft\OLE

c. This key should have a REG_SZ value EnableDCOM and a value of Y.

VMMSSP2.0 releases!

2010-11-09T19:41:20Z

Moving to the cloud? Use this free toolkit to help customers build a private cloud infrastructure.

System Center Virtual Machine Manager Self-Service Portal 2.0 is now available!

The Microsoft System Center team is pleased to announce the launch of System Center Virtual Machine Manager Self-Service Portal 2.0 (SSP).

Download SSP Now!

The System Center Virtual Machine Manager Self-Service Portal 2.0 (SSP) is a fully supported, partner extensible solution that enables customers to dynamically pool, allocate, and manage their compute, network and storage resources to deliver a private cloud platform in their datacenter. Learn more.

Using System Center Virtual Machine Manager Self-Service Portal 2.0 (SSP), you can respond more effectively—and at a lower cost—to the rapidly changing needs of your organization. Build on top of Windows Server 2008 R2, Hyper-V and System Center VMM, it enables you to offer infrastructure as a service.

It includes a pre-built, role-based self-service portal for both the datacenter managers and business unit IT consumers – all in a dynamic running engine. The portal reduces time needed to provision infrastructures and their components by offering a business unit “on-boarding” infrastructure request and change management. It also includes detailed guidance on how to implement the portal inside your environment. SSP is freely available, and fully-supported by Microsoft.

Key Features:

· Automation and Guidance: To assess, plan and design your private cloud foundation infrastructure

· Customer/business unit on-boarding: Automated workflows to onboard business unit IT departments onto to your virtualized shared resource pool

· Dynamic provisioning engine: To rapidly provision virtualized infrastructure in conjunction with System Center and Hyper-V

· Self-Service portal: To empower consumers of IT to request and provision infrastructure for their apps/services

· Partner Extensibility: Enable partners to expose their unique hardware capabilities through familiar Microsoft scripting technologies while providing variety and flexibility to IT

What is Hyper-V Dynamic Memory?

2010-10-21T18:50:17Z

Are you ready for Dynamic Memory and RemoteFX?

I'm sure that everyone has heard of these new technologies being introduced in R2SP1 for Windows 2008. But do you now what they really mean? Here are some basic definitions and excellent blogs about each for your reading pleasure.

Hyper-V Dynamic Memory

So, what is Dynamic Memory? At a high level, Hyper-V Dynamic Memory is a memory management enhancement for Hyper-V designed for production use that enables customers to achieve higher consolidation/VM density ratios. With Hyper-V Dynamic Memory, Hyper-V will enable greater virtual machine density suitable for servers and VDI deployments.

RemoteFX

With Microsoft RemoteFX, users will be able to work remotely in a Windows Aero desktop environment, watch full-motion video, enjoy Silverlight animations, and run 3D applications within a Hyper-V VM – all with the fidelity of a local-like performance.

Hyper-V Dynamic Memory

Part 1: http://blogs.technet.com/virtualization/archive/2010/03/18/dynamic-memory-coming-to-hyper-v.aspx

Part 2: http://blogs.technet.com/virtualization/archive/2010/03/25/dynamic-memory-coming-to-hyper-v-part-2.aspx

Part 3: http://blogs.technet.com/virtualization/archive/2010/04/07/dynamic-memory-coming-to-hyper-v-part-3.aspx

Part 4: http://blogs.technet.com/b/virtualization/archive/2010/04/21/dynamic-memory-coming-to-hyper-v-part-4.aspx

Part 5: http://blogs.technet.com/b/virtualization/archive/2010/05/20/dynamic-memory-coming-to-hyper-v-part-5.aspx

Part 6: http://blogs.technet.com/b/virtualization/archive/2010/07/12/dynamic-memory-coming-to-hyper-v-part-6.aspx

How to change ownership of virtual machines via PowerShell with SCVMM 2008 R2

2010-10-01T15:28:00Z

Just wanted to make everyone aware of a method to change the owner field of multiple VMs via Powershell, written by a colleague, Dave Guenthner. This is a great method to use if you need to change the owner field of a lot of VMs at once. Please visit his blog for more information.

* Where "%Domain\1stUser% is the current owner and "%Domain\2ndUser% is the desired owner

Get-VM -VMMServer "%YourVMMServername%" | where {$_.Owner -eq "%Domain\1stUser%"} | Set-VM -Owner "%Domain\2ndUser%"

Also be sure and check out the VMM08R2 Cmdlet Reference. It is a great doc to read to learn about lots of cool tricks like this using Powershell to manage your VMM environment. Especially if you're one of those scripting guys :-)

Saving and re-applying the virtual machine metadata in VMM

2010-08-24T18:27:52Z

Occasionally it is necessary to remove a host from management and then re-add it back in. This will result in the loss of any metadata associated with that particular host. Such metadata includes the custom properties, descriptions, tags, owner, cost center, etc. If it is 1 or 2 VMs, its not a big deal to add them back, but when you are talking about a cluster with 200 VMs it is quite an effort. Michael Michael has posted a great blog that outlines exactly how to restore the metadata through the use of powershell scripts.

http://blogs.technet.com/b/m2/archive/2010/04/16/saving-and-re-applying-the-virtual-machine-metadata-in-vmm.aspx

End of Support Lifecycle for Windows XP SP2/2000

2010-08-18T17:28:28Z

As already published in several blog postings all over the web since December 2009, still some customers are asking for the Microsoft Support Lifecycle of WIndows XP SP2 and Windows 2000.

To post again the information about this topic and to remind customers to plan upgrade/migration considerations from Windows XP and 2000 up to the newer editions like Windows Vista or Windows 7, here you may find all answers or resources for this important topic!

Upcoming end of support for Windows XP SP2 and Windows 2000

Coverage highlights:

Microsoft has used blog postings and Twitter feeds over the past few days to remind users that support for Windows XP Service Pack 2 and Windows 2000 will expire in July 2010, perhaps encouraging users of those aging operating systems to upgrade to Windows 7 if they choose to stay with a Microsoft operating system. Microsoft has created an end-of-support solution center for Windows 2000, and posted materials online designed to help users migrate from Windows XP to Windows 7. --eWeek
Windows 7 is, of course, the best choice for an upgrade, especially if the migration also implies a hardware upgrade, as is generally the case for corporate customers. Users that are intent on ridding XP for all it’s got can continue doing so, however, they too must also upgrade, at least to XP SP3. With the third service pack for XP customers will enjoy extended support from Microsoft until 2014.--SoftPedia
Microsoft has issued a reminder this week that it will stop providing support for Windows 2000 and Windows XP Service Pack 2 on July 13, 2010… For Windows XP SP2, users are encouraged to move to Windows 7, Windows Vista, or simply Windows XP Service Pack 3, for which support will end two years after the next service pack (likely not happening) or at the end of the product's supported lifecycle, whichever comes first. --ARS Technica
… the clock is ticking for Windows 2000 (server and client) and Windows XP Service Pack 2. Extended support for those products will end on July 13, 2010…Users of XP SP2 have the option to upgrade to SP3. Extended support for XP SP3 will end on April 8, 2014, according to Microsoft's XP lifecycle page.—Redmond Magazine
For a more strategic approach to OS and application migrations, Microsoft provides a guide called "Choosing a Deployment Strategy."
If all else fails, there’s Microsoft Services, which offers consulting services to enterprises. Microsoft or its partners provide the support, which includes desktop planning, application compatibility testing, desktop imaging and desktop deployment. .—Redmond Magazine

Microsoft Support Lifecycle Policy

The Microsoft Support Lifecycle policy took effect in October 2002, and applies to most products currently available through retail purchase or volume licensing and most future release products. Through the policy, Microsoft will offer a minimum of:

10 years of support (5 years Mainstream Support and 5 years Extended Support) at the supported service pack level for Business and Developer products
5 years Mainstream Support at the supported service pack level for Consumer/Hardware/Multimedia products
3 years of Mainstream Support for products that are annually released (for example, Money, Encarta, Picture It!, and Streets & Trips)

Additional links and resources:

Bug in extended support:

If you are facing a bug while your product is in extended support phase, please note that typically perspective is that a product in extended support has most bugs fixed or known bugs are documented and published on web, TechNet, kb Article or MSDN and many Blog posts of the community. Therefore Non-security hot fixes and bugs handling is fee based in extended support phase.

So my best advice for you: upgrade as fast as possible to either Windows 7 client OS or Server 2008 OS for no worries about lifecycle support ;-)

What does this mean for VMM?

This also touches VMM in that we no longer support Windows 2000 as a source in a conversion, whether P2V or V2V. What that means is that you cannot open a case with CSS to troubleshoot a failed conversion when the source computer is running Windows 2000. You however may continue to receive support from the community at large by posting your question to our TechNet forums.

How to remove a VM with the "missing" status from the VMM console

2010-08-18T13:05:00Z

Occasionally, after a cluster failover, duplicate virtual machines may appear in the System Center Virtual Machine Manager (VMM) Administrator Console: one with a status of Missing, the other with a different status. The missing virtual machines can be difficult to remove. The script in this topic is a SQL Server script that removes the missing virtual machines for you.

Note The script removes all virtual machines with the status of Missing from the VMM database. The script does not delete any virtual machines from any host computer, whether it is a Hyper-V, Virtual Server, or VMware-based host.

The following steps help you prepare your system and run the script:

1. Close the VMM Administrator Console.

2. Stop the Windows service named VMMService on the VMM server.

3. Make a full backup of the VMM database.

4. Install Microsoft SQL Server Management Studio Express on the same computer on which the VMM database is stored.

Tip Microsoft SQL Server Management Studio Express is a free download from Microsoft that you can find on the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=190524).

5. Open SQL Server Management Studio Express, select the VMM database, and then run the following SQL Server script. This should delete all missing virtual machines with a status of Missing from the VMM database. If the script was successful, you will see the following output: Commands(s) completed successfully.

6. After the SQL Server script has completed, restart the VMMService and open the VMM Administrator Console to verify that the missing virtual machines are now deleted.

BEGIN TRANSACTION T1

DECLARE custom_cursor CURSOR FOR

SELECT ObjectId from

dbo.tbl_WLC_VObject WHERE [ObjectState] = 220

DECLARE @ObjectId uniqueidentifier

OPEN custom_cursor

FETCH NEXT FROM custom_cursor INTO @ObjectId

WHILE(@@fetch_status = 0)

BEGIN

DECLARE vdrive_cursor CURSOR FOR

SELECT VDriveId, VHDId, ISOId from

dbo.tbl_WLC_VDrive WHERE ParentId = @ObjectId

DECLARE @VDriveId uniqueidentifier

DECLARE @VHDId uniqueidentifier

DECLARE @ISOId uniqueidentifier

OPEN vdrive_cursor

FETCH NEXT FROM vdrive_cursor INTO @VDriveId, @VHDId, @ISOId

WHILE(@@fetch_status = 0)

BEGIN

DELETE FROM dbo.tbl_WLC_VDrive

WHERE VDriveId = @VDriveId

if(@VHDId is NOT NULL)

BEGIN

DELETE FROM dbo.tbl_WLC_VHD

WHERE VHDId = @VHDId

DELETE FROM dbo.tbl_WLC_PhysicalObject

WHERE PhysicalObjectId = @VHDId

END

if(@ISOId is NOT NULL)

BEGIN

DELETE FROM dbo.tbl_WLC_ISO

WHERE ISOId = @ISOId

DELETE FROM dbo.tbl_WLC_PhysicalObject

WHERE PhysicalObjectId = @ISOId

END

FETCH NEXT FROM vdrive_cursor INTO @VDriveId, @VHDId, @ISOId

END

CLOSE vdrive_cursor

DEALLOCATE vdrive_cursor

-----------------

DECLARE floppy_cursor CURSOR FOR

SELECT VFDId, vFloppyId from

dbo.tbl_WLC_VFloppy WHERE HWProfileId = @ObjectId

DECLARE @vFloppyId uniqueidentifier

DECLARE @vfdId uniqueidentifier

OPEN floppy_cursor

FETCH NEXT FROM floppy_cursor INTO @vfdId, @vFloppyId

WHILE(@@fetch_status = 0)

BEGIN

DELETE FROM dbo.tbl_WLC_VFloppy

WHERE VFloppyId = @vFloppyId

if(@vfdid is NOT NULL)

BEGIN

DELETE FROM dbo.tbl_WLC_VFD

WHERE VFDId = @vfdId

DELETE FROM dbo.tbl_WLC_PhysicalObject

WHERE PhysicalObjectId = @vfdId

END

FETCH NEXT FROM floppy_cursor INTO @vfdId, @vFloppyId

END

CLOSE floppy_cursor

DEALLOCATE floppy_cursor

----------------

DECLARE checkpoint_cursor CURSOR FOR

SELECT VMCheckpointId from

dbo.tbl_WLC_VMCheckpoint WHERE VMId = @ObjectId

DECLARE @vmCheckpointId uniqueidentifier

OPEN checkpoint_cursor

FETCH NEXT FROM checkpoint_cursor INTO @vmCheckpointId

WHILE(@@fetch_status = 0)

BEGIN

DELETE FROM dbo.tbl_WLC_VMCheckpointRelation

WHERE VMCheckpointId = @vmCheckpointId

FETCH NEXT FROM checkpoint_cursor INTO @vmCheckpointId

END

CLOSE checkpoint_cursor

DEALLOCATE checkpoint_cursor

-------------------------

---------Clean checkpoint

DELETE FROM dbo.tbl_WLC_VMCheckpoint

WHERE VMId = @ObjectID

exec [dbo].[prc_VMMigration_Delete_VMInfoAndLUNMappings] @ObjectId

DECLARE @RefreshId uniqueidentifier

exec [dbo].[prc_RR_Refresher_Delete] @ObjectId, @RefreshId

DELETE FROM dbo.tbl_WLC_VAdapter

WHERE HWProfileId = @ObjectId

DELETE FROM dbo.tbl_WLC_VNetworkAdapter

WHERE HWProfileId = @ObjectId

DELETE FROM dbo.tbl_WLC_VCOMPort

WHERE HWProfileId = @ObjectId

DELETE FROM dbo.tbl_WLC_HWProfile

WHERE HWProfileId = @ObjectId

DELETE FROM dbo.tbl_WLC_VMInstance

WHERE VMInstanceId = @ObjectId

DELETE FROM dbo.tbl_WLC_VObject

WHERE ObjectId = @ObjectId

FETCH NEXT FROM custom_cursor INTO @ObjectId

END

CLOSE custom_cursor

DEALLOCATE custom_cursor

COMMIT TRANSACTION T1

SCVMM Comprehensive Updates

2010-04-30T19:48:00Z

There are many updates available for SCVMM and the technologies it manages. Staying up to date can be difficult. There is a tool, the VMMCA, that will check the configuration and updates installed on the SCVMM Server and any Hosts specified and produce a simple report. This covers a great number of required updates. Now, how about all the updates that have been released since the VMMCA was last released? This article will list all of the updates the VMMCA already checks for as well as those that you will have to verify on your own. I’ll note that there is another post on this blog that explains how to check for updates across many computers automatically, given that firewall settings are as they should be. That post can be found here.

Updates the VMMCA already verifies

Install on the SCVMM Server
961983
971244

Install on SCVMM Hosts
950050
956589
956774
958124
954563
955805

Hyper-V updates for SCVMM Hosts
952247
956697
957967
958184
959978
971677

Failover Cluster Management updates for SCVMM Hosts
951308
958065

New updates, not verified by the VMMCA

I do not have these broken down by installation location as in the above list. I’ll try to get this sorted out. In the meantime, here are the technologies affected and what OS and SCVMM versions they apply to. We use these with our support customers on a daily basis to resolve issues. If it will install on your system, install it!

WinRM-Win2003
936059 An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP

WMI - Win2008, SP2
968936 Memory corruption may occur with the Windows Management Instrumentation (WMI) service on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1

WMI - Win2008, SP2
971403 A rollup hotfix package for Windows Server 2008 Failover Clustering WMI provider

WMI - Win2008, SP2
970520 The Wmiprvse.exe process creates a memory leak on a computer that is running Windows Server 2008 if you remotely monitor this process by using the WMI interface on a computer that is running Windows Server 2003 or Windows XP

WMI - Win2008R2
974930 An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception

WMI - Win2008R2
981314 The "Win32_Service" WMI class leaks memory in Windows Server 2008 R2 and in Windows 7

Hyper-V - Win2008R2
981618 The computer stops responding or restarts during the Hyper-V Live Migration process in Windows Server 2008 R2

P2V - Win2000
834010 A deadlock occurs when a program that uses WMI calls the LoadLibrary() or the FreeLibrary() function in Windows 2000

P2V - Win2000, 2003
892294 A WMI event notification query does not detect a user permissions change on Windows 2000 or Windows Server 2003

P2V - Win2000
843527 The Win32_SCSIController WMI class cannot obtain SCSI controller information after you install the MS04-011 security update

P2V - SCVMM2008
959596 Description of the System Center Virtual Machine Manager 2008 update to address physical to virtual (P2V) issues

P2V - SCVMM2008
971816 Using P2V together with System Center Virtual Machine Manager 2008 may fail with error 3154 (0x8099319E) or error 13252 (0x809933C4)

VMM Rollup - SCVMM 2008R2
976244 Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: November 10, 2009

VMM Rollup - SCVMM 2008R2
978560 Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: February 9, 2010

Other - SCVMM2008R2
976246 When you remove a virtual hard disk from a virtual machine in System Center Virtual Machine Manager 2008 R2, the .vhd file on the Hyper-V server is deleted without warning

Conclusion

This article is clearly a work in progress, and will be updated as regularly as needed. If you are experiencing any issues with SCVMM, or simply want to prevent them… install these updates. They matter. Thanks!

How SCVMM Determines CPU Average Displayed in the Admin Console

2010-04-07T16:12:00Z

This article describes the performance metrics details that SCVMM collects and how to make sense of performance information that is displayed in SCVMM.

VMM uses a periodically running performance refresher that gathers performance data from Hosts and virtual machines (VMs) and stores it in the VMM database to be used by the Intelligent Placement feature (this is the nifty star rating prioritization of hosts that you see when you try to migrate a VM or when you try to create a new VM). Besides Intelligent placement purposes, the UI (SCVMM Administrator Console) also displays this performance data. This refresh happens every 9 minutes by default and can also be triggered as a side effect of certain SCVMM actions (explained below). With every refresh, SCVMM gets the average of every metric over the past 9 minutes. Here is how it’s done on different platforms.

Hyper-V – Hyper-V hosts** expose certain performance counters for a physical host and the virtual machines residing on it. SCVMM Server talks to each Hyper-V host over WSMAN to gather these performance metrics for the host and its VMs. SCVMM collects virtual machine performance metrics directly from its host because of some limitations of what a virtual machine understands about its true performance. Here a few interesting metrics explained.

1- Host CPU Average is exposed in SCVMM console as the “%Total Run Time” counter of “Hyper-V Hypervisor Logical Processors(_Total)” counter set*** averaged over past 9 minutes. This counter captures processor utilization being caused on the host (parent partition) and by the VMs. This value and other host performance metrics could be refreshed on demand as part of Refresh-VMHost or Refresh task in the SCVMM Console. Note that this value is different than what the Host’s Task Manager or %Processor Time(_Total) counter would show, which only considers parent partition utilization.

2- VM CPU Average is exposed in SCVMM console as the “%Guest Run Time” counter of “Hyper-V Hypervisor Virtual Processor(_Total)” counter set . This is the percent of time spent by the virtual processor(s) that run the VM. Since Hyper-V allows control of how many processors and what percent of their capacity can be assigned to a VM, the Guest Run Time counter value can never exceed the specified limit. Note that this is very different from the VM CPU% displayed in Hyper-V console, in which CPU utilization is displayed as VM Host Logical Processors utilization.

For example: The Hyper-V VM settings shown in the image below have been intentionally allotted 60% of 2 processors capacity. So, if this VM’s utilization is 100% from inside the guest, this VM is actually using 60% of the 2 virtual processors assigned to it from a Host perspective. The SCVMM console would show ~60% in this case, Hyper-V console will show ~30% for this VM.

The reason the Hyper-V console shows 30% is because the physical system has 4 logical processors. Thus 60% of 2 logical processors assigned to the VM is 30%. The 60% that SCVMM shows in the UI is averaged/tiered over the last 9 minutes and is not an instant value for a point-in-time CPU percentage of a VM.

*= default time interval of performance refresh, which is configurable through registry for troubleshooting purposes

**= Windows Server computer with HyperV role enabled

***= All counter sets on a computer can be seen using Performance Monitor (perfmon.exe).

VMware – SCVMM talks to Virtual Center server to get performance metrics for all its Hosts and their VMs.

Host in Needs Attention state after installation of KB978560

2010-02-25T14:44:00Z

Just a quick note to say that once the latest rollup for VMM R2 has been applied, you will need to update the agent on each managed host. Until the agent has been updated, the host status displayed in the VMM console will be "Needs Attention".

To update the VMM agent on multiple hosts, follow these steps:

1.	Open the Virtual Machine Manager console.
2.	Click Administration , and then click Managed Computers .
3.	Select the hosts, and then click Update Agent .
4.	Enter your credentials, and then click OK.

978560 Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: February 9, 2010
http://support.microsoft.com/default.aspx?scid=kb;EN-US;978560

This hotfix can be found on Windows Update or downloaded manually.

To manually download the hotfix rollup from the Microsoft Update Catalog, visit the following Microsoft Web site :

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=978560

Note The Microsoft Update Catalog has different versions of the update package. These different versions have the EVAL , OEM , RETAIL , and WORKGRP labels. Download the appropriate version for your installation.

If the rollup was downloaded from the Microsoft Update Catalog, do the following to install the hotfix rollup package on the Virtual Machine Manager server:

1.	Extract the VmmServer64Update-RETAIL.cab to a temporary directory.
2.	Open an elevated command prompt, and then run the following command to install the update: msiexec /update vmmServer64Update-RETAIL.msp BOOTSTRAPPED=1 Note The name of the package varies based on the version that was downloaded.
3.	After the hotfix rollup package is installed on the Virtual Machine Manager server, update the VMM agent on the Hyper-V and Virtual Server hosts.