TFS On Prem Maintenance Mode - tfs

I would like to do some maintenance on my on premise TFS instance.
Is there a way to show take it offline while i do changes on the application configuration and backup the database?

You can use the TFSServiceControl command to stop or start all of the services and application pools used by Azure DevOps Server or Team Foundation Server (TFS). For example, you use this command when backing up or restoring databases.
TFSServiceControl [quiesce|unquiesce]
This is mentioned in the document, please refer to this docs for details.

Related

How to perform code migration from TFS 2018 to Azure DevOps?

We are trying to migrate code from TFS2018 to Azure DevOps. I am new to code migration from TFS to VSTS. I would like to know is there any tool for code migration?
I saw TFS-GIT utility. I am really not sure how much efficient this tool.
GIT-TFS list remote repostiory
You may do it through OpsHub tool: OpsHub Visual Studio Online Migration Utility
My recommendation would be to either upgrade your on-premise server to Azure DevOps Server 2019 or the latest Team Foundation Server 2018 update pack that's supported by the migration tool.
You can perform this upgrade on a clone instance of your existing server, so it won't break or change your existing machine or database in case anything goes wrong.
We regularly perform these types of migrations and we generally use a temporary Azure Virtual Machine. We install SQL Server on it, we restore the backup of the on-premise server, we install the desired TFS application tier version on it. If the Azure machine is joined to your domain, then that's all you need to start the import into Azure DevOps. If the machine isn't domain joined, be sure to turn off the AD Sync job as part of the migration. My colleague Jasper has a couple of scripts to fix that for you.
Alternate options. In my opinion there aren't any. At least not good ones. There is a whole set of tools that an migrate parts of TFS to Azure DevOps, tools like OpsHub, git-tfs, git-tf, Migration Tools for Azure DevOps. None offer a complete migration, some do work items, some sources, some builds, but none of these offer a complete migration.
All of these also have the issue that they reset metadata such as Commit/Approval dates, work item IDs. Which will impact retention jobs, history and other things you may care about.

Unable to install Test Manager extension on Azure DevOps Server 2019

Recently we have upgraded our TFS server to the latest 2019 version.
As the Admin, I was trying to install the downloaded Test Manager extension just like we did in TFS2017 and TFS2018.
However, I was unable to install it even with full access and TFS test plan subscription.
This extension does not support the version of the Server you are
currently using. See Works With for supported Server versions.
What should I do, am I missing something? Why it not work with TFS2019? Appreciate your help.
This is the expected behavior when you try to install the extension in Azure DevOps Server 2019. You do not need to install extra Test Manger for Azure DevOps Server 2019.
The official link is also clearly: This extension does not support the version of the Server you are currently using. See Works With for supported Server versions.
It only work Works with
Team Foundation Server 2017
Team Foundation Server 2018
Note:
Manual testers do not need this extension and can execute tests as a
Basic user in an Azure DevOps organization/collection. Read more on
this here.
This extension is available out-of-the-box in Azure DevOps Services and Azure DevOps Server (2019 onwards) and hence doesn't need to be acquired for them.
We strongly recommend you to use Azure Test Plans or the Test hub in Azure DevOps Service/Server (a fully featured Test management solution) over Microsoft Test Manager for all your test management requirements. There will be no new versions of Microsoft Test Manager.Microsoft Test Manager 2017 (which shipped with Microsoft Visual Studio 2017) is the last version.
More details please take a look at our official tutorial here.
Besides, to use Azure Test Plans in Azure DevOps service you need some License requirements
Azure Test Plans uses an access level called Basic + Test Plans, which is available from Azure DevOps.
For the Manual testing permissions and access suggest refer this link: https://learn.microsoft.com/en-us/azure/devops/test/manual-test-permissions?view=azure-devops#license-requirements
Hope this helps.
As mentiond in the Extension page:
This extension is available out-of-the-box in Azure DevOps Services and Azure DevOps Server (2019 onwards) and hence doesn't need to be acquired for them.
So you don't to install it, it's exist :) just go to the "Test Pans" tab in the left menu (maybe you need give permissions in the settings).

team foundation server 2012 restore

I am trying to restore a Team Foundation Server database to another server.
The Original server was a Team Foundation server express 2012 install.
Steps so far
Created backup of all the databases using SQL management studio
i.e. TFS_defaultCollection,TFS_Configuration, Tfs_Company1, TFS_Company2.
Installed TFS Express 2012 on another server
Restored all the SQL Server database's to the new server
I get an error the SQL instance is missing.
Is there any way to restore the TFS databases to the new server.
or
is there any way to extract the project data from the databases.
Make sure you have created the SQL instance in SQL server.
Based on your description your backup should be executed manually. So,to restore data for Team Foundation to a different server or instance, you must complete the procedures that your deployment topology requires the sequence mentioned in below link:
https://www.visualstudio.com/en-us/docs/setup-admin/tfs/admin/backup/restore-data-different-instance#back-up-data
Recommend you follow the steps in this link provided by Daniel to backup and restore the database from TFS Administrtion Console, it's more convenient than manually backup.

Can we use TFS as Source Code Repository for Salesforce?

Can we use TFS as Source Code Repository for Salesforce? If yes then is there any TFS/Salesforce API which can be used to fetch the latest code from Salesforce Dev Org?
You can store your code in any SCM system. Salesforce orgs also have meta-data that affect configuration and this must be exported, usually via an SFDC plug-in to an IDE like eclipse. Deploying code to SFDC must be through their interfaces and requires test code. This could all be scripted in .NET / PS via SFDC API, but that is beyond the scope of a post like this IMO.
Yes. You can fetch the code from Project collection and deploy into Sandbox.
However, the command line fetch from TFS is still evolving and in TFS 2013 , there are some new changes.
AutoRABIT - a release management suite for Salesforce Applications has support for deployments from Team Foundation Server [ TFS 2013 ] - Salesforce Sandbox or auto-commit from Sandbox to TFS .
Niranjan

Replacing TFS App Tier

I plan on replacing my existing app tier (TFS 2010) when upgrading to TFS 2013. I'll quiesce the services and rename the old machine from MYTFS to MYTFS_OLD. The new app tier will have a fresh, un-configured installation of TFS 2013 and will be renamed from MYTFS_NEW to MYTFS.
My question is, will it be necessary to run the ChangeServerID or RemapDB commands if the new app tier is named the same as the old one?
If I understand your scenario correctly you will end up with:
A new server that's completely clean
The 'old' database server that contains all the TFS databases.
If that's the case, you should install TFS and select 'Upgrade'. You then point your TFS Application Tier to your database server and let TFS upgrade your databases.
You cannot have both version running on the same set of databases.
Study the ALM Ranger's Upgrade guide before doing anything.
I don't think you need to run remapdbs or changeserverid commands:
you typically need remapdbs when the server name changes which is not the case
you should use changeserverid if you plan to clone a TFS server meaning that you have restored TFS databases to a different machine and set up another TFS instance on that machine without killing the original server. Again it's not the case from what you have described here.

Resources