Today is the big day, with the Launch of Visual Studio 2010 already done in Asia, and rolling around the world towards us, we are getting ready for the RTM.
We have had TFS 2010 Beta 2 and RC in Production for nearly 6 months and have had only joy, so moving to the RTM on launch day gives me warm and fuzzy feelings.
Update 12th April 2010
- Adam Cogan – Adam suggested I get our disagreement out in the open, improve the proposed solution description with some visual cues and move the Pros and Cons to the top.
- Added Scott Hanselman’s tweet about the MSDN download release time.
- Added – Testing TFS to make sure it is working.
- Added – Configured build services.
Updated 13th March 2010
- Adam Cogan pointed out that I had not followed the rule “Do you use Microsoft Word’s spelling and grammar checker to make your web content professional?” – Done
- Tatham Oddie suggested making the bullet list clearer as the strikethrough made it less readable, and he wondered why the product key was not pre-pidded (Key included) like most MSDN downloads. Well this is because I did not get it from MSDN
Updated 13th September 2010
- Adam Cogan asked for a couple of grammatical and phrasing changes and I have implemented the ones that I liked.
SSW was the first company in the world outside of Microsoft to deploy Visual Studio 2010 Team Foundation Server to production, not once, but twice. I am hoping to make it 3 in a row, but with all the hype around the new version, and with it being a production release and not just a go-live, I think there will be a lot of competition.
I already had the RC live, so lets look at how this went today:
First I checked my backups, then same as before, I needed to Uninstall 2010 RC and install 2010 RTM. The installer takes care of all the complexity of actually upgrading any schema changes.
I checked source control was working and then got the SharePoint 2007 Portal going.
We run TFS 2010 in a Hyper-V virtual environment, so we have the advantage of running a snapshot as well as taking a DB backup.
- Done – Snapshot the hyper-v server
Microsoft does not support taking a snapshot of a running server, for very good reason, and Brian Harry wrote a post after my last upgrade with the reason why you should never snapshot a running server.
- Done – Uninstall Visual Studio Team Explorer 2010 RC
You will need to uninstall all of the Visual Studio 2010 RC client bits that you have on the server.
- Done – Uninstall TFS 2010 RC
- Done – Install TFS 2010 RTM
- Done – Configure TFS 2010 RTM
Pick the Upgrade option and point it at your existing “tfs_Configuration” database to load all of the existing settings
- Done – Upgrade the SharePoint Extensions
- Done – Upgrade Build Servers
- Done – Test the server
The back out plan, and you should always have one, is to restore the snapshot.
Upgrading to Team Foundation Server 2010 – Done
The first thing you need to do is off the TFS server and then log into the Hyper-v server and create a snapshot.
Figure: Make sure you turn the server off and delete all old snapshots before you take a new one
I noticed that the snapshot that was taken before the Beta 2 to RC upgrade was still there. You should really delete old snapshots before you create a new one, but in this case the SysAdmin (who is currently tucked up in bed) asked me not to. I guess he is worried about a developer messing up his server
Turn your server on and wait for it to boot in anticipation of all the nice shiny RTM’ness that is coming next. The upgrade procedure for TFS2010 is to uninstall the old version and install the new one.
Figure: Remove Visual Studio 2010 Team Foundation Server RC from the system.
Figure: Most of the heavy lifting is done by the Uninstaller, but make sure you have removed any of the client bits first. Specifically Visual Studio 2010 or Team Explorer 2010.
Once the uninstall is complete, this took around 5 minutes for me, you can begin the install of the RTM. Running the 64 bit OS will allow the application to use more than 2GB RAM, which while not common may be of use in heavy load situations.
Figure: It is always recommended to install the 64bit version of a server application where possible. I do not think it is likely, with SharePoint 2010 and Exchange 2010 and even Windows Server 2008 R2 being 64 bit only, I do not think there will be another release of a server app that is 32bit.
You then need to choose what it is you want to install. This depends on how you are running TFS and on how many servers. In our case we run TFS and the Team Foundation Build Service (controller only) on out TFS server along with Analysis services and Reporting Services. But our SharePoint server lives elsewhere.
Figure: This always confuses people, but in reality it makes sense. Don’t install what you do not need. Every extra you install has an impact of performance.
If you are integrating with SharePoint you will need to run this install on every Front end server in your farm and don’t forget to upgrade your Build servers and proxy servers later.
Figure: Selecting only Team Foundation Server (TFS) and Team Foundation Build Services (TFBS)
It is worth noting that if you have a lot of builds kicking off, and hence a lot of get operations against your TFS server, you can use a proxy server to cache the source control on another server in between your TFS server and your build servers.
Figure: Installing Microsoft .NET Framework 4 takes the most time.
Figure: Now run Windows Update, and SSW Diagnostic to make sure all your bits and bobs are up to date.
Note: SSW Diagnostic will check your Power Tools, Add-on’s, Check in Policies and other bits as well.
Configure Team Foundation Server 2010 – Done
Now you can configure the server. If you have no key you will need to pick “Install a Trial License”, but it is only £500, or free with a MSDN subscription. Anyway, if you pick Trial you get 90 days to get your key.
Figure: You can pick trial and add your key later using the TFS Server Admin.
Here is where the real choices happen. We are doing an Upgrade from a previous version, so I will pick Upgrade the same as all you folks that are using the RC or TFS 2008.
Figure: The upgrade wizard takes your existing 2010 or 2008 databases and upgraded them to the release.
Once you have entered your database server name you can click “List available databases” and it will show what it can upgrade.
Figure: Select your database from the list and at this point, make sure you have a valid backup. At this point you have not made ANY changes to the databases.
At this point the configuration wizard will load configuration from your existing database if you have one. If you are upgrading TFS 2008 refer to Rules To Better TFS 2010 Migration.
Mostly during the wizard the default values will suffice, but depending on the configuration you want you can pick different options.
Figure: Set the application tier account and Authentication method to use. We use NTLM to keep things simple as we host our TFS server externally for our remote developers.
Figure: Setting your TFS server URL’s to be the remote URL’s allows the reports to be accessed without using VPN. Very handy for those remote developers.
Figure: Detected the existing Warehouse no problem.
Figure: Again we love green ticks. It gives us a warm fuzzy feeling.
Figure: The username for connecting to Reporting services should be a domain account (if you are on a domain that is).
Figure: Setup the SharePoint integration to connect to your external SharePoint server. You can take the option to connect later.
You then need to run all of your readiness checks. These checks can save your life! it will check all of the settings that you have entered as well as checking all the external services are configures and running properly. There are two reasons that TFS 2010 is so easy and painless to install where previous versions were not. Microsoft changes the install to two steps, Install and configuration. The second reason is that they have pulled out all of the stops in making the install run all the checks necessary to make sure that once you start the install that it will complete. if you find any errors I recommend that you report them on http://connect.microsoft.com so everyone can benefit from your misery.
Figure: Took a while on the “Web site” stage for some point, but zipped though after that.
Figure: Now we have everything setup the configuration wizard can do its work.
Figure: last wee bit. TFS Needs to do a little tinkering with the data to complete the upgrade.
Figure: All upgraded. I am not worried about the yellow triangle as SharePoint was being a little silly
Exception Message: TF254021: The account name or password that you specified is not valid. (type TfsAdminException)
Exception Stack Trace: at Microsoft.TeamFoundation.Management.Controls.WizardCommon.AccountSelectionControl.TestLogon(String connectionString)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
[Info @16:10:16.307] Benign exception caught as part of verify:
Exception Message: TF255329: The following site could not be accessed: http://projects.ssw.com.au/. The server that you specified did not return the expected response. Either you have not installed the Team Foundation Server Extensions for SharePoint Products on this server, or a firewall is blocking access to the specified site or the SharePoint Central Administration site. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=161206). (type TeamFoundationServerException)
Exception Stack Trace: at Microsoft.TeamFoundation.Client.SharePoint.WssUtilities.VerifyTeamFoundationSharePointExtensions(ICredentials credentials, Uri url)
Inner Exception Details:
Exception Message: TF249064: The following Web service returned an response that is not valid: http://projects.ssw.com.au/_vti_bin/TeamFoundationIntegrationService.asmx. This Web service is used for the Team Foundation Server Extensions for SharePoint Products. Either the extensions are not installed, the request resulted in HTML being returned, or there is a problem with the URL. Verify that the following URL points to a valid SharePoint Web application and that the application is available: http://projects.ssw.com.au. If the URL is correct and the Web application is operating normally, verify that a firewall is not blocking access to the Web application. (type TeamFoundationServerInvalidResponseException)
Exception Data Dictionary:
ResponseStatusCode = InternalServerError
I’ll look at SharePoint after, probably the SharePoint box just needs a restart or a kick If there is a problem with SharePoint it will come out in testing, But I will defiantly be passing this on to Microsoft.
Upgrading the SharePoint connector to TFS 2010
You will need to upgrade the Extensions for SharePoint Products and Technologies on all of your SharePoint farm front end servers. To do this uninstall the TFS 2010 RC from it in the same way as the server, and then install just the RTM Extensions.
Figure: Only install the SharePoint Extensions on your SharePoint front end servers. TFS 2010 supports both SharePoint 2007 and SharePoint 2010.
Figure: When you configure SharePoint it uploads all of the solutions and templates.
Figure: Everything is uploaded successfully.
Figure: TFS even remembered the settings from the previous installation, fantastic.
Upgrading the Team Foundation Build Servers to TFS 2010
Just like on the SharePoint servers you will need to upgrade the Build Server to the RTM. Just uninstall TFS 2010 RC and then install only the Team Foundation Build Services component. Unlike on the SharePoint server you will probably have some version of Visual Studio installed. You will need to remove this as well.
Figure: You only need to install the Team Foundation Build Service.
Figure: Team Build Services only work with one Team Project Collection so you need to select one.
Figure: Now that you have selected a Project Collection, you can choose a Controller.
You should only have more than one Build Agent running if you have more processors and lots of RAM.
Figure: All checks passed
Figure: Configuration complete.
Figure: Lots of little green ticks makes on big one!
Testing the Team Foundation Server
Figure: Team Web Access is working
Figure: VS2010 RC connecting to TFS2010 RTM
Connecting Visual Studio 2010 / 2008 / 2005 and Eclipse to TFS2010
You will have no problems connecting to TFS2010 from VS2010 RC or VS2010 RTM, but what about legacy versions of Visual Studio or developers working with Java?
If you have developers still on Visual Studio 2005 or 2008 you will need do download the respective compatibility pack:
- Visual Studio Team System 2005 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010
- Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010
If you are using Eclipse you can download the new Team Explorer Everywhere install for connecting to TFS.
Get your developers to check that you have the latest version of your applications with SSW Diagnostic which will check for Service Packs and hot fixes to Visual Studio as well.
-Every company deserves working software that successfully and consistently meets your customers needs. We can help you get working software with continuous feedback so that you agile teams can deliver continuous value with Visual Studio, Team Foundation Server & Scrum. We have experts on hand to help improve your process and deliver more value at higher quality.
[subscribe] While we love helping you individually we provide much of our resultant consulting understanding here for you to use. By writing about our experiences we gain a better understanding of them ourselves. You can get notified of all content that we publish with our weekly newsletter and see exactly what we are doing and how we are doing it. [/subscribe]