This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Central: More actions: Diagnose (create SDU) has lack of documentation

Why is this the documentation for this feature so bad?  "Diagnose: This diagnoses potential issues with the computer." That's all.

docs.sophos.com/.../DeviceDetailsComputers.html

I'd expected, I could get this file somewhere centrally without the need to collect this on the endpoint. Now I read in the forums, that this uploads a file to Central and only supoort can access it there, after I created a case and mention the file name.

Can I pick this file somewhere on the client or download it via central live response or whatever?



This thread was automatically locked due to age.
Parents
  • If you run "Diagnose" from Central, it will leave the zip file in the system user's temp directory, e.g. \windows\temp\.. I believe the zip is in a sub-folder under \windows\temp named "sdu-<pid>".  You could grab that yourself with what ever agent or C$ access you might have to the computer.

    "C:\Program Files (x86)\Sophos\Sophos Diagnostic Utility\sducli.exe" is essentially what gets called and sduconfig.xml is the config which defines the files to collect and commands to run.  So you could run that through whatever means you may have.

Reply
  • If you run "Diagnose" from Central, it will leave the zip file in the system user's temp directory, e.g. \windows\temp\.. I believe the zip is in a sub-folder under \windows\temp named "sdu-<pid>".  You could grab that yourself with what ever agent or C$ access you might have to the computer.

    "C:\Program Files (x86)\Sophos\Sophos Diagnostic Utility\sducli.exe" is essentially what gets called and sduconfig.xml is the config which defines the files to collect and commands to run.  So you could run that through whatever means you may have.

Children