When Mirage is already implemented, you can prepare new devices to be part of the organization using layer provisioning.

The layer provisioning process first cleans up the device files and applies an existing base layer and app layers, if you selected app layers, as a common template. The device is then freshly imaged, and assigned to and synchronized with a newly created CVD.

After the Mirage client is installed on the new device, the Pending Devices panel shows the device as pending assignment.

After the Mirage client is installed on the new device, the Pending Devices tab shows the device as pending assignment.

The user can use the desktop as usual, performing offline work and network transitions, after the centralization processing associated with the provisioning operation starts. The Mirage client monitors user activities and adjusts its operation to optimize the user experience and performance.

After the server synchronization is completed, the transaction log shows a successful provisioning entry. The desktop is protected and you can centrally manage the desktop at the data center.

You can use the post_provisioning.bat custom post-base layer script to perform certain actions after layer provisioning.