Endpoint Protection

 View Only
  • 1.  Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:01 AM

    Hello all,

    I would like to know if you can update the SEPM without updating all clients.  If this is possible, will someone please point me in the right direction?



  • 2.  RE: Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:05 AM

    You can, but it's not advisable. Updating the clients is easy, you don't even have to push it out, they update themselves.

    Title: 'Migrating to Symantec Endpoint Protection 11.0 RU6'
    Document ID: 2010041310404248
    > Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010041310404248?Open&seg=ent



  • 3.  RE: Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:09 AM

    The reason I need to do this if possible, is that I have clients that do not have the system resources to update to the lastest version.  Should I stay at my current version?



  • 4.  RE: Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:10 AM

    During the upgrade process the first thing you do is upgrade your SEPM...Its possible

    http://98.129.119.162/connect/fr/forums/can-sepm-mr4-mp2-server-manage-sep-ru5-client



  • 5.  RE: Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:18 AM

    But, How do I stop the auto update on the clients?



  • 6.  RE: Updating SEPM to lastest version.
    Best Answer

    Posted Oct 20, 2010 11:21 AM

    Open sepm

    click on clients

    click on install packages on the right

    delete whatever is assigned.

    that would stop



  • 7.  RE: Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:25 AM

    So easy.  I am ashamed, I had to ask.



  • 8.  RE: Updating SEPM to lastest version.

    Posted Oct 20, 2010 11:48 AM

    Keep in mind when you migrate the server, there will be no packages assigned to your groups  unless you put them there manually. If there are packages already assigned to the groups, they would be old packages and the clients would do nothing at that point since they are already running that build. You would then have to manually assign the RU6 packages in order for your clients to migrate to that build.

    If you have certain clients you don't want to migrate. Move them into their own group temorarily, then assign the RU6 package to the original group until they migrate. Once migrated, you can delete the RU6 package from the group and move the clients you didn't want to migrate back into their original group.