July 22nd, 2013

Creating Fence Environments using Team Foundation Server 2013 Preview Lab Management can put Lab Environment in “Not Ready” state

Anisha Pindoria
Anisha Pindoria
Senior Program Manager

This issue can occur if the guest OS is Windows 2012 R2 Preview.

 

Workaround:

Install Agents for the Lab Environment once. It should fix the problem. 

Cause:

When the test agent is installed and configured, by default it enables firewall exception for tcp port 6910 in private
and current profiles. If the guest OS is Windows 2012 R2 Preview the firewall exception is enabled for private,
domain profiles, but the current profile is public. This results in test controller not able to reach to test agent ends
up in putting Lab Environment in “Not Ready” state..

 

This is a known bug on Lab Management 2013 Preview.

 

Category
Azure & Cloud

Author

Anisha Pindoria
Anisha Pindoria
Senior Program Manager

Anisha is on the Azure DevOps Community team, where she promotes engagement with leading technical community experts and groups to support awareness for Azure DevOps and accelerate the adoption via offline (meetups, conferences and workshops) and online (forums like Stack Overflow, MVP Program, and product group interactions).

0 comments

Discussion are closed.

Read next