So, for example, if you were a consultant with your own TFS system and you built a starter project for the company Contoso, you can build the project on your own TFS instance and then deliver it in its entirety to Contoso when you are done.  Here are the steps for this process

 The attached Word document includes pictures to help you through this process.

Pre-Deliver Steps

Step 1: Make a new Team Project Collection

It can be difficult to deliver a single project if it is in a Team Project Collection (TPC) that is populated with non-delivered projects. So, for best results, if you know you are going to deliver a project, then create a new TPC for it.

Step 2: Make a new Team Project

You need a project if you are going to deliver it 

Step 3: Work on and finish your project

Deliver Steps On Original Server:

Step 4: Stop Working on the project

Once you are ready to deliver a project, you should stop working on it to avoid problems

Step 5: Detach the team project collection

You will need to detach the team project collection from the TFS server. This will store crucial information in the team project collection that allow it be hooked up to another TFS instance.

Step 6: Backup the project collection

You'll need to backup the team project collection database in SQL using the process described here: https://msdn.microsoft.com/en-us/library/ms187510.aspx

Set 7: Backup the SharePoint Site collection (only if SharePoint site collection will be delivered)

You'll need to backup the SharePoint site collection using the backup command under stsadm. This command must be run as an admin

stsadm -o backup -url <site_name> -filename <file_where_backup>

for example

stsadm -o backup -url https://contoso/sites/DefaultCollection -filename c:\default_collection.bak

More information on this command can be found here: https://technet.microsoft.com/en-us/library/cc263441.aspx Note: stsadm is usually stored in c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin (although not allways) Must be run as admin

Set 8: Backup the Reporting Services Reports (only if reports will be delivered)

Modify the script GetReportsFromServer.rss (located here) so that gMovingCollection is the name of the project collection that you are delivering. Executing this script will create a local copy of all RDL files stored in this collection.

This script is executed by running the command:

rs -i GetReportsFromServer.rss -s https://<tfsServer>/reportserver

for example

rs -i GetReportsFromServer.rss -s https://contoso/reportserver

Deliver Steps on New Server

Step 9: Restore the project collection

You'll need to restore the team Project collection database in SQL: https://msdn.microsoft.com/en-us/library/ms177429.aspx

Step 10: Restore the SharePoint site collection (only if SharePoint site collection will be delivered)

You'll need to restore the SharePoint site Collection via the following command the restore command in stsadm. This command must be run as an admin

stsadm -o restore -url <site_name> -filename <file_where_backup>

for example

stsadm -o restore -url https://contoso/sites/DefaultCollection -filename c:\default_collection.bak

More information on this command can be found here: https://technet.microsoft.com/en-us/library/cc262087.aspx. Note: stsadm is usually stored in c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin (although not allways) Must be run as admin

Step 11: Restore the Reporting Services Reports (only if you are delivering reports)

Modify the script PushReportsToServer.rss (located here) so that gMovingCollection is the name of the project collection that you are delivering. Executing this script will push all RDL files to the server.

This script is executed by running the command (in the parent folder of the output of Step 8 to the Reporting Server on the new system).

rs -i PushReportsToServer.rss -s https://<tfsServer>/reportserver

for example if Step 8 was in the folder C:\TFS_DefaultColleciton, then while in the C:\ directory execute:

rs -i PushReportsToServer.rss -s https://contoso/reportserver

Step 12: Attach the project collection

In the admin console, attach the the newly restored database

Step 13: Edit the Default Site location for the SharePoint site (only if SharePoint site collection will be delivered)

In the admin console, change the default site location for SharePoint.

Step 14: Change the SharePoint Web application and repair connection (only if SharePoint site collection will be delivered)

When you attach the project collection, the old SharePoint web application will be added to the system. You need to change this URL to match the location of the new SharePoint connection, and then Repair this connection so that each of the projects in your delivered project collection will connect to the correct site.

Note: This step will give you two SharePoint Web Applications that have the same URL. If you want to consolidate these two SharePoint Web Applications, then you will need to manually change the SharePoint Web Application for each project. Directions for this are given in "Alternative Steps 14 and 15" below. The only problem with having two SharePoint web applications with the same URL is that if you ever want to change your SharePoint web application URL, then you will have additional Web Applications to adjust.

Step 16. You're done!

