Endpoint Protection

We currently have Endpoint 11 RU6 MP2 installed in multiple offices and I need to update them to MP3. When we updated to MP2, the update running at night maxed out the connections to the offices and caused some serious issues (it was transferring a 100+ meg files to systems). I'm trying to avoid that this time.

What is the best way of upgrading without causing network issues, other than running a setup.exe manually? From what I understand, a GUP would not help this situation.

Thanks

You can create a new package and push it group wise one by one.

this worked on one of our such situations

https://www-secure.symantec.com/connect/forums/deploying-sep-client-installation-package-over-wan

Hello,

Correct, GUP would not update the clients with Install packages.

Do you have a webserver in local site?If yes keep the install package in that web server and you can use same URL.Refer this article

How to Auto-Upgrade Remote Site Clients using IIS

OR

Use the Auto Upgrade Method as below:

To migrate client software with additional Features on Existing Clients follow the Steps provided below:

1. Log on to the newly migrated Symantec Endpoint Protection Manager Console.
2. Click Admin > Install Packages.
3. In the lower-left pane, under Tasks, click Upgrade Groups with Package.
4. In the Welcome to the Upgrade Groups Wizard panel, click Next.
5. In the Select Client Install Package panel, all existing client packages are listed in the drop down box. Select one of the following:
   • Symantec Endpoint Protection <appropriate version>.
   • Symantec Network Access Control <appropriate version>.
6. Click Next.
7. In the Specify Groups panel, check one or more groups that contain the client computers to be migrated, then click Next.
8. In the Package Upgrade Settings panel, check Download client from the management server.
9. Click Upgrade Settings.
10. In the Add Client Install Package dialog box, on the General tab, specify whether or not to keep existing client features or specify new ones, then configure a schedule for when to migrate the client computers. Under the Notification tab, specify a message to display to users during the migration.
11. For details about settings on these tabs, click Help.
12. Click OK.
13. In the Upgrade Groups Wizard dialog box, click Next.
14. In the Upgrade Groups Wizard Complete panel, click Finish.

Note: Client computers that take a long time to automatically upgrade to Release Update 6 Maintenance Patch 1 may need to be restarted. This occurs on client computers that run Windows Vista or Windows Server 2008.  We recommend migrating clients to RU6 or RU6a before completing the upgrade to MP1.

NOTE: To get the NTP feature activated (if installed), machines may require a restart after the successful installation.

this is the procedure:

Upgrading the Symantec Endpoint Protection clients
The easiest way to migrate Symantec Endpoint Protection clients is by using the auto-upgrade feature. All other client software deployment methods are supported, but the auto-upgrade approach is the easiest way. The client migration installation can take up to 30 minutes. It is recommended to migrate when most users are not logged on to their computers.

Note: Test this migration approach before rolling out migration to a large number of computers. Create a new group and place a small number of client computers in that group for testing purposes.

To migrate client software
• 1. Log on to the newly migrated Symantec Endpoint Protection Manager Console.
  2. Click Admin > Install Packages.
  3. In the lower-left pane, under Tasks, click Upgrade Groups with Package.
  4. In the Welcome to the Upgrade Groups Wizard panel, click Next.
  5. In the Select Client Install Package panel, all existing client packages are listed in the drop down box. Select one of the following:
     • Symantec Endpoint Protection <appropriate version>.
     • Symantec Network Access Control <appropriate version>.
  6. Click Next.
  7. In the Specify Groups panel, check one or more groups that contain the client computers to be migrated, then click Next.
  8. In the Package Upgrade Settings panel, check Download client from the management server.
  9. Click Upgrade Settings.
  10. In the Add Client Install Package dialog box, on the General tab, specify whether or not to keep existing client features or specify new ones, then configure a schedule for when to migrate the client computers. Under the Notification tab, specify a message to display to users during the migration.
      • If the clients in the group run a version of Symantec Endpoint Protection previous to MR2, turn off scheduling. Scheduling is on by default when a new client install package is added to a group. If scheduling is turned on, the upgrade fails. To turn off scheduling, in the Add Client Install Package dialog box, uncheck Upgrade Schedule.
  11. For details about settings on these tabs, click Help.
  12. Click OK.
  13. In the Upgrade Groups Wizard dialog box, click Next.
  14. In the Upgrade Groups Wizard Complete panel, click Finish.

Note: Client computers that take a long time to automatically upgrade to Release Update 6 (RU6) may need to be restarted. This occurs on client computers that run Windows Vista or Windows Server 2008.

Article URL http://www.symantec.com/docs/TECH131653

Thanks. It's odd. The last time I had it go out to a maximum of about 30 systems, set the rollout for 5 days between 6pm and 4am and it still took the connection down. We started getting alerts that servers were down because packets were getting dropped on pings.