Team Foundation Server (TFS) Best Practice Analyzer (BPA) tool.
To demystify the process of receiving the TFS tool via a PSS support incident, we will step through the various steps and conclude showing the view the PSS engineer will have of the collected data. In the next post, TFS BPA - View 2, we will compare it with the more "visual" and interactive BPA tool view.
Step 1 - You receive an email with an invitation to execute the support data collection tool, TFSCmd.exe in our case.
Step 2 - You are requested to select the relevant region.
Step 3 - You are prompted to select whether the computer to be analyzed if the current one or another computer.
Step 4 - An agreement for the Microsoft support diagnostic framework must be accepted.
Step 5 - You may need to grant permission for the data collection ActiveX control to be installed.
Step 6 - You can then give control to the diagnostic process and allow all date to be collected or manually control which data should be gathered. We recommend you use automatic when possible.
Step 7 - You need to select between the "prior", "during" and "after" installation modes, whereby the latter is the typical option to run when investigating an existing TFS server environment.
Step 8 - After the collection process has completed ... a process that ranged from minutes to close to 40min in our tests to date ... you are prompted for the last time. In this case the system wants permission to send the gathered files to Microsoft for analysis.
Step 9 - Once uploaded, a confirmation is issued by Microsoft. This is the end of the BPA visit and control is turned to the PSS engineer.
Step 10 - The PSS engineer views your data using the support diagnostic console as shown below.
In the next post, we will compare the SDC view as above, with the output generated and viewed after running the tool in an interactive manner. See you then ...