One note, if you've migrated Reporting Services reports, then this may take 2-3 hrs to populate.

Alterative Step 14: For each project in the new collection, Change the portal settings to point to the new SharePoint server (only if SharePoint site collection will be delivered)

Step 14 a. Right-Click on each project

Step 14 b. Choose Team Project Settings->Portal Settings

Step 14 c. Under the Process Portal tab check Configure URL and choose the new web application from the drop down

Step 14 d. Under the Process Portal tab check Configure URL and choose the new web application from the drop down. Click Refresh and choose Process Guidance

Alternative Step 15 Clean up the SharePoint web applications on the new server.

Step 15 a. In the Administration Console under the SharePoint Web Application tab, click on the old SharePoint application (if it exists) and click Change. In the pop-up dialog, go to Dependents and check to make sure that there are no entries present. If projects exist,  follow step 13 for those projects

Step 15 b. In the Administration Console under the SharePoint Web Application tab, delete the old server (if it exists). If you get the popup elow and you finished step 15 a. then click Yes

Team Project Collection Deliver.docx

This script is executed by modifying it so that gMovingCollection variable is the name of the project collection that you are delivering, then running the command while in the parent direcotry of the folder created from GetReportsFromServer

The code in this script is given here and can be found in the attached file.

'=============================================================================
'  File:      GetReportsFromServer.rss
'
'  Summary:  Dowloads all reports from a TFS Reports Server to a specified directory
'     
'
'---------------------------------------------------------------------
'
'  Copyright (C) Microsoft Corporation.  All rights reserved.
'
' This source code is intended only as a supplement to Microsoft
' Development Tools and/or on-line documentation.  See these other
' materials for detailed information regarding Microsoft code samples.
'
' THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
' KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
' IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
' PARTICULAR PURPOSE.
'=============================================================================
'
' 1.0 Documentation
'
' Read the following in order to familiarize yourself with the sample script.
'
' 1.1 Overview
'
' This sample script uses a script file (.rss) and the script environment to run
' Web service operations on a specified report server. This script copies all of
' the RDL files from a local folder to the server and is designed to be used
' with GetReportsFromServer.rss
'
' To correcly run this script you will need to modify the global variable:
' "gMovingCollection"
'
'
' 1.2 Sample Command Lines
'
'
' 1.2.1 Use the script to publish the sample reports to an AdventureWorks Sample Reports folder.
'
'       rs -i PushReportsToServer.rss -s https://myserver/reportserver
'

