Microsoft System Center Management Pack for Windows Print Server 2016


 

This management pack monitors the performance and availability of the Print Server role running on Windows Server 2016 operating systems.

image

Details

Note:There are multiple files available for this download.Once you click on the "Download" button, you will be prompted to select the files you need.

 

image

 

The Microsoft Windows Server Print Server Management Pack monitors the performance and availability of print servers running on Windows Server 2016. In addition to monitoring the health of print servers, the management pack can also provide insight into the status of shared printers. By detecting, alerting on, and automatically responding to critical events and performance indicators, this management pack helps indicate, correct, and prevent possible operating system service outages.

Feature Summary
The management pack provides functionality to:

  • Monitor performance and Windows events
  • Display detailed monitoring data through views
  • Allow operator to manage print servers
  • Ensure correct configurations

System Requirements

Supported Operating System

Windows Server 2016

  • Other Software: System Center Operations Manager 2012 R2 or later

Install Instructions

    Please refer to MP guide.
    Note: To use the language packs, you must install the English version of the management pack first.

 

What’s in the Management Pack Guide:

 

The Windows Server Print Server 2016 Management Pack monitors the performance and health of print servers running the Windows Server 2016 operating system. This management pack highlights performance, health, and availability conditions of Windows Server 2016 that might indicate problems with print servers and shared printers.

Note:

The Windows Server Print Server Management Pack download includes management packs for the Print Server role on Windows Server 2016. The content in this guide applies to Windows Server 2016 management pack unless otherwise stated.

 

Changes in Version 10.0.4.0

· Fixed compatibility issue: some event-based workflows were not changing states on Windows Server 2016 Full.

· Fixed issue: “Windows Server 2016 Print Services Role Discovery” was throwing warning 10000 to event log if server had Print Server role disabled.

 

Supported Configurations

This management pack requires System Center 2012 R2 Operations Manager or later.

The Print Server Management Pack supports monitoring the Print Server role on the following operating systems:

· Windows Server 2016

 

Before You Import the Management Pack

Before you import the Print Server Management Pack, note the following limitations of the management pack:

· The Print Server Management Pack includes support for agentless monitoring of the Print Server role however; the tasks provided in this management pack will not work on agentless managed systems and are therefore not supported.

Before you import the Print Server Management Pack, take the following into consideration:

· If you do not install the 10.0.8.0 version of Windows Server 2016 Base Operating System Management Pack before you import the Print Server Management Pack, the import will fail, indicating that it cannot locate management packs upon which it is dependent.

 

Security Considerations for the Print Server Management Pack

You might need to customize your management pack. This section provides information about using a low-privilege account with the Print Server Management Pack for the Operations Manager.

Certain monitors, rules, discoveries, tasks, and recoveries cannot be run in a low-privilege environment or must have minimum permissions.

 

Low-Privilege Environments

The Print Server Management Pack uses the agent action account to perform discovery and run monitors, rules, and tasks. The agent action account can run as Local System or as a named account. When running as Local System, the agent action account has the privileges needed to perform discovery and run monitors, rules, and tasks.

If the action account for the agent is using a low-privilege account, you need to configure the Print Server Action Account Run As profile with an account that has the appropriate rights to access the system(s). If you do not perform this configuration, discovery, monitoring, tasks, and recoveries will not function.

To use the Print Server Management Pack in low-privilege configuration, the agent Action Account must have the following minimum privileges:

· Member of the Local Users Group

· Member of the Local Performance Monitor Users group

· Manage auditing and security log permission (SeSecurityPrivilege)

· Allow log on locally permission (SeInteractiveLogonRight)

· Access rights to the Windows Event Log

The Print Server Management Pack is supported on computers running Windows Server 2016 using low-privileged accounts. However, you must configure the agent Action Account as described in the preceding section.

Notes:

· Tasks are not supported in low-privilege configuration.

· Service-based monitors will fail in a low-privilege environment. Please, disable it in this configuration.

 

Known Issue: Some workflows may not switch back to healthy state

Issue: The following workflows may not switch back to healthy state upon recovery:
Monitors:

· Print Job: Check the printer and driver and then retry printing

· Print Job: Restart the Print Spooler service or reinstall the printer driver By Print Queue

· Print Queue: Recreate the printer port

· Print Job: Restart the Print Spooler service or reinstall the printer driver By Print Job Status

· Print Spooler: Check printer security settings

· Print Spooler: Check Windows resources

· Print Spooler: Install or reinstall the printer driver

· Print Spooler: The print spooler failed to complete a task

· Print Spooler: Recreate the port and monitor

· Print Spooler: Reinstall the printer driver check registry permissions and restart the print spooler

· Print Spooler: Restart the Print Spooler service

· Print Spooler: Restart the server or troubleshoot hardware problems

· Print Spooler: Retry printing or restart the print spooler

Alert Rule:

· Print Filter Pipeline Manager: Retry printing or restart the print server

Workaround: Enable the Windows Event Log manually and restart it.

Display Strings Known Issue: “Populate the Print Services Computer Group” discovery name and description are incorrect

Issue: The discovery name is displayed as “Populate the Print Services Computer Group”, while it should be displayed as “Populate the Print Services Role Computer Group”. The same issue is observed with the description.

Workaround: No workaround available.

Display Strings Known Issue: “Populate the Printing Instances Group with Managed Entity instances” discovery name and description are incorrect

Issue: The discovery name is displayed as “Populate the Printing Instances Group with Managed Entity instances ”, while it should be displayed as “Populate the Print Services Instance Group with Managed Entity instances”. The same issue is observed with the description.

Workaround: No workaround available.

Known Issue: Some Printer 2016 Queue attributes of the discovered printer may be empty

Issue: The following Printer 2016 Queue attributes of the discovered printer may be empty:

· Spool enabled

· Path

· Version

Workaround: No workaround available.

 

 

Comments (0)

Skip to main content