Registering Workgroup Test Agent with Test Controller in Domain 22 June 2012 Donovan-Brown Work (0) Problem: I have a test controller in a domain and a test agent in a workgroup and I can’t register the agent with the controller. Solution: Create shadow accounts on the agent machine and on the controller machine that are in the Administrators Group. Shadow accounts are accounts with the exact same name and password. You can test your shadow account by trying to map to a share on the controller machine from the agent machine. Try to access \\controlerMachine\c$ when you are challenged for credentials use the shadow account. Note you may have to disable your firewall to perform this test. Install and configure the controller on the controller machine. In the Configure Controller dialog use your TFS account and select the project collection. Using Microsoft Test Manager (MTM) under the Lab Center tab verify that your controller is registered on the controller tab. Second log in to the test agent machine as the shadow account and install and configure the test agent with the test controller. When asked for a user name use the shadow account again. Using MTM refresh the contoller and you should see the Test Agent listed. This machine is now ready to be used in Lab to create a physical environment.
One lab machine will not connect to test controller! 22 June 2011 Donovan-Brown Work (0) Problem I have a lab environment configured with 4 machines. It is running in Network Isolation, and has workflow and test capability enabled. The testing capability fails only on one machine. Solution Adjust the binding order of your network adapters so that external adapter is first. To do this bring up the Network Connections window and click on the Advanced menu. If the Advanced menu is not showing press the Alt key to display it. From the Advanced Menu selected Advanced Settings. The Advanced Setting dialog will open. Use this dialog to move the external network adapter to the top of the list. Explanation If you are getting a message like the one below: "The machine is not ready to run tests because of the following error: Unable to connect to the controller on '<TestControllerFQDN>:6901'. Reason: No such host is known. Make sure the test controller is online and the firewall on the test controller is not blocking the connection." The chances are if you try to ping the Test Controller machine from the lab machine it will fail. If the internal network adapter binds first it may cause issues when trying to resolve network names. Simply move the external network adapter to the first position.
I can't run VMM and I am an admin 15 June 2011 Donovan-Brown Work (0) Problem When I run VMM I am given the error I don't have permissions to run VMM on localhost. Solution You have to have a current VMM administrator to add you to the Administrator role in VMM under Administration tab. Start VMM Click the Administration tab Select User Roles Double Click Administrator under Profile Type Click the Members tab Click Add… and add the user