When robot_update is deployed, if the Nimsoft Watcher Service is set to "Manual", it is changed to "Automatic (Delayed)".
Is this by design?
Is there any way to avoid the robot_update to change the default service status to "Automatic (Delayed)"?
Robot service first install, and any robot_update is by design including the assumptions about how the software should run so it sets the service accordingly.
By design, robot_update set the service to Automatic (Delayed).
There is no configuration key that changes this default behavior.
An enhancement request has been posted in the community.
A workaround would be to add as manual task (for the subset of robots affected) with a remote command when performing upgrade to enforce the service to default back to "Manual"
Eg:
/c sc config "NimusWatcherService" start= demand