This is the first post in a multi-part series I’m going to be doing on Horizon Mirage 4.4. To get a foundation in what we’re doing here, let’s take a look at the different components. From the Installation and Configuration Guide:
Horizon Mirage Management server
The Horizon Mirage Management server, located in the data center, is the main component that controls and manages the Horizon Mirage server cluster.
Horizon Mirage Management console
The Horizon Mirage Management console is the graphical user interface used to perform scalable maintenance, management, and monitoring of deployed endpoints.
Through the Management console, the administrator configures and manages clients, base and app layers, and reference machines. The administrator uses the Management console to perform operations such as update and restore, and monitors the system operation through the dashboard and event logs.
Horizon Mirage Web Manager
The Horizon Mirage Web Manager enables help-desk personnel to respond to service queries, and the Dashboard feature assists the Protection manager role to ensure that user devices are protected. The Web Manager mirrors Horizon Mirage Management console functionality.
Horizon Mirage Server
The Horizon Mirage servers, located in the data center, manage the storage and delivery of base layers, app layers, and CVDs to clients, and consolidate monitoring and management communications. You can deploy multiple servers as a server cluster to manage endpoint devices for large enterprise organizations. It is good practice to keep the server on a dedicated machine or a virtual machine. However, a server can be co-hosted with the Management server.
Horizon Mirage File Portal
End users can use appropriate login credentials and the Horizon Mirage file portal to access their data from any Web browser. The file portal front-end component runs on any server machines that have IIS 7.0 or later installed, and the back-end component runs on the Management server.
Horizon Mirage Edge Server
The Horizon Mirage Edge server is the secured gateway server that is deployed outside the Mirage datacenter environment. The Horizon Mirage Edge server meets the enterprise security and firewall requirements and provides a better user experience for Mirage clients that access the Horizon Mirage servers through the Internet. The Edge server seamlessly integrates with the Horizon Mirage system with minor modifications to the Mirage system and protocol.
For this article, each role will be co-located on the same server, except the Horizon Mirage Edge Server, which will be covered separately.
Hardware and Software Configuration
Please consult the Installation and Configuration Guide for a full list of Operating System, software, and hardware requirements for your deployment. In my lab deployment, I will be using the following:
- Windows Server 2012 Standard Edition, 64-bit
- VMware vSphere 5.5 U1 virtual machine
- 2 vCPUs
- 4 GB RAM
- 1 vNIC
- 150GB system drive
- 500GB data drive
- Microsoft SQL Server 2008 R2 – remote database server
In the next article in the series, I’ll cover the Horizon Mirage 4.4 Management server installation procedure.