Endpoint Protection

 View Only
  • 1.  Multiple groups vs multiple locations

    Posted May 10, 2009 11:01 PM
    I'm starting to deploy SEP and have a question about designing the heirarchy. Currently I set up groups based on remote offices > desktop > laptops. On the other hand, is there any advantage of having 1 single group (or 2) and using locations based on IP address to manage policies? (mainly point towards local GUP). Currently most of my groups are not inheriting policies because I need to assign different GUPs for each location.



    I'm thinking of creating multiple locations at the root and still have groups present for each of the district office locations, but have them inherit policies from the root. With multiple locations I should be able to assign policies for them based on their IP.

    Does adding multiple locations to SEP policies make the policies bigger? Will it take longer for the client to process them.


  • 2.  RE: Multiple groups vs multiple locations

    Broadcom Employee
    Posted May 11, 2009 01:24 AM

    hi,

    though not verified by our team/me. We have set only three locations we have not seen any difference in processing and as per client policies are considered, they are hardly in KB's( if you are referring to the size).

    Pete!



  • 3.  RE: Multiple groups vs multiple locations

    Posted May 11, 2009 06:48 PM
    Thanks, anyone else have any input?


  • 4.  RE: Multiple groups vs multiple locations

    Posted May 11, 2009 07:05 PM
    I believe yes
    1. Single Group and Multiple Locations (as per the Total No. of Offices and as per IP range for each)
    2. Each Location consisting a unique Liveupdate Non-Shared Policy with a Local GUP (Group Update Provider) configured for each Office
    Thanks :)