SharePoint Server 2019

The Microsoft SharePoint Server 2019 Management Pack is designed to be used for monitoring SharePoint Server 2019 events, collecting SharePoint component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically correlating critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage SharePoint servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, and health monitoring.

• Health monitoring of SharePoint Server 2019
• Monitors Events and Services and alerts when service outages are detected
• Monitors Performance and warns users when SharePoint performance is at risk
• Forwards users to up-to-date TechNet knowledge articles

---

Configuration file Microsoft.SharePoint.Library.MP.config

This is the configuration file for the admin task in Microsoft SharePoint 2019 Management Pack.

To run the task, save this file on the Root Management Server machine under %ProgramFiles%\System Center Management Packs

Association Element

Association element specifies account association. You can have 0, 1, or many Association elements.

• The Account attribute specifies what RunAs account to be associated. The account must exist before running the admin task. RunAs account can be created in the Administration pane of the Operations Console.
• The Type attribute may have one of two values: "Agent" and "ManagementServer". "Agent" indicates that the account applies to agent managed machines. "ManagementServer" indciates that the account applies to management servers.
• Each Machine node serves as a machine filter. Machine that matches any filter will be associated with the account in the profile.
• The Name attribute of Machine node holds a regular expression value on full machine name. Go to http: "Regex Tutorial" to learn more about regular expression. If you leave the Name attribute empty, all of machines (agent managed or management server depending on the type) match.
• For "Agent" type, discovery proxy is also enabled on the matched machines so that farm level discoveries can work correctly.

WorkflowCycle Element

WorkflowCycle element specifies the schedule of list workflows. You can have 0, 1, or many WorkflowCycle elements. But if you have multiple WorkflowCycle elements, you should avoid listing the same workflow in different WorkflowCycle elements.

• The BaseStartTime attribute can have value in the form of "HH:mm" or integer. "HH:mm" format works as the start time alignment based on which the cycle repeats. Integer format functions as setting the alignment start time to be the current time plus that many seconds. Be aware that if you set integer value, every time you rerun the admin task, the cycle start time is recalculated.
• The Length attribute specifies the length (in seconds) of each cycle.
• The Spacing attribute specifies the spacing time (in seconds) between one workflow's timeout time and the next workflow's start time.

For example, SPFarm.Discovery has timeout 300 and base start time at "14:00". If the Spacing is 60, the base start time of SPService.Discovery is set to 14:00 + Ceiling[(300 + 60) / 60] = 14:06. If you set negative Spacing, workflows may overlap and cause performance and out of memory problems.

• The WorkflowTimeout attribute (optional) if defined applies to each workflow in the cycle unless being overridden in the Script node.

If not set, current timeout values are respected.

• The Id attribute of Workflow node is a list of the discovery/monitor Id(s) separated by ';' (for the workflow).
• The MP attribute (optional) of Workflow node is for workflow not defined in the Microsoft SharePoint 2019 MP.
• The Type attribute of Workflow node indicates the workflow type. Only "Discovery" and "Monitor" are supported.
• The Times attribute of Workflow node specifies how many times the workflow needs to run within a cycle.

If you set it to 0 or negative, the workflow is disabled.

• The Timeout attribute (optional) of Workflow node if defined overrides the timeout of the workflow.