If you are upgrading your VSTS 2008 server to VSTS 2010 Beta1, you will need to enable Lab Management for existing projects.

Note: Starting Beta2 there is no need for these steps and they are part of the standard TFS upgrade.

So, first upgrade your TFS server. Then you can configure Lab Management using TFS administration console and start using these features for new projects. To enable Lab Management features on existing team projects use the following steps.

Pre-Conditions

· Install SCVMM server and add lab hosts to host groups. For more details see scenario “Installing Lab Management” in Team Foundation Installation guide for Visual Studio Team System 2010.

· Install SCMM admin console on TFS application tier machine. For more details see scenario “Installing Lab Management” in Team Foundation Installation guide for Visual Studio Team System 2010.

· Enable Test Case Management for the project. See Hakan’s blog for a sample script to easily enable Test Case Management features on an existing project.

Step 1 - Configure Lab Management

You can configure Lab Management by using the administration console for Team Foundation.

· Click Start, point to All Programs, and then click Microsoft Team Foundation Server 2010 Beta1.

· Click Team Foundation Administration Console.

· In the tree, click Lab Management under Application Tier.

· On the Lab Management pane, click Configure Lab Management.

· In SCVMM server name, type the fully qualified name of the server that is running Virtual Machine Manager and that you will use to manage the virtual machines.

· Click Test to determine whether Visual Studio Team System Team Foundation Server can communicate with the VMM server. If Team Foundation Server cannot contact the VMM server, a red x and an error message will appear.

· In Network location, type the address of the network to which the virtual machines will connect. If you do not know the name of the network location for each host that you want to include, open the Virtual Machine Manager Administrator Console, view the Hardware properties of each host, and identify the network location for each network adapter.

· Now if you want to use Network Isolation (You can use network isolation to enable multiple copies of a lab environment to run at the same time without causing network conflicts, such as conflicts in computer names and Domain Name System (DNS) registration.) select Network Isolation tab and click “Configure Network Isolation”.

· In DNS suffix, type the suffix of the domain name to be assigned to the environment when an isolated network is created. Each virtual machine in a network-isolated environment is registered with a unique external name and DNS suffix that you specify. You should use a suffix that is configured to support non-secure updates in your DNS server. To confirm that the suffix is correctly configured in the DNS hierarchy, contact your network administrator.

· Click Test to determine whether Visual Studio Team System Team Foundation Server can use the suffix. If the suffix is valid, a green check mark appears. Click OK. If the suffix is not valid, a red x and an error message appear. You must fix the error before you can continue. Click OK.

Step 2 - Configure Lab Management for the Project Collection hosting upgraded projects

· Click Start, point to All Programs, and then click Microsoft Team Foundation Server 2010 Beta1.

· Click Team Foundation Administration Console.

· In the tree pane, click the Team Project Collections node under Application Tier.

· Select the project collection hosting upgraded projects.

· Click on Lab Management tab for the selected project collection.

· In the results pane, click Configure Library Shares.

· Click Add, select one or more VMM library shares that this team project collection will use, and then click Add. You can add a library share to only one team project collection at a time.

· Now to configure Host Groups for this collection, select Host Groups tab.

· Click Add, select one or more host groups that this team project collection will use, and then click Add.

· Click Verify to verify the status of selected host groups.

· Now if you want to use Network Isolation select Network Isolation tab. This option will be available only if you have configured network isolation at application tier in step 1.

· In DNS suffix, type the suffix of the domain name to be assigned to the environment when an isolated network is created. To confirm that the suffix is correctly configured in the DNS hierarchy, contact your network administrator.

· Click Test to determine whether Visual Studio Team System Team Foundation Server can use the suffix. If the suffix is valid, a green check mark appears. Click OK. If the suffix is not valid, a red x and an error message appear. You must fix the error before you can continue. Click OK.

Step 3 - Configure Lab Management for upgraded Team Project(s)

Download the zip file attached to this post, and extract it to a local directory such as C:\Upgrade.

Before you run the script, open “EnableLabManagemet.bat” in a text editor and complete the configuration by specifying values for the following:

  • Team Foundation Server URL
  • Name of the team project collection
  • Name of the team project
  • Path to TFSLabConfig.exe utility
  • Set ConfigComplete = 1 to indicate that you’ve completed this step

This script will perform following 3 steps to enable Lab Management

· Grant default Lab Management permissions to standard security groups e.g. Readers, Contributors, Project Administrators and Project Collection Administrators.

· Create Project Host Groups

· Create Project Library Shares

Rerun the batch file for each existing project, after updating  project name in the batch file.