VMware Horizon View and VMware Horizon Mirage – Both these solutions have its own distinct use cases. But there are many scenarios where these two solutions can be leveraged together, so that View Virtual desktops can be extended to become managed by Mirage Server. VMware EUC blog discusses on How to Set Up Horizon View Desktops Managed by Horizon Mirage
Additionally VMware View introduces a simple and powerful integration with Mirage, which will enable the administrator to automate the Mirage Client configuration on all newly provisioned View Desktops. Below steps explains the integration aspects and configuration.
Setup Mirage Client along with View Agent.
The master VM (for View Desktop deployment) is typically prepared by installing VMware View Horizon Agent on it and converting the VM to a template (or by taking a powered off snapshots). Having VMware Horizon View 6.0.x, you can also install Mirage Client on the Agent VM. I have used Mirage 5.2 client to prepare this write-up. While installing Mirage Client on a View Agent machine, we must enter a server address to connect with a Mirage Server. But this is something we are going to set through View Administrator configuration. Since the wizard-prompt does not allow us to proceed with an empty input for ‘VMware Mirage Server location’, you need to place some dummy text there.
When prompted, I have used a simple text ‘ViewConfigured’ and completed the Mirage Client installation on the View Agent Master VM. We can verify the installation by checking the status of Mirage Client from the Windows notification area. The status will show as ‘Disconnected’. This means Mirage Client is installed and services are up and running, but the mirage client is not connected to any specific Mirage server. The master VM preparation is now complete. and the VM can now power-off and convert to a template for automated View Desktop deployment (or take powered off snapshot for linked-clone provisioning)
Configure View Administrator global settings for Mirage
When each desktops are created from the above template VM, we need to make sure those desktop VMs are associated with a Mirage Server. This configuration can be done from the “Global Settings” of View Administrator console. Open the View Administrator Console, and from the left panel inventory, click global settings, and click “Edit’ on the general settings. Specify the Mirage Server at the bottom of the wizard. Refer below figure.
If SSL has been configured on the Mirage Server, then the syntax will be ‘mirages’ instead of ‘mirage’ i.e. mirages://<MirageServer>:<PortNumber>. You can specify IP address or host-name, but host-name is recommended while with SSL configuration.
Configure Pool Settings for Mirage Server connection.
The above global settings will be populated during the View Desktop Pool configuration wizard. During the ‘Desktop Pool Settings’ page , optionally you can override the settings per pool to configure the desktops in that pool to associate with a different Mirage server.
The newly provisioned desktops will take the Mirage Server configuration from the pool settings and will be listed in the “Pending Devices” list of Mirage Management Console. On the Provisioned View agent, the Mirage Client will show as connected with status “Pending Assignment”.
This way, we can automate View Desktops’ Mirage Server association through View Administrator Console.
VMware Horizon View 6.0.1 and VMware Horizon Mirage 5.2 were the Software Versions used for this article. View Agent and Mirage Client were configured on Windows 7 Enterprise 64 bit.
Permalink to this article: View and Mirage Integration – Configuring View Desktops for Mirage Management