Managing SteelHead Mobile Clients : Managing SteelHead Mobile packages : Deploying SteelHead Mobile packages
  
Deploying SteelHead Mobile packages
This section describes how to deploy SteelHead Mobile packages using the Microsoft Windows Installer for Windows clients and the Apple PackageMaker for Mac OS X clients.
You can use any of these methods to deploy packages to the endpoint clients in your network:
Deployment Tools - Typically, in larger organizations, you might use deployment tools to install the SteelHead Mobile client software (for example, Microsoft SMS and GPO, Altiris, Tivoli, Radia, and Zenworks). Deployment of SteelHead Mobile software has been tested with Microsoft SMS, Active Directory, and GPO (Group Policy Object). Consult your vendor’s documentation for information about its products.
Email - You can use email to send the link provided on the Mobile Controller.
Manual Installation - If your deployment is small, you might want to install each package manually on the client machines.
Scripts - You can use login scripts or batch files to trigger an installation when users log in to their systems.
After you save the SteelHead Mobile package to your computer, double-click the package to install the package on your computer.
If the package is to be downloaded by more than 50 SteelHead Mobile clients, we recommend that you put the package on a file server so the Mobile Controller is not overloaded with requests.
Basic steps for deploying packages
Perform these basic steps to deploy packages to your SteelHead Mobile clients.
1. Choose Manage > Services: Packages to display the Packages page.
2. Click the group name to display a list of packages.
3. Click the package name to view package details, including the download URL for Windows and Mac packages.
4. Click the URL for the Windows or Mac package and save it to your local machine.
5. Distribute your package using a deployment tool of your choice:
You use a deployment tool, for example, you can use Microsoft GPO or SMS.
You can deploy your package from an internal website, by email, or manually. If you use one of these methods, you must install the SteelHead Mobile clients manually by double-clicking on the SteelHead Mobile package to install the package on your computer.
6. Verify the SteelHead Mobile connections and optimization in the Reports > Endpoints: Endpoint Report on the Mobile Controller.
Installing the SteelHead Mobile packages on Windows and Mac clients
Perform these steps to install the SteelHead Mobile package on a Windows Client. For details on Microsoft Windows Installer Properties (MSI) properties, see Appendix: Windows Installer Properties.
The SteelHead Mobile installer for the Mac OS X is a standard Apple PackageMaker installer. Perform these steps to install the SteelHead Mobile package on Mac clients.
To install the SteelHead Mobile package on a Windows client
1. After you have saved the SteelHead Mobile package to your computer, double-click the msi file to execute the package.
2. Accept the license agreement.
3. Choose the installation destination folder.
4. Specify whether to have a Desktop icon or a Start menu icon.
5. Choose a Typical or Advanced installation. If you select Advanced, set your SteelHead Mobile RiOS data store size and configure your Mobile Controller.
6. Click the desktop icon to launch the SteelHead Mobile.
7. Reboot your machine, if prompted.
To install the SteelHead Mobile package on a Mac client
1. After you have saved the SteelHead Mobile package to your computer, double-click the tgz file to run it.
2. Accept the license agreement.
3. Select the installation Destination disk.
4. Specify an administrator name and password, and click OK.
5. Click Close to complete the installation.
If the Show Client in the System Tray option is enabled in the policy, the SteelHead Mobile software icon is now shown in the system tray.
The SteelHead Mobile runs in the background and optimizes traffic transparently. After approximately thirty seconds, the client is visible on the Mobile Controller.
To verify your client connections and optimization, navigate to the Reports > Endpoints: Endpoint Report page on the Mobile Controller. For details, see Viewing Endpoint reports.
Updating SteelHead Mobile software
You use packages to provide automatic software updates to your SteelHead Mobile clients. After a package is created, it can’t be edited.
HTTP access must be enabled on the Mobile Controller for automatic updates to be downloaded to your SteelHead Mobile clients.
When the SteelHead Mobile software is installed a client is assigned a group ID based on the package that was installed. If you used the Default package, then the client will be in the Default group. Using groups allows you to assign upgrades and policies to several SteelHead Mobile clients at a time. For details on groups, see Managing SteelHead Mobile assignments.
If you want to change a SteelHead Mobile’s group while still having the client using the same version, you must manually uninstall the SteelHead Mobile software to install the package with the new group. The SteelHead Mobile’s group can also be changed using the Group Policy Object (GPO) template. For details, see Changing an endpoint group for clients using a GPO.
Basic steps for creating a package for SteelHead Mobile software updates
This list describes the basic steps for creating a package for SteelHead Mobile software updates.
Task
Reference
1. Create new packages for each group.
2. Modify the package assigned to the current group or assign your policies to group.
3. Deploy the package to the endpoint clients in your network using the deployment tool of your choice. When using the upgrade method built into the Mobile Controller, the endpoint user will be prompted to install the update.
4. Verify your connection and optimization in the Reports > Endpoints: Endpoint Report page.
5. You can also make individual assignments to Active Directory users based on their username identified by the Mobile Controller without using a group.
Upgrading can terminate existing connections on the client. Client connections are terminated each time the policies are updated.