Troubleshooting Virtual Machines and Templates
[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
This topic describes some common problems you might encounter when you are working with virtual machines and templates and provides troubleshooting steps.
You attempt to import a virtual machine or a template, but you cannot find any virtual machines or templates available for import when you click Browse in the wizard. Alternatively, you cannot find the specific virtual machine or template you are looking for.
One of the following situations could cause this:
The system administrator has not created any virtual machines or templates for you to import.
The system administrator has not copied the virtual machines or templates to the library share that has been assigned to your team project.
The system administrator has copied the files to the correct library share, but System Center Virtual Machine Manager (VMM) did not refresh the library share.
The state of the virtual machine or the template in VMM is not ‘Stored’.
When you import a template from Virtual Machine Manager, one or more of the OS profile parameters are lost and you have to re-enter them.
When system administrators create templates in VMM, they can specify OS profile properties. When the template is imported into a team project, all these values are retained except for:
Administrator password
Product key
Domain credentials.
These values are emptied out and have to be re-entered after the template is imported. This is a limitation of the current version of the product.
You see an error associated with a template in Microsoft Test and Lab Manager similar to "Error in virtual machine. TF260042: Team Foundation Server could not find the hardware profile: …".
Lab Management internally creates and uses hardware and OS profile objects in VMM each time a template is imported. If a system administrator unintentionally deletes these profiles from VMM, you will see this error. When this occurs, use Microsoft Test and Lab Manager to edit the virtual machine template and re-enter the necessary information such as the hardware profile in the previous example.
The system administrator edits the memory, product key, or another property of a virtual machine or a template in VMM. The changes are not reflected in what you see in Microsoft Test and Lab Manager.
Changes made to virtual machines and templates in VMM after they are imported are not reflected in Lab Management. To allow the same virtual machine or template to be imported multiple times into different team projects, and to allow each of them to be individually edited without changing the underlying object in VMM, Lab Management creates and uses additional hardware and OS profile objects. Changes you make in VMM are not automatically updated in Lab Management, and you must make those same changes again in Microsoft Test and Lab Manager.