When an agent is not behaving the way its policy says it should, Skyrsoft Autologon Manager can turn on verbose logging for that one machine and read the result in the console, without remoting in or touching the machine at all. Diagnostics is off by default on every install, and turning it back off purges what was collected.
How it works
Enabling diagnostics on an agent’s own page — or as a group default — sets a flag the agent picks up on its next poll. From then on, two independent sources start logging: the credential provider writes its own logon-and-lock-screen decisions to a local file, and the agent mirrors its own activity into an in-memory buffer. On every poll, the agent tails whatever is new in the provider’s file and drains its own buffer, and ships both to the server over the same mutually-authenticated channel it already uses to check in — no separate connection and no open port on the client. The console’s Diagnostics page shows both sources live, with a download option, and disabling collection purges the server-held logs for that agent immediately.
What it contains, and what it does not
The logs record usernames and session layout — which account was being considered for auto-logon, why a tile was or was not offered, what the schedule and licence checks decided — the same categories of decision covered on hands-free Windows logon and behaviour policies. They never contain a password. Reading them in the console is restricted to the Admin role.
Limits
Diagnostics collects nothing until you turn it on for a particular agent. It is built for an agent that is already misbehaving, so there is no standing telemetry stream behind it: a production install with diagnostics never enabled writes and streams nothing extra.
The client-side log file is size-capped, and the server-side copy is capped per agent as well. Neither grows without bound; the provider’s own file truncates and rolls over locally, and the server retains a bounded number of lines per agent regardless of how long diagnostics has been left on.
Turning diagnostics off purges the server’s copy but does not reach back to the machine. The agent’s own local log file, already locked down to Administrators and SYSTEM, is left in place rather than deleted at the moment collection stops.