I'll preface this by saying this works for renaming your TFS server for internal use. I have not tried this for external use. There might be some more steps to get it to work from the Internet.
In the past month we migrated our infrastructure from 2005 to 2008 and in order to upgrade we needed to change a few things. If you recall from this my blog post on the subject Changing to a friendly Team Foundation Server Name we changed the NETBIOS name a new nicer to remember name. Well it turns out that in order to upgrade we needed to change some tables row back to the original server name. There are two location you'll need to change manually to get the upgrade going.
Open SQL Management Studio
Navigate to the TFSIntegration
Change url values in table tbl_service_interface. Anything that has the friendly name change to the NETBIOS name.
Change value in the tbl_registration_extended. Anything that has the friendly name change to the NETBIOS name.
Now you can upgrade.
After the upgrade you'll probably want to change it back to the friendly name, I know I wanted too ;-).
So there was a lot of the manual changes that we needed to do before (see previous post) that are now in the command line.
1) Navigate to x:\program files\Microsoft visual studio 2008 team foundation server\tools
2) run TfsAdminUtil ActivateAT tfs.myorg.mycompany.com
3) This will change the names in the DBs and the proper web configs and registry entry (what we needed to do by hands before)
4) On thing you still need to do is to navigate to x:\program files\Microsoft Visual Studio 2008\TFSServerScheduler and change the TFSServerScheduler.exe.config and change
[ADD value="http://rtmtgbs001 :8080" key="TFSNameUrl" /]
To
[ADD value="http:// tfs.myorg.mycompany.com:8080" key="TFSNameUrl" /]
This is a small change from 2005 we keep the same key and just change the value. After changing that we need to restart the TFSServerScheduler.
5) You will need to add few zones in SharePoint Administration v3. Start > All Programs > Administrative Tools > SharePoint 3.0 Central Administration
6) Operations > Alternate Access Mappings (that's under global configuration)
7) Add two mappings
internal URL
http://tfs.myorg.mycompany.com Zone: Intranet
http://tfs.myorg.mycompany.com:17013 Zone: Intranet
You need to do this so that the document node in Team Explorer will map to the proper URL.
You should be good to go after that.
Cheers,
ET