Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Patch Manager primary application server is bound to wrong IP address

Patch Manager primary application server is bound to wrong IP address

Updated July 12, 2017

Overview

Patch Manager is displaying the wrong IP address inside the registry and in the Management Server section in the Patch Manager Console, which can affect agent creation and automation server and secondary application server connections.

Environment

All Patch Manager versions

Cause 

This may occur because of an IP address change to the primary application server.

Resolution

  1. Run mmc.exe.

  2. Click File > Add Remove/Snap-in > Add Certificates, and then select Computer account.

  3. Click Next > Finish > OK.

  4. Go to Trusted Root Certification Authorities > Certificates.

  5. Delete EminentWare Certificates.

  6. Remove CAHostname and CAIPAddress from the HKLM\SOFTWARE\EminentWare\Data Grid Service registry.

  7. Run SQL Management Studio and clear the record for PAS from dbo.gc_device and dbo.device.
    Note: Perform this step for both the Primary and Automation databases.

  8. Run setuphelper /provisionserver /type primary.

  9. Go to Patch Manager System Configuration > Security and User Management.

  10. Select Credentials, click Change Password, and then change the password.

  11. Go to Patch Manager System Configuration > Patch Manager Servers.

  12. Click the Patch Manager Server wizard, and then register the primary server.

 

 

Last modified

Tags

Classifications

Public