Endpoint Protection

 View Only
  • 1.  View Auto-Upgrade Settings

    Posted Oct 26, 2010 11:39 AM

    I created a group for upgrading clients from 11R5 to 11R6PM1 - the autoupgrade settings worked perfectly last night. Is there a way to view these settings or modify them if I need to? Or do I have to start the Upgrade Group with Package wizard each time to make changes? Is there a way to turn the Autoupgrade off on a group other than removing the Installation package?

    Thanks in advance - I certainly have found the posts very useful in our Endpoint environment. smiley



  • 2.  RE: View Auto-Upgrade Settings

    Posted Oct 26, 2010 11:45 AM

    You cannot stop that you can remove Installation package for that particular group then add it afterwards.

    SEPM -Clients--Select your Group--Install package



  • 3.  RE: View Auto-Upgrade Settings

    Posted Oct 26, 2010 11:55 AM

    Hopefully you did not migrate from RU5 to RU6MP1 as that's not a supported migration path. 

    From the RU6MP1 migration document:

    Symantec Endpoint Protection 11.0.6100 (RU6 MP1) can migrate seamlessly over the following:
    Symantec Endpoint Protection 11.0.6000.550 (RU6) and 11.0.6005.562 (RU6a).



  • 4.  RE: View Auto-Upgrade Settings

    Posted Oct 26, 2010 12:08 PM

    Ok.... so the upgrade doesn't work? Are there problems that crop up afterwards in the client?  We are using very minimal settings and haven't seen any issues with the clients yet...

    Servers went 11R5 -> 11R6a -> 11R6 MP1 - easily, successfully and no hiccups....  

    What was strange and why it seemed 'normal' to run to MP1 was that after the first server was upgraded, there was only the installation package for the MP1 version 11.0.6100.645. We wanted to do some testing so left the main site server at R5 (of course, no replication) for a couple days while the remote site was all updated to the MP1 version. All the updates seemed to go fine, no error messages, all seem to be updating fine.

    It wasn't until I upgraded the 2nd server to R6 MP1 that the R6a version showed up in the installation packages list. Used the same exe's and steps to upgrade both. Replication picked up properly....

    If it is expected that we will run into issues without doing a 2 stage deployment, then that certainly puts a crimp in the plans. The big issue with our deployment is finding times agreeable to the clients for the reboot necessary after deploying each new version.

    Thanks for the heads up... any ideas on what we've deployed so far?

     

     



  • 5.  RE: View Auto-Upgrade Settings

    Posted Oct 26, 2010 12:16 PM

    I have seen done many direct upgrades of clients without any issues..

    However BEST PRACTICE says you should migrate to RU6 first then RU6MP1