Endpoint Protection

 View Only
  • 1.  Sep 14 MP2 Locations

    Posted Aug 23, 2017 04:59 AM

    Hello all, 

    I am thinking about using quite a lot of different locations on a client due to a specific needs of their infraestructure. I have read a TN (https://support.symantec.com/en_US/article.TECH97369.html), in which says that SYM does not recommends to create more than seven locations per group. 

    Note: Symantec does not recommend more than seven (7) locations per group when using Location Awareness. Exceeding this number can negatively affect the execution time on how long it takes the Endpoint Protection client to process and ultimately connect to a valid location when it meets all conditions.

     

    In my experience, I have used a maximum of four locations for a group. Does anyone have experience using more than seven locations? Do you really notice the execution time badly affected?

    In my environment I do not mind to check the location once per hour or even longer. 

     

    Kind regards,

     Juan

     



  • 2.  RE: Sep 14 MP2 Locations

    Posted Aug 23, 2017 06:45 AM

    Yes. I've used up to 11 for various reasons.

    What to look out for is when you have a policy with a lot of exceptions (hundreds). SEP will parse and load the serdef.dat file each time the client switches to a different location or if you make additions to the policy. This can cause a high spike in CPU, causing the client to hang. It's rare, but, it can happen.