TL;DR; Overview of preparing handover documentation for a TFS 2005 deployment, including server details, reference materials, and integration with SharePoint 2007.

I am just writing some handover documentation for our TFS deployment in the office. Thank goodness that I wrote installation and disaster recovery documents when I originally deployed the system, other wise this would have been a very long process.
All I really need to do is reference those documents in a wrapper document that details of all of the servers and any online resources that I use.
TFS 2005 is a pain to install, but it is just fine to manage and over the last 8 months I have only had to log onto the server 3 times with one of them being to configure TFS 2005 to work with Sharepoint 2007.
I would always rather a painfully install than painfully management…
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.

Capita Secure Information Solutions Ltd

YearUp.org

Genus Breeding Ltd

Akaditi

Flowmaster (a Mentor Graphics Company)
CR2

Boeing

Kongsberg Maritime

Jack Links

Healthgrades

Illumina

Freadom

Microsoft

Ericson

Xceptor - Process and Data Automation

Schlumberger

ALS Life Sciences
Boxit Document Solutions

Department of Work and Pensions (UK)

Ghana Police Service

Nottingham County Council

Washington Department of Enterprise Services

Washington Department of Transport

New Hampshire Supreme Court

Workday

Deliotte

Freadom

Brandes Investment Partners L.P.

Epic Games

Ericson