When we recycle our scheduling servers every month, the agentparm.txt on each agent gets updated. Historically the server address has not been a FQDN
communication.managerid_1=ESP_XXXXXXX_7500
communication.manageraddress_1=XXXXXXX
communication.managerport_1=7507
communication.monitorobject_1=NT_XXXXXXX/AGENTMON1.0/MAIN
We now have one agent in a more secured cloud network that requires FQDN
communication.managerid_1=ESP_XXXXXXX_7500
communication.manageraddress_1=XXXXXXX.XXXXXXX.COM
After the reboot of the scheduling server, this agentparm.txt was set back to using the non FQND name.
Any advice?
------------------------------
Andy Reimer
------------------------------