About the Client Accelerator Solution

Business performance depends on application performance. When applications do not perform, employees cannot work efficiently, and productivity quickly decreases. This effect is especially true for the mobile workforce as they consume applications from home, coffee shops, airports, client sites, and anywhere around the world.

The challenges of always-changing network latency and bandwidth conditions can be unpredictable and hard for IT teams to resolve. Slowdowns can lead to missed business opportunities, which, when considered at scale, can come at a great cost to any enterprise.

To stay competitive, build strong and lasting customer and client relationships, increase pipeline and revenue streams, take new products to market on time, and execute high-risk, time-sensitive missions, your mobile workforce must be able to collaborate and share in real time, download files quickly, and send large file attachments rapidly to any destination. Your workforce needs fast access to corporate documents and information anywhere they are working in the world. Your organization should have the freedom to decide the optimal location where data and applications reside—locally, in branch offices and global data centers, and in the cloud.

Riverbed’s Client Accelerator solution delivers application acceleration to mobile workers. Extending the functionality of our WAN optimization and application acceleration services and solutions, the Client Accelerator solution provides mobile employees with fast and reliable access to SaaS and on-premises applications. With a lightweight software package installed transparently on laptops or desktops, the Client Accelerator solution allows your mobile workforce to be highly efficient and productive anywhere.

In most cases, the Client Accelerator service requires only the hostname and IP address of the Client Accelerator Controller (the controller) to be operational.

For details about features and supported platforms, go to the Client Accelerator datasheet.

For details about product specifications, go to the product family specification sheet.

Here are some of the key features of the Client Accelerator solution:

• Improves application performance—Application optimization for branch offices and mobile workers. Includes URL learning, page parsing, embedded-object prefetching, and metadata acceleration capabilities.

• Accelerates web applications—On-premises and SaaS applications, intranet portals, document management systems, ERM and CRM solutions. Supports macOS clients.

• Provides visibility and control—Logical groups, policy control, aggregated and individual reporting. Offers native visibility that includes endpoint health checks and an alarm library.

Depending on your organization, your Client Accelerator solution can include:

• Client Accelerator Controller—Manages licenses and controls the deployment, management, and reporting of Client Accelerator service instances. As a virtual appliance, the controller can be installed anywhere in your network where it is accessible to client service instances.

• Client Accelerator software—Runs as a service on endpoint devices. Enables LAN-like performance, no matter where users are located. Client Accelerator software is managed by the controller and connects to a SteelHead.

The Client Accelerator Controller, typically located in the data center, is required for deployment, management, and licensing control of Client Accelerator software. After the controller is deployed, packages that contain client software can be distributed to endpoint devices.

The controller is a powerful management tool that includes these capabilities:

• Group assignments—Manage client software in groups. Push policies, install updates, and manage security for any number of endpoints that have the same resource requirements.

• Enterprise scalability—Cluster controllers to scale beyond the capacity of an individual controller. Configure high-availability topologies for maximum uptime.

• Web-based management—Manage controllers from anywhere through the web-based Management Console. While a full set of CLI commands is also available, we recommend you use the Management Console. Read about command-line features in the Riverbed Command-Line Interface Reference Manual.

• SSL Agent—Install a free license that enables the controller to operate in SSL Agent mode. Simplify the exchange and authentication of the SSL certificates needed for optimization of SSL traffic between endpoints and the controller and the SteelHeads.

For improved security, the controller will stop optimizing with endpoint devices that have been disconnected from the network for more than one month.

You use packages to install and update the Client Accelerator software on each endpoint. A package is an installation bundle specific to the endpoint’s operating system that contains the Client Accelerator software and the information necessary for the service to communicate with the controller. Using packages and group assignments together, you can set the installation and connection details for all endpoints with identical needs just once, and then install the package to all endpoints in the assigned group with a single push.

In most cases, you can deploy the default package included with the controller.

For details, see Managing packages.

Group assignments govern which policies and packages your Client Accelerator endpoints receive. Group assignments enable you to deploy different policies to groups of endpoints, based on their individual performance needs. When you deploy a package to a group, the controller uses the group assignment to identify the proper subset of Client Accelerator endpoints and automatically provides policy and software updates to them.

For details, see Managing assignments.

A policy is a set of optimization, security, endpoint storage, and other configuration settings for a group assignment (endpoints that have the same requirements). Policies can also be shared by controllers that are cluster members. A policy can be for a specific endpoint, or it can represent settings for groups of endpoints and SteelHeads.

A policy is required for optimization to occur.

The Client Accelerator Controller comes with a default policy, Initial. For basic settings, you can install and deploy the software without modifying the default policy.

