Running Diagnostics
Last updated
Last updated
To launch the diagnostic view, select the Diagnostic Icon on the bottom-right of the console in the Endpoint Manager View.
The selected dope.swg endpoint must be put into debug mode while you run diagnostics. Click Enable Debug Mode.
On the rare occasion that a dope.endpoint goes into error, the dope.endpoint will automatically run a set of diagnostic tests to try and help understand what the problem is. When a dope.endpoint is in error on selection in the Endpoint Manager View, you can view the results of diagnostic tests by launching the diagnostic view. This will display errors like this:
In some cases it may be necessary to retrieve more detailed diagnostics from a dope.swg endpoint that is in error. With dope.swg there’s no need to bother the end user to get this information: it can all be done from the dope.cloud Endpoint Manager View.
If you click this icon a .zip file will be downloaded to your administrator’s machine. This .zip file can be shared with dope.security to help fix an endpoint issue.
Once the endpoint error has been fixed, you are ready to take the endpoint out of Debug mode. Just select the Exit Debug mode button at the bottom of the console.
When this is selected, the endpoint will come out of debug mode and the Endpoint Manager View will return to normal. You’re good to go again.
By selecting the Enable Debug Mode button , you can put the selected dope.swg endpoint into debug mode. The endpoint views background will turn blue to clearly indicate that the selected endpoint is running in Debug mode. The Endpoint Manager View status will also indicate that the selected Endpoint is in Debug mode.
When in debug mode the endpoint will run further diagnostic tests, enable deeper endpoint logging, and gather OS level logs. During this time, you will see the following icon in the diagnostic view. Once all the debug information has been gathered and has been sent to the cloud, a new download icon will appear.
