Endpoint Protection

 View Only
Expand all | Collapse all

Out-of-Date definitions will NEVER be "0"

olek kolor

olek kolorFeb 18, 2019 03:38 PM

olek kolor

olek kolorFeb 22, 2019 09:54 AM

John Owens

John OwensFeb 22, 2019 01:14 PM

olek kolor

olek kolorFeb 22, 2019 02:03 PM

  • 1.  Out-of-Date definitions will NEVER be "0"

    Posted Feb 07, 2019 06:20 PM

    I have been working with Symantec for a number of years now and our company has had Symantec products for well over 10 years, dating back to the days when we had Symantec Antivirus.

    I've come to learn lots, get frustrated a heck of a lot, bang my fists on my table, and throw small things (like pens or pencils) because something with Symantec isn't working right.

    For the last 3 days I've been fighting with our SEPM console because I keep looking at our Endpoint Status on the main page, where it tells me that 523 devices are out of date.  3 days ago this was 822 devices, and I had no clue why.  It didn't just happen overnight, it's been an ongoing battle for several years.  I got it down to 523 after re-installing from a pre-defined package but this was done by trial and error, and seemed to work.

    Over the years I've upgraded version after version and on occasion, the number would fluctuate up and down, and it would never stay constant.  This is because I've come to the conclusion that there are way too many factors causing out of date definitions.  Machines are sometimes out of drive space, local firewalls are sometimes enabled and SEP can't communicate through the firewall and SEP won't install, or the definitions are corrupt.  Who makes a product like this????

    I've run the SymDiag tool many times, where it collected information about the SEPM console, and each time I ran it, it would find corrupt definitions, and when  clicking "FIX" it would never fix it even after several attempts.  Point here is, that no product created professionally would ever self-corrupt files.  I know it's not intentional, and depending on network conditions, it should never happen, but it does and it's bloody frustrating when it does happen and sometimes I can't seem to fix it.

    When we had a problem installing SEP 14.0 on a Windows 2013 server, we called Symantec who called back, did a remote connection to our computer, installed and uninstalled, rebooted, installed again, and every time we tried installing 14.0 on the server, it simply would not install.  In the documentation however, it says that SEM 14 is compatible with 2013 server, but obviously in our case it was not.  So that made us scale down to Windows server 2012, where installation occurred flawlessly, but Symantec Support did not help us discover this.  I discovered it on my own.

    We have over 3500 devices in our network and today I sit here with 2910 that are up to date, 523 that are out of date, 70 that are offline, and 355 that are in a "Disabled" state, whatever that means.  To date I have never actually been able to figure out why a device is out of date, if all I did was install SEP normally from the SEPM console.  Why would software do this?  Why would Symantec make a product so inferior to today's standards and put us through this agony?

    The SEPM console is a logistical nightmare.  I can never find out where something is, and I always have to resort to looking back on the SEP forums for help.  All I See are SEP representatives quoting links to more information without trying to respond to the question someone asked.  I hate this kind of support with a passion!  This is not good customer service.  I think the reps on the forums are getting so frustrated with so many customers having so many problems, they simply do not want to take on another issue to explain in plain English to someone who can't understand their software, and simple responses have only links to other forum conversations. 

    When I have an emergency sitation on my hands, a colleague will say, "Call Symantec Support" and I just CRINGE when I hear this suggestion.  I absolutely without a doubt, despise the Symantec telephone support.  I know that all the phone support reps mean well, but I can't understand half of them because of their heavy Indian accents, and some don't really know the product well enough to troubleshoot our issues.  This comes from outsourcing to call centres in India to save a few bucks.  Nobody wants to say it, but I am simply stating a fact.

    Lately we've been looking at cloud-based alternatives to SEP, and something that doesn't have so many configuration options.  I think shortly we'll be switching products if Symantec can't get their act in gear and make this easier for us, and make a product that simply WORKS.  As a matter of fact, I believe we will be using another product by the time our next renewal is due.

    I hope some day soon I will never have to look at the SEPM console again.  My anxiety level goes sky-high every time I have to look at it.  I can't wait for the day  I never have to look at it again.

    Respond if you feel this way too and want to add your two cents.  Maybe Symantec will look at this and say, "Hey guys, we really need to change our product".  Given enough people who complain, something must be done, and soon!

    Is everyone readng this 100% completely satisfied with Symantec Endpoint Protection?



  • 2.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 08, 2019 09:39 AM

    I agree with you .I use SEP only as Firewall to my computer.And version 12 block well ports .The Version 14 passing my 2 ports.Port 1032 and 1033 cannot be blocked --VPN at logs

    Opened case two times .Support Outsourcing from India .My English is not good but I have problem understanding what this people in India saying.

    Totally his knowledge about Symantec Firewall is small .I think Symantec reduce cost and this service go down

    India service said me this words " Don't worry we can help you sure,sure I can help you of course I can help you .After 1 month they put this issue to another country.

    Only answered is Symantec cut cost of service and we can see that a lot of case and problem with Symantec.

     

     

     



  • 3.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 11, 2019 01:14 PM

    Dan43, I whole heartily agree with you. I thought that one of our team members had posted this information, because it is almost 100% what we are encountering! I'm on the Architecture and Engineering team with over 25 years of IT experience. Unfortunately this product was chosen for us, so there was not a chance to research the product. We paid to have a SEP consultant come to our facility to help integrate it into our environment. We have over 10,000 desktop client systems - not mentioning the servers that have this suite of products loaded upon them as well. Our Server Operations team are seasoned professionals with much background experience supporting antivirus softwares on an enterprise level. We have had the SEP training classes from their trainers, and so are well versed with how to support the product before calling support. (I have to state/defend that their trainers were great)

    I blabbed on providing this information to help make a point that there is a serious issue with this software. We have had professional services install the product for us. We just had a SEP health check because management was concerned that we had something misconfigured. It all checks out fine to Symantec. Yet despite this, we battle keeping our SEP clients definition files up to date. In everything that you started, we have seen and are fighting. Even with freshly images systems... one of the issues we see on occasion are that the definition files are corrupt?!

    If we hear "Run SymDiag" or "rebuild your SEP Server" one more time as an alternative - we're gonna blow! 

    The SEPM interface is the worst I have EVER seen. This dates back to the mid nineties where I started in the business.

    I think I've posted once in my professional career. This will the second time... just to provide a reference to Symantec how bad their product truely is. I hope that this comment may help you, Dan43, in knowing that you are not alone and you are not doing anything wrong. Hopefully it may serve as a warning to those companies that are considering purchasing this suite.

    Pssst, I'll tell you a secret - Don't do it!



  • 4.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 12, 2019 11:36 PM

    SEP is undergoing a major modernization of its management console. If you'd like try the new cloud-based version of SEP 15, you can get the account creation link from FileConnect.

    Adam



  • 5.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 15, 2019 07:49 AM

    Do not forgot modernize and close 2 ports Port 1032 and 1033 cannot be blocked --VPN at logs .Or just release version for invidual station as I use.

    Fix close 2 ports.



  • 6.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 15, 2019 04:18 PM

    @adamli9:

    Are you kidding me?  We want to get away from Symantec, not create more problems for ourselves with "new" Symantec strategies.  I said all of that out of the sheer amount of frustration Symantec Endpoint Protection causes my company and myself as a SEPM administrator.  I still stand by my words.

    @olek kolor:

    I have no idea what you're talking about.  Sorry man.

     



  • 7.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 16, 2019 01:36 AM

    I have SEP firewall as my individual protection as Norton Symantec.I create rules where Firewall can not block all ports .Just has hole .

    Fixing this issue by support is as talking with Monkey .

    Support open case which is open 1 month

    Support from India

    Do you understand my issue

    Symantec can not block all ports .Because passing 2 ports --VPN

    ###############

    Dan as I understad you have just claim and you regret Symantec behavior that bad .You just can have chose look for any diffrent product on the market .

    Symantec just is neglect .I sent dozens eamil for help to Symantec.Nobody help me with my issue .

    Look for new solution on the market or just wait maybe Symantec will change they face.

     



  • 8.  RE: Out-of-Date definitions will NEVER be "0"

    Broadcom Employee
    Posted Feb 17, 2019 03:25 PM

    @Dan43

     

    If you would like to open a case and send me the case number I would be happy to assist you with your issues.  With software like AV there are many factors as to why a system will not update with many being environmental and not product related.  Let me know if you would like to proceed.

    Thanks,

    John



  • 9.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 10:18 AM

    Yes John I think he will be happy assisting by you .!!!!
    In the meantime may you tell your Team about My issue Firewall can not block 2 ports Just passing it .That situation is not acceptable.

     

    Port 1032 and 1033 cannot be blocked --VPN



  • 10.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 10:22 AM

    John I think he will be happy by your assisting .

    May you look for my issue.



  • 11.  RE: Out-of-Date definitions will NEVER be "0"

    Broadcom Employee
    Posted Feb 18, 2019 10:51 AM

    @Olek Kolor

    What was the case number you had with support?  Any port should be able to be blocked with a correct rule in place.  I have not heard of ports not being blocked when a FW rule to block it is in place.  What generally happens is their is a rule in place above the block rule that specifically allows the traffic...

    John Owens



  • 12.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 02:15 PM

     

    I use unmanaged Firewall SEP for protect my own computer.Firewall worked well at Version 12 but version 14 has some problem .Generally I have only one rule

    Block all incoming IP/TCP

    And application as Browser firefox  ,Skype for ASK !!

    But Firewall pass me 2 ports 1032 and 1033 TCP .Scanner online see this ports .Firewall pass it

    At log I have see it as  pass VPN .

    Firewall has embedded at code rule pass this "VPN"

    For Business may be it is ok but for my individual station is danger .Anyone can attract me this 2 remote ports

    SET Team should fix this or release version for Individual client ??

    Open case is number case # 28429089

    Why people complain ?

    India support has strong English accent

    low knowledge about Symantec Firewall

    Hold case and after 2 week put for high lever !!

    ##############

    """Dan""" completely I understand his situation .Big business and product which cost big money not works as should .Totally I understand his behavior .

    I believe Symantec will has never lost his reputation.



  • 13.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 03:13 PM

    1.You block all incoming traffic

    2.You allow appliction as Firefox go out for ASK !!!

    3.You see all ports are blocks .

    You do somthing wrong .

    This issue is confirm by Symantec support

    Buddy don't smile from my I use symantec more then 6 years

     



  • 14.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 03:16 PM

    Check her scanner online enable ports scaner detection

    https://www.grc.com



  • 15.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 03:34 PM

    I know what I'm saying .This issue is conformed By India support and Polish support .

    .Don't father teach how to children do

     



  • 16.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 18, 2019 03:38 PM

    You are clever then Symantec Support.



  • 17.  RE: Out-of-Date definitions will NEVER be "0"

    Broadcom Employee
    Posted Feb 19, 2019 02:06 PM

    Hi All,

    Let's try to keep it professional in the forums.  I am looking into this.

    Thanks,

    John



  • 18.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 22, 2019 09:54 AM

     John and answers with my case ?



  • 19.  RE: Out-of-Date definitions will NEVER be "0"

    Broadcom Employee
    Posted Feb 22, 2019 01:14 PM

    Do you have a case number?

     



  • 20.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 22, 2019 02:03 PM

    Open case is number case # 28429089



  • 21.  RE: Out-of-Date definitions will NEVER be "0"

    Broadcom Employee
    Posted Feb 22, 2019 03:02 PM

    Thank you. It looks like your case was misqueued. I sent it over to the Advanced Teams manager and he is getting everything sorted out. You will have someone contact you shortly to continue on with the case.

    Sincerely,

    John Owens



  • 22.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Feb 26, 2019 04:43 AM

    John If I have a company I just be bankrupt.Wher your team work at US or on the moon .No movement no answers .No help nothing



  • 23.  RE: Out-of-Date definitions will NEVER be "0"

    Posted Mar 12, 2019 03:41 PM

    John I'm very confuse .The Polish support create my file.exe for my as unmanageable firewall which will be block this 2 ports VPN .This is unauthorized copy. Why Symantec do not release unmanageable firewall for client.
    John what to do .??   .I can't install this file .I don't know waht is inside ??