Forrester Total Economic Impactâ„¢ study finds Edwin AI delivered a 313% ROI for composite organization.

Read more

The Windows Remediation Monitoring package provides PowerShell-based remediation for Microsoft Windows and Windows Server environments, enabling you to automate corrective actions such as process and service control, cluster node maintenance, and system restarts.

These LogicModules use PowerShell remoting over WinRM to execute remediation, surface success or failure status, and provide operational insight into process and service health and cluster availability.

Remediation actions run over WinRM using the configured credentials and execute in the context of the specified Windows user.

As of April 2026, this package is compatible with Windows Server 2012 R2 through Windows Server 2025.

Requirements for Windows RemediationSources Monitoring

To use Windows remediation monitoring, you need the following:

  • A LogicMonitor user with Manage permission for modules and resource permissions for “Remediation Source” settings.
  • WinRM and remote PowerShell are reachable from your Collector
    For more information, see Preferred Collector Management.
  • Remediation credentials are configured for Resource
    For more information, see Resource and Instance Properties.

For cluster actions, ensure the following:

  • You use a hostname (not an IP)
  • Windows Failover Clustering PowerShell components are available on the target

Adding Resources into Windows RemediationSources Monitoring

Add Windows Resources into LogicMonitor. For more information, see Adding Resources.

Note: During setup, ensure WinRM and remote PowerShell are reachable from the Collector, remediation credentials are configured, and cluster targets use a hostname with required Failover Clustering PowerShell components available.

Windows RemediationSources Properties

Configure RemediationSources behavior using the following properties:

PropertyDescriptionUsed ByRequired
remediation.processThe exact process to match on the host so the script can find and terminate or launchKill Windows Process, Launch Windows ProcessYes
remediation.forcerestartForce restart without confirmation. Default value is true. Values are true, falseRestart Windows ResourceNo
remediation.process.duplicateEnables starting a second instance of the process when one is already runningLaunch Windows ProcessNo
remediation.winrm.userWindows username for PowerShell remoting authentication. The user must have permissions to operate the task. Some tasks require administrative rights. In most cases this differs from wmi.userSuspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupYes
remediation.winrm.passWindows password for PowerShell remoting authenticationSuspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupYes
remediation.forcekillForce kill the process without confirmation. Passes -Force to Stop-Process, values are true, falseKill Windows ProcessNo
remediation.killallKill all matching processes instead of the first, values are true, falseKill Windows ProcessNo
winrm.usesslEnables SSL WinRM connectionSuspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupNo
winrm.portCustom WinRM port, default value is 5985 or 5986Suspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupNo
winrm.skiprevocationcheckSkip certificate revocation check when using SSL, default value is false)Suspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupNo
winrm.skipcacheckSkip certificate authority check when using SSL , default value is falseSuspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupNo
winrm.skipcncheckSkip common name check when using SSL, default value is falseSuspend Windows Server Cluster Node, Resume Windows Server Cluster Node, Restart Windows Resource, Launch Windows Process, Kill Windows Process, Windows Disk CleanupNo
remediation.windowstempClean Windows temp folder (for exampleC:\Windows\Temp), default value is trueWindows Disk CleanupNo
remediation.usertempClean user temp folder (for example,%TEMP%), default value is trueWindows Disk CleanupNo
remediation.tempolderthandaysOnly delete temp files older than specified days, default value is 30Windows Disk CleanupNo
remediation.iecacheClean Internet Explorer and Edge cache, default value is falseWindows Disk CleanupNo
remediation.recyclebinEmpty Recycle Bin, default value is falseWindows Disk CleanupNo
remediation.oldlogsRemove old log files, default value is falseWindows Disk CleanupNo
remediation.logretentiondaysAge threshold for log file deletion in days, default value is falseWindows Disk CleanupNo

For more information, see Resource and Instance Properties.

Import LogicModules into Monitoring

Install all Windows RemediationSources LogicModules from the LogicMonitor Module Exchange. For more information, see the list of LogicModules in Package. If these LogicModules are already present, ensure you have the most recent version of each module. 

Data collection automatically starts when the LogicModules are imported.​

LogicModules in Package

LogicMonitor’s package for Windows RemediationSources Monitoring consists of the following LogicModules. For full coverage, import the following LogicModules into your platform:

Display NameTypeDescription
Kill Windows ProcessRemediationSourceTerminates a process or service on a Windows system
Launch Windows ProcessRemediationSourceLaunches a process or starts a Windows service
Restart Windows DeviceRemediationSourceRestarts a Windows Resource via PowerShell remoting
Resume Windows Server Cluster NodeRemediationSourceResumes a suspended node in a Windows Failover Cluster and brings it back online
Suspend Windows Server Cluster NodeRemediationSourceDrains and suspends a node in a Windows Failover Cluster
Microsoft Windows Disk CleanupRemediationSourcePerforms disk cleanup operations on Windows systems by removing temporary files and clearing system temporary folders to free up disk space

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations.

Recommendation: If necessary, adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Static Thresholds for Datapoints.

14-day access to the full LogicMonitor platform