Troubleshooting

This is a simplified version of the Specops Support pages, optimized for users of Internet Explorer (version 10 and 11). To view the full version, please access this page using another browser, such as Chrome, Edge or Firefox.

Specops

uReset (7.12 and earlier)

Back to Specops website

Back to Support landing page

Search the Support site

End-of-life Notice

Specops uReset 7.12 and below has reached end-of-life. Therefore no services of any kind will be available for this product. Please migrate to uReset 8 with our migration guide.

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, read the Client Debugging page.

Command

HKLM\Software\Specopssoft\uReset\Command\Logging\Debug

Enable debug logging for uReset PowerShell cmdlets.
Default value: 0

Gatekeeper

HKLM\Software\Specopssoft\uReset\Gatekeeper\Logging\Debug

Enable debug logging for the Gatekeeper.
Default value: 0

Server Admin

HKLM\Software\Specopssoft\uReset\Server.Admin\Logging\Debug

Enable debug logging for the Server Administration Tool.
Default value: 0