Allen Clark has posted the document on upgrading beta 3 to RTM so you’ll know what to expect.

Preparing to upgrade to RTM

If you’re using Beta 3 Refresh, you may be wondering what you can do now to make the server upgrade to RTM as painless as possible. Here are a few things that will help.

• If you customize work item types, don’t create work item field reference names that have more than 70 characters, or that begin with a number.
• If it’s not too late, deploy Team Foundation Server on the hardware you’re going to use at RTM.
• If you are going to deploy to new hardware, go ahead and install Team Foundation Server on the new hardware and try it out just to make sure you don’t have configuration issues. You can uninstall Team Foundation prior to upgrading.
• Keep track of the customizations you’re making to the process templates; you’ll need to do these again before you’ll be able to create new projects with your custom process templates.

I’ve included the specification below so that you can get a better idea of what the upgrade will be like and let us know if you feel like we haven’t covered your scenario. Keep in mind that this isn’t final, but the actual upgrade will be similar to what’s described here.

Allen Clark

Program Manager, Team Foundation Server

Design Goals

When V1 ships, customers must be able to upgrade their data without support from Microsoft.

• Upgrading to RTM will not be effortless, but the work required must be reasonable.
• Customers should not get into a server-down state unexpectedly.
• Minimize the impact on the Setup team.