Skip to main content

Upgrading TFS Beta 2 to RTM

I have a client migrating to TFS 2008 who was leveraging an old version: 2008 Beta 2. We had difficulty getting the RTM software bits so I ended up extending the license for 30-days. (previous post) Well, it expired yesterday. Arg.

We finally got the RTM bits and I'm upgrading now. My steps:
  1. Follow the uninstall steps to the letter. Get rid of all that old stuff!
  2. Backup your existing TFS databases.
  3. Kick off the TFS 2008 installation and follow instructions
  4. Restart
  5. Install everything else you need: Build, Proxy, Explorer, etc. Oddly, the installation utility must be re-executed and these services installed individually.
  6. Execute the TFS Best Practices Analyzer (BPA) found within the TFS 2008 Power Tools.
    (Good how to here on BPA from Richard Hundhausen.)
  7. Resolve issues discovered with the BPA tool.
My experience (pretty darn good):



The databases were updated automatically.



I received a "Processor type and speed do not meet recommendations." warning but pushed on...this is a proof-of-concept box.



Excuse you? I can't run the services under the account I'm installing under? Great...starting over.

Had some red flags with the Best Practices Analyzer but they were easily fixed. BPA is a great tool (check out this tool for other products as well: Sharepoint, SQL Server).

Comments

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i