Environments and TFS, Test controller in different domains?

Locked Environments and TFS, Test controller in different domains?

  • Wednesday, May 30, 2012 8:38 PM
     
     

    We would like to have Virtaul machines (environments) in domain1 and TFS, Test controler in domain2, Is this possible?

    we were able to get Test agent running fine on VMs but not build agent, when installing buildagent it is asking for local user who has permission with TFS!!!

    so we couldnt able to get Workflow capability ready. is there any we can have VMs in different domain other than then TFS. 

    I am not clear about network isolation, is that something will help with this need?

    Thanks

    Srini


    srini

All Replies

  • Friday, June 01, 2012 5:37 AM
    Moderator
     
     Answered

    Hello Srini,

    Quoted from this blog:

    You cannot have Test network completely isolated from Corp network. If you have such a topology then the test agent or the build agent will not be able to talk to TFS or the Test/Build Controller which are in Corp domain. Hence you will not be able to leverage the testing and workflow capabilities in such a topology. You can however be able to operate on the Lab environment and do the basic Lab environment operations on it.

    For network-isolated environments, Visual Studio Lab Management automatically configures the test agents in the network-isolated environment with the test controller using the lab service account. For more information about network-isolated environments, see How to: Create and Use a Network Isolated Environment.

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us