''''' Modify gMovingCollection to be the collection name you want to move.

Dim gMovingCollection As String = "DefaultCollection"

''''' Only change the variable gHDLocation, if your Reports are stored in a different directory then
''''' .\TFS_gMovingCollection

Dim gHDLocation As String = ".\TFS_"+gMovingCollection

''''' Only change the variable gReportsLocation, if some reason your reports are stored in a direcotry other thean
''''' "/TFSReports" (i.e., never change this).

Dim gReportsLocation As String = "/TFSReports"

'This function recursively navigates through the local hard drive uploading files and creating folders
'in the process
public Sub OnNodeArrival(myParentServerPath As String, myServerFolder As String, myHDFolder As String)
 
 'Create the parent folder on Reporting Server
 Try
         rs.CreateFolder(myServerFolder, myParentServerPath, Nothing)
         Console.WriteLine("Folder {0} created successfully", myServerFolder)
     Catch e As Exception
  Console.WriteLine("Failed to Create Folder")
         Console.WriteLine(e.Message)
     End Try

 '' We need to handle the possible base cases "C:\" and "/" differntly because the end in a slash
 Dim parentHDPath As String
 Dim parentRepPath As String
 If (myHDFolder = "C:\")
  parentHDPath = myHDFolder
 Else
  parentHDPath = myHDFolder+"\"
 End If

 If (myParentServerPath = "/")
  parentRepPath = myParentServerPath
 Else
  parentRepPath = myParentServerPath +"/"
 End If

 ' Retrieve a list of all items from the local and upload them.
    Dim returnValues As String()
 Dim fileWithPath As String
 Dim file As String

 'Publish reports in myHDFolder
 returnValues = Directory.GetFiles(myHDFolder)
 For Each fileWithPath in returnValues
  If (Path.GetExtension(fileWithPath) = ".rdl")
   file = Path.GetFileNameWithoutExtension(fileWithPath)
   PublishReport(fileWithPath, parentRepPath+myServerFolder, file)
  End If
 Next

 ''Recursively navigate through all sub directories
 Dim subFolderWithPath As String
 Dim subFolder As String

 returnValues = Directory.GetDirectories(myHDFolder)
 For Each subFolderWithPath in returnValues
  'the below line is nescssary because subFolderWithPath contains "C:\blah-blah\...\reportfolder"
  'and we just need "reportfolder"
  subFolder = subFolderWithPath.Replace(parentHDPath, "")

  OnNodeArrival(parentRepPath+myServerFolder, subFolder, subFolderWithPath)
  
 Next
End Sub

'This function actually publishes the report
Public Sub PublishReport(filePath As String, reportPath As String,  ByVal reportName As String)

 Dim definition As [Byte]() = Nothing
 Dim warnings As Warning() = Nothing

 Dim combinedString As String
 If (reportPath="/") Then
  combinedString = reportPath+reportName
 Else
  combinedString = reportPath+"/"+reportName
 End If

 Try
  Dim stream As FileStream = File.OpenRead(filePath)
         definition = New [Byte](stream.Length-1) {}
         stream.Read(definition, 0, CInt(stream.Length))
         stream.Close()

     Catch e As IOException
         Console.WriteLine(e.Message)
 End Try

     Try
         warnings = rs.CreateReport(reportName, reportPath, False, definition, Nothing)

         If Not (warnings Is Nothing) Then
       
   'We ignore the warnings where the DataSources are not hooked up because
   'we fix this up after the report is uploaded

              Dim warning As Warning
              For Each warning In warnings
    If (warning.Code <> "rsDataSourceReferenceNotPublished") Then
     Console.WriteLine("--Warning For :" + combinedString)
     Console.WriteLine("Warning Code:" + warning.Code)
     Console.WriteLine(warning.Message)
     Console.WriteLine("")
    End If
   Next warning
         Else
             'Console.WriteLine("Report: {0} published successfully with no warnings", reportName)
         End If

     Catch e As Exception
  Console.WriteLine("--Error For :" + combinedString)
         Console.WriteLine(e.Message)
  Console.WriteLine("")
 End Try
 
 '''''
 'Modify the data source of uploaded reports
 '''''
 'In the TFS suplied reports, only two datasources are used:
  ' 1)"TFSOlapReportDS" and 2) "TfsReportDS". These values are located at respectively,
 ' 1) "/Tfs2010OlapReportDS" and 2) "/Tfs2010ReportDS".
 '
 'If your custom reports have other datasources that need to be changed, you
 'can add these datasources here or you can modifiy them by manual after upload
 'by navigating to their report at the Report Manager URL (https://myserver/reports)
 'and viewing thier datasources under the properties tab.

       Dim dataSources() As DataSource
 dataSources = rs.GetItemDataSources(combinedString)
 Dim oldDS as New DataSource()
 
 Dim count As Integer
 count = 0
 For Each oldDS In dataSources
  If (oldDS.Name = "TfsOlapReportDS")
   Dim referenceDS As New DataSourceReference() 
   referenceDS.Reference = "/Tfs2010OlapReportDS"
   oldDS.Item = referenceDS
  Else If (oldDS.Name = "TfsReportDS")
   Dim referenceDS As New DataSourceReference() 
   referenceDS.Reference = "/Tfs2010ReportDS"
   oldDS.Item = referenceDS
  End If

  dataSources(count) = oldDS
  count = count + 1
 Next oldDS

       Try
          rs.SetItemDataSources(combinedString, dataSources)
       Catch e As SoapException
  Console.WriteLine("Failed to Write Reference for :" + combinedString) 
         Console.WriteLine(e.Detail.InnerXml.ToString())
       End Try

 '''''
 'Modify the paramaters of uploaded reports
 '''''
 'In the TFS suplied reports, only one paramater is modified "ExplicitProject"
 'For the ExcplicitProject paramater, the default value is set to empty (i.e., "")
 'and PromptUser is set to False.
 '
 'If your custom reports have other paramaters that need to be changed, you
 'can add these paramaters here or you can modifiy them by manual after upload
 'by navigating to their report at the Report Manager URL (https://myserver/reports)
 'and viewing thier parameters under the properties tab.

       Dim forRendering As Boolean = False
       Dim historyID As String = Nothing
       Dim values As ParameterValue() = Nothing
       Dim credentials As DataSourceCredentials() = Nothing
       Dim parameters As ReportParameter() = Nothing
 

 parameters = rs.GetReportParameters(combinedString, historyID, forRendering, values, credentials )
 Dim par as New ReportParameter()
 
 count = 0
 For Each par In parameters
  If (par.Name = "ExplicitProject")
   Dim defVals(0) As String
   Dim emptyString As String = ""
   defVals(0) = emptyString
   par.DefaultValues = defVals
   par.PromptUser = False
  End If

  parameters(count) = par
  count = count + 1
 Next par

 Try
          rs.SetReportParameters(combinedString, parameters)
       Catch e As SoapException
  Console.WriteLine("Failed to Write Parameters for :" + combinedString) 
         Console.WriteLine(e.Detail.InnerXml.ToString())
       End Try
End Sub

Public Sub Main()

     rs.Credentials = System.Net.CredentialCache.DefaultCredentials
    Console.WriteLine("Starting")
     OnNodeArrival(gReportsLocation, gMovingCollection, gHDLocation )
 Console.WriteLine("Files from " + gHDLocation + " were published in " + gReportsLocation+"/"+gMovingCollection)
End Sub

PushReportsToServer.rss

This script is executed by modifying it so that gMovingCollection variable is the name of the project collection that you are moving , then running the command:

rs -i GetReportsFromServer.rss -s https://<tfsServer>/reportserver

for example

rs -i GetReportsFromServer.rss -s https://contoso/reportserver

The code in this script is given here and can be found in the attached file.

'=============================================================================
'  File:      GetReportsFromServer.rss
'
'  Summary:  Dowloads all reports from a TFS Reports Server to a specified directory
'     
'
'---------------------------------------------------------------------
'
'  Copyright (C) Microsoft Corporation.  All rights reserved.
'
' This source code is intended only as a supplement to Microsoft
' Development Tools and/or on-line documentation.  See these other
' materials for detailed information regarding Microsoft code samples.
'
' THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
' KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
' IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
' PARTICULAR PURPOSE.
'=============================================================================
'
' 1.0 Documentation
'
' Read the following in order to familiarize yourself with the sample script.
'
' 1.1 Overview
'
' This sample script uses a script file (.rss) and the script environment to run
' Web service operations on a specified report server. The script creates coppies
' all files from a TFS collection and stores them on the specified directory.
'
' To correcly run this script you will need to modify the global variable:
' "gMovingCollection"
'
'
' 1.2 Sample Command Lines
'
'
' 1.2.1 Use the script to publish the sample reports to an AdventureWorks Sample Reports folder.
'
'       rs -i GetReportsFromServer.rss -s https://myserver/reportserver
'

''''' Modify gMovingCollection to be the collection name you want to move.

