Endpoint Protection

hi

I have sepm v 11.0.4000.2295 I need update to 11.0.6 ?

can any person help me??

You firstly have to update it to the version 11.0.6005.562 RU6a

Afterwards, it's possible to update to the most recent version RU6 MP2

The latest SEPM version is RU6 MP2, however you cannot directly upgrade to RU6 MP2 from MR4, you need to upgrade to RU6a first and then to RU6 MP2.

First upgrade the SEPM to RU6a and then upgrade the clients. Then further upgrade the SEPM to RU6 MP2 and upgrade the clients to the latest version.

This is what you need to follow
 Migrating to Symantec Endpoint Protection 11.0 RU6

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

If you want to upgrade to RU6Mp2 then first upgrade to RU6 and then upgrade to RU6MP2,

few considaration before upgrade.

check the FAQ's before upgrade

https://www-secure.symantec.com/connect/forums/sepm-6

question?

if I have sep 11.0.5002.333 and sepm 11.0.4000.2295?

and if I have sepm 11.0.5? what's solve?

can I use same method for upgrade??

yes, same method

http://www.symantec.com/business/support/index?page=content&id=TECH95976&locale=en_US

ok, the last one so from 11.0.4000.2295 into 11.0.6 RU6 MP3 is not possible also ?

why Symantec makes the upgrade so hard ? I can't believe it happens until this year :-|

Hi Dushan,

From 11.0.4000.2295 into 11.0.6 RU6 MP3 is not possible.

Upgrade path would be 11.0.4000.2295 --> 11.0.6x RU6 /11.0.6x RU6a --> 11.0.6 RU6 MP3. 

hm.. the upgrade process is harder than I thought before :-|

Hey ,let me make this a bit clear People above have been saying that the upgrade is not possible, Itis not correct
Upgrade is possible, but it is NOT SUPPORTED.

This migration path is not supported.
RU6MP3 is a Maintenance patch and not a maintenance release, A MP can only be installed on the main build. You can install RU6 over RTM or MR3 or MR4MP2 but not RU6MP3.
 For that you need to have RU6
 It is not recommend to upgrade directly from RU5 or MR4  to RU6MP3

This migration path is not supported.

Possible effects after a direct upgrade to RU6MP3 from a lower version [except RU6]:
Schema Corruption.
Possible dll corruption.
Policies Corruption.
Network breakdown.
Challenges with uninstalling SEP.
So what you need Upgrade the clients to RU6 and then upgrade to RU6MP1. 

OK, I got official explanation from Mr. 2-d, according to him, it is better to wait until there is MR7 upgrade for my case, so I'll just upgrade between MR to MR and just skip the MP for simplicity reason.

source documentation for upgrade path: https://www-secure.symantec.com/connect/articles/general-supported-migration-paths-symantec-endpoint-protection-manager-sepm

Hello

I have SEPM 11.0.4202.75 that want to upgrade to lastest version.

So it required 11.0.6005.562 RU6a then RU6 MP2, what have to attention with clients during upgrade SEPM? and where to download SEPM upgrade software ?

Thanks !

All the software you download from (you need your serial number from Symantec contract to enter):

https://fileconnect.symantec.com

To upgrade just follow these documents:

Migrating to Symantec Endpoint Protection 11.0 RU6
http://www.symantec.com/business/support/index?page=content&id=TECH131653

Migrating to Symantec Endpoint Protection 11.0.6300 (RU6 MP3)
http://www.symantec.com/business/support/index?page=content&id=TECH155655

Hi,

Upgrade first to 11.0.6 /11.0.6a then to 11.0.6 MP3 (most recent built.)

Other upgrade paths are not recommended nor supported. 

Once your SEPM & all the clients upgraded to 11.0.6/11.0.6a then go for MP3.

You may have to go phase wise because to upgrade all the clients it may take some time.

Hello,

Is it possilbe upgrade all client from SEPM ? and existing serial number  match with lastest version?

Yes, you can use autoupgrade feature which is described in the migration documents:

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 may need to be restarted. This occurs on client computers that run Windows Vista or Windows Server 2008.

yes, w-d post is working for me man.