Lab Center incorrectly stores or validates the CodedUIUserName in the LabEnvironment when distributing Test Agents to LabSystems. - by Grey Ham

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 749436 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 6/15/2012 11:47:06 PM
Access Restriction Public

Description

THE PROBLEM:
------------
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. 

NOTES: 
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. 



MACHINE SPECIFICATIONS:
-----------------------
"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 :-)
Sign in to post a comment.
Posted by Whiskey Jim G on 8/2/2013 at 8:47 AM
Does anyone know if this issue has been addressed in any recent releases?    If so which release do I need to fix it?

Thanks

Dave
Posted by Microsoft on 6/27/2012 at 11:08 PM
Hi Grey Ham,

Thank you for reporting this issue.

You are right that for workgroup environments, users should specify the interactive account in the format .\username. This is required because this account is common across all the machines of the workgroup environment.

Note: - This restriction is applicable only for workgroup environments and is not applicable for domain joined environments.

Also you will be glad to know that we have fixed this issue in our latest code by giving UI guidance and the fix should be available in one of the future release of Visual Studio.

Regards
Visual Studio Product Team

PS: - The repro steps and the details you gave on this bug were amazing. !! Thanks for that.
Posted by Microsoft on 6/18/2012 at 1:52 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 6/16/2012 at 12:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)