This article describes the Microsoft Center Virtual Machine Manager 2008 issues that are fixed in the System Center Virtual Machine Manager 2008 update.
List of issues that are fixed
You use System Center Virtual Machine Manager 2008 to perform an offline physical to virtual (P2V) conversion. The computer that is running System Center Virtual Machine Manager 2008 is located on a different subnet from the source computer. However, both computers are configured to use an IP address range, such as 10.x.x.x. The offline P2V conversion fails with the following error message:
Error (3133)Virtual Machine Manager could not connect to source computer servername.domainname.com after it restarted into Windows PE (temporary computer name is p2v-ldjj). Automatic restart to the original operating system is scheduled to occur within 15 minutes. Recommended ActionIf servername.domainname.com does not restart in 15 minutes, manually restart it back into the original operating system using the boot menu
You convert a physical computer to a virtual machine by using VMWare VirtualCenter. One of the disks on the physical computer is larger than 256 gigabytes (GB). You add the VMWare VirtualCenter server to System Center Virtual Machine Manager 2008. When you try to create a virtual machine, the operation fails with the following error message:
VMM Cannot find VirtualHardDisk object.Ensure the library object is valid, then try the operation again.ID: 801
If you receive this error message before you apply this update, you can use SQL Server Management Studio to run a SQL Server script against the VMM database to correct this issue.
Note To download the Express version of SQL Server Management Studio, visit the following Microsoft Web site:
To create this SQL script, create a new .txt file, and then paste the following text in the new file. After you create the file, rename it to a .sql file name extension.
BEGIN TRANSACTION T1DECLARE custom_cursor CURSOR FORSELECT VHDId, VDriveId fromdbo.tbl_WLC_VDrive WHERE [VHDId] NOT IN(SELECT VHDId from dbo.tbl_WLC_VHD WHERE VHDID IS NOT NULL)DECLARE @VHDId uniqueidentifierDECLARE @VDriveId uniqueidentifierOPEN custom_cursorFETCH NEXT FROM custom_cursor INTO @VHDId, @VDriveIdWHILE(@@fetch_status = 0)BEGINif(@VHDId is NOT NULL)DELETE FROM dbo.tbl_WLC_VDriveWHERE VDriveId = @VDriveIdFETCH NEXT FROM custom_cursor INTO @VHDId, @VDriveIdENDCLOSE custom_cursorDEALLOCATE custom_cursorCOMMIT TRANSACTION T1
To run the SQL Server script, follow these steps:
Start SQL Server Management Studio, and then connect to the server that is running the Virtual Machine Manager SQL database.
On the File menu, click Open, and then click File.
Browse to the location where you stored the SQL Server script file.
Select the .sql file, and then click Open .
On the Query menu, click Execute.
Close the SQL Server Management Studio window.
How to obtain the System Center Virtual Machine Manager 2008 update for physical to virtual conversion
The following files are available for download from the MicrosoftDownload Center:
You must have Virtual Machine Manager 2008 installed.
You do not have to restart the computer after you apply this update package.
Update replacement information
This update does not replace any other updates.
The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This issue is resolved in System Cetner Virtual Machine Manager 2008 R2.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates