locked
Is there a way to restrict who can access specific Lab Environments, when running automated tests from MTM? RRS feed

  • Question

  • Is there a way to restrict who can access specific Lab Environments, when running automated tests from MTM?

    For example, let’s say I have 3 environments A, B, and C, each with one machine. And let say that I don’t want anyone else but me to be able to run automation from MTM on environment C.

    Is it possible to configure this at some level so that if I open MTM from my main developer machine, and go to specify an environment to run my automated test on, I see Environments A, B, and C. however if Sally opens MTM and attempts to specify an environment, she can only see Environments A and B?

    Thursday, August 23, 2012 8:45 PM

Answers

  • Hi JETFIRE,

    If Environments A, B and C are grouped in different team projects, you can previent Sally from accessing environment C by denying the View Lab Resources permission on that team project. You can achieve that by using the TfsLabConfig Permissions command: TfsLabConfig Permissions /collection:http://TfsServerName:8080/tfs/collectionName /user:domain\userName /deny:Read

    For further information about Permissions for Lab Management, see: http://msdn.microsoft.com/en-us/library/dd380760.aspx

    However, if environments A, B and C are in the same team project, I am afraid there is no approach for you to prevent Sally from accessing C. But you can prevent other users from accidentally connecting to your environment when you run your tests by choosing the drop-down arrow next to Mark 'In Use' in the toolbar. Add a comment about who is using the environment and choose Mark 'In Use'. If another user tries to connect to the environment that is being used, a warning with the comments that you entered is displayed in the Connect to Environment dialog box.

    Thanks.


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

    Monday, August 27, 2012 3:40 AM
    Moderator

All replies

  • Hi JETFIRE,

    If Environments A, B and C are grouped in different team projects, you can previent Sally from accessing environment C by denying the View Lab Resources permission on that team project. You can achieve that by using the TfsLabConfig Permissions command: TfsLabConfig Permissions /collection:http://TfsServerName:8080/tfs/collectionName /user:domain\userName /deny:Read

    For further information about Permissions for Lab Management, see: http://msdn.microsoft.com/en-us/library/dd380760.aspx

    However, if environments A, B and C are in the same team project, I am afraid there is no approach for you to prevent Sally from accessing C. But you can prevent other users from accidentally connecting to your environment when you run your tests by choosing the drop-down arrow next to Mark 'In Use' in the toolbar. Add a comment about who is using the environment and choose Mark 'In Use'. If another user tries to connect to the environment that is being used, a warning with the comments that you entered is displayed in the Connect to Environment dialog box.

    Thanks.


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

    Monday, August 27, 2012 3:40 AM
    Moderator
  • Thanks you Vicky,

    you mentioned a "drop-down arrow next to Mark 'In Use' in the toolbar".

    Where exactly is this located, I’m using MTM 2010?

    From “Lab Center”, under “Environments”, I have one environment created (It’s a physical environment) with 2 Web Client machines. If I do a right click on my environment (in my case its name is “WinXP & IE8 Pool”), I receive a drop down menu which shows the options “Mark in use” and “Unmark in use”, however they’re both disabled. Is this what you were referring to above, and if so do you know why they’re disabled?

    Friday, October 12, 2012 9:45 PM