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”

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”

Rate This
  • Comments 4

Getting ready for Code Camp Seattle i  decided to do a demo of Build-Deploy-Test using a non domain joined Windows 8  Release Preview machine as my lab management/hyper V Server creating a Windows 7 Standard Environment as my test environment.

Unfortunately everything I did kept getting the error below in the verification step…

“Verify that the machines are accessible using the user name and password provided”

image

Turns out you MUST turn off something called “Remote User Access Control” in the Standard Environment machine if you are using a non domain joined computer….if you look closely the the error does give you a hint that this could be the problem –but with no visual UI in Windows to toggle this setting (it doesn’t even have a registry key!) let me tell you it was a non trivial task to find the answer!!!!

 

To disable UAC remote restrictions, follow these steps:

  1. Click Start, click Run, type regedit, and then press ENTER.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type LocalAccountTokenFilterPolicy, and then press ENTER.
  4. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
  5. In the Value data box, type 1, and then click OK.
  6. Exit Registry Editor.

For more information on User Account Control and remote restrictions in Windows Vista see:

http://support.microsoft.com/kb/951016 

 

image

Leave a Comment
  • Please add 1 and 2 and type the answer here:
  • Post
  • Thanks Charles, I just has this problem, it's really helpful :-)

  • Ahh, That did it! I thought I had to turn off UAC

  • Thank you!

  • I had a similar problem on Windows 8.1...tried everything (firewall, security)...and ended up rebooting the test agent, then running MTM as an administrator on the test agent and setting up the lab environment from the agent itself and it worked! Hopes this could help someone.

Page 1 of 1 (4 items)