TechNet
Expand All
This documentation is archived and is not being maintained.

Virtual Machine Manager Known Issues

This article documents known issues with System Center Virtual Machine Manager (VMM) 2007.

Known Issues

  • AMD Athlon hosts may display incorrect CPU name
  • Two properties on the administration console are displayed as UTC instead of local time
  • Failure to create a template from a virtual machine may leave it in an unusable state.
  • Creating a new VM and storing it in the library using a non-FQDN path is not supported on the command line
  • VMM Service restarts after the VMM server is added as a host with remote SQL server
  • Adding/moving disks on a shared scsi adapter may crash the UI
  • Localization issues

AMD Athlon hosts may display incorrect CPU name

For both 64-bit and 32-bit host computers running Microsoft Windows Server 2003 SP1, the CPU may display incorrectly as "Pentium" instead of "Athlon." This issue can be corrected by installing Windows Server 2003 SP2.

Two properties on the Administrator Console are displayed as UTC instead of local time

The Date modified displayed on the summary pane of managed computers, and the Modified property displayed on the Summary tab of host properties are shown in Coordinated Universal Time (UTC) instead of local time.

Failure to create a template from a virtual machine may leave it in an unusable state

If you create a template from a virtual machine in a domain with Group Policy that prohibits blank passwords, the template creation will fail. The template status will read "Customization failed," and the virtual machine will be left in an unusable state. You must delete the virtual machine before you can try to create the template again. To prevent having to do this, it is a best practice to always clone the virtual machine first, then remove the clone from the domain to stop Group Policy from being applied. Create the template from the clone and then delete the clone. If the process fails, you can delete the clone and try the best practice steps again.

Creating a new VM and storing it in the library using a non-FQDN path is not supported on the command line

Creating a new virtual machine and storing it in the library by using the new VM cmdlet and a library share path other than a fully qualified domain name (FQDN) is not supported on the command line. No error message appears, however, the virtual machine is marked with the state of "incomplete configuration" and the VHD displays in the library as a standalone VHD.

VMM Service restarts after the VMM server is added as a host with remote SQL server

You can use the Add hosts action in the Administrator Console to add the VMM server as a host. However, if you installed the VMM server database on a remote computer running SQL Server, adding the VMM server as a host will cause the VMM services to stop working temporarily because of a network stack reset.

Adding/moving disks on a shared scsi adapter may crash the UI

Because of an issue in Virtual Server, if you add a VHD to a shared scsi adapter, move a VHD that is on a shared scsi adapter, or change a scsi adapter that has multiple VHDs into a shared scsi adapter, the Administrator Console may crash. The only workaround is to remove the VM and recreate it.

Localization issues

For some languages, X64 versions may display unexpected fonts, for example, fonts may appear smaller than usual.

For some languages, hot key settings might be duplicated.

For some languages, some help links and text in wizards may be partially obscured.

'Administrator Console' and 'Self-service portal' are not localized in Add/Remove Programs.

Documentation issues and errata

Throughout Virtual Machine Manager documentation, reference is made to "WinRM". All references are to the WS-Management v1.1 available at , which delivers WS-Management functionality on Windows XP SP2, Windows Server 2003 SP1, Windows Server 2003 SP2, Windows 2003 Server R2. In the past, this functionality has been called both Ws-Man and WinRM. Knowledge Base articles refer to this functionality as WinRM, and the command-line tool is called winrm.cmd.

In Self-Service Portal Help, the second instance of "Additional Resource" should be “Using VMRC client to access virtual machines" (http://go.microsoft.com/fwlink/?LinkId=69963)

There is a typographical error in the Virtual Machine Manager Help topic "About Physical-to-Virtual Conversions". The unsupported boot options should read as follows: "Virtual Machine Manager P2V does not support /HAL or /KERNEL boot options."

The Virtual Machine Manager Help topic "How to Modify VMRC Settings on a Host" incorrectly states the default key length for a VMRC encryption certificate as 256 bits. The correct default key length is 512 bits.

The Virtual Machine Manager Help topic "How to Modify VMRC Settings on a Host" incorrectly states the maximum time interval for VMRC host setting as 600. You can enter a timeout limit of up to 1440 minutes.

The Virtual Machine Manager Help topics "Troubleshooting Host Statuses" and "How to Troubleshoot Host Status" incorrectly states overall host status as being either OK or Needs Attention. These statuses display in the Administrator Console as "Responding" or "Not Responding."

Additional Resources

Show:
© 2016 Microsoft