How to: Create an Environment from Virtual Machines or Templates
You can create virtual environments from stored virtual machines, templates, or stored environments. A virtual environment is a collection of virtual machines or templates that is controlled by Visual Studio Lab Management. This topic describes how to create virtual environments from stored virtual machines and templates.
You create deployed environments on the host groups in your team project lab. A deployed environment contains only virtual machines and can be running or stopped. When an environment is created on a team project host group, the virtual machines of the environment are hosted on one or more Hyper-V hosts. When the environment is started, the corresponding virtual machines are started and you can interact with those virtual machines.
Note
You can also compose an environment from virtual machines that were created outside of Lab Management and are located on a Hyper-V host. For more information, see How to: Compose an Environment from Deployed Virtual Machines.
You create stored environments in your team project library. A stored environment is used to create new virtual environments. A stored environment can contain virtual machines or templates. When an environment is created on a team project library share, the virtual machines or templates of the environment are stored on the disk of the SCVMM library server. A stored environment is a passive set of files. Until the environment is deployed onto a team project host group, you cannot do anything more with it. For information about how to create deployed environments from stored environments, see How to: Deploy a Stored Environment.
You create environments from the following sources in the team project library:
One or more templates.
One or more stored virtual machines
A combination of stored virtual machines and templates
Usually, a best practice is to only stored virtual machines or only templates in your library. For more information, see the Guidelines For Stored Virtual Machines and Templates section of Virtual Environments Concepts and Guidelines.
Creating an Environment From Templates or Stored Virtual Machines
Creating an environment from templates or stored virtual machines involves three steps.
If it is necessary, add and configure virtual machines and templates to use in the environment to the project library.
Create the environment and then add and configure the templates or virtual machines.
If you are creating a deployed environment from stored virtual machines that does not use network isolation or if you are creating a deployed environment that uses network isolation and a private domain, you need to perform additional configuration after the environment is deployed.
For information about how to configure an environment that was created by using stored virtual machines, see Creating Deployed Environments That Do Not Use Network Isolation From Stored Virtual Machines.
For information about how to configure an environment that uses network isolation, see How to: Create and Use a Network Isolated Environment.
To add and configure virtual machines and templates in the project library
Open Microsoft Test Manager.
To display the Microsoft Test Manager window, click Start, and then click All Programs. Point to Microsoft Visual Studio 2010 and then click Microsoft Test Manager.
Click Lab Center.
Click the Library tab, and then click Virtual Machines and Templates.
Add the virtual machines and templates for the environment to the Library.
For information about how to add templates from SCVMM, see How to: Import a Virtual Machine or a Template from SCVMM.
For information about how to create stored virtual machines and templates from virtual machines in deployed environments, see How to: Create a Virtual Machine or Template from an Environment.
If it is necessary, set the properties of the templates. For more information, see How to: Set the Properties of a Virtual Machine or Template. You can also set the properties as you add the stored virtual machines or templates to the environment.
To create an environment from virtual machines or templates |
|
At the start of the creation process, Lab Management performs a series of validations. This includes verifying that there is enough capacity on hosts to create the environment when an active environment is being created.
If any of the validations fail, you will be presented with information about the failures. At that point, you can correct the information in the wizard, and try the creation operation again by clicking Create.
If the validations succeed, the creation process is automatically initiated. During the creation process, a progress bar is displayed to indicate the progress of creation. You can also view the current creation step displayed under each virtual machine.
Creating Deployed Environments That Do Not Use Network Isolation From Stored Virtual Machines
To avoid network name conflicts, a best practice is to create stored virtual machines as workgroup machines. If you create a deployed environment that does not use network isolation, you should follow these steps to change the computer names of the machines and join them to the domain.
In the Lab tab of Test Manager, select the environment and then click Start.
After the environment has started, click Connect.
In Environment Viewer, follow these steps for each virtual machine that was created from a stored virtual machine:
Select the machine and then click Connect.
Log on to the machine using an account that has administrator privileges on the machine.
Open the System Properties dialog box.
Click Start, click Computer, and then click System properties. On some versions of Windows, you must then click Change Settings in the System explorer window.
On the Computer Name tab of the System Properties dialog box, click Change.
Enter a name that is unique to the network in the Computer name box.
Click Domain and enter the fully qualified name of the domain. You will be prompted for the name and password of an account that is allowed to join computers to the domain.
See Also
Concepts
Change History
Date |
History |
Reason |
---|---|---|
March 2011 |
Added an instruction to avoid using commas in the name of the environment. |
Customer feedback. |