Some weeks ago I installed Microsoft Team Foundation Server 2018 on a single virtual server. The description of the installation I put in a blog post with a few comments (link).
Update 1 for TFS 2018 was released 2018-02-20, and in the Brian Harrys blog there is a post (link) on the release of TFS 2018.1 with some great key links to documentation and downloads.
I choose to download the ISO-image which is one file on 547 MiB named "tfsserver2018.1.iso". I do like the short and still precise naming.
After mounting the ISO-file to the virtual TFS server the update is started by executing the file "TfsServer2018.1.exe":
The update has a splash screen somewhat similar to the installation:
The Windows User Account Control come with a warning when the update actually starts:
The installation takes several minutes:
During the installation there are some activity on the CPU's. This could affect users in a Production installation:
After the unpacking and initial installation a wizard starts. I this case I choose to participate in the Visual Studio Experience Improvement Program. This I would never do outside a sandbox installation like this:
The next message in the wizard is rather odd I think. I am asked if this is a new deployment or if I have an existing database. I think that this indicates that the update is actually a complete reinstallation. Looking at the sizes of the ISO-files for TFS 2018 RTM and Update 1, the Update 1 ISO-file is 20 MiB larger than the RTM ISO-file.
Before touching the TFS installation the update wizard asks if I have a current database backup. At first I thought that the wizard could do it and then I didn't check the box. The result was that I was presented the same question later. This is from my second round:
The wizard need the password of the TFS service. This I think is another indication of a complete reinstallation:
The yellow warnings is because I didn't confirn an existing database backup. The configuration of the TFS Application Tier I just leave with the defaults:
Installation of the Search I also leave with the defaults. I think that this is the Code Search feature, that actually is a ElasticSearch installation.
I find it somewhat amusing that Microsoft includes a component written in Java with their development server.
And I - still - want Reporting for my TFS:
The Reporting installation is with the defaults:
The TFS Warehouse database is found by the wizard. Notice that the connection is on the short servername even the installation is local:
The SQL Server Analysis Services instance is also on the short servername:
The service account for TFS Reporting must also be entered into the update wizard. It is the service account for TFS Reporting, not the SQL Server Reporting Services service account:
This is the review presented by the update wizard after my second trip around the database backup confirmation. If the backup is not confirmed this is where the wizard has deactivated the Next-button:
Before the actual update - reinstallation - the wizard does a readiness validation:
After a short time you will hopefully get a green light:
And the the configuration begins. This takes several minutes:
After some tine you will get a completion message:
We are now close to the end with this status on the upgrade:
Finally the update is complete:
When the update wizard is closed the TFS Configuration Center is started to configure the Search:
When the last configuration is complete you can open the TFS Administration Console to view the configuration logs:
Finally you can verify the new version level in the root of the TFS Administration Console:
Now the updated TFS is running and ready to use.
Please notice that this update does not update the SQL Server installations. If you are using SQL Server 2017 there is a Cumulative Update 4 (link) released 2018-02-17.


























No comments:
Post a Comment
Note: only a member of this blog may post a comment.