Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Scenario 5: Using an Application and Management role server in a Testing Lab

Scenario 5: Using an Application and Management role server in a Testing Lab

Table of contents
No headers

Updated Jun 23, 2016 

A typical example of this scenario is deploying functionally identical Patch Manager servers in a production and testing environment. Deploy an additional Patch Manager server with both the Application and Management roles to test packages before you deploy them. This architecture allows you to isolate the testing environment completely from the production environment.

In this example, define a separate management group for the resources in the test environment. These resources should include the subdomain or workgroup for the environment, along with a dedicated WSUS server.

Additional Application and Management Role Servers for Testing


A similar example would be to use the additional server for a special business or perimeter network (DMZ).

Last modified