Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Microsoft Forefront Endpoint Protection 2010 (Server)

This template allows you to monitor the status of Microsoft Forefront Endpoint Protection (FEP) 2010 Server installed on a Windows machine by using PowerShell and Service monitors.

Prerequisites

WinRM must be installed and properly configured on the target server and WMI access to the target server.

Credentials

Administrator on target server.

Each PowerShell monitor uses the same argument.

For Example: S01 where S01 is the 3-character site code where FEP installed. This code you provide during installation of Microsoft System Center Configuration Manager (SCCM).

You must specify the correct arguments for each monitored component in the Script Arguments field. If you fail to do this, the monitor will return with a status error of "Undefined."

Component monitors

Click here for an overview about SAM application monitor templates and component monitors. SAM API Poller templates are also available.

Deployment Status

This monitor returns the deployment status of FEP. The returned values are as follows:

  • Deployment Succeeded – This component returns the number of computers with FEP clients deployed. The value returned should be as high as possible. You should set thresholds according to your requirements.
  • Out of Date – This component returns the number of computers for which the reported FEP version is older than the one installed at the server.
  • Deployment Failed – This component returns the current number of operations queued and waiting on a read lock. The returned value should be as low as possible.
  • Deployment Pending – This component returns the number of computers for which an active Configuration Manager software distribution advertisement is trying to install the FEP client.
  • Locally Removed – This component returns the number of computers where the FEP client was locally removed either by a user with local administrator permission or by some other software (e.g. malware). The returned value should be as low as possible.
  • Not Targeted – This component returns the number of computers in your organization to which the client software was not targeted. The returned value should be as low as possible.

Policy Distribution Status

This monitor returns FEP policy distribution status. The returned values are as follows:

  • Distribution Failed – This component returns the number of computers to which a policy could not be deployed. The returned value should be as low as possible.
  • Distribution Pending – This component returns the number of computers to which a policy is in the process of being deployed.
  • Policy Distributed – This component returns the number of computers to which a policy was successfully deployed.

Definition Status

This monitor returns the definition status of FEP. The returned values are as follows:

  • Up to Date – This component returns the number of client computers with up-to-date definitions. The returned value should be as high as possible.
  • Up to 3 Days – This component returns the number of client computers with definitions that are up to three days old. The returned value should be as low as possible.
  • Up to 7 Days – This component returns the number of client computers with definitions that are up to seven days old. The returned value should be as low as possible.
  • Older Than 1 Week – This component returns the number of client computers with definitions more than one week old. The returned value should be as low as possible.

Malware Activity Status

This monitor returns the malware activity status of FEP. The returned values are as follows:

  • Infected – This component returns the number of computers on which the FEP client software has detected active malware. The returned value should be as low as possible.
  • Restart Required – This component returns the number of computers running the FEP client software that require a restart to complete malware cleaning.
  • Full Scan Required – This component returns the number of computers running the FEP client software that require a full scan.
  • Recent Malware Activity – This component returns the number of computers on which the FEP client software detected and cleaned malware within the last 24 hours.

Health Status

This monitor returns the malware activity status of FEP. The returned values are as follows:

  • Protection Service Off – This component returns the number of computers on which the FEP antimalware service is turned off. The returned value should be as low as possible.
  • Not Reporting – This component returns the number of computers to which the FEP client has been deployed, but have not sent a status report back to the Configuration Manager server in the past 14 days. The returned value should be as low as possible.
  • Healthy – This component returns the number of computers running the FEP client software and have sent a status report back to the Configuration Manager server in the past 14 days.

Service: Forefront Endpoint Protection Monitoring

This monitors returns the CPU and memory usage of the Forefront Endpoint Protection Monitoring service. This service monitors security events from computers that are protected by Microsoft Forefront Endpoint Protection.