Upgrading Agent reflects wrong service name

book

Article ID: 242305

calendar_today

Updated On:

Products

Workload Automation Agent

Issue/Introduction

The v11.5 install PDF has a setting available for the Windows service name:
WIN_SERVICE_1
Specifies the name of the Windows service for the agent, where n is an integer that corresponds to the scheduling
manager being configured. You can control the agent on Windows as a service.
Default: CA WA Agent
86
Workload Automation System Agent 11.5
Example: WIN_SERVICE_1=CA WA Agent
NOTE
For Windows, you must specify a value for this parameter.

 

My Win_installerProperties file has this setting (see attached):
    WIN_SERVICE_1=CA Workload Automation Agent 11.5

 

However on an unattended upgrade the service name and service display name default to "CA WA Agent"   This is causing problems for some of our users that have scripts that refer to the specific service name of "CA Workload Automation Agent 11.5"

What needs to change in the properties file?

 

This is the win_properties file:

 

ACCEPT_EULA=ACCEPT
INSTALLER_UI=SILENT
AGENT_UPGRADE_PATH=E:\\CA\\WA Agent R11.3.7
USER_INSTALL_DIR=E:\\CA\\WA Agent
USE_BUNDLED_JVM=TRUE
#something New next lins
AUTOSYS_MODE=FALSE
AGENTPARM_CONVERT_2=No
AGENT_INFO_1=ASCCA7RND02
AGENT_INFO_2=7520
NUM_MANAGER_1=1
MANAGER_1_INFO_1=TESTWAMGRID1
MANAGER_1_INFO_2=Hoste09b
MANAGER_1_INFO_3=7110
STRONG_ENCRYPTION_CIPHER=AES
STRONG_ENCRYPTION_KEYGEN=0x<key goes here >
#STRONG_ENCRYPTION_FILE=<CRYPTKEYLOCATION>
#STRONG_ENCRYPTION_FILE=$USER_INSTALL_DIR$$/$cryptkey.txt
STRONG_ENCRYPTION_FILE=E:\\CA\\WA Agent R11.3.7\\cryptkey.txt
LOCAL_SECURITY=on
SNMP_MGMT_CONN=0
JMX_PLUGIN=0
FTP_PLUGIN=0
SNMP_PLUGIN=0
CA_SOCKET=0
NUM_MANAGER_VARS_2=0
NUM_USER_VARS_2=0
LOOKUPCMD=true
JOBLOG=true
RAW_DATA=
WIN_SERVICE_1=CA Workload Automation Agent 11.5

Environment

Release : All release levels

Component : Workload Automation System Agent

Resolution

Unfortunately you cannot rename a service on Windows. This is a restriction at the OS level. Perhaps Microsoft might be able to provide some guidance on how this can be accomplished. Now, you can change the Description of the windows service for the agent, which can be done through Windows sc command.

One way to change service name from our standpoint would be to install a new agent and respond appropriately to the interview question which asks you to enter the name of Service for the Agent. Outside of this, the only other option to consider is through modifying the registry to reflect the service name of your choosing. While this is not a recommendation, it is an option. You'll need to work with your System Administrator to assist if you are not sure how to do this.

As a point to consider with future agent installations, perhaps steer away from using the version details in the service name and instead use maybe the manager node/instance that the agent will connect with.
Examples:

  • WA Agent (CAPR1)
  • WA Agent (CAPR2)