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 Documentation > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Set up a Management Server role to segregate patch and asset data

Set up a Management Server role to segregate patch and asset data

Table of contents
No headers
Created by Caroline Juszczak, last modified by Steve.Hawkins on Jul 10, 2018

Views: 236 Votes: 0 Revisions: 7

You can add Management Server roles to improve performance or limit space requirements to avoid purchasing an additional SQL Server instance. The Management Server roles allow you to segregate patch data collected from the WSUS server from the asset inventory data collected from managed computer inventory tasks. 

This scenario can help you manage your patch data if you installed Microsoft SQL Server Express as your primary Patch Manager database. Because this SQL version has a 10 GB size limit, it is not enough space to store both patch and asset data. To stay within the 10 GB restriction, you can deploy an additional Management Server role to store the asset data from a domain inventory. This scenario reserves the PAS for patch data from the WSUS server.

If you exceed the 10 GB limit, you must migrate your Patch Manager database to an SQL Server instance. 

SPM-Admin-Guide-Scenario-4-Management-Server.png

Since Patch Manager physically segregates the data, each database is significantly smaller. This scenario also improves performance and enhances security by keeping unique data sets separate from each other.

Last modified

Tags

Classifications

Public