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

With 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 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, Mirage must limit the level of concurrency when you perform image management operations in the View pool. An administrator can control the concurrent level through the concurrency value, which controls the effect Mirage has on the ESX resources.

Mirage supports the following View configurations.

View 5.3.2, 5.3.3, 6.0.0, and 6.0.1

Full-clone, dedicated assignment desktop pools

View Persona management is not supported with Mirage.

The following Mirage operations are supported with View:

Supported Mirage Operations in View

Mirage Operation

Supported with View

App layer assignment


Base layer assignment


Enforce layers


Apply driver library




File Portal


HW migration


Layer provisioning




Revert to snapshot


Steady state uploads


Windows OS migration


You can update View Agent with the base layer or the app layer from Mirage. Only a single layer, either the base layer or the app layer, can manage View Agent.

You cannot downgrade View Agent to an earlier version in a Mirage environment.

CVDs that use the 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 Mirage snapshot or restore user files to previous versions. Mirage only periodically uploads metadata about these devices, for example the list of installed applications.

No WAN optimizations

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