This updates addresses issues in Team Foundation Server 2012 Update 1.
This update fixes eight issues in Team Foundation Server 2012 Update 1.
Issues addressed in this patch:
- Collections that are attached to a server that is running TFS 2012 Update 1 may lose permissions
- Group scopes may incorrectly cause permission errors
- Severe decrease in performance after TFS 2012 Update 1 is installed
- Identity sync jobs may fail repeatedly
- Warehouse is not updated correctly, or fields that represent a person are not filled
- Users can see names of collections of which they are not a member
- You cannot remove a user or a group after you attach a collection to a TFS 2012 Update 1 server
- You cannot view artifacts that reference an identity that is no longer a part of a collection
After installing the patch, you will need to manually initiate a rebuild of the warehouse in order to correctly populate the fields which reference people for the latest revisions of work items. Please see this article
for more information on how to rebuild the warehouse.
Supported Operating System
Windows 7 Service Pack 1, Windows 8, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 2012
Team Foundation Server 2012 Update 1
On this page, choose the Download button.
- To install the software now, choose the Run button.
- To install the software later, choose the Save button.
Before you install the update:
- Close any instances of Event Viewer that are running (EventVwr.exe).
- Close any instances of Server Manager that are running (ServerManager.exe).
- Close the Team Foundation Administration Console (tfsmgmt.exe).
Download and run patch_kb2803625.exe
Note: This patch is only targeted for the Team Foundation Server Application Tier, it does not need to be run on stand-alone build servers, remote SharePoint servers, or proxy servers.
If you have multiple load-balanced application tiers (ATs):
- Shut down all the ATs except for the one on which you will install the update. Make sure that you close the Admin Console on all these ATs.
- Remove the AT from the load balancer.
- Install the update (as discussed earlier).
- After you install the update to the first AT, install the update on the other ATs one at a time.
- Add the ATs back to the load balancer.
If you are using SQL Mirroring or SQL AlwaysOn features for your databases:
This update requires your SQL Databases to be set to simple recovery mode. To make sure that the update can set simple recovery mode for your databases, do the following before you apply the update:
- If your databases are in a SQL AlwaysOn Availability group, you must remove them from the availability group before you apply the update.
- If the databases are part of a SQL Server database mirroring, you must remove (break) the mirror before you apply the update.
As soon as the update process is complete, you may return the databases to the AlwaysOn group or re-enable database mirroring.