Browse Troubleshooting
- Dashboard overview
- Insights overview
- Sites Overview - Network Deployments
- Policies Overview - Create and Edit
- Custom Lists overview
- Clients Overview - Device Agents and Profiles
- Users Overview - Directory Users and Personas
- Organizations Overview - MSP Tenant Management
- Lookup Tool Overview
- Query Log Overview
- Settings Overview - Account Administration
- Help & Support Overview
- Signing In - Login, 2FA, and Password Reset
- Two-factor authentication (2FA)
- Add system users (role-based access)
- Check domain classification with the Lookup Tool
- Configurable objects and their associations
- Configure notifications
- Working with organizations (multi-tenant)
- Working with policies
- Content categories
- Security categories
- Application categories (Zero Trust app management)
- Working with allow and block lists
- Zero Trust TLD Filters
- Safe Search explained
- Safe Search supported search engines
- YouTube Restricted Mode explained
- Custom block pages
- Prevent DNS bypass
- Don't mix DNS providers
- Active Directory group policies
- Entra ID group policies
- Tracking individual users
Windows Client Diagnostic Tool
Collect diagnostic data for the ScoutDNS Windows agent: run a baseline and post-issue capture, then send results.yaml and agent.log to support.
The ScoutDNS Windows Client Diagnostic Tool collects system and configuration data from a Windows device running the agent. Output goes to a results.yaml file you send to support. The tool is silent, fast, and safe to run on production devices.
When to run it
For the most useful capture, run the tool twice on the affected device:
- Baseline, while the agent is working normally. This gives support a known-good reference state.
- Post-issue, as soon as the issue is detected, ideally before disabling the agent. Capturing the agent in its broken state preserves the symptoms.
The diff between the two captures is what makes root cause obvious in most cases.
Download
Run the tool
From a local PowerShell window
.\scoutdiag.exe -silentHeadless (remote or background)
For RMM or remote sessions where you don’t want a window to appear:
Start-Process -FilePath ".\scoutdiag.exe" -ArgumentList "-silent" -WindowStyle Hidden[!NOTE] The tool runs as the current user. If the agent is running as
LocalSystem(the default), some agent-side data may not be readable by a non-admin shell. Run as administrator when possible.
Files to send support
| File | Location | What it contains |
|---|---|---|
results.yaml |
Same directory as scoutdiag.exe |
The diagnostic capture: agent state, OS info, network config, resolver health |
agent.log |
C:\Program Files\ScoutDNS\Device Agent\agent.log |
The agent’s own log over time |
Attach both files to your support ticket. If you have the baseline + post-issue pair, label them clearly.
Common pre-ticket checks
Before opening a ticket, a couple of quick checks resolve a surprising share of “DNS failure” reports:
- Forwarding domains, confirm the profile’s Local Forwarders match the device’s actual local DNS needs. A missing forward zone for a corp domain shows up as DNS failure on internal resolutions.
- Upstream connectivity, occasional upstream resolver failures appear in the log but don’t necessarily mean ScoutDNS is broken. The agent’s fail-open behavior protects the user; check whether real DNS resolution is actually failing on the device or only certain queries.
Summary
- Download
scoutdiag.exe - Run it once during normal operation, then again after any issue
- Send
results.yamlandagent.logto support, plus a description of what the user saw and when