Austin Agile DevOps

Set Lab Management (LM) Permissions for Team Projects Created before LM was Configured

What a long title! Anyway, I didn't add LM until sometime after I had setup my Team Foundation Server 2010 instance. There are 2 important realities to face when you do this:

1. The LM permissions in the process template are not applied because LM was configured when the team project was created
2. There's no UI to set LM permissions (arrrgh)

All you have are the permissions established by the accounts used to setup LM (i.e. TfsSetup, etc...).

Here are the commands I developed to grant permissions to existing team projects after you enable LM for them.

Lookup TfsLabConfig in the MSDN library to get command line details.

Grant permissions for a team project group to have environment read, start, pause and stop permissions:

1. Grant read access for all lab management objects in the collection to all team project members:

TfsLabConfig permissions /collection:{your collection url}  

/group:"[{team project namel}]\Team Members" /allow:Read    

2. Grant start, pause and stop permissions to project administrators, team leaders and contributors

TfsLabConfig permissions /collection:{your collection url}  

/group:"[{team project namel}]\{project group name}" /allow:Start,Pause,Stop     
 
TfsLabConfig permissions /collection:{your collection url}  

/group:"[{collection name}]\{collection group name}" /allow:Start,Pause,Stop      

NOTE: you can display permissions simply by omitting the /allow parameter

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/cvq

Print | posted on Friday, October 7, 2011 2:38 PM | Filed Under [ Agile SCM Talk Blog ]