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.

Supported Configurations

Mirage supports the following View configurations.

  • Full-clone, dedicated assignment desktop pools

  • View Persona management is not supported with Mirage.

Supported Mirage Operations

The following Mirage operations are supported with View:

Table 1. Supported Mirage Operations in View

MirageOperation

Supported with View

App layer assignment

Yes

Base layer assignment

Yes

Enforce layers

Yes

Apply driver library

Yes

Centralization

No

File Portal

No

HW migration

No

Endpoint provisioning

No

Restore

No

Revert to snapshot

No

Steady state uploads

No

Windows OS migration

No

Behavior of Mirage CVDs with the View Policy

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.