Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts

Sunday, 25 September 2016

TFS15 RC1 Setup Guide

This is a step by step guide on setting up TFS 15 RC1 for evaluation purpose. This a “go-live” release and supported by Microsoft support team. Requirements for TFS15 is specified here.image

Download  TFS15 RC1, ISO image or web installer.

Make sure you have installed supported SQL Server version, with reporting services in native mode.

  • SQL Server 2016
  • SQL Server 2014

Setup SharePoint Foundation 2013. This is optional. How to setup SharePoint Foundation 2013 is here.

Run the installer.01

02

Restart the machine03

Launch the TFS Admin Console after restart and start configuration wizard for “Configure Team Foundation Server”.04

05

Select new deployment and select advance configuration.06

07

08

Provide the SQL Server name and verify.09

Specify a service account for TFS.10

Specify a public URL for TFS.11

You have option to provide HTTP or HTTPS access.12

11.2

Optional search feature can be configured as well. More information of the feature here.13

14

Configure reporting.15

Report server urls are set to access local only.16

17

18

Configure optional SharePoint for TFS, if the SharePoint foundation is setup earlier. Make sure alternate access mappings for SharePoint urls properly set.19

27

19

Provide a project collection name and review.20

21

Run readiness checks.22

23

Accept download and install of JRE (java Runtime Environment) which is a prerequisite of Search feature, and run configure.24

25

JRE configuration might fail. If this happens manually download and install JRE.26

Download Java runtime 8u102 from here and install.27

28

29

30

Run the configuration wizard for TFS again and in readiness checks still shows JRE unavailability.31

This happens because JAVA_HOME is not properly set with JRE install. how to set JAVA_HOME is here. Setting JRE_HOME is not working for TFS, You have to set JAVA_HOME environment variable. Make sure to use the shortened path name.39

Readiness checks should pass and configuration of TFS should be successful.36

40

41

To configure report services urls for network access with FQDN follow the steps below. Click edit on Reporting  tab of TFS Admin Console.42

Test warehouse analysis services connectivity.43

44

Manually type in FQDN for report services urls.45

46

Reporting services set to use FQDN.47

Sunday, 20 July 2014

Setup Release Management Client

This is the second step of setting up VS 2013 Release Management environment. Prerequisite for this step is Release Management Server which is described here.
Trial version of VS 2013 Release Management with update 2 can be downloaded from http://go.microsoft.com/?linkid=9843020.
Note: You cannot apply a license key for the trial to make it licensed version. Instead you have to uninstall trial and install licensed copy downloaded with MSDN or Volume License to apply license.

In the downloaded ISO run rm_Client.exe to install Release Management Client. This is a very quick install.
001

Installation is quick and smooth.

002
 003

Once lunched provide the url of the release management server. example – http://ReleaseManagmentServer:1000
Below picture shows TFS since this installation of the Release Management Client is done on tfs box.

004

This url is correct but cannot be connected by the client.

005

Check if Release Management Server app pool is running and if not start it.

 006

Try browsing to http://releasemanagemntserver:1000/ReleaseManagement

008

This could happen, if the Release Management Server is installed in TFS box with Sharepoint Foundation. To resolve this issue refer Release Management Server in TFS box with Sharepoint Foundation, the fix specified in there is below.


  • On the machine where the Release Management Server was installed with TFS and Sharepoint, start a Command Prompt. Run as Administrator but not sure this was required.
  • Navigate to C:\Windows\System32\Inetsrv
  • Enter the following command
    appcmd.exe set config -section:system.webServer/globalModules /[name='SPNativeRequestModule'].preCondition:integratedMode,bitness64

  • 009

    Browsing to http://releasemanagemntserver:1000/ReleaseManagement succeeds.

    012

    Below error occur if the user running Release Management Client is not added as a user in Release Management Server.

    013

    To resolve this issue add the user to Release Management Server, users, by clicking new on Administration tab Manage Users. (To do this log on to the Release Management Client with a user already available in release management server – example - run client as installation user of release management server).

    020

    Add the required user.

    021
     022

    Release manager is the super user role in Release Management Server.

    023

    The user should be able to connect to the Release Management Server from a remote machine using the Release Management Client.

    025
     026
     027

    We have setup a Release Management Server, and Release Management Client accessing the server from a remote machine successfully. Next step is to set up Deployment Agent(s).

    Popular Posts