|
|
|
|
|
Before updating make sure both nodes have been synchronized. Then stop the MOVEit Automation service on both nodes (using the MOVEit Automation Admin Shut Down Service command on the primary node). After the services have been stopped on both nodes, run the update on the primary node first and make sure that the MOVEit Automation service is started on this node before you update the secondary node. (By upgrading the primary node first, no unnecessary failover will occur.)
After the update, you might receive an email from one or both MOVEit Automations reporting that they could not contact the other MOVEit Automation node. This is a result of having the service running on one node and not the other during the upgrade process. Youi can ignore this message.
Windows Updates
Windows updates can normally be applied without shutting the MOVEit Automation services down. However, if a reboot is required by a Windows update package, plan to take down the MOVEit Automation service on the secondary node, then boot the primary node and let it come back up before you reboot the secondary node. (Make sure that the secondary node also brings its MOVEit Automation service up after its reboot.)