This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Automatically patching automation servers

I scheduled a number of servers to install windows patches using the update management wizard. In the first phase I scheduled the 2 automation servers (Server1 and Server2) to patch which both failed. The next phases which were servers using automation server routing rules to point to either Server1 or Server2 worked fine.

Server1 and Server2 gave the below results:

Operation                                      Result    Information                                                  Executed On Server

Update Management with rules        Failed     Attempt to connect to Server1 failed.             SERVERx

Update Management with rules        Failed     Attempt to connect to Server2 failed.             SERVERx

The server that they "Executed" on, SERVERx, is another automation server for a random customer that has nothing to do with Server1 or Server2. There are no routing rules that link these servers together.

Any ideas as to why these would fail and point to a random server? Can you actually automate patching on an automation server and should it be using itself to "Execute" on?