Updated 7/16/2012: Please note this an archived post and the Lab Management VHD has been retired and been removed from the Microsoft Downloads site.
Visual Studio Lab Management 2010 enables teams to accelerate setup/tear down and restoration of complex virtual environments to a known state for test execution and build automation. It extends build automation by automating virtual machine provisioning, build deployment and build verification in an integrated manner. It also allows testers to file rich bugs with links to environment snapshots that developers can use to recreate complex environments; effectively reducing wasted time and resources in your development and test lifecycle. A few months back, we had released a similar VHD with Visual Studio RC bits; but the new version has the following distinctions
To enable quick evaluation of the Lab Management 2010 pre-RTM, we have created a Windows Server 2008 R2 Hyper-V based Virtual Machine (VM) that provides an all-in-one setup with pre-configured System Centre Virtual Machine Manager, Visual Studio, Team Foundation Server with Lab Management enabled. You can download this pre-configured VM from here.
This document consists of the following sections:
In order to use the Lab Management features, a physical Hyper-V host is required. The Hyper-V host is used to run both the downloaded VM (LabServer) and the virtual environments.
Physical Hyper-V Host
Hyper-V Host for hosting Virtual Machines listed below
LabServer (the VM you downloaded)
Machine name: labserver.labdomain.local
TailSpin VM Template
A Windows Server 2008 R2 based Stored Virtual Machine template
Application and Database tier for TailSpin Application
Shown below is the diagram once the LabServer VM and the Hyper-V host are configured.
Setup a clean install of Windows Server 2008 R2 on a Hyper-V capable machine with
In case you are not able to complete the Setup and Scenarios section within 10 days, you must first activate this VM to continue using for 180 days (trial period). Refer to Activation section for more details.
This completes the Lab setup and configuration. The subsequent sections help you to exercise various Lab Management scenarios.
Once you have configured the LabServer VM and the host as above, you can perform the following scenarios. These exercises are designed to enable a quick introduction to deploying a Virtual Environment, running an build-deploy-test workflow and creating a rich bug with environment snapshot.
For these scenario walkthroughs, we are using a sample web application called TailSpin, which is an online storefront for buying Airplanes. The company has decided to adopt virtualization to consolidate its hardware footprint and increase its utilization. The company decides to adopt Visual Studio 2010 Lab Management as it offers an out of the box integrated solution to leverage all the benefits of virtualization for application lifecycle management (ALM). Using Lab Management, the company is able to accelerate their software release cycle and also improve the overall quality as
Following artifacts have already been created to carry out the scenario walkthroughs
(Estimated Time: 30 minutes)
In this exercise, the Test Lead uses Microsoft Test Manager to deploy a virtual environment that will be later used for nightly build verification.
Visual Studio 2010 enables you to automate your whole build-deploy-test cycle using Lab Management, build and testing tools. This helps you to address some of the following key pain points with build-deploy-test cycles
As part of this walkthrough you will experience how Visual Studio 2010 helps you to overcome the above challenges by running an end to end Workflow that builds the application, deploys the application on the Clean state of virtual environment and runs Coded UI Tests.
Visual Studio 2010 enables testers to file rich bugs that help developer to debug the issue without wasting time in bug ping pong between developer/tester (e.g. developer claiming that a bug does not reproduce on his/her machine and wants more details e.g. system info, event logs etc.)
As part of this walkthrough you will experience how Visual Studio 2010 enables filing of rich bugs with automatic collections with each bug. Also with a bug you can create a Snapshot of the whole environment which can be used by developer to debug the issue. With Snapshot developer gets the whole environment in exactly the same state where the bug was filed.
As a tester you have a created a rich bug. Now let’s see how developer can easily reach the state of the environment where the bug was filed.
The evaluation period for this virtual machine image is 180 days; once the evaluation period terminates, the image should be discarded. NO EFFORT SHOULD BE MADE TO ACTIVATE THIS IMAGE after that date. Please read the following to get an idea of the risks and key things you need to know.
Guidelines on usage:
For complete use-rights, please refer to the EULA contained within this evaluation package.
You can follow the same approach for activating the VM’s which are part of virtual environment (disabling DHCP is not required). Connect to the environment and Click System Info in the environment viewer. Note down the “SCVMM VM Name” and shutdown the environment. Using Hyper-V Manager, temporarily add an external network adapter for this virtual machine. Follow the steps similar to 7-12 mentioned in the above section to activate the image, and later remove the external adapter.
(Estimated Time: 60 minutes)
A typical application requires multiple machines to test it. E.g. a Web application has a Web Server, a Database server and a web client. Since more than one machine is likely to be used in the production, testing in similar distributed environment is very important. Using Lab Management, you can create complex environments to test multi-tier application and assign a Role (Web Server, Database Server etc.) to each machine in the environment.
In this scenario, we will be deploying on a two machine environment for testing the TailSpin application. One of the machine will act as a Web Client and the second machine hosts both the Database Server (SQL) and the Web Server (IIS).
(Estimated Time: 90 minutes)
Network Isolation enables you to run multiple copies of the environment in parallel without machine name or IP conflicts. The machines in a network-isolated environment are protected from network conflicts by using two network adapters. One network adapter is used for a private network inside the environment. The second adapter is configured by Lab Management to present a separate, unique identity to the external network.
In this scenario, we will first deploy a Network Isolated TailSpin Environment (the VM inside the environment will be a workgroup machine). Next we run a build-deploy-test workflow to deploy the TailSpin application. Then we store a copy of this environment in the library, and later create a new environment using this stored copy. Hence we will be able to run two environments with TailSpin application, where the machines have the same machine name etc.
The following table lists the details of all the artifacts in the VM
VM Machine Name
Service account for test/build agent-controller communication
Default SCVMM Library Share
MSSCVMMLibrary, “C:\ProgramData\Virtual Machine Manager Library Files”
Default Host Group
Template with agents installed
Stored environment in library
TailSpin Source code
Sample Test Plan
TailSpin Test Plan