You do not need to install it on the server. After associating your Gemini check in policy you should commit TFS source control so that other colleagues can see it.

Simran, My issue is that I don't have Gemini Check-in Policy as an option in the checkin policies.

OK, I got this working. I had installed the wrong plugin for this. I had installed the Gemini Project Management Plugin. Once I installed the Gemini TFS Source Control Check-in Policy, it worked.

One question that I have, is it possible so that I can edit the policy so that it either doesn't force every user to reference a Gemini issue on check in (or force them to select why this checkin is an exception), or to only force this policy on certain directories under a TFS project.

The reason I ask, is that we have different development groups all of which are using the same TFS Project (with different folders below it). Not all of these Dev groups are currently using Gemini. I don't want to force these groups to reference an issue, as they don't use Gemin, yet I would like to force those that are using Gemini to reference it. (We do not want to create a different project in TFS for this, as there are many other shared items on the project that we'd like to still utilize.)

Seems like I may be able to accomplish this after installing TFS Power Tools as per this blog http://blogs.msdn.com/b/girishp/archive/2012/02/16/tfs-2010-how-to-apply-check-in-policies-to-only-certain-branches-or-folders.aspx. I will post an update after I try this.

As of yet I was not able to get it working. It seems that my regex are not working. I am simply putting in the path to my branch or folder and the policy doesn't seem to be enfoced.

I have yet to figure out how to do this. Can anyone provide a pointer? I need to be able to apply the Gemini check-in policy to specific folders and\or branches within a TFS project but not to others.