For details, see About Policies.

Clusters are groups of two or more controllers used to pool available endpoint licenses and share configurations when multiple controllers are needed to support large deployments. Endpoints associated with clusters have access to the licenses on all controllers in the cluster, even if one or more of the controllers is unavailable or has used all of its licenses. Endpoints can connect to any controller in the cluster and receive shared configuration settings. Any cluster member can modify settings used by the cluster, and the settings are then automatically updated to the entire cluster.

For details, see About Controller Clusters.

Reports and logs provide a high-level view into network activity and let you drill down to specific endpoints, users, alarms, status, and so on.

The controller receives bandwidth and connection metrics from currently connected Client Accelerator endpoints every five minutes, and aggregates statistical data by hour and day. The controller stores this data for three months or longer, depending on your network environment.

If the controller is part of a cluster and you set aggregated statistics, the endpoint reports display time-series data aggregated across the entire cluster. If the controller is part of a cluster and you do not set aggregated statistics, the report only shows data from the current controller.

Reports are available for these items:

Logs are available for current and continuous monitoring, and for historical review. Logs can be filtered, allowing you to focus on specific items. User logs are filtered system logs, showing just user-related information. You can download logs.

For details, see About Reports and Logs.

You can scale the solution to the size your organization requires by clustering controllers. The Client Accelerator software can be deployed to any number of endpoints.

For details, see About Controller Clusters.

Manage your Client Accelerator Controllers from anywhere on your network. You can configure local role-based accounts or integrate with a variety of security protocols. Users with administrator privileges can configure and administer the controller. Users with monitor privileges can view reports and user logs, and change their own password. Controllers use self-signed certificates to provide encrypted web connections to the Management Console.

For details, see Using the Management Console.

Exchange and authenticate TLS/SSL certificates automatically between endpoint devices and controllers and SteelHeads. Simplifying certificate-related processes enables you to seamlessly optimize TLS/SSL traffic across your network. By simply adding a free license to your controller, you can enable the controller to operate in SSL simplification mode. In this mode, a single policy is assigned to the default, Group, and Active Directory Path assignments and pushed to service instances.

If no other licenses are applied to the controller or paid licenses have expired, optimization services for all other protocols and policy configuration are not available. Only the Endpoint Settings > Controller Settings in the policy can be modified.

Client Accelerator supports optimization of end-to-end TLS 1.3 connections when in branch mode, where the client-side SteelHead performs optimization. TLS 1.3 optimization requires private key signing using a probabilistic signature scheme (PSS) padding.

Client Accelerator does not support optimization of TLS 1.3 while operating in optimization mode. TLS 1.3 connections are down-negotiated to TLS 1.2.

The Client Accelerator software is designed to be deployed to endpoint devices on your network without additional configuration and runs as a service. The Client Accelerator Controller ships with a default policy, Initial, that provides default values for the service. The default policy is designed to be suitable for most network environments. In most cases, you can install and deploy the client software on endpoints without modifying the default policy. You can create your own packages and policies as needed.

A package created on a Client Accelerator Controller contains complete endpoint settings, including the fully qualified domain name (FQDN) of the controller and a certificate that secures communication between the client and the controller.

When you start the client service, it accesses the specified controller to obtain a license and a policy. After the endpoint retrieves a license and a policy from the controller, traffic can be optimized between the client service and the server-side SteelHead. The client service performs data optimization using the same mechanisms as a client-side SteelHead, and it maintains a connection with the controller to download new policies and software upgrades. This connection also enables the controller to monitor your endpoints and to upload logs from them.

Running in SSL Simplification mode, the service can facilitate the seamless exchange and authentication of the SSL certificates required for optimization of TLS/SSL traffic. See About TLS and SSL simplification.

When installing Client Accelerator software versions 6.3.0 and later on endpoints with macOS versions 11 and later, you’ll need to allow a system extension from the SteelheadMobile.app to load and authorization for the Client Accelerator to filter and monitor traffic. For information on options for mass deployment of these settings or for manually allowing the extension on individual clients, see Reference: Client Accelerator Endpoint System Extensions.

First, you need to decide on a deployment topology. Do you need clusters? Is high-availability desirable? Do you want endpoints to share among a pool of licenses?

Next, you’ll want to think about the endpoint devices you need to support. What operating systems will be running on those endpoints? Do all endpoints have the same optimization needs, or will you need to break them out into different groups with similar needs?

After you’ve installed your controllers and mapped out endpoint needs, it’s time to log in to the Management Console to license and configure your controllers. You might want to create group assignments and policies for those groups too.