Team Foundation Server 2015 Update 2 RC 1 Known Issues and Fixed Bugs
Microsoft released Team Foundation Server 2015 Update 2 RC 1 on February 10, 2016. This article lists the known issues and fixed bugs for the Team Foundation Server 2015 Update 2 RC 1.
To see the full list of Team Foundation Server 2015 products and to select a product for download, check out Team Foundation Server Downloads.
To discover what is new in Team Foundation Server 2015 Update 2 RC 1, see the Team Foundation Server 2015 release notes.
Download the latest Team Foundation Server 2015 update package now.
Fixed bugs
This release fixes many bugs.
Known issues
TFSJobAgent
This update has an issue in which the TFSJobAgent may have high CPU utilization.
Resolution:
To fix this issue, run the following command before you configure your TFS server:
del "C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\TFSJobAgent\Plugins\Microsoft.TeamFoundation.SshService.JobAgentPlugins.dll"
Note This is the default path, adjust this path if you install to a custom location.
If you have configured your TFS server, you have to stop the TFSJobAgent before you delete the file. To do this, run the following commands in the given order:
• Net stop tfsjobagent • del "C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\TFSJobAgent\Plugins\Microsoft.TeamFoundation.SshService.JobAgentPlugins.dll" • net start tfsjobagent
Windows Machine File Copy
Assume that you have created some build definitions that use a Windows File Copy step. The step fails to run if the step parameters rely on the target system’s environment variables, such as $env:Systemdrive.
Workaround:
To work around this issue, update the build definition to reflect the absolute path on the target. Windows Machine File Copy will not resolve the target system’s environment parameters. These changes may require you to open your release definitions, update them, and save them again.
For more information about Windows Machine File Copy tasks, see Windows Machine File Copy.
Azure File Copy
Assume that you have created some build definitions that use an Azure File Copy step. The step fails to run if it doesn't find the matching resource group or cloud service name that includes the input machine group name. The step continues to work if the machine group name matches the target Azure resource.
Workaround:
To work around this issue, update the build definitions that have an Azure File Copy step. To do this, follow these steps:
In the Azure File Copy step, the Machine Group field has been renamed to Resource Group/Cloud Service. Update this field to reflect the correct resource group or cloud service to copy the files.
Provide admin login credentials.
Review and then save the task.
For more information about Azure File Copy tasks, see Azure File Copy.
How to download Microsoft support files
Updates for other products in the Team Foundation Server family can be found on the Microsoft download site for Team Foundation Server website.
Requirement
For detailed system requirements, see Team Foundation Server 2015 Compatibility.
Restart requirement
You may have to restart your computer after you install this package.
Software requirement
To apply this update, you must have the Team Foundation Server 2015 installed on your computer.
Supported architectures
32-bit (x86)
64-bit (x64) (WOW)
Applies to
Team Foundation Server 2015
Team Explorer Everywhere 2015
Team Foundation Server Express 2015
Team Foundation Server Extensions for Project Server 2015
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. |