Video Screencast Help

Script for automating SEP 12.1.2 client installation

Created: 20 Feb 2013 | 4 comments
gmunyadzwe's picture

I am looking for a a way to automate client installation of SEP 12.1.2, such as a script. Here's how the environment is configured...

1. Single domain; multiple locations connected through WAN connections of various speeds

2. All clients authenticate at the HQ, no other servers remotely

3. All clients in the HQ installed thru remote push without any issues and are well managed thru SEPM, that is, updated and scanned per schedule


When i try to push install to other areas in remote areas, the installation takes forever, I suspect that packets are lost on the way as when I do a ping there is a timeout, but the connection then returns, making the whole process to take forever and without any luck as it ultimately times out. As an alternative, i can copy the installation package to a remote location and script the installation, the main challenge being how to go about it. I would love to keep the installation simple but with adequate functionallity:

-silent installation so that users dont zap it

-use the likes of powershell, which i have not really used much except copying it somewhere

-any other solution to meet the installation requirements.

-AD and SCOM are possibilities but are likely to cause traffic congestion 

Comments 4 CommentsJump to latest comment

ᗺrian's picture

Have you seen the Push Deployment Wizard:


Push Deployment Wizard - Standalone deployment app for SEP install packages

padding: 1px;padding-bottom: 3px ;font: 12px Arial; text-align: left;color: #666666; background-color:#f2f2f2">Article:TECH195705 padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2;"> |  padding: 0px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2;">Created: 2012-08-27 padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2"> |  padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2">Updated: 2012-10-11 padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2"> |  padding: 1px;font: 12px Arial; text-align: left;color: #666666;background-color:#f2f2f2">Article URL

You can copy to a file server at a remote site and push from there to conserve bandwidth. I use this all the time in combination with SEPPrep.

Basically, you would create a silent install package in SEPM and point the tool at it. It will than copy to the target machine and being the install.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

James-x's picture

Came here to say this.

You'll copy the tool and installation package to a computer local to the remote site. You can then push out the installation files from that remote computer to the destination computers.


The Symantec Endpoint Protection Knowledgebase

Please remember to mark the post which resolved your issue as the solution!

Chetan Savade's picture


How to upgrade a client from a non-manager server using the "Download the client package from the following URL (http or https)" option.

How to Auto-Upgrade Remote Site Clients using IIS

I hope you are using GUP at remote sites to update the definitions.

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

Rafeeq's picture

I would suggest you to follow these steps

Best practices when deploying Symantec Endpoint Protection client package over saturated 64k WAN links.
install without AV defs it will be only 40MB size
then assign a client as GUP for your remote site so that the local client can get it from GUP
What is GUP?
Or copy the package on to any of the remote site
and then use clientremote.exe to push those. |Here is the document for that