TFS Upgrade - Short Lead Checklist
Any upgrade of TFS, regardless of how basic or complex, whether in-place or including hardware migration, needs to be planned. That planning should start long before the migration happens and should include all parties of the TFS ecosystem, meaning all the user roles as well as infrastructure roles.
Week or two prior to upgrade
Step |
Instructions |
1 - TfsPreUpgrade Tool ꙱ - Done |
If your database is large enough to warrant running the TfsPreUpgrade tool prior to the upgrade it can be done while still using the server in production. The process is non-destructive, cancelable and can be undone. Given that though it shouldn't be taken lightly or run too far in advance because it does have a performance impact on the server once it's run. |
Weekend of upgrade
Step |
Instructions |
1 – Backup ꙱ - Done |
Backup current TFS data using Scheduled Backups (available since TFS 2012 Update 2). |
2 - Backup encryption key ꙱ - Done |
Reporting Services uses an encryption key to secure sensitive data that is stored in the report server database. To ensure that you have continued access to encrypted data, it’s important that you create a backup of the encryption key in case you need to restore it later due to changes in the service account or as part of a planned migration.
Refer to rskeymgmt Utility (SSRS) for more information. |
3 - Uninstall TFS ꙱ - Done |
|
References
Related Posts
- New Elements of TFS 2015 that influence an upgrade
- Long Lead Preparations
- Long Lead Checklist
- Post Upgrade Checklist
Authored by Mike Abrahamson
Mike is a Principle Consultant, based in Minnesota focusing on Application Lifecycle Management. Mike has Enterprise level experience leading ALM projects that help customers use Team Foundation Server to enable their business and ALM processes. Mike focuses on defining and delivering software solutions with an emphasis on process maturity and quality throughout the software development lifecycle.