This topic describes how to install the Forefront Unified Access Gateway (UAG) endpoint components using an installation file.

Users who do not have ActiveX download rights on Windows Internet Explorer, and are non-privileged (guest/user) users, can use a downloaded installation file to install the endpoint components. In this setup, the administrator must log in to the endpoint computer by using Administrator privileges, and install the components before the user accesses the site.

Deploying offline component installation to end users

After you have configured the installation settings, you can deploy the installation to end users in unattended or interactive mode:

Note:
You should inform users that during component installation, they should not access the portal home page or any other location within the site. If the installation detects that client components are already installed on the computer, it upgrades the components from previous versions, even if their installation is not enabled in the current installation configuration.
Note:
The .msi file must be run with administrator privileges on the client endpoint.

To deploy the offline component installation

  1. On the Forefront UAG server, locate the folder ...\Microsoft Forefront Unified Access Gateway\von\PortalHomePage.

    The folder contains five installer files:

    • WhlClientSetup-All.msi

    • WhlClientSetup-Basic.msi

    • WhlClientSetup-NetworkConnector.msi

    • WhlClientSetup-NetworkConnectorOnly.msi

    • WhlClientSetup-SocketForwarder.msi

    The components that are installed by the different installers are described in Configuring the Forefront UAG endpoint components Installer.

  2. Distribute the relevant installer file to your end users.

  3. To install the components in interactive mode on the client endpoint, double-click the installer file, or right-click the installer file and click Run as administrator.

    The Forefront UAG Client Components Installation Wizard starts. Users can follow the instructions to complete the wizard, and install the components on their client endpoints.

  4. To install the components in unattended mode on the client endpoint, at an elevated command prompt on the endpoint, run the following command:

    <Installer_file> /qn

    where <Installer_file> is the name of one of the five installer files. For example, to install all of the client components, run the following command:

    WhlClientSetup-All.msi /qn

    Note:
    When running an unattended deployment, no user interaction is required; end users cannot do a custom installation nor select which of the components to install.