Change Release Management Server URL in Release Management Client (Resolve “The Release Management Server is not currently available. ”)

Setting up Release Management Server URL in Release Management Client should be done when it is set up initially. In an already configured client, it is possible to change the URL of the server, in Administration tab like shown below.
  
If the configured server is not accessible, the client will show error,
“The Release Management Server is not currently available. If the problem persists please contact your administrator. The application will now close.”

Since the client is getting closed when OK button is clicked, it is not possible to change the server URL in the Release Management client.
In Release Management 2013, generally following path contains the file (Microsoft.TeamFoundation.Release.Data.dll.config) containing the server URL.
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin

It is possible to manually edit the “Microsoft.TeamFoundation.Release.Data.dll.config” file, and URL needs to be set in multiple locations in this file.

There is easier option to do this with RM server 2013 update 2 onwards. That is by using the “ReleaseManagementConsoleAdjustConfigFile.exe” in the same folder (C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin).

Two parameters are required to be passed to this executable to set the new URL for the release management client.

• configfilename  config file name that is Microsoft.TeamFoundation.Release.Data.dll.config
• newwebserverurl New RM Server URL

Example command below.

ReleaseManagementConsoleAdjustConfigFile.exe -configfilename .\Microsoft.TeamFoundation.Release.Data.dll.config -newwebserverurl http://YourRMServer:1000

This command should be run in Administrative command prompt.



The command updates the “Microsoft.TeamFoundation.Release.Data.dll.config” file.



When the correct URL is set the RM Client can connect to RM server.

Visual Studio Release Management

Do we need to manage software releases/deployments in a well planned methodology? Do we need to track the details of the releases/deployments? Do we need to have a proper rollback strategy if something goes wrong in a deployment to production? I could keep asking more and more questions like this related to the software release management, and always the answer would be “YES”.
So what are our options, in terms of Microsoft ALM set of tools. TFS Lab environments can be used, but can we use it for production releases automation? Yes, if the client is willing to provide trusted access to production environment, via TFS Lab environments. But in most cases client would not like this. To add more pain to this Lab environments deployments would over utilize the build servers, with long running deployments. The solution for all this pain is addressed well in, new Visual Studio 2013 Release Management.
First we need to understand “Why” we need to manage releases. This post in NorthWest Cadence provides great insight.
There are three major components in VS 2013 Release Management.
1. Release Management Server.
Set of windows and web services that act as the core part of the release management. There is a portal providing approval capability to the release check points, without having to install Release Management Client or Visual Studio.
2. Release Management Client.
Windows Presentation Foundation (WPF) application provide the interface to manage the releases and configurations of release management.
3. Deployment Agent
Resides in target servers in the environment and performs the deployment actions such as installing, uninstalling, configuration etc. of software components.
Each of above performs its own duty, and resides in different computers. Together they make deployment automation a possibility with all the visibility and traceability expected in proper Application Lifecycle Management process.
The following diagram extracted from VS 2013 Release Management Installation Guide provides overview of “How it works”.



Even though above picture shows TFS, it is not mandatory to have TFS for VS Release Management to work. If the TFS is available can be tightly integrated with it. If not it could obtain payload for the deployment from any accessible drop locations (UNC path). This means the deployment could be even something not developed with .Net .
Below diagram from VS 2013 Release Management Installation Guide  explains communication between components of release management.



The most important thing here is the Deployment Agent is downloading the components for deployment as a pull request. Nothing is pushed from Release Management Server to Deployment Agent. This enables the possibility of Release Management Server not requiring access to Production environments. Deployment Agent notify Release Management Server it’s availability via heartbeat.

Let’s start our journey to explore Visual Studio Release Management by setting up an environment step by step, with my series of blog posts in next few weeks.
1. Setup Release Management Server.
2. Setup Release Management Client.
3. Setup Deployment Agent.
4. Configure SMTP.
5. Configure TFS Connection
6. Setup Stage Types.
7. Setup Servers & Environments.
8. Setup Release Path.
9. Demo Release Template - Part 1.
10. Demo Release Template - Part 2.