Intel,Altiris Group

I installed RU5 today and have noticed a change in the Group Updater section.  There is now a selection for Multiple Group Update Providers.  Looks like you can add more then one GUP per location or can it be used to add all your GUP's based on the rules so you only have to deal with one Live Update Policy instead of the 24 we now have?

Anyone see these new changes that can help?

Thanks,

Kris

From the release notes (another thread on the forum):

You can configure the following features for the
Group Update Provider:
■ Limit the amount of bandwidth that the Group
Update Provider can use when the Group
Update Provider downloads content from the
management server.
■ You can define a Group Update Provider by
using rules and conditions, such as an IP address
or host name. You can configure a single Group
Update Provider in a single LiveUpdate Policy
that applies across multiple groups for multiple
clients.
■ Define clients to connect to a Group Update
Provider within the same site to improve
performance.
■ Identify which clients act as Group Update
Providers.

Rick,

Thanks for the fast response...  so, right now I have 24 remote sites.  Each of those sites I have GUP but currently I have to have 24 Live Update polices 1 for each site.  With the new featues can I only have one Live Update policy and build a list of GUP's based off rules now?  So it would be easier to manage?

I've just seen this change also, however I understand it may benefit those who use Multiple GUPS at one particular site. Rather than having a seperate LiveUpdate policy for each group of computers specifying a GUP, you can now have one LiveUpdate policy to specify multiple GUPS within one site. Anyone confirm?

I haven't installed RU5 so I can't confirm but this is from the admin docs (the second bulleted item sounds very interesting):

Use multiple Group Update Providers when your network includes
any of the following scenarios:
■ You run the latest client software on the computers in your network
Multiple Group Update Providers are supported on the computers
that run the latest client software. Multiple Group Update Providers
are not supported by legacy clients. Legacy clients cannot get
content from multiple Group Update Providers. Legacy clients
cannot be designated as a Group Update Provider even if they meet
the criteria for multiple Group Update Providers.
You can create a separate LiveUpdate Settings Policy and configure
a single, static Group Update Provider for a group of legacy clients
■ You have multiple groups and want to use different Group Update
Providers for each group
You can use one policy that specifies rules for the election of
multiple Group Update Providers. If clients change locations, you
do not have to update the LiveUpdate Settings Policy. The
Symantec Endpoint Protection Manager combines multiple Group
Update Providers across sites and domains. It makes the list
available to all clients in all groups in your network.
■ Multiple Group Update Providers can function as a failover
mechanism. Multiple Group Update Providers ensure a higher
probability that at least one Group Update Provider is available in
each subnet.

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} 2) Roaming<o p=""></o>

 

-The systems that become GUPs, send that data to the SEPM to let them know that they are now a GUP. The GUP then populates a single list of all known GUPs. This list is provided to all SEP clients that are configured to use the GUP. The way this will work is that when a client talks to SEPM, and realizes it is time to update content, the SEPM tells the client to speak to the GUP, and the client looks at the GUP list to find the GUP on the same subnet as the client. If there is no GUP on that subnet, the client (optionally) can speak directly to SEPM, or another GUP.<o p=""></o>

<o p=""> </o>

3) Bandwidth Throttle via SEPM GUI<o p=""></o>

-This specifies to the GUP to not use x amount of Kbps, Mbps, or Gbps when speaking to the SEPM and pulling down content updates. This will help in the event that a system has been off the network for some time, and requires as an example, a full definition set. That is a 30-50MB download, so this setting will ensure that the network does not become saturated during this file transfer.<o p=""></o>

It has the same look and feel of adding a location some ways.  I can take a screen shot and post it. 

Yes, you can use one policy for client in mulitple locations/sites.

With the new RU5, clients will look at the list of GUPs and attempt to contact one that is in the same subnet.
The new changes in RU5 also allow you to elect multiple GUPs in one location -- that way if you GUP goes down, the will use the next one.