Dim gMovingCollection As String = "DefaultCollection"

''''' Only change the variable gHDLocation, if you don't want the report files stored in the
''''' directory ".\TFS_gMovingCollection"

Dim gHDLocation As String = ".\TFS_"+gMovingCollection

''''' Only change the variable gReportsLocation, if some reason your reports are stored in a direcotry other thean
''''' "/TFSReports" (i.e., never change this).

Dim gReportsLocation As String = "/TFSReports"

public Sub OnNodeArrival(MyServerFolder as String, MyHDFolder as String)
 
 'Create Folder on HD
 If(Not System.IO.Directory.Exists(MyHDFolder)) Then
     System.IO.Directory.CreateDirectory(MyHDFolder)
 End If

 ' Retrieve a list of all items from the report server database.
       Dim items As CatalogItem() = Nothing
 Try
         items = rs.ListChildren(MyServerFolder, False)     
       Catch e As SoapException
          Console.WriteLine(e.Detail.InnerXml.ToString())
       End Try
     
       
 Dim catalogItem As CatalogItem
 Dim reportDefinition As Byte() = Nothing
 Dim doc As New System.Xml.XmlDocument
 Dim serverFolderString As String
 Dim hdFolderString As String

 '' Get list of all children reports and seralize it locally.  
 For Each catalogItem In items
  If (catalogItem.Type=ItemTypeEnum.Report)
        Try
   
   '' We need to handle the appended string name differently if
   '' 1) the base report path is \
   '' 2) or the base hard drive path is C:\ (if you want to store to a differnt drive change this)

   If (MyServerFolder = "/")
    serverFolderString = "/"+catalogItem.Name
   Else
    serverFolderString = MyServerFolder + "/"+ catalogItem.Name
   End If

   If (MyHDFolder = "C:\")
    hdFolderString = "C:\"+catalogItem.Name +".rdl"
   Else
    hdFolderString = MyHDFolder+"\" + catalogItem.Name +".rdl"
   End If

   'Console.WriteLine(serverFolderString)
   'Console.WriteLine(hdFolderString)

   ' Serialize the contents as an XML document and write the contents to a file.
          reportDefinition = rs.GetReportDefinition(serverFolderString)
          Dim stream As New MemoryStream(reportDefinition)
          doc.Load(stream)
          doc.Save(hdFolderString)
   Console.WriteLine("Coppied " + serverFolderString + " to " + hdFolderString)

        Catch e As SoapException
           Console.WriteLine(e.Detail.InnerXml.ToString())

         Catch e As IOException
            Console.WriteLine(e.Message)
        End Try  
  End If
  Next catalogItem 

 ''Go through and get all reports and rescursively navigate them
 For Each catalogItem In items
  If (catalogItem.Type=ItemTypeEnum.Folder)
    If (MyServerFolder = "/")
    serverFolderString = "/"+catalogItem.Name
    Else
    serverFolderString = MyServerFolder + "/"+ catalogItem.Name
    End If

    If (MyHDFolder = "C:\")
    hdFolderString = "C:\"+catalogItem.Name
    Else
    hdFolderString = MyHDFolder+"\" + catalogItem.Name
    End If

    OnNodeArrival(serverFolderString, hdFolderString)
  End If
  Next catalogItem 
End sub

Public Sub Main()
 Dim baseReportFolderName As String
 Dim baseHDFolderName As String

 baseReportFolderName = gReportsLocation+"/"+gMovingCollection
 baseHDFolderName = gHDLocation

 rs.Credentials = System.Net.CredentialCache.DefaultCredentials
  
 Console.WriteLine("Starting")

 OnNodeArrival(baseReportFolderName, baseHDFolderName)
      
 Console.WriteLine("")
 Console.WriteLine("Reports downloaded into  " +baseHDFolderName)
End Sub 'Main

GetReportsFromServer.rss

MSConnect: https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=25150

Code Gallery: https://code.msdn.microsoft.com/KB977226

Please let me  know if you run into any problems since the primary reason why we are releasing a non-critical patch for a beta product is to get feedback about our servicing infrastructure.

Fixes

·         Fixes an intermittent race condition that prevents WIT data from making it to the Warehouse

·         Fixed an issue where the iteration backlog for each build workbook is based on the root iteration and not on the individual iterations

·         Fixes an issue where in the Regional Options, the Decimal Symbol is defined to something other than “.” (For example ”,”)

·         Fixed an issue that prevents saving multiple work-items in excel or project when connected to TFS 2010 server from a 2008 client.

The Final Fix and Some Additional Steps

In order to get the final fix included in this patch

·         Fixed an error where after buddy builds some files appeared checked out to the build service account.

You will need apply some additional manual steps as detailed below.

The reason why there are additional steps is because this fix requires changing the process template files which are user editable. As a result, we cannot automatically replace those files.

NOTE: before continuing, it is important to note that the following steps assume that you have not made any changes to the default process templates, or the build template files. If you have, then the process will involve manually porting the changes. Let me know if you are in this boat, and I will help you through it.

Overview of Steps for Changing Process Template Files

If you haven’t change the default process templates or the build template files, then you will need to follow these steps

1)      Replace the file \Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfAgile\Template.zip with  \Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfAgile\Template_new.zip.

2)      Replace the file \Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfFormal\Template.zip with \Program Files\Microsoft Team Foundation Server 2010\Tools\Deploy\ProcessTemplateManagerFiles\MsfFormal\Template_new.zip

