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 > Patch Manager 2.1.4 Administrator Guide > Wake on LAN > Scenario 4: Using a Management Role Server to Segregate Patch and Asset Data

Scenario 4: Using a Management Role Server to Segregate Patch and Asset Data

Table of contents
No headers
Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 6 Votes: 0 Revisions: 4

A typical example of this scenario is physically segregating patch data collected from the WSUS server from the asset inventory data collected from Managed Computer Inventory tasks. Deploy additional Management role servers to improve performance, or limit database space requirements to avoid the need for a licensed instance of SQL Server.

In the following example, assume the 10 GB database size limitation of SQL Server 2008 R2 Express Edition is not sufficient for both patch and asset data. To stay within that limit, deploy an additional Management role server to house the asset data from a domain inventory. This reserves the PAS for patch data from the WSUS server.

Additional Management Role Server for Separate Databases

File:Success_Center/New_Articles/PatchManager_Admin_Guide_MT/0F0/0E0/0300000C_444x302.png

Since Patch Manager physically segregates the data in this example, each database is significantly smaller than they would be if combined. In addition to limiting space requirements, this example also improves performance and enhances security by keeping unique data sets completely separate.

Last modified
01:13, 23 Jun 2016

Tags

Classifications

Public