Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Enable Patch Manager agents to communicate with the Automation Server during the initial deployment

Enable Patch Manager agents to communicate with the Automation Server during the initial deployment

Table of contents

Overview

This article describes how to enable Patch Manger agents to communicate with an Automation Server besides the Primary Application Server on initial deployment.

Environment

Patch Manager 2.1 and later

Steps

  1. Ensure that you have created routing rules for the computers and that there are no conflicting routing rules.
  2. Log in to the Patch Manager Admin Console as an administrator.
  3. In the navigation pane, expand Patch Manager System Configuration
  4. Under Patch Manager System Tasks, click Policy Editor.
  5. In the Policy List window, click Create New Policy.
    policy-list.png
  6. In the Category column, locate the Target category.
    target-category.png
  7. In the Target category, provide the following information about your Automation Server, and click Save:
    • IP Address
    • Device ID
    • Host Name
    • Port
  8. Open Regedit.

    Consult with your System Administrator before you edit your registry settings.

  9. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service to view the DeviceID field value stored in the registry on the Automation server.
  10. Save the policy.
  11. Click Policy Assignment.
  12. Click Create a New Scope and add clients. 
  13. Assign a new Policy to the machines, and click Save. 
    After several minutes, the agent configuration is updated.
  14. On the Automation Server that will communicate with the Patch Manager agents, test the environment using the Provision Offline Agent.

The Provision Offline Agent option creates an installer specific to the agent the Provision Offline Agent was performed for. To prevent multiple installs from creating an error state, SolarWinds recommends that you do not install on additional devices.

On the agent, the EminentWare.Agent.Service.exe.cfg file located at C:\Program Files\SolarWinds\Patch Manager\Agent\ contains details about the Automation Server the agent is pointed to.

 

 

Last modified

Tags

Classifications

Public