Upgrading from Visual Studio 2010 Team Foundation Server to Visual Studio 11 Team Foundation Server beta is very easy and as we have seen, fully supported in production. Today I got the new bits and I an going to upgrade our Northwest Cadence production server.
You need a couple of things before you get started:
- Admin on your Team Foundation Server environments
That includes your data tier and app tiers
- Your TFS account details
This means TFSService & TFSReports accounts at the least.
- Download Updates
- SQL Server 2008 R2 SP1 (Windows Update)
- SQL Server 2008 R2 SP1 CU1 (Download here)
Here is my TODO list for this install:
- DONE – Unpacking Visual Studio 11 Team Foundation Server
- DONE – Uninstalling Visual Studio 2010 Team Foundation Server
- DONE – Installing Visual Studio 11 Team Foundation Server
- DONE – Upgrading SQL Server 2008 R2 to SQL Server 2008 R2 SP1
- DONE – Apply SQL Server 2008 R2 SP1 CU1
- DONE – Upgrading to Visual Studio 11 Team Foundation Server
- DONE – Test your environment
- Email Everyone in your company to go check
Once you have those things you can move on to the good bits:
- Unpacking Visual Studio 11 Team Foundation Server
This is one of the longest processes as you need to unpack over 1gb of data from your ISO. I use WinRAR, but you can use anything you like.
Yes, you heard me right, its only a 1GB iso for TFS11. The team has done some amazing work pairing down the install (It was over 2GB in 2010.)
- Uninstalling Visual Studio 2010 Team Foundation Server
When you run the install on a box that has Visual Studio 2010 Team Foundation Server you will need to uninstall it first. But don’t worry, all you data will be left alone.
This is an easy process and is completed in a couple of minutes.
Once it is off you computer you can start with the Visual Studio 11 Team Foundation Server upgrade.
- Installing Visual Studio 11 Team Foundation Server
Installing TFS 11 is quick and easy. It takes only a few minutes, although you may need to make sure that you have the latest updates and service packs for all of the affected products as I would always recommend that you do.
You will see that even the Install has become cleaner and less cluttered. This may change when for the release, but it looks pretty good.
This is checked by default, but it is always good to get all of the updates before you start.
Always prep the machines with .NET prior to starting if you can. If you do that, you are doing this in minutes.
After that the install automatically starts after you log in and carries on.
Now that you have everything installed you need to begin the configuration. In TFS 2010 you had to stop here and install the Service Pack but as we just got these bits there is no SP, so … wooohooo..Done.
- Upgrading to Visual Studio 11 Team Foundation Server
But not really. Now we need to get to the real hard stuff. I am upgrading our current TFS 2010 server, so I need to select the Upgrade Wizard. There are many other options but I don’t need them for now.
Once you get into the wizard you will only see the options and be lead through the story that you want. Make sure that you select the correct story, and often the “Advanced” wizard is the most appropriate.
You need access to the database server for the next bit.The upgrade wizard is going to upgrade the schema of your server and you need “sysadmin” in order to do that. I forgot and had to get Steven Borg to add me.
The wizard will check to make sure that you have a data base that you can import. It will list all of your DB’s but you can only do one through the interface. There is a command line for upgrading subsequent databases if you have more than one configuration database.
note: You only need to do this ONCE per TFS Instance and not per team Project Collection. It will upgrade all of your collections.
You then need to specify the TFS Service account to use. Now I forgot this as well and had to ask Shad Timm (get a blog Shad) to get the password , which he provided with the speed that only Shad can.
I have very few circumstances where anything other then NTLM is not appropriate and as we have a separate data tier and app tier I have to use AD credentials. To be honest every time that I have used “network service” I have run into many problems. Just suck it up and use AD Credentials.
If you have TFS basic (or express) then you don’t get reporting, but this is an enterprise solution that has both reporting services and analysis services to configure.
In my case Reporting Services runs on the same server as the App Tier and it prepopulates the data. Remember that we already selected a TFS 2010 configuration database, so everything except the accounts is pre populated.
You need to select your warehouse, but enter your server and it will find it.
My Analysis Services database is sitting on my Data Tier so I have to enter that server name here. I love the “Test” feature on the pages so that you make less mistakes.
We use an Enterprise SharePoint farm so I will be leaving it configured as is.
If you have not done a TFS upgrade since 2008 you will love the readiness checks that the TFS team added. It looks at all of the things that it can to make sure that we catch any errors NOW, before we go any further.
The readiness checks run…. and…
My SQL server does not have SP1 or the required CU…. let me go do that….
WARNING: While I can get SP1 from Windows Update I need to jump though a bunch of hoops in order to get the CU, so:- SQL Server 2008 R2 SP1 CU1 Download
Now that you have fixed the problem, you just need to rerun the Readiness Checks to before you can Configure your server.
Figure: If you have express you get upgraded
Figure: Depending on your hardware the upgrade may take some time
Some updated take longer than other, but it really depends on your feature usage and hardware.
Each collection is upgraded individually after the configuration database has been completed and these again depend on the size and complexity. In this case the first collection has very little data and was upgraded quickly, but the second one is the main collection so will take a little longer.12345[2012-02-29 19:55:43Z][Warning] Team Foundation Server could not tear down the existing deployment rigs.Delete the Visual Studio 2010 Team Foundation Build Agents associated with your environments manually using Team Foundation Server Administrator Console.Exception Details:TF259046: Team Foundation Server could not complete the operation because of an internal error. Try the operation again.If the problem persists, contact your system administrator.
Figure: Warning message for Lab Management integrate collections
This is just to let me know that it did not do something against the Lab environment that is setup. I am going to leave it for now, but I will tell Shad that it happened
It looks like the existing configuration settings for SharePoint were not honoured in the beta. So it is worth noting that you will need to manually configure the if you get this error.
It looks like it is just a false message. When I looked in the admin tool all was well.
You will want to do lots of exercising of the features to make sure that everything works so we only have a few tasks left:
Remember that there is Go-Live for Visual Studio 11 Team Foundation Server!
Go on… be a kid again!