TFS 15 RC2 installation

I haven’t blogged about the TFS installation procedure for some but when I tried the installations wizard for TFS 15 RC2 I found some things I wanted to share.

The first thing you notice is that you don’t get a lot och options like, basic, advanced, aplication tier and so on, you just get configure Team Foundation Server, the options are built in later on in the Wizard.

tfs-15-1

The second thing we have to select is if we want to do a new installation or if we have existing databases to upgrade or a pre-production upgrade testing. In my case I have existing TFS databases.

 tfs-15-2

 Before starting the upgrade you confirm that you have a backup and SQL instance as usual.

tfs-15-3

Now comes the part a really like, I get to select if its a production environment or a Pre-Producktion Upgrade Testing. That means that I don’t need to run TfsConfig PrepareClone, TfsConfig ChangeServerID and TfsConfig RemabDB anymore! Great!

tfs-15-4

tfs-15-5

When it comes to the app tier the installation recognizes the existing IIS settings and you can change the public URL directly in the wizard instead of afterwards.

tfs-15-6 

As I see it this is a really god installation improvement that simplifies some of the more complicated upgrade scenarios.

License change for Release Management in TFS “15”

Since the new version of Release Management was introduced in TFS 2015.2 it has been in trial mode, anyone with at least a TFS CAL/Basic License could use it.

Based on the old Release management system I thought that you would need Visual Studio Enterprise to create releases when the trial was over, I was wrong.  From TFS “15” RC2 1 all Release Management features, including authoring of release definitions, are included in TFS CAL. Stakeholder can as before approve or reject releases.

Concurrent pipelines

From now you can run one release pipeline at a time for free, additional releases that you create will be queued automatically, additional pipelines will cost $15/concurrency each month or it looks like you will be able to utilize Visual Studio subscriptions in increasing the number concurrent release pipelines .