Troubleshooting

You can configure the components of Specops uReset to log their internal activity to a verbose debug log. The debug log allows you to follow the events leading up to the error. Debug logging is enabled by changing the relevant registry key from “0” to “1.” Additional logging will be returned by using the higher debug levels “2” or “3.”

Client

For Client debug information, see: https://specopssoft.com/support-docs/client-debugging/

Command

HKLM\Software\Specopssoft\uReset\Command\Logging\Debug
Enable debug logging for uReset PowerShell cmdlets
Default value: 0

Gatekeeper

HKEY_LOCAL_MACHINE\SOFTWARE\Specopssoft\Authentication\Gatekeeper\Logging\Debug
Default log file location: C:\Temp\SpecopsLogFiles\

Gatekeeper Admin

HKEY_LOCAL_MACHINE\SOFTWARE\Specopssoft\Authentication\GatekeeperAdmin\Logging\Debug
Default log file location: C:\Temp\SpecopsLogFiles\

Server Admin

HKLM\Software\Specopssoft\uReset\Server.Admin\Logging\Debug
Enable debug logging for the Server Administration Tool
Default value: 0

  • Was this Helpful ?
  • Yes   No