I like your distinction between Projects and Maintenance. What I understand is that after a Project is completed, you move the source to the Mainteance folder. So a project is closed down in that it produced a release, but the source code is moved to “Maintenance Mode” is that correct?

One question I have is what if you have another Project that produces another major release of the same product. Does your model have you doing maintenance on multiple versions, or just one?

Also, if you had your way, would you have a team project for each of the products in “maintenance” mode, as long as you were able to enforce process across all of them, and report across all of them easily? It would seem that would be helpful for things like builds, websites, bugs.

I’ll try the following tomorrow to make sure we have a fallback scenario untill december…

Question: How do I add a user to a TFS Group from the command line?

Answer: Use the tfssecurity.exe command line tool

Eg:
add a domain user to the Project Administrators Group:
tfssecurity /server:servername /g+ “[Project Name]\Project Administrators” n:Domain\username

add a domain user to the Server level “Team Foundation Administrators” Group:
tfssecurity /server:servername /g+ “[server]\Team Foundation Administrators” n:Domain\username

remove a domain user from the Server level “Team Foundation Administrators” Group:
tfssecurity /server:servername /g- “[server]\Team Foundation Administrators” n:Domain\username

as found on
http://dotnet.org.za/ahmeds/archive/2007/08/08/tfs-q-amp-a-changing-service-accounts-and-adding-users-from-the-command-line.aspx

Cause if it truly is the team explorer this should work, I hope…