Endpoint Protection

 View Only
  • 1.  test

    Posted Sep 02, 2016 02:46 PM

    test



  • 2.  RE: test

    Posted Sep 02, 2016 02:51 PM

    What's up?



  • 3.  RE: test

    Posted Sep 02, 2016 02:52 PM

    Not sure if this will make it, was trying to start a new discussion and got this

    Access Denied

    You don't have permission to access "http://www.symantec.com/connect/node/add/sc-forum?" on this server.

    Reference #18.e5600c50.1472842238.12063f18

     

    This is what I was originally trying to post, and still cant for some reason

    I have an odd situation, a bit hard to explain. We manage several remote partner companies. Most have a local SEPM, some are managed by a SEPM in our office. We have 4-5 servers, where the client software stops getting defs regularly. In the case of SEPMs, the other clients that are managed are not affected, they stay current of defs. It just wont update itself.  When we see that the server's SEP client is out of date, nothing we have tried on them to update (LU, manually download defs...) works. If you try to stop the service (start smc -stop), the service hangs at the stopping phase and will never fully stop. Only a reboot will clear that, as far as what we have found. Once the system is rebooted, the service is started, and defs are up to date once again. A few days later it will occur again. This is only on server 2012 R2 servers. All are the office DC, most are running a local EPM for their office, though one is not running SEPM, but is managed by our SEPM. They are all set to go to their SEPM firswt for defs. Any suggestions?

     



  • 4.  RE: test

    Posted Sep 02, 2016 02:53 PM

    Have you run SymDiag first to see what it shows? What version are SEPM/clients on?



  • 5.  RE: test

    Posted Sep 02, 2016 03:18 PM

    Yes, just did on one. Doenst really show anything at a glance that points to an issue. Part of it is due to the fact that i am in the middle of trying to update the client and move it off to our SEPM here and it needs a reboot. Will run one on our central SEPM, though it only has the 1 client out of a thousand or so clients, including 10 servers, that is having this issue



  • 6.  RE: test

    Posted Sep 02, 2016 03:39 PM

    We have one on 12.1.6 MP5, for both SEPM and client, the others are in  12.1.6 MP4 for SEPM, with 12.1.2 clients. The one on MP5 we tried updating to that to resolve this issue. Gonna try ripping off the clients and reinstalling with 12.1.7004.xxxx



  • 7.  RE: test

    Posted Sep 02, 2016 03:41 PM

    on the central sepm, the Symdiag returned only 2 red X's. "some of the endpoint protection client features are disabled" and "the windows autorun feature is enabled



  • 8.  RE: test

    Posted Sep 02, 2016 03:42 PM

    12.1.6 MP5 is 12.1.7004. Just an fyi but the build number is misleading.