Robotname being changed due to environmental change

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When an environmental change occurs that affects the hostname of a server where a robot is installed, how can we prevent the robot from starting up with a new, unexpected, name?

Environment

Release : 20.3+

Cause

If the robotname is set to "automatically detected", the Nimsoft Robot Watcher service collects this name from the OS and starts the robot using this.  In the config file, the "robotname" key will either be missing or will be blank.

This is a correct configuration with expected behavior.

Resolution

It is possible to force the robot to ignore the environment and start with the same name.  This requires the robotname field being set in the robot.cfg file.  This change may manually be done to the config file of the Robot Name can be populated in the "Set Specific Name (Override)" section of the controller probe.

Other than this, it is not possible to prevent the creation of a new robot when an incorrect name is detected.