From DSM console (recommended)

1. Log in to the DSM.
2. Go to Administration tab > System Information in the tree view.
3. Click the Create Diagnostics button.

From command line

1. Log in to the machine hosting the DSM.
2. Open the command prompt.
3. Navigate to the Deep Security Manager folder.
4. Enter either of these commands:
   • • dsm_c -action diagnostic (does not include the debug.xml file)
     • dsm_c -action debug (includes the debug.xml file)
    

   Diagnostic log is found in C:\Program Files\Trend Micro\Deep Security Manager

    

From DSM console (recommended)

1. Log in to the DSM and go to the Computers tab.
2. Navigate to the computer's tree view and select the computer that you will create the diagnostics for.
3. Double-click the computer.
4. In the Overview page, go to the Actions tab.
5. Click the Create Diagnostic Package button.

From command line (Windows)

1. Log in to the machine hosting the DSA.
2. Open the command line.
3. Navigate to the Deep Security Agent folder.
4. Run the following command:

   dsa_control –d

    

   DSA log is found in C:\ProgramData\Trend Micro\Deep Security Agent\diag

    

From command line (Linux, AIX, or Solaris)

1. Connect to the server that you want to generate the diagnostic package for.
2. Enter the command:

   sudo /opt/ds_agent/dsa_control -d

   The output shows the name and location of the diagnostic package: /var/opt/ds_agent/diag

From DSM console (recommended)

1. Log in to the DSM and go to the Computers tab.
2. Navigate to the computer's tree view and select the computer that you will create the diagnostics for.
3. Double-click the computer.
4. In the Overview page, go to the Actions tab.
5. Click the Create Diagnostic Package button.

From command line

1. Log in to the DSVA. 
2. Press Alt+F2 to switch to the terminal.
3. Log in with username: dsva
4. Navigate to the /opt/ds_agent folder.
5. Run the following command:

   sudo ./dsa_control -d

    

   The command line diagnostics generation is a feature added in version 7.5. The later versions of DSA do not have this ability. There is a script on Linux called dsa-state-capture that can be run to get the Linux information, but there is none for Windows.

   You can run msinfo32 on a Windows machine if you wish to collect some information.