Hi,

I have to install Symantec SCSP agent on some 500 odd machines inside one of the ODC.

It's very harrassing to go on each machine and run the wizard.

Is there any command which can be executed from the command prompt so that the installation does not require physical intervention during the installation.

Can we automate the process through a script ?

you can use the script or any third party tool

agent.exe /s /v”MANAGEMENT_SERVER=192.168.1.103 SSL_CERT_FILE=c:\Agent-cert.ssl
-l*v+! %temp%\SISAgentSetup.log /qn”

or

agent-windows-nt.exe /s /v”MANAGEMENT_SERVER=192.168.1.103 SSL_CERT_FILE=c:\Agent-cert.ssl
-l*v+! %temp%\SISAgentSetup.log /qn”

this is part of the installation guide.

See this

Command line syntax for silent installation, upgrade and removal of Symantec Critical System Protection 4.5

What Pete said...

I have personally used both Altiris and System Center (SCCM) to deploy the agent so it can be done!

For Windows systems I would create a bat file that has the script in it;

cd \temp

agent.exe /s /v"MANAGEMENT_SERVER=192.168.1.103 SSL_CERT_FILE=c:\temp\Agent-cert.ssl -l*v+! %temp%\SISAgentSetup.log /qn"

For Linux/Unix a sample command would be;

./agent-aix.bin -silent -prefix=/opt/Symantec -server=192.168.1.1 -cert=/var/tmp/agent-cert.ssl agentport=443

You will need to tweak it some to reflect your environment. This information in in the installation guide on pages 63 and 87.

This command is not getting executed.
I've changed the parameters as per my environment.

I believe it is being ran, remeber this is running silent. Please verify that the agent has been installed.

Still not able to run through command line.

Are you seeing any log file being generated in the location you set?  Even if its a failed install a log file will be created

You don't sasy if you are running under Windows or Linux  , but it might be helpful to tell us that. Also, as shown above the syntax is pretty critical. Below is what works for me in Windows. I have taken the -Silent switch off, which then will prompt you completely through the options for testing. Then you can simply add the silent when you get everything else working. If you don't see an error, make sure to find the install_csp.log file and see what it says as the error may not appear in the GUI, but only in the log file.

CALL D:\temp\agent.exe /s /v"/qf MANAGEMENT_SERVER=hqcsp01 SSL_CERT_FILE=D:\temp
\agent-cert.ssl IPS_POLICY_GROUP=Windows /Lv*+! %temp%\install_csp.log"

I would like to do this through powershell, can the same syntax above be used? i am using the following code.

$server = "*.*.*.*" , "*.*.*.*"

Copy-Item

"C:\software\CSP\agent.exe" -Container -recurse \\$server\c$\software\

Invoke-Command

-ComputerName $server -ScriptBlock {Start-Process "c:\software\agent.exe" /s /v"Management_Server=*.*.*.* SSL_CERT_FILE=c:\Program Files (x86)\Symantec\Critical System Protection\Server\Agent-cert.ssl

-l*v+! %temp%\SISAgentSetup.log /qn"

}

So did the script work afterall? To address your Powershell question, this would be answered by trying the above script and testing if it works.

I agree with RCMZZ, you will have to test.

To simplify, I would suggest you first quit trying to copy the file and modify your script to run everything from one directory where all files exist. After you get that working, then you could always trying adding in the copy of the file and the long file/directory names which are going to require quotes.

    One thing you have to keep in mind with scripting languages and executing commands is quotation marks. You have a path to the agent-cert.ssl file which (if you have already copied the agent-cert.ssl file to the location in the SSL_CERT_FILE= paramter is going to have a space in the file name (in more than one place). If you don't have quotes setup on the commandline for powershell you could get a syntax error. I would suggest you put the command in a batch file (.bat or .cmd) and get it working.  You may then be able to migrate to Powershell, but keeping quotation marks in mind.

  As we pointed out earlier, you will probaly want to delete , then run the command, then look at the file %temp%\install_csp.log for errors. If %temp%\install_csp.log is not getting created you are likely running into a syntax issue with the Command line (Powershell, .bat, etc...) and the command is not running.

I don't know Powershell well enough to know if you are going to have major syntax issues with the spaces in the directory names or not. I would think it could be done, but there may be extra work to make it work correctly. Good luck !