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 a conversation. Tell us where you are and what you're trying to change. Martin reads every inquiry and replies personally.
Start the conversationWe partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.

Healthgrades

Cognizant Microsoft Business Group (MBG)

Boeing

Lean SA

YearUp.org
NIT A/S

Illumina

Ericson

Capita Secure Information Solutions Ltd

Qualco

Teleplan

Flowmaster (a Mentor Graphics Company)

DFDS

Trayport

Alignment Healthcare

Slicedbread

Higher Education Statistics Agency

Epic Games

Ghana Police Service

Washington Department of Enterprise Services

Washington Department of Transport

Nottingham County Council

Royal Air Force

Department of Work and Pensions (UK)

Genus Breeding Ltd

Hubtel Ghana

Trayport
CR2

Workday

Teleplan