Using Debug Tools for Dr. Sprinto

Use Dr. Sprinto’s debug tools to generate device diagnostics, review sync history, and troubleshoot screen-lock and registry issues for accurate monitoring in Sprinto.

Dr. Sprinto comes with built-in debug capabilities to help users and administrators identify sync issues, misconfigurations, and system limitations. These tools can be used to generate diagnostic data, validate agent health, and accelerate issue resolution when working with Sprinto Support.

This article explains how to use the debug tools built into Dr. Sprinto, when to use them, and what data to include when reporting issues.

---

What Are Debug Tools?

Dr. Sprinto includes the ability to:

• Generate a debug report with detailed system and sync logs

• View the last successful sync timestamp

• Validate registry or policy compliance status

• Capture failure reasons (e.g., lock policy missing, permission denied)

These debug tools are available via the agent interface and work silently in the background.

---

When to Use the Debug Tools

Use the debug tools when:

• A monitor linked to Dr. Sprinto remains in Failing state

• The agent appears installed but device status is Inactive

• You suspect system-level restrictions (e.g., registry access blocked)

• Sprinto Support requests logs or evidence from the agent

---

How to Copy the Debug Report

1. On the user’s machine, open Dr. Sprinto from the tray icon (Windows) or menu bar (macOS)

2. Look for the “Copy Debug Report” or similar option

3. Click it to copy logs and diagnostic information to clipboard

4. Paste the copied text into:

   • A plain text file (.txt)

   • Email to Sprinto Support

   • Internal ticketing system for IT troubleshooting

The debug report includes non-sensitive metadata such as sync time, errors encountered, registry lookup results, and system readiness for each check.

---

Additional Manual Diagnostics

In cases where registry access is blocked or PowerShell is restricted, ask users to provide:

• Screenshots of relevant registry paths (e.g., InactivityTimeoutSecs)

• Output from:

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System"

• Screenshots of local group policy settings (e.g., auto lock, password policy)

These can be uploaded directly as evidence for the relevant check in Sprinto.

---

Tips for Interpreting the Debug Report

Debug Output Field	Description
lastSync:	Date/time of last data push to Sprinto
registryReadStatus:	Indicates if Windows registry could be accessed
lockPolicyStatus:	Pass/fail result for screen-lock enforcement
agentVersion:	Helps confirm if the latest version is installed
error:	Lists any failure reason (e.g., denied access)

Always check if the timestamp is recent. If not, network/firewall issues may be affecting sync.

---

Sharing with Sprinto Support

When submitting a support request, include:

• The copied debug report (pasted or attached)

• A short description of the observed issue

• Device operating system and name

• Screenshot of the failing monitor (optional)