Consider deploying the SteelHead Mobile client software to your endpoints using the policy defaults and modifying them only as necessary. A policy specifies computer-specific software settings for acceleration such as protocol and SSL settings and endpoints such as data store size and Mobile Controller to connect to.
A policy is required for optimization to occur. The GID enables you to assign policies to groups of endpoints. When you create the package, you can assign a GID to it.
The GID is associated with the endpoint upon installation. The Mobile Controller subsequently uses the GID to identify the endpoint and provide assigned policies and updates. A demilitarized zone DMZ is a computer or small subnetwork that sits between a trusted internal network, such as a corporate private LAN, and an untrusted external network, such as the public internet.
You can also use the Management Console for endpoint software upgrades, licensing, reporting, and monitoring. You distribute SteelHead Mobile software to endpoints using packages. You create packages using the Management Console, and you deploy them to your endpoints using the deployment tool of your choice. You can use a commercial deployment tool for example, Microsoft SMS, Active Directory, or Altiris to deploy packages, or you can email the link to your remote users.
When you start the SteelHead Mobile client, it accesses the specified Mobile Controller to obtain a license and a policy. After the endpoint retrieves a license and a policy from the Mobile Controller, traffic can be optimized between the SteelHead Mobile client and the server-side SteelHead.
The SteelHead Mobile client performs data optimization using the same mechanisms as a client-side SteelHead. The endpoint maintains a connection with the Mobile Controller to download new policies from the Mobile Controller. This connection also enables the Mobile Controller to monitor your endpoints and to upload logs from them. The Mobile Controller is located at the main data center. SteelHead Mobile clients communicate with the Mobile Controller for management and reporting purposes.
SteelHead Mobile clients are optimized by SteelHeads at the data center. Figure: Typical Mobile Controller deployment. This section provides information about product dependencies and compatibility. This table summarizes the software and configuration requirements for deploying the Mobile Controller. A Mobile Controller console is any computer including Microsoft Surface Pro tablets that supports a web browser with a color image display. If you want to encrypt your communication, you must have an SSL-capable browser.
A total of concurrent user licenses and users that are connected but not optimized. Only can be optimized at a time. Mobile Controller-v for Hyper-v is supported on Hyper-v version 6. Mobile Controller-v for Azure is supported on Azure. Mobile Controller-v can be installed and run in Azure. This table lists the supported operating systems for SteelHead Mobile. Operating system. This section lists the required firewall settings for Mobile Controller deployments. Port 22 must be open for access to the command-line interface CLI.
SteelHead Mobile 6. Depending on your deployment scenario, this rule might be the first rule in the list. If the port uses UDP, no rule is required. For details, go to Knowledge Base article S You can either configure an in-path, fixed-target rule for the Mobile Controller policy, or you can make configuration changes on the Cisco ASA.
For specific versions supported, go to Knowledge Base article S You must add a subnet for each of the following components: the data center, the server being accessed, the SteelHead, and the Mobile Controller.
Follow the safety precautions outlined in the Safety and Compliance Guide when installing and setting up your equipment. Caution: Failure to follow these safety guidelines can result in injury or damage to the equipment.
Mishandling of the equipment voids all warranties. Please read and follow safety guidelines and installation instructions carefully. Many countries require the safety information to be presented in their national languages. You create packages using the Management Console, and you deploy them to your endpoints using the deployment tool of your choice. You can use a commercial deployment tool for example, Microsoft SMS, Active Directory, or Altiris to deploy packages, or you can email the link to your remote users.
When you start the SteelHead Mobile client, it accesses the specified Mobile Controller to obtain a license and a policy. After the endpoint retrieves a license and a policy from the Mobile Controller, traffic can be optimized between the SteelHead Mobile client and the server-side SteelHead.
The SteelHead Mobile client performs data optimization using the same mechanisms as a client-side SteelHead. The endpoint maintains a connection with the Mobile Controller to download new policies from the Mobile Controller. This connection also enables the Mobile Controller to monitor your endpoints and to upload logs from them. The Mobile Controller is located at the main data center.
SteelHead Mobile clients communicate with the Mobile Controller for management and reporting purposes. SteelHead Mobile clients are optimized by SteelHeads at the data center.
Figure: Typical Mobile Controller deployment. This section provides information about product dependencies and compatibility. This table summarizes the software and configuration requirements for deploying the Mobile Controller.
A Mobile Controller console is any computer including Microsoft Surface Pro tablets that supports a web browser with a color image display. If you want to encrypt your communication, you must have an SSL-capable browser.
A total of concurrent user licenses and users that are connected but not optimized. Only can be optimized at a time. Mobile Controller-v for Hyper-v is supported on Hyper-v v ersion 6. Mobile Controller-v for Azure is supported on Azure. Mobile Controller-v can be installed and run in Azure. For detailed information, see Installing Mobile Controller-v for Azure. This table lists the supported operating systems for SteelHead Mobile. Operating system. This section lists the required firewall settings for Mobile Controller deployments.
Port 22 must be open for access to the command-line interface CLI. SteelHead Mobile 6. Depending on your deployment scenario, this rule might be the first rule in the list. If the port uses UDP, no rule is required. You can either configure an in-path, fixed-target rule for the Mobile Controller policy, or you can make configuration changes on the Cisco ASA.
You must add a subnet for each of the following components: the data center, the server being accessed, the SteelHead, and the Mobile Controller. Follow the safety precautions outlined in the Safety and Compliance Guide when installing and setting up your equipment. Caution: Failure to follow these safety guidelines can result in injury or damage to the equipment. Mishandling of the equipment voids all warranties.
Please read and follow safety guidelines and installation instructions carefully. Many countries require the safety information to be presented in their national languages. If this requirement applies to your country, consult the Safety and Compliance Guide. The guide contains the safety information in your national language.
Before you install, operate, or service the Riverbed products, you must be familiar with the safety information. Because the server is aware of the hostname, it returns a host-specific security certificate. This release adds SMB lease sharing support. Previous versions of macOS High Sierra are not supported. Each software release includes release notes. The release notes identify new features in the software as well as known and fixed problems.
Examine the release notes before you begin the installation and configuration process. Log in to the Management Console using the administrator account admin. Use one of these formats:. The downloaded image includes only the incremental changes.
0コメント