Deploying SymHelp Remotely
|Article:HOWTO84128|||||Created: 2013-05-15|||||Updated: 2013-10-30|||||Article URL http://www.symantec.com/docs/HOWTO84128|
Symantec Endpoint Protection Manager
The SEPM comes with two ways of deploying client install packages to remote systems that can be repurposed to push an executable to run on remote systems. SymHelp can be deployed in this way to remote systems but must be wrapped in a container capable of launching SymHelp and passing a command-line so that SymHelp can be configured to run silently and with the desired scan types. Also, running SymHelp in this way will cause SymHelp to run under the local System account. This can impact some data collecting as well as the comprehensiveness of Threat Analysis Tool scans that take some of their data from the user account under which SymHelp is run.
Client Deployment Wizard
For detailed steps on using the Client Deployment Wizard see…
In much the same way the utility ClientRemote.exe can be used to deploy SymHelp. This utility can be found in the following directory:
<SEPM Install Directory>\tomcat\bin
<SEPM Install Directory> = HKEY_LOCAL_MACHINE\SOFTWARE\Symantec Endpoint Protection\SEPM\’TargetDir’
Symantec Network Access Control
Symantec Network Access Control can be used to require clients on the network to run a scan and report back results. This function can be leveraged to deploy SymHelp. Contact Sales or Support for more information on this product.
Symantec Endpoint Management
Symantec Endpoint Managemet can be used to deploy and launch software on client systems. SymHelp can be used to deploy and run SymHelp. Contact Sales or Support for more information on this product.
Article URL http://www.symantec.com/docs/HOWTO84128