Endpoint Protection

 View Only
  • 1.  Distribution Points

    Posted Jul 07, 2010 02:04 AM
    hi everyone,

    i have two branches, in 1st branch there is 25 hosts, in 2nd branch there is about 100 hosts.
    i want to use in each branch one host as distribution point...

    how it is possible and how strong PC is needed?


  • 2.  RE: Distribution Points

    Posted Jul 07, 2010 02:08 AM
    Are you planning to use SEPM for the updation or LUA.?
    For LUA refer these articles
    Configuring Distribution Center in LUA


    Installation and configuration of LUA




  • 3.  RE: Distribution Points

    Posted Jul 07, 2010 03:24 AM
    You may simply use LUA and distribute the updates to a file share over the network. Those PCs which will host those files shares don't have to be so strong in terms of hardware.
    It will be best to have at least 5GB of free disk space on those remote machines (it will increase according to the revision count you'll keep).

    You may consider randomizing the LiveUpdate schedules within sites, to decrease the load on the distribution PCs.



  • 4.  RE: Distribution Points

    Posted Jul 07, 2010 04:56 AM
    What would happen if the SEP management server is also configured as LU server?


  • 5.  RE: Distribution Points

    Posted Jul 07, 2010 06:14 AM
    You can do that using GUP ( Group Update Provider )..Normal Windows 2003 server should be enough to handle these many clients.


  • 6.  RE: Distribution Points

    Posted Jul 07, 2010 08:10 AM

    I think GUP would be a good solution also. GUPs will only distribute content updates (virus defs, ips defs, ptp defs) and will not distribute client updates. Also, if you use RU5 or later you can create GUP failover so that if a GUP is down (turned off or whatever), the group will update from the backup GUP.

    Any client can be a GUP even XP machines, but like Vikram says a server OS would be the way to go because of the connection limit. XP has a limit of 10 connections, while a server OS has umlimited.

    We use the GUP setup here, and it has helped curb our bandwidth use tenfold. Our setup is like this - the SEPM sits in our data center, and we have three locations. I setup the DCs in each location as GUPs (win2k3 boxes). The SEPM updates only the three DCs, and from there the GUPs update the machines in their group. So, if you break your groups down to subnets, bandwidth will be saved.

    In a future release GUPs will be able to push client updates as well. That would be so cool.

    The clients will still connect to your SEPM and get policy updates, but that's no big deal. Hope that helps.

    This may help as well:
    https://www-secure.symantec.com/connect/articles/tips-installing-sep-low-bandwidth-environment

    Mike