# Microsoft Windows Server (SP Agent)
This package is designed to monitor Microsoft Windows Servers using the ServicePilot Windows System Agent.
This package automatically configures the ServicePilot Manager to collect statistics from the Microsoft Windows Server on which the ServicePilot Windows System Agent has been deployed. The statistics gathered in this way include:
CPU and Memoryutilization, global network and disk IOs
- Storage: detailed
physical diskutilization (optional)
- Network: detailed
Interfacestatus and utilization (optional)
running Processes and Servicesand related resource consumption
The Microsoft Windows Server (SP Agent) package supports:
- Windows Server 2003 (R1/R2), Windows Server 2008 (R1/R2), Windows Server 2012, Windows Vista, Windows 7 and Windows 8.
A ServicePilot Windows System Agent must be installed on the Microsoft Window Server to be monitored. (In your ServicePilot Manager Web Interface, go to Settings > Agents, click on Install an agent first and then click on Get Started for Windows Agent. The steps to download and install the Windows Agent will be displayed.)
Network Flows - It is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure with a firewall, all of the following flows must be opened:
ServicePilot Manager Web server access (by default TCP/80 when using HTTP or TCP/443 when using HTTPS although this port is configurable): Between ServicePilot Windows System Agent and ServicePilot Manager
- ServicePilot Manager minimum version: 8.5
- ServicePilot Windows System Agent Minimum version: 8.5 installed and configured
Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager.
Add resource using Views Configuration web interface
- As an administrative user of ServicePilot, open the ServicePilot web interface.
- Navigate to Administration. The Configuration > Views web page will open.
- Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
- From the Packages list on the right of the interface, click and drag the server-microsoft-windows-sp-agent package into the View editor and let go.
- The Resource properties dialog box will open to allow resource configuration.
- Click OK to close the Resource properties dialog box. Note that the dialog box will not close if required parameters are not set.
- Click Save to apply the new resource to ServicePilot configuration.
Key field notes
In the Monitoring Policies tab, specify the policy or policies to apply to the resource
- Disks: Tick to get statistics for all disks
- Interfaces: Tick to get statistics for all network interfaces
- Processes tab:
- Processes: A multi-line text field containing one process per line. Each line consists of 4 fields that are comma (,) separated. The first field is the process Name. The second field is a process alias. If the alias field is empty then the process name will be used. Use an alias if the process Name is not unique. The third field is the process CommandLine parameter. If the CommandLine parameter is empty then it is assumed that only one process with a particular name is running. The last field is the process ExecutablePath parameter. If the ExecutablePath parameter is empty then it is assumed that only one process with a particular name is running. Following is an example:
`svchost.exe,DCOM Server Process Launcher,C:\Windows\system32\svchost.exe -k DcomLaunch,C:\Windows\system32\svchost.exe`
- Services tab:
- Services: List the names of the services to monitor, separated by commas (,)
It is posible to get a list of processes by opening a Windows Command Prompt as Administrator with escalated UAC privileges and running
wmic process|more. The process Name is 16th parameter, the process CommandLine is the 2nd parameter and the ExecutablePath is the 8th parameter.
It is posible to get a list of services by opening a Windows Command Prompt and running
sc query|more. The SERVICE_NAME field is required.