Endpoint Protection

 View Only
  • 1.  Upgrade Client With Package

    Posted Jul 31, 2014 09:33 PM

    Hi,

    I planing to upgrade my SEP client from SEP 11 to SEP 12. However I have a few doubts need so clarification.

     

    1) "Distribute upgrade over XX days" If I plan to have this upgrade run over the network over 7 days, do it mean I need to enter 7 inorder for the upgrade to be active within 7 days after I implement the policy?

     

    2) I had a mix environment of Win 7 32bit and 64bits. Do it mean I need to create 2 different upgrade policy for. 1 for 32 bits and 1 for 64 bits?

     

    3) will SEP able to identify the different OS function such as 32 bits and 64 bits?

    Hope to hear from you soon.



  • 2.  RE: Upgrade Client With Package

    Posted Jul 31, 2014 09:36 PM

    1) It means it will happen over 7 days time. This starts when the client first checks in. If you enable now, 7 days later they will be done.

    2) Yes, you need to add both 32/64 bit, the client will pull down the correct one.

    3) Yes, no problem



  • 3.  RE: Upgrade Client With Package

    Posted Jul 31, 2014 10:14 PM

    1) So I want it to happen once the client check in to the SEPM, I uncheck that option? Am I right?



  • 4.  RE: Upgrade Client With Package
    Best Answer

    Posted Jul 31, 2014 10:20 PM

    Yes, then you wouldn't set this number. I believe default is 1. Just be aware that if you set it to 0, it depends on how many clients you have but you could saturate your bandwidth quickly. Just something to think about.



  • 5.  RE: Upgrade Client With Package

    Posted Jul 31, 2014 10:24 PM

    Thks for the advise. As such, setting it to 1 day will be a better choice.



  • 6.  RE: Upgrade Client With Package

    Posted Jul 31, 2014 10:25 PM

    Correct. You should be fine then.



  • 7.  RE: Upgrade Client With Package

    Posted Aug 01, 2014 11:16 AM

    You should be careful while using this setting

     Example: If you have 2 clients and set it to distribute over 30 days, the first one will go immediately and the second will go after 15 days.

    Using Distribute Clients over X days will assign a time to each client and only allows the client to get the update at that time. If the client misses it, it doesn't get the update until the cycle starts over. Example: That client that had to wait 15 days is offline on Day 15. On Day 16, the SEPM denies the update. On Day 17, the SEPM denies again... this will continue until Day 31 when the SEPM will assign new times to the clients. Even though this is an extreme example, you can see how this could make clients take a long time to get their updates. Even on a more reasonable 2-3 day distribution, a client could miss a number of consecutive update cycles.

    https://www-secure.symantec.com/connect/forums/complete-behavior-install-packages-and-upgrade-schedules



  • 8.  RE: Upgrade Client With Package

    Posted Aug 01, 2014 01:33 PM
    Major issue which I observe was client fails to communicate after upgrade as root cause as 11.0 use port 80 for communication but after upgrade Symantec will use port 8014, as Symantec will do its configuration need to keep you manager running until upgrade complete. Second root kit issue make sure you have update the patch before upgrade Pl check this discussion for better understanding of upgrade https://www-secure.symantec.com/connect/blogs/latest-symantec-endpoint-protection-release-sep-12-ru4-mp1-12141004126