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

Summary
This post addresses a specific issue where creating fence environments using Team Foundation Server 2013 Preview Lab Management can result in the Lab Environment being in a "Not Ready" state. The cause is identified as the test agent firewall exception for TCP port 6910 not being correctly applied to the public profile when the guest OS is Windows 2012 R2 Preview. A workaround is provided: installing agents for the Lab Environment once. This post also references a known bug in Lab Management 2013 Preview.
More from the Team Foundation Server Backup and Restore Planning trail
- Monitoring Team Foundation Server 2018
- How to perform Lab management operations in Build and Release.
- Test Controller, Test Agent versions and their usage in different scenarios
- Breaking change in TFS 2015 Update 1 for server-side plugins
- New Environment Verification fails Saying invalid 'Domain User Name' using Microsoft Test Manager