Horizon Mirage allows administrators to use Horizon Mirage base and app layering capabilities to manage full-clone, dedicated assignment Horizon View desktop machines.

With Horizon Mirage, a View administrator of a large scale environment can automatically update operating system and infrastructure software, add and remove application layers, and fix software problems. Users in View persistent desktop pools with Mirage image management can preserve user data customizations and user installed applications through Mirage image updates.

Desktop devices undergoing a Horizon Mirage layer update require more resources than usual. Mass image management operations can affect user experience for users in an updated pool and in neighboring pools with which it shares resources. To diminish this effect, Horizon Mirage must limit the level of concurrency when you perform image management operations in the Horizon View pool. An administrator can control the concurrent level via the concurrency value, which controls the effect Horizon Mirage has on the ESX resources.

Horizon Mirage supports the following Horizon View configurations.

VMware Horizon View 5.3, 5.3 Feature Pack 1, or later

Full-clone, dedicated assignment desktop pools

The following Horizon Mirage operations are supported with Horizon View:

Supported Horizon Mirage Operations in Horizon View

Mirage Operation

Supported with Horizon View

App layer assignment


Base layer assignment


Enforce layers


Apply driver library




File Portal


HW migration


Provisioning base layer




Revert to snapshot


Steady state uploads


Windows 7 migration


The Horizon View Agent can be updated by the base layer or the app layer from Horizon Mirage. There can only be a single layer, either the base layer or the app layer, to manage the Horizon View Agent.

It is recommended to manage the Horizon View Agent with app layers.

The Horizon View Agent cannot be downgraded to a previous version in a Horizon Mirage environment.

CVDs that use the Horizon View-optimized policy have special characteristics.

No data protection

The corresponding devices do not upload files to the data center. You cannot revert the devices to a Horizon Mirage snapshot or restore user files to previous versions. Horizon Mirage only periodically uploads metadata about these devices, for example the list of installed applications.

No WAN optimizations

To improve performance for managing Horizon View pools, Horizon Mirage disables most WAN optimizations for these CVDs because they are assumed to be hosted in the same data center as the Horizon Mirage server.

This topic describes the general workflow of how to manage a Horizon View desktop pool with Horizon Mirage. This workflow comprises the following procedures:


Capture initial base and app layers.


Create a virtual machine.


Assign the base layer and any app layers to the virtual machine.


Create a template from the virtual machine and create a full-clone Horizon View desktop pool from the template.


Create CVDs for all desktops in the newly created pool.

When a base or app layer update is needed, you perform an image update on the relevant CVDs. This process comprises the following procedures:


Capturing new or updated base or app layers.


Assigning the new layers to the pool.

The desktop machines are updated gradually, until all the machines have the new layers.