Configuration needs to reject/warn when "localhost" or is used for Deployment Controller

Install Processes
On our radar

At least a few times a year, I bump into a client that has a messed up environment that they just built, and the problem is that when they configured the deployment controller, the specified either "localhost" or for the "Deployment Controller address", and then used its ACTUAL address when configuring the other front end servers in the environment.

The configuration tool (Windows) and script (Linux) needs to be smarter about this, and either detect this entry and say "if you plan on adding other front end servers, this is wrong!" or prevent front end servers from being added ("the deployment controller has been configured with 'localhost' as its address, this will not work!"), or something similar. Clients lose HOURS trying to figure this out when it happens.


Created on 26 Dec 2017
Comments (0)