I know that 4.5 now enforces Security Descriptors. Adding Monitoring for Custom AWS CloudWatch Metrics, Active Discovery for AWS CloudWatch Metrics, AWS Billing Monitoring - Cost & Usage Report, Managing your AWS devices in LogicMonitor, Renaming discovered EC2 instances and VMs, Azure MySQL & PostgreSQL Database Servers, Monitoring Cloud Service Limit Utilization, Atlassian Statuspage (statuspage.io) Monitoring, Cisco Unified Call Manager (CUCM) API Monitoring, Cisco Unified Call Manager (CUCM) Records Monitoring, Windows Server Failover Cluster (on SQL Server) Monitoring, About LogicMonitor's Kubernetes Monitoring, Adding your Kubernetes Cluster into Monitoring, Updating Monitoring Configuration for your Kubernetes Cluster, Upgrading Kubernetes Monitoring Applications, Cisco Firepower Chassis Manager Monitoring, Interface Status Alerting and Bandwidth Utilization, VMware ESXi Servers and vCenter/vSphere Monitoring, VMware vCenter Server Appliance (VCSA) Monitoring, Windows Server Failover Cluster Monitoring, Cohesity DataProtect and DataPlatform Monitoring, Viewing, Filtering, and Reporting on NetFlow Data, Troubleshooting NetFlow Monitoring Operations, Disabling External Website Testing Locations Across Your Account, Executing Internal Web Checks via Groovy Scripts, Web Checks with Form-Based Authentication, Tokens Available in LogicModule Alert Messages, Advantages of using Groovy in LogicMonitor, Viewing Config Files from the Resources Page, Example ConfigSource Active Discovery Script, Creating JobMonitor Definitions in LogicMonitor. We've decided that a couple of the staff The Properties dialog box displays. Microsoft recommends administrator level permissions to ensure remote WMI functionality, which the Collector depends on. No. Allow Users to Run Certain Programs as Administrator. #1: Use a 3rd party Task Manager such as Process Explorer or Process Hacker. Run the Process Explorer as administrator and find the process of the service you need. Ask to be local admin on the machine.