3)      Uncompress these template files stored in the patch. (Don’t delete the zip file)

4)      For each existing team project collection, upload the new process templates.

5)      For each existing team project, replace the Build Process Template files DefaultTemplate.xaml and UpgradeTemplate.xaml in version control with their new files.

Details for steps 4 and 5 are given at the end of the post.

A Bug

One final note, we have already found one bug with this patch.  We should, but do not, change the default process templates stored on the server to include the new file. The end result of this bug is that every time you create a new team project collection, you will need upload the new process templates to the new team project collection if you want their associated fix. This will not be a problem with RTM patches.

If y’all have any questions, please let me know.

--Aaron

Detailed Steps for Changing Process Template Files

After you have replaced the files on the application tier and uncompressed the template files,  follow these steps (detailed steps for 4 & 5 above)

1)      For each existing team project collection, upload the new process templates.

a.       For each Project collection, connect to the project collection, right-click on the Project Collection name, and select Team Project Collection Settings->Process Template Manager

b.      In the dialog box that pops up, click on upload

c.       Select the folder for MsfFormal

d.      Overwrite the previous version of the file

e.      Repeat steps C and D for MsfAgile

2)      For each existing team project, replace the Build Process Template files DefaultTemplate.xaml and UpgradeTemplate.xaml in version control with their new files.

