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).

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
10 comments
Read more

Switching the Parents to Ubuntu...?

I spent a half hour or so recently on the phone walking my Mom through a technical issue. Tentatively, I diagnosed her issue as a hard drive failure. She brought it over on her last visit and sure enough, the Dell XPS 450 from circa 1999 sounds like a bad coin-operated laundry at full capacity. I was aghast to discover she's running Windows 98. Ugh. Also, her recovery disk is just that--for recovery. I don't believe I'll be able to re-install Win98 on a new hard drive. That, coupled with the end of Microsoft (and Dell) support for Win98, got me thinking about Linux. (and she's not intense about her computing needs...and she doesn't want to spend much money...) I've been reading good things about switching one's parents to Ubuntu. Any thoughts out there?
4 comments
Read more

VSTS Tester Demo Follow-ups

Last week, I delivered a VSTS 2008 Tester Edition demo to a prospective client. Following up on a few questions to which I didn’t know the answer: Q. Can I use Subversion with TFS? A. I get this question all the time from developers. It’s a perfectly valid question. The answer is no…but yes…sort of. The version control repository (and all data) must remain SQL Server. Yes, it’s proprietary. Further, if you plan to use TFS in your software development environment, but choose not to leverage it for version control, it severely limits the usefulness of the information elicited from TFS (because you’re not feeding in the crucial VC data). If you’re not leveraging VC in TFS, you’re probably not leveraging Team Build either. That said, while a fully-integrated TFS for ALM and SCM is the ideal, there’s a compelling argument to leverage TFS as a repository for requirements, scenarios, test cases, functional and load testing as well as defect tracking. TFS is an excellent repository to s...
2 comments
Read more