Endpoint Protection

 View Only
Expand all | Collapse all

Enable LiveUpdate

Migration User

Migration UserMay 07, 2011 03:20 PM

Migration User

Migration UserMay 11, 2011 11:33 PM

  • 1.  Enable LiveUpdate

    Posted May 06, 2011 04:02 PM

    I'm sure this has likely been addressed ad nauseum here, but my search skills are fried at 3 on a friday...

    We have Endpoint Protection 11 and are wondering what configuration setting needs to be changed on the management server install to allow workstations to be able to use the liveupdate feature when not in office.

    Everything I am trying is not changing the fact that the liveupdate button is greyed out on the workstation installs.



  • 2.  RE: Enable LiveUpdate

    Posted May 06, 2011 04:20 PM

    Enable Location Awareness, and create a non-shared policy for your remote group. Select the setting "Use a LiveUpdate server" as shown in the screeenshot.

     



  • 3.  RE: Enable LiveUpdate

    Posted May 06, 2011 04:40 PM

    What I did was to create two locations, "in office" and "out of office" that I configured based on known range of ip addresses (if in the range of known internals then in office, otherwise out).

    Then created LiveUpdate policy to allow both connection to Windows Live Update server AND Liveupdate.



  • 4.  RE: Enable LiveUpdate

    Posted May 06, 2011 05:03 PM

    Edit the "Out of Office" location and make the requirement

    When SEP clients cannot connect to SEPM ( this will come after you select SEP clients can connect to SEPM)

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



  • 5.  RE: Enable LiveUpdate

    Posted May 06, 2011 05:25 PM

    Once "Use a LiveUpdate server" is selected, you will get additional options to configure under Schedule (to set a schedule) and Advanced Settings (to enable the LiveUpdate button that you mentioned is currently greyed out).

    sandra



  • 6.  RE: Enable LiveUpdate

    Posted May 06, 2011 05:38 PM
      |   view attached

    I just finished installing symantec endpoint protection and I'm unable to start the Manager service. Does anyone know how to fix this issue.



  • 7.  RE: Enable LiveUpdate

    Posted May 06, 2011 09:49 PM

    check if you are able to start the symantec manager service; frm services.msc

    under the symantec manager folder you will see logs folder; paste the scm-server0.log

    check if u r default app pool is started in IIS



  • 8.  RE: Enable LiveUpdate

    Posted May 07, 2011 03:18 AM

    Failed to connect to the server

    * Type of database ? SQL/ Embedded?

    * Multiple website hosted in the IIS ?

    * Endpoint management service does not start at all  or doed not stay started ?

    * Event viewer shows Semsrv error : Java1 ? or Java -1 ?

     

    If java-1 click the link below

    http://www.symantec.com/business/support/index?page=content&id=TECH104318&actp=search&viewlocale=en_US&searchid=1304752295508

    If its Java 1 then try this

    In order to resolve this issue, you must either change the port that the conflicting application runs on, or alter the Tomcat port.

    To alter the Tomcat port, following these steps:

    1. Ensure that the Symantec Endpoint Protection Manager service is stopped.
    2. Right-click the server.xml file and click Edit to modify the file:
      \Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\conf\server.xml

      For conflicts with port 8005, change the port to another unused port:
      port="8005"

    3. So change 8005 to 8006

      For conflicts with port 9090, change the port to another unused port:
      port="9090"

    4. Save the changes to the "server.xml" file.
    5. Start the SEPM service.
    6. Attempt to login to the SEPM.

     

    Cheers

    Gersh

     

     

     



  • 9.  RE: Enable LiveUpdate

    Posted May 07, 2011 03:20 PM

    any update ?



  • 10.  RE: Enable LiveUpdate

    Posted May 09, 2011 03:24 PM

    Here is the log file. What I am i looking for?

     

    2011-05-06 19:17:18.140 SEVERE: ================== Server Environment ===================
    2011-05-06 19:17:18.140 SEVERE: os.name = Windows Server 2008
    2011-05-06 19:17:18.140 SEVERE: os.version = 6.1
    2011-05-06 19:17:18.140 SEVERE: os.arch = x86
    2011-05-06 19:17:18.140 SEVERE: java.version = 1.6.0_14
    2011-05-06 19:17:18.140 SEVERE: java.vendor = Sun Microsystems Inc.
    2011-05-06 19:17:18.140 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2011-05-06 19:17:18.140 SEVERE: java.vm.version = 14.0-b16
    2011-05-06 19:17:18.140 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2011-05-06 19:17:18.140 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2011-05-06 19:17:18.140 SEVERE: java.user = null
    2011-05-06 19:17:18.140 SEVERE: user.language = en
    2011-05-06 19:17:18.140 SEVERE: user.country = US
    2011-05-06 19:17:18.140 SEVERE: scm.server.version = 11.0.6300.803
    2011-05-06 19:17:20.859 SEVERE: ================== StartClientTransport ===================
    2011-05-06 19:17:20.906 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 500 Internal Server Error, URL: http://localhost:8014/secars/secars.dll?action=34
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:626)
     at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:147)
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
     at org.apache.catalina.core.StandardService.start(StandardService.java:450)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
     at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
     at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:650)
     at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:147)
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
     at org.apache.catalina.core.StandardService.start(StandardService.java:450)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
     at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
     at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
     



  • 11.  RE: Enable LiveUpdate

    Posted May 09, 2011 03:26 PM

    Gersh,

    I did try the follwing steps above, but this didn't work. I been breaking my head all week trying to figure this out.

    please let me now if you have another solution...

     

    Thanks,

    Marcus



  • 12.  RE: Enable LiveUpdate

    Posted May 10, 2011 09:56 AM

    Try to repair on Add Remove but please make sure to backup the database.

    Please check dependencies services, if running



  • 13.  RE: Enable LiveUpdate

    Posted May 10, 2011 09:57 AM

    Cause

    IIS is set to 32 bit mode on Windows Server 2003 64 bit operating system when installing Symantec Endpoint Protection Manager.

    Solution

    Switch IIS to 64 bit mode per Microsoft KB document: http://support.microsoft.com/kb/894435

    Restart the Symantec Endpoint Protection Manager service after following the Microsoft procedure.
     


  • 14.  RE: Enable LiveUpdate

    Posted May 10, 2011 04:17 PM

    Thanks for all your help Gersh.. This worked. I'm able to login to the console now. You're the best... 



  • 15.  RE: Enable LiveUpdate

    Posted May 11, 2011 11:32 PM

    Cool, Thanks for the Update.

    Please don't forget to mark your thread solved with whatever answer helped you :)
     

    Cheers
    Gersh

     



  • 16.  RE: Enable LiveUpdate

    Posted May 11, 2011 11:33 PM

    Cool, Thanks for the

    Cool, Thanks for the Update.