Recently I have done a TFS upgrade from 2012.2 to 2013.4 with a hardware move. DNS settings changed to access new TFS server using the previous TFS URL. All went well and I when I started TFS 2012.2 build farm (plan to upgrade them later) it was working as expected.
Started the test controllers and when viewed in MTM Lab Center the controllers shown offline.
My plan was to upgrade the test controllers later since currently lot of lab environments in use. Event viewer in test controller indicated an error.
Restarted test controller service, restarted test controller machine, but was not helpful.
Tried clean TFS cache in Test Controller machine.
All of above was not helpful. So I decided to take a risk and reconfigure the test controller 2012.2 with the new TFS (2013.4) server. My only worry was what will happen to the existing lab environments after reconfiguring test controller.
After reconfiguring everything was smoothly working. All my previously up and running labs were working as expected.
SQL Server Integration Services (SSIS) projects can be created to perform ETL (Extract Transform and Load) operations. As Implementing of Co...
Generally windows services are deployed by creating an msi installer. It is possible to deploy msi via VSTS/TFS release management using the...
Task groups are really useful to share common actions with multiple build or release pipelines in Azure DevOps (VSTS). You can group multip...
GItHub has a easy way to get raw contents of a file by clicking on Raw button for any code file in GitHub, where it will redirect to url sta...
It is great if the latest updates to TFS can be applied as and when they are released. But for a large organization it might not be sometime...