Windows - Data Collection & Auditing - Automox Agent & Remote Control Health Check

What the agent diagnostics Worklet does

This Automox Worklet™ performs comprehensive diagnostic checks on the Automox agent and remote control components, collecting configuration details, service status, network connectivity, and communication logs. The Worklet tests connections to Automox cloud endpoints, verifies TLS protocol support, checks Windows Update dependencies, and validates DNS resolution for Automox services.

The diagnostic output generates as a CSV file containing structured data about agent version, operating system details, PowerShell version, TLS configuration, Windows Update service state, endpoint connectivity test results, and timestamps for each diagnostic check. You can import this CSV into spreadsheet applications or ticketing systems for systematic troubleshooting.

Why run agent diagnostics

Automox agents occasionally fail to communicate with cloud services due to network configuration, proxy settings, firewall rules, certificate validation failures, or Windows Update service dependencies. Support teams waste time manually checking multiple system components, registry settings, and network paths when troubleshooting connectivity issues.

This Worklet automates the complete diagnostic workflow, collecting all relevant troubleshooting data in a single execution. You can deploy the diagnostic Worklet to problematic endpoints remotely, eliminating the need for interactive sessions or manual command execution. The structured CSV output provides support teams with complete diagnostic information formatted for analysis and documentation.

How agent diagnostics works

1. Evaluation phase: The Worklet collects system information including operating system version, PowerShell version, Automox agent version from registry, .NET Framework versions, TLS protocol registry settings, and Windows Update service configuration. It resolves Automox service DNS names and tests HTTPS connectivity to cloud endpoints.

2. Remediation phase: The Worklet compiles all diagnostic data into a CSV file saved to the endpoint's temporary directory. It outputs the file path and displays a summary of critical findings including connectivity test results, service status, and configuration warnings. The CSV contains timestamped entries for each diagnostic check with pass/fail indicators.

Agent diagnostic requirements

• Windows 7 SP1 or later with PowerShell 3.0+

• Automox agent installed (any version)

• Outbound HTTPS connectivity to test Automox endpoints

• Write permissions to %TEMP% directory

• Administrator privileges to read registry and service configuration

Expected diagnostic output

After the Worklet completes, a CSV file appears in the endpoint's temporary directory containing all diagnostic data. The Automox console displays the file path and a summary of critical findings. The CSV includes columns for diagnostic category, test name, result status, value or message, and timestamp.

You can retrieve the CSV file using remote access tools or another Worklet that uploads files to cloud storage. The diagnostic output identifies specific configuration problems such as disabled Windows Update service, missing TLS 1.2 support, DNS resolution failures, or blocked connectivity to Automox cloud endpoints. Support teams can use this data to resolve connectivity issues without manual endpoint access.

How to validate automox agent & remote control health check changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for automox agent & remote control health check.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as the evaluation and remediation scripts.

4. Validate remediation effects from script operations such as the evaluation and remediation scripts, then rerun evaluation for compliance.