Using Group Update Providers to distribute content to clients
A Group Update Provider (GUP) is a client computer that distributes content updates directly to other clients.
Advantages of the GUPs include:
- They conserve bandwidth and management server resources by offloading processing power to the GUP.
- They deliver updates effectively to clients with limited or slow network connectivity.
- They are easier to set up than an internal LiveUpdate server.
Step 1: Understand the differences between the types of Group Update Providers that you can configure
You can set up single, multiple, or cross-subnet Group Update Providers. The type of Group Update Provider that you set up depends on your network and the clients on that network. The types of Group Update Provider are not mutually exclusive. You can configure one or more types of Group Update Provider per policy. See:
Step 2: Verify client communication
Before you configure Group Update Providers, verify that the client computers can receive content updates from the server. Resolve any client-server communication problems.
You can view client-server activity in the System logs on the
Logstab of the
Step 3: Configure Group Update Providers in one or more LiveUpdate Settings policies
You configure Group Update Providers in the LiveUpdate Settings policy. See:
Step 4: Assign the LiveUpdate Settings policy to groups
You assign the LiveUpdate Settings policy to the groups that use the Group Update Providers. You also assign the policy to the group in which the Group Update Provider resides.
For a single Group Update Provider, you assign one LiveUpdate Settings policy per group per site.
For multiple Group Update Providers and explicit lists of Group Update Providers, you assign one LiveUpdate Settings policy to multiple groups across subnets. See:
Step 5: Verify that clients are designated as Group Update Providers
To view the client computers that are designated as Group Update Providers, do one of the following tasks: