Endpoint Protection Small Business Edition

 View Only
  • 1.  What updates SEP SBE.Cloud on Windows Servers?

    Posted May 24, 2015 08:22 AM

    I have one Windows 2012 server that is running Protection Version sep-12.1.2015.2015 of Symantec Endpoint Protection, and I have several Windows 2008 R2 servers running sep-12.1.4013.4013.  Granted, I installed this software at different times on these servers.

    sep server.JPG

    But I don't see any control in the software on the agent installed on the server, because clicking "Check for Latest Software" doesn't do it.

    And I don't see anything in the Partner Management Console that controls this, nor do I see anything on the pages of hostedendpoint.spn.com.

    What I would like to know is how does the 2015 version get updated to 4013?  And how does the 4013 version get updated to any later edition?

    Thanks!



  • 2.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Broadcom Employee
    Posted May 26, 2015 03:09 PM

    Hi,

    Thank you for posting in Symantec community.

    Check policies --> System polices --> Default System policies --> Liveupdate Schedule

    Make sure it's not disable.

    SBE_0.jpg



  • 3.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Broadcom Employee
    Posted May 26, 2015 03:24 PM

    Also at client machine can click on check for latest software.

    See the screenshot.

    SEP verison.png



  • 4.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Posted May 26, 2015 04:41 PM

    The server in question is using the Default policy (as are all of the desktops), so LiveUpdate is most definitely enabled.

    I have clicked the "Check for Latest Software" button and have been informed that everything is up to date.

    sep server1.JPG

     

     



  • 5.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Broadcom Employee
    Posted May 27, 2015 02:53 PM

    As you know if we compared both the screen-shots there is only one difference i.e. cloud agent version.

    I tried to check with SEP.cloud team as well, we don't have specific control over the deployment. So you may see different versions at different Server operating systems.

     



  • 6.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Posted May 28, 2015 11:58 AM

    I took the screen shots on different days; that is what accounts for the different cloud agent versions.

    However, I am not talking about that!

    I am talking about the Protection Version, in this case: SEP-12.1.2015.2015.

    Are you suggesting that because this is Windows Server 2012, the software will never be upgraded to 12.1.4013.4013 - or later?

    I would like some clarification, please.

     



  • 7.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Posted Jun 01, 2015 09:43 AM

    Antivirus engine for all server operating is SEP 12.1.4013.4013. On your 2012 server Antivirus engine is SEP-12.1.2015.2015, which is old version. We need to upgrade antivirus engine to latest one.

    To upgrade to latest version, we have three methods.

    1. Under about we have option to check for latest version. (In your case it failed to upgrade )

    2. Second option is to remove service from Hosted Portal under computer. This option will uninstalled SEP engine. after reboot. Please check the server listed in Computer status with "View Computers With No Service" from it add services on it.

    3. Uninstalled and reinstalled SEP.cloud client.

     

     



  • 8.  RE: What updates SEP SBE.Cloud on Windows Servers?

    Posted Jun 02, 2015 07:31 AM

    Those three responses are what I have heard very often while working with this product for the past few years.

    However, what is missing from option 1 is finding out WHY it failed.  Is there a log I can review to see if there is something getting flagged?  Are there diagnostics that can be run so that when I click the Check button someone from the back-end can view what is happening?  Is there ANYTHING that can help fix this before resorting to option 2?

    This is a server, not a desktop, so scheduling a day and time to reboot is already fixed by contract.  If option 2 fails - and it has in many cases on desktops - I am going to have to reboot to remove the software altogether, and then run the clean utilities and reboot twice more.  And then I am going to be using option 3.  I am also going to have to devote several hours to get all of this accomplished.

    As I have stated in other posts, I have alot vested in this product; therefore, I want it to improve.  So I would like to know how best to identify what ails it, rather than patching around it.  Otherwise, I'll be forced to find another vendor with a product that doesn't have a list of problems that recur without vendor-provided solutions.