a.       For each existing project, go to the source control for that project.

b.      Go to the BuildProcessTemplate Folder

c.       Get the latest and checkout the files DefaultTemplate.xaml and UpgradeTemplate.xaml

d.      If this is an agile project, then open the folder where you uncompressed MsfAgile. If this is a formal project, then open the folder where you uncompressed MsfFormal.

e.      Under either the MsfAgile or MsfFormal folder, go to the folder \build\Templates

f.        If you haven’t made any changes to DefaulTemplate.xaml or UpgradeTemplate.xaml, you can just replace those files in the local BuildProcessTemplate folder. If you have, then you will need to move the modified lines manually into the DefaultTemplate.xaml and UpgrageTemplate.xaml files.

g.       After you have made changes to DefaultTemplate.xaml and UpgradeTemplate.xaml. Check those changes back in.

right-click.jpg

I've recently put together a document about how to expose TFS 2010 (Beta 2+) to the Internet. If interested, take a look through it and let me know what you think (positive or negative). Note: This document does not apply to Beta 1.

EDIT: Updated the document to incoperate feedback.

Thanks,

--Aaron

Exposing Team Foundation Server to the Internet.docx

TF31001: Cannot connect to Team Foundation Server at xxx.com. The server returned the following error: The ServicePointManager does not support proxies with the https scheme.

This problem appears to be related to our decision to switch the default behavior of the BypassProxyOnLocal setting.  The BypassProxyOnLocal setting indiciates whether the proxy server should be bypassed for local addresses. (Local requests are identified by either the lack of a period [such as https://webserver] or those that are talking to the local server [such as https://localhost or https://127.0.0.1]). If true, the local requests bypass the proxy; otherwise, if false, all Internet requests are made through the proxy server.

In TFS 2008, the default value for BypassProxyOnLocal was false. This changed in 2010. Setting BypassProxyOnLocal to true improves the performance of the initial connection and resolves a performance problem experienced by some customers. So, unless you are reciving this error, you should not change the value of BypassProxyOnLocal.

If you are receiving the TF31001 error, you should be able to resolve this issue by running the following commands:

On all machine:

reg add hklm\SOFTWARE\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

reg add hklm\SOFTWARE\Microsoft\TeamFoundationServer\10.0\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

Additionally on a 64-bit machine:

reg add hklm\SOFTWARE\Wow6432Node\Microsoft\TeamFoundationServer\10.0\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

reg add hklm\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

 --Aaron

 I've written a post on the TFS admin & Ops site on  how to upgrade to TFS 2008 while changing servers that might be helpful, https://blogs.msdn.com/tfsao/archive/2009/04/20/upgrading-to-team-foundation-server-2008-while-changing-servers.aspx

--Aaron

--Aaron

P.S. I had a hard time choosing between titling the series “Server Change We Can Believe In” or “Maverick Moves”

If you are interested in learning more about using TFS for Hyper-V. I've made a post at the TFS A&O blog. Enjoy

 https://blogs.msdn.com/tfsao/archive/2009/02/03/hyper-v-and-tfs.aspx

--Aaron

https://msdn.microsoft.com/en-us/library/dd206696.aspx 

If you have any questions, feel free to post them in the comments section.

 --Aaron