Submit a ticketCall us
Home > Success Center > Patch Manager > Enable the communication of Patch Manager agents with Automation server on initial deployment

Enable the communication of Patch Manager agents with Automation server on initial deployment

Table of contents
Created by Abraham Toribio, last modified by MindTouch on Jun 23, 2016

Views: 123 Votes: 2 Revisions: 14


This article describes how to enable the communication of Patch Manger agents with an AS besides the Primary server on initial deployment.


Patch Manager 2.1 and later


  1. Ensure that you have created routing rules for the computers and that there are no conflicting routing rules.
  2. On Patch Manager console, click on Patch Manager System Configuration > Policy Editor > Create New Policy.
  3. In the Target category, provide the following information about your Automation Server:
    - IP Address
    - Device ID
    - Host Name
    - Port
  4. Run Regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service to view the DeviceID stored in the registry on the Automation server. The DeviceID field will be shown.
    Warning: Consult your System Administrator before performing this procedure.
    1. Save the policy and click Policy Assignment.
    2. Add clients using the Create a New Scope button.
    3. Assign a new Policy to the machines and save changes. After several minutes, the agent configuration will be updated.
  5. On the Automation server that you plan on having the agents communicate with deploy the agents, test the environment using the Provision Offline Agent option.



  • The Provision Offline Agent option creates an installer specific to the agent the Provision Offline Agent was performed for. SolarWinds recommends that you do not install on other devices because multiple installs create an error state.
  • On the agent, the file EminentWare.Agent.Service.exe.cfg located at C:\Program Files\SolarWinds\Patch Manager\Agent\ contains details on the automation server the agent is pointed to.



Last modified