Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

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

Re-provision an Automation Server

Table of contents
Created by Erica Gill, last modified by MindTouch on Jun 23, 2016

Views: 5 Votes: 1 Revisions: 3

Overview

This article provides steps to re-provision an Automation Server. 

This can help in a scenario where an automation server was incorrectly deployed or was changed after being deployed resulting the automation server being incorrectly reported in the Patch Manager mmc GUI as having different details. 

Environment

Patch Manager version 2.1 or earlier

Steps

Perform a re-provisioning of an Automation Server:
 

  1. Run mmc.exe. Click File > Add Remove/Snap-in... Add Certificates, select Computer account, click Next and Finish. Click OK. Go to Trusted Root Certification Authorities > Certificates and delete EminentWare Certificates.
  2. Remove deviceID and CADeviceID from registry (HKLM\SOFTWARE\EminentWare\Data Grid Service).
  3. Run SQL Management Studio and clear record for Automation from dbo.gc_device and dbo.device (do it for both DB: Primary and Automation);
  4. Run setuphelper /provisionserver /type automation.
  5. Reset passwords in Patch Manager (Go to Patch Manager System Configuration > Security and User Management > choose Credentials and click Change Password).
  6. Go to Patch Manager System Configuration > Patch Manager Servers > click on Patch Manager Server Wizard and register Automation Server.

 

 

 

 

Last modified
01:16, 23 Jun 2016

Tags

Classifications

Public