I am creating a Standard Environment within Lab Center VS2012 RC. I wish to push out a Test Agent to a fresh machine and have that Agent run tests interactively. After installing the Agent, Lab Center gives the following error:
TF259637: The test machine configuration does not match the configuration specified on the environment. The account under which the test agent process has been configured does not match the account under which the process is currently running. Click 'Repair' to fix the problem.
Repair does not work.
I have done some investigation and know how to fix it manually - I provide my findings and full repeatability in the DESCRIPTION.TXT file. Please pay particular attention to the Workgroup qualification for user names because this appears to be the underlying cause of the issue.
1. Pushing out an Agent to run as a Service works fine.
2. I have applied the registry fix set here: http://blogs.msdn.com/b/visualstudioalm/archive/2012/06/13/creating-team-foundation-server-2012-lab-management-standard-environments-and-getting-error-verify-that-the-machines-are-accessible-using-the-user-name-and-password-provided.aspx
3. The Agent installs correctly; the machine reboots correctly and logs on as the correct user; but MTM gives the above error. The issue appears to be solely the way that Lab Center populates the LabEnvironment.CodedUIUserName property that is set by the 'Standard Environment' wizard.
"DEV" machine - W7-2012-DEV
Windows 7, 64, UAC Enabled. VS2012 RC, MTM, TFS, Build Services, Test Controller installed. Running MTM as 'Graham' (administrative user) but not running elevated. Workgroup security (Workgroup == W7-2012-DEV). Test Controller is also running as Graham.
"AGENTS" machine - W732AGENTS
This is the machine I am pushing the Agent out to. Has no Agent installed; no .Net 4.5 stuff. Works fine if Agent does not have to run interactively.
Windows 7, 32, UAC Enabled. Logged in interactively as 'Graham'. 'Graham' is Administrative user. Workgroup = W732AGENTS. Password of 'Graham' the same as on W7-2012-DEV above.
--- PLEASE SEE DESCRIPTION.TXT (Attachment) for further information + findings. I ran out of space here :-)