Configuring Lab Environments that Contain Windows XP or Windows Server 2003 Machines
You can use lab environments that contain virtual and physical machines that run Windows XP or Windows Server 2003. However, those lab environments will have some issues during configuration that other lab environments don't have. These issues require you to perform additional steps when you configure and make changes to lab environments that contain Windows XP or Windows Server 2003 machines.
Note
Windows Server 2003 machines are only supported using Visual Studio 2012 Update 2.
The following table lists the issues that you might encounter when you configure lab environments that contain Windows XP machines:
Issue |
Solution |
|---|---|
Creating a lab environment: Creating a lab environment will fail if the environment contains Windows XP or Windows Server 2003 machines. |
See the section: Creating Lab Environments that Include Windows XP Machines |
Editing a lab environment Editing a lab environment will fail if the environment contains Windows XP or Windows Server 2003 machines. |
See the section: Reconfiguring Lab Environments that Include Windows XP Machines |
Repairing a lab environment: Repairing a lab environment will fail if the environment contains Windows XP or Windows 2003 Server machines. |
See the section: Reconfiguring Lab Environments that Include Windows XP Machines |
Configuring a lab environment to run as a service: If a lab environment contains Windows XP or Windows Server 2003 machines and is configured to run coded UI tests, reconfiguring the environment to run as a service will cause an error. |
See the section: Reconfiguring Lab Environments that Include Windows XP Machines |
Changing a test controller If a lab environment contains Windows XP or Windows Server 2003 machines, changing the test controller for the environment will cause an error. |
See the section: Reconfiguring Lab Environments that Include Windows XP Machines |
Changing the settings for a test controller If a lab environment contains Windows XP or Windows Server 2003 machines, changing the settings for the test controller in Microsoft Test Manager using the Test Controller Manager tab will cause an error. |
See the section: Reconfiguring Lab Environments that Include Windows XP Machines |
Creating a lab environment that uses Windows XP or Windows Server 2003 machines
To create a lab environment that contains Windows XP or Windows Server 2003 machines, follow these steps:
Create your lab environment:
Create your lab environment using Microsoft Test Manager. See Creating Lab Environments. When you finish creating the environment using the New Environment wizard, Lab Management will attempt to install test agents on your machines. However, Lab Management will fail to install test agents on your Windows XP or Windows Server 2003 machines and the Status of your lab environment will display Not Ready.
Manually install test agents on your Windows XP or Windows Server 2003 machines:
Manually install a test agent on each Windows XP or Windows Server 2003 machine in your environment. See the section: Manually Installing Test Agents in Lab Environments.
Verify your test agents:
Open your lab environment in Microsoft Test Manager.
Open Microsoft Test Manager
Choose Lab Center from the drop-down menu.
Choose the Lab tab.
Highlight your lab environment in the Environments list, and then choose the Open on the toolbar.
Choose the Verify button. A set of verifications will run.
Choose the Finish button.
Lab Management will attempt to reinstall test agents on the machines in your lab environment, and will display an error or warning. However, if the procedure is successful, the Status of the environment will change to Ready and you can use the environment.
Reconfiguring a lab environment that uses Windows XP or Windows Server 2003 machines
This section describes how to reconfigure an existing lab environment that contains Windows XP or Windows Server 2003 machines. You must complete these steps in the following scenarios:
Repairing your environment.
Editing your environment.
Changing the test controller that is used in your environment.
Reconfiguring the test controller that is used in your environment.
Reconfiguring an environment to run test agents as a service after they have been configured to run coded UI tests.
Reconfigure your test controller:
Optional: If you need to reconfigure your test controller, reconfigure the test controller before you complete the steps below. For information about configuring a test controller in a lab environment, see Setting Up Test Controllers in Lab Environments.
Manually uninstall the test agents on your Windows XP or Windows Server 2003 machines:
Log on to the Windows XP machine.
In Control Panel, open Add/Remove Programs.
If Microsoft Visual Studio Agents is on the list of programs, uninstall it. Otherwise, continue to the next step.
Manually install test agents on your Windows XP or Windows Server 2003 machines:
Manually install a test agent on each Windows XP or Windows Server 2003 machine in your environment. See the section: Manually Installing Test Agents in Lab Environments.
Verify your test agents:
Open your lab environment in Microsoft Test Manager.
Open Microsoft Test Manager
Choose Lab Center from the drop-down menu.
Choose the Lab tab.
Highlight your lab environment in the Environments list, and then choose the Open on the toolbar.
Reconfigure the settings for the test controller and UI tests
Optional: If you need to change the test controller, or the settings for running coded UI tests, choose the Advanced tab, and then reconfigure those settings.
Choose the Verify button. A set of verifications will run.
Choose the Finish button.
Lab Management will attempt to reinstall test agents on the machines in your lab environment, and will display an error or warning. However, if the procedure is successful, the Status of the environment will change to Ready and you can use the environment.
Manually installing test agents in lab environments
This section describes how to install a test agent on a machine that is part of a lab environment using the Visual Studio 2012 Agents installation software instead of Microsoft Test Manager. You must perform this step on every Windows XP or Windows Server 2003 machine in your lab environment.
Required permissions
To install a test agent, you must be a member of the Administrators security group on the computer. When you register a test agent with a test controller, you must also be a member of the Administrators security group on the test controller machine.
To manually install a test agent
Load the "Visual Studio Agents" CD or a downloaded ISO image and then launch setup.exe, which is located in the root folder.
The Visual Studio Test Agent installation wizard appears. Follow the steps in the wizard.
When the wizard finishes the installation, choose Configure test agent now.
Note
You can run this tool to reconfigure your test agent at any time. Choose All Programs, Microsoft Visual Studio, Microsoft Visual Studio Test Agent Configuration Tool.
Choose Run Options and then choose one of the following options. These options will determine how your test agent is run:
Service: If you do not have to run automated tests that interact with the desktop, such as coded UI tests or creating a video recording when your test runs, under Run the test agent as, choose Service and then choose Next.
- Under Run test agent as a service, in the User name and Password fields, specify the logon credentials that you used to create your lab environment. In the Lab Center of Microsoft Test Manager, these are the credentials that were used in the Machines tab of New Environment wizard.
Interactive Process: If you want to run automated tests that interact with the desktop, such as coded UI tests or creating a video recording when your test runs, choose Interactive Process and then choose Next. For information about how to run a test agent as a process, see How to: Set Up Your Test Agent to Run Tests that Interact with the Desktop.
Under Run test agent as an interactive process, in the User name and Password fields, specify the logon credentials that you used to create your lab environment. In the Lab Center of Microsoft Test Manager, these are the credentials that were used in the Machines tab of New Environment wizard.
If you configure the test agent to run as an interactive process with a different user account than the one that was used to log on to the machine, you must restart the machine and log on with account that you entered in the Test Agent Configuration Tool. This must be done so the test agent service can start.
To make sure that a computer that has a test agent can run tests after it reboots, you can set up the computer to log on automatically as the test agent. Choose Log on automatically. This will store the user name and password in an encrypted form in the registry.
To make sure that the screen saver is disabled because this might interfere with any automated tests that must interact with the desktop, choose Ensure screen saver is disabled.
Warning
There are security risks if you log on automatically or disable the screen saver. By enabling automatic log on, you enable other users to start this computer and to be able to use the account that automatically logs on. If you disable the screen saver, the computer might not prompt for a user to log on to unlock the computer. This lets anyone access the computer if they have physical access to it. If you enable these features on a computer, you should make sure that these computers are physically secure. For example, these computers are located in a physically secure lab. (If you clear Ensure screen saver is disabled, this does not enable your screen saver.)
Choose Register with test controller. Type the name of your test controller followed by a colon (:) and the port number that you are using in Register the test agent with the following test controller. For example, type agent1:6901.
Note
The default port number is 6901.
To apply your changes, choose Apply Settings.
A Configuration summary dialog box is displayed. It shows the status of each step that is required to configure your test agent.
Note
The last step in the installation process resets the network adapter. This might cause a network outage for brief period of time. This is expected behavior.
To close the Configuration summary dialog box, choose Close. Then choose Close again to close the Test Agent Configuration Tool.