At several customers I have seen that some Virus Scan Systems (no names) have a serious negative impact on the performance of Team Foundation Server. Especially the Build Server may be an easy target for the Virus Scanning actions.
Here’s my latest recommendation I have sent to the Ops Team. Note that all involved servers run Windows Server 2008 R2 (64 bit) and the software is installed on the C drive. The TFS Application Tier also has WSS 3.0 (SP2) installed. Use at your own risk and good luck to get this approved by your Ops Team. Traditionally they handle the presumption of innocence principle: the virus scan is innocent until proven guilty!
- TFS Application Tier
- C:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\Web Services\_tfs_data [TFS Version Control Cache folder]
- C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions [SharePoint Portal]
- C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files [SharePoint Portal + Web Access]
- C:\Users\TFSWSSAccount\AppData\Local\Temp [SharePoint Portal]
- TFS Build Server(s)
- Build Agent(s) working directory: D:\Builds
- TFS local cache folder for TFSBUILD account: C:\Users\TFSBUILDAccount\AppData\Local\Microsoft\Team Foundation
- TFS Data Tier
- SQL Server data files: .mdf + .ldf
- Client DevSeat
- TFS workspaces folder: D:\TFS
I did find some official references: