Endpoint Protection

Hi,

I've been reading many articls about SEP client upgrades and the number of different methods. I have not come across any article explaining the best method of deploying client upgrades to remote sites (meaning sites in another country, e.g. France, Spain)

I've already created client installation packages for my remote sites and attempted to deploy the upgrade. However, due to the slow WAN / MPLS links many clients have complaning of slow performance to the extent I had to stop the upgrade process and prevent any more clients being upgraded.

I'm upgrading my clients from a mixture of 11.0.7101.1056 and 11.0.6300.803 to 12.1.2015.2015

In order to successfully upgraded my clients and, at the same time, preserve their system performance over this slow link what cause of action would I need to take? Can I still use SEPM and simply create an upgrade schedule to suit?

I have tried using GPO's to deploy client upgrades and had some success but would like clarification of the best upgrade method over a slow WAN link.

Regards and Thank you   

Check this article "ClientRemote.exe" is the best solution

https://www-secure.symantec.com/connect/articles/overview-push-deployment-wizard-symantec-endpoint-protection-121

You can copy the package in one of the system at remote location and also copy the tool there. Run the tool using the above link and deploy the package on that location.

I've posted about this a couple of times, but can't seem to find any of them!

Anyhoos, for upgrading remote clients, I'd recommend using the "download package from the following url" option, available via the SEPM (article below):

http://www.symantec.com/docs/TECH97406

Essentially, this allows you to export and copy a client package to a server/machine on your remote site, make it available on a web server there, and point the clients in that remote site as this server which is local to them.

Try this

Push Deployment Wizard - Standalone deployment app for SEP install packages

if using SEPM 12.1 ru2, use the basic package.

While slightly off-topic, you should be aware of the client migration paths too, as you're upgrading from various different versions.

Essentially, the only supported upgrade path is to goto SEP12.1RU2 first, before then upgrading to SEP12.1RU2MP1 as per the below articles:

http://www.symantec.com/docs/TECH197426
http://www.symantec.com/docs/TECH204449

While my own testing seems to suggest you can jump straight to SEP12.1RU2MP1, you won't have the support of Symantec should it go wrong.

If you believe such a transition should be supported, please vote for the below IDEA (again, apologies for the off-topic post):

https://www-secure.symantec.com/connect/ideas/support-more-sep-121-client-migration-paths

Many thanks once again for all your input. There is enough feedback and information here to ensure my issue gets resolved.