The first Horizon FLEX installation step is to install and configure the Mirage system.

The Horizon FLEX server package includes the following components:
  • VMware Mirage for Horizon FLEX (the Mirage Core Software)
  • Mirage PowerCLI for Windows
  • Mirage Gateway Appliance Software
    Note: The Mirage Core Software is required for the Horizon FLEX server. The Mirage PowerCLI for Windows and Mirage Gateway Appliance Software are only required if you will use Mirage to manage the Horizon FLEX virtual machines.
Download the installation files from the Horizon FLEX Server product download page.

The Mirage deployment involves the installation of the following components.

  1. Mirage Management Server
  2. Mirage Server
  3. Mirage Management Console
  4. Mirage Web manager

To install and configure the Mirage system, follow the installation instructions in the Mirage documentation at https://www.vmware.com/support/pubs/mirage_pubs.html.

When you install the Mirage system, you must select certain options for the Horizon FLEX server to operate correctly.

  • The Mirage Server and Mirage console are only required if you are installing the Mirage client in the source virtual machines.
  • If placing the virtual machine images on the same system as the Horizon FLEX Server, place the images in the IIS "Default Web" server.
  • The Web Management Server and the Mirage Management Server can be installed on the same server, but installing them on different servers improves scalability. The SQL server can also be installed on a separate server from the Web Management Server and the Mirage Management Server to improve scalability.
  • During Mirage server installation, choose SSL for the Mirage server transport. SSL is required to use the Mirage Gateway feature for external access and management of Horizon FLEX systems. Before configuring the Mirage Server for SSL, you must install the server SSL certificate.
  • Horizon FLEX does not require the MongoDB database, so the additional storage is not required. When installing the Mirage server, disregard the prompt and click Next.

  • You can deploy the two components of the Horizon FLEX server, the Horizon FLEX Admin Console and the Horizon FLEX Policy Server, on the same port or on separate ports.

  • Before you install the Mirage Web Manager, verify that .NET Framework 4.5.1 is installed on the server.
  • The Mirage Management Server must run as a user who has Active Directory read permissions. If you plan to join Horizon FLEX virtual machines to an Active Directory domain, the Mirage Management Server must run as a user who has domain join permissions. The user must have permission to add computer objects to the domain.
  • FLEX uses the Win32 Logon API to authenticate the end users to the Web Management Server (IIS server). Therefore, client users must be able to perform an interactive login on to the IIS server. If there is a GPO blocking this login, the authentication fails. For added security, you can turn on remote access on the server. Configure the local server security to allow FLEX users to log in to the file portal. This configuration is performed by modifying the Local Security Policy.
    1. On the Windows server where IIS and the Mirage Web Access components are installed, log in as Administrator.
    2. Under ADMINISTRATIVE TOOLS, open the Local Security Policy by selecting LOCAL SECURITY POLICY.
    3. Under LOCAL POLICIES | USER RIGHTS ASSIGNMENT, browse to ALLOW LOG ON LOCALLY and double-click to open it.
    4. Ensure that ADMINISTRATORS and USERS local security groups are defined here. If not, ensure that the appropriate Domain Security Groups are defined at their place