They must also supply the authentication password when running CLI commands. On Windows, when self-protection is enabled, local users cannot uninstall, update, stop, or otherwise control the agent. You can use dsa_control to configure some agent settings, and to manually trigger some actions such as activation, anti-malware scans, and baseline rebuilds. To get started with the API, see First Steps Toward Workload Security Automation. You can also automate many of the CLI commands below using the Workload Security API. The CLI can also configure some settings, and to display system resource usage. So when Technical Support asks for a diagnostic package you need to run the command directly on the managed computer.You can use the local command-line interface (CLI) to command both agents and Workload Security to perform many actions. You can produce a diagnostic package for a managed computer through the Deep Security Manager but if the computer is in agent-initiated activation (AIA) mode it cannot collect all of the required logs. From there you can send it to Technical Support. The diagnostic package is created in a zip file which is downloaded locally. opt/ds_agent/dsa_control –r Create a diagnostic packageĭeep Security Technical Support might ask you to create a diagnostic package to help them troubleshoot and diagnose your issue. & "\Program Files\Trend Micro\Deep Security Agent\dsa_control" –rĬ:\Windows\system32>"\Program Files\Trend Micro\Deep Security Agent\dsa_control" -r Linux This command will remove target agent's activation information and deactivate it. opt/ds_agent/dsa_control –m Reset the agent & "\Program Files\Trend Micro\Deep Security Agent\dsa_control" -mĬ:\Windows\system32>"\Program Files\Trend Micro\Deep Security Agent\dsa_control" -m Linux opt/ds_agent/dsa_control -m "AntiMalwareManualScan:true" Force the agent to contact the manager Windows
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |