Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Re-provision an Automation Server

Re-provision an Automation Server

Table of contents

updated Aug 09, 2018

Overview

This article describes how to re-provision an Automation Server for deployments running Patch Manager 2.1 and later.

This article applies to deployments where an Automation Server was incorrectly deployed changed after being deployed. In this example, the Automation Server is incorrectly reported in the Patch Manager Administrator Console with inaccurate information. 

 

You may see below errors in MMC error window and DGS logs

2018/08/08 11:22:30:914 PID: 7104 TID: 7948 [ERROR] ComputerViewControl::ExecuteEnumerateComputerTargetsQuery() failed. Message: Source: Data Grid Server (IDC-SW-PMNG02) Reason: Failed to send partitioned task to automation server ABCWSUS.mydomain.com. Reason: Communication failure. The authentication service is unknown. Details: dgsrpcinterface::createsession failed! Object: ABCWSUS.mydomain.comObject Type: wsusserver

2018/08/08 08:47:38:954 PID: 3080 TID: 2864 [ERROR] clientcertificatecache::initialize() - Unable find and load this servers certificate. Server is not provisioned and will not be able to communicate with downstream servers. 2018/08/08 08:47:38:954 PID: 3080 TID: 2864 [ERROR] clientcertificatecache::createthisserversfullsicspn() failed to find certificate for

Environment

  • Patch Manager version 2.1 with Advanced Deployment using Automation servers

Steps

The following steps describe how to re-provision an Automation Server. 

Perform the following steps from the Automation Server and not the Primary Application Server. 


Solution 1:

  1. Run mmc.exe.
  2. Click File > Add Remove/Snap-in.
  3. Under Available snap-ins, select Certificates and click Add.
  4. In the dialog box, select Computer account, and click Next.
  5. Click Finish, and then click OK.
  6. Go to Trusted Root Certification Authorities > Certificates and delete EminentWare Server Certificate Only.
  7. Remove deviceID and CADeviceID from the following location in the registry:
    HKLM\SOFTWARE\EminentWare\Data Grid Service.
  8. Open SQL Management Studio.
  9. On the Primary and Automation databases, clear the record for Automation from dbo.gc_device and dbo.device
  10. Run:
    setuphelper /provisionserver /type automation.
  11. Reset the Patch Manager passwords
  12. In the Patch Manager Administration Console, expand Patch Manager System Configuration > Security and User Management.
  13. In the Actions pane, click Credentials and click Change Password.
  14. Go to Patch Manager System Configuration > Patch Manager Servers.
  15. In the Actions pane, click Patch Manager Server Wizard.
  16. Register the Automation Server.

 

Solution 2

The following steps work in Patch Manager 2.1.3 as well.

  1. Run mmc.exe.
  2. Click File > Add Remove/Snap-in.
  3. Under Available snap-ins, select Certificates and click Add.
  4. Select Computer account, and click Next.
  5. Click Finish, and then click OK.
  6. Go to Trusted Root Certification Authorities > Certificates.
  7. Delete Eminent Ware Certificates.
  8. Run a Patch Manager repair from Add/Remove.
  9. Complete the configuration wizard.

 

Last modified

Tags

Classifications

Public