After a base layer is updated at the server and tested on at least one CVD, you can assign it to individual or multiple CVDs.

About this task

If collections are defined, you can assign the new base layer to all the CVDs in a collection in one step. See Working with CVD Collections.

The download to the endpoint transfers only new files and incremental changes to existing files of the target endpoint.

When a file exists in a base layer, it overwrites the corresponding file in the target endpoint, unless one of the following conditions apply:

  • The file is defined in the Do Not Download rules in the Layer Rules.

  • The file is defined in the Unprotected Area in the CVD Policy Details.

When software or system registry keys and values exist in the base layer, they overwrite the corresponding registry keys in the target endpoint, unless the registry entry is defined in the Registry Keys To Exclude in the System Hive or Software Hive tabs in the Layer Rules.

User profiles, for example c:\users\john, and any corresponding user registry hives are not overwritten by the base layer update operation.

The process swaps the old base layer with the new one, assigning the base layer to the endpoint and instantiating the endpoint. The changes in an endpoint are propagated back to the endpoint CVD on the server.

Before a new or updated base layer is applied, the Mirage server takes a CVD snapshot so that it can roll back in case of post-update problems.

Before and during base layer download, Mirage verifies that enough disk space is available to proceed with the operation.

The same interfaces are used to apply or modify a base layer for multiple CVDs, or a collection.

You can upgrade an existing base layer or app layers to all CVDs that are already assigned with previous versions of those layers. See Assign a Previous Layer Version.

During the assignment process, certain system aspects are validated.

Table 1. Assignment Validations

System Aspect

Validation Description

Operating System

The system checks that the CVD and the new base layer have the same OS and type (32- or 64-bit). If they are different, the system blocks those CVDs from receiving the base layer.

Computer Type

The system checks that the CVDs and the base layer share the same computer type (for example, laptop versus desktop). A warning appears if they are different. If the base layer was prepared to support both desktops and laptops, you can approve and continue.

Vendor and Model Name

The system checks that the base layer and the CVDs are from the same computer vendor. A warning appears if they are different. If the base layer was prepared to support the different vendor types, you can approve and continue.

Drive Letters

The system checks that the CVDs include the required drive letter in the base layer. If the CVDs do not have the appropriate drive letters, the system blocks these CVDs from receiving the base layer.

Prerequisites

Assign a base layer to a CVD only after endpoint centralization is completed for that CVD and its content is protected in the server. You can revert to the previous CVD state.

Procedure

  1. In the Mirage Management console tree, select Common Wizards > Assign Base Layer
  2. Select individual or multiple CVDs, or a collection of CVDs to update, click Select and click Next when you are finished.

    The selected CVD details appear in the bottom pane.

  3. Select the base layer with which you want to update the CVDs and click Next.

    The details of a base layer appear in the bottom pane.

  4. Correct mismatches between the base layer and the selected CVDs if needed.

    Ignore any warnings that are not applicable. The following system aspects are validated.

  5. Click Finish.

    An update task is created. The client periodically checks the server for updates to download as part of its regular processing.

Results

The administrator procedure is finished.

When the client next connects, download and swap operations take place, which ask the user to restart. Allow some time for the changes to download.