Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Patch Manager > Patch Manager instance and database limitation

Patch Manager instance and database limitation

Table of contents

Overview

This article explains the relationship between a Patch Manager instance and its database. 

Environment

All Patch Manager versions

Detail

Patch Manager does not allow host migration. Each database is married to the installed instance of Patch Manager. A fresh instance of Patch Manager and a new database are required when connecting from a different host or IP address. Delete the database to connect to the same instance of SQL that the database of the old Patch Manager server resides, or install Patch Manager and connect it to a different instance of SQL.

 

If you uninstall the Patch Manager server software and install it on another server, you will need to create a new database.  You will need to delete or drop any existing EminentWare database from the SQL server and instance if it already exists.

 

In the database, the key information is largely the Inventory (both WSUS and Managed Computers Inventory), Scheduled Tasks and Task History.  Most of the pertinent information is on the WSUS server or in the environment where an Inventory Task will quickly rebuild the information in the new database.  If you need any currently scheduled tasks or task history, you are encouraged to document the task for re-creation or export the pertinent information prior to uninstalling or dropping the existing database.

 

Instructions for the migration of the database from on SQL server to another are documented here.

 

Last modified
13:51, 13 Jan 2017

Tags

Classifications

Internal Use Only