Change the Release Management Server that your Client connects to

Published on
2 minute read

As a consultant I am onsite at a different customer every week and as I use my own laptop for most engagements I need to be able to change the Release Management Server that I connect to from the thick client.

Change the Release Management Server that your Client connects to

Figure: The Release Management Client

The Release Management team kindly added a UI to allow us to change which server that we are connected to. Open you RM client ad head over to “Administration | Settings| System Setting” and you can then click the “Edit” button next to the current “Release Management Server URL”.

Change the Release Management Server that your Client connects to

Figure: Editing the configured Release Management Server

However if you try to open the client without being able to access that server you get an error message and you are unable to get to that screen to change the server URL. It would have been nice if it just asked us if we wanted to reconfigure and launched the original configuration dialog, however that is not the case.

Change the Release Management Server that your Client connects to

Figure: Can’t open Release Management Client with no Server available

By default the port of your RM server is 1000 but you may have changed it so you need to know both the port and the server. Unfortunately if your correct release management server is unavailable then the client will error our and close.

In order to work around this you need to change the URL that tells the Release Management Client to connect to that specifc server and it is fairly well hidden. You need to head over to the Microsoft.TeamFoundation.Release.Data.dll.config file and update it manually.

The Release Management team however have created a handy utility that may make it a little quicker. You can run ReleaseManagementConsoleAdjustConfigFile.exe and pass in both the configuration that you want to change and the configuration property along with the value.

C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\bin\ReleaseManagementConsoleAdjustConfigFile.exe –configfilename   .\Microsoft.TeamFoundation.Release.Data.dll.config -newwebserverurl http://bvtirserverpod1:1000

In this way you can update the server when you move from site to site. If you switch between client sites often it might be useful to create batch files on your desktop for launching the client with the right connection. Just call the connection change and then launch the app. Simples…

System Configuration Install and Configuration Release Management Practical Techniques and Tooling

Related blog posts

Related videos

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Boxit Document Solutions Logo
Schlumberger Logo
Epic Games Logo
Boeing Logo
Graham & Brown Logo
Kongsberg Maritime Logo
Akaditi Logo
Milliman Logo
Lean SA Logo
Slicedbread Logo
Workday Logo
Alignment Healthcare Logo

CR2

Ericson Logo
Big Data for Humans Logo
Microsoft Logo
Jack Links Logo
Sage Logo
Department of Work and Pensions (UK) Logo
New Hampshire Supreme Court Logo
Ghana Police Service Logo
Washington Department of Enterprise Services Logo
Royal Air Force Logo
Nottingham County Council Logo
Genus Breeding Ltd Logo
Schlumberger Logo
YearUp.org Logo
Slaughter and May Logo
ALS Life Sciences Logo
Milliman Logo