After an app 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 app layer to all the CVDs in a collection in one step. See Working with CVD Collections.
The assignment process swaps the old app layer with the new one, thereby assigning the app layer to the endpoint and instantiating the applications to the endpoint. The changes in the endpoint are propagated back to the endpoint’s CVD on the server.
The download to the endpoint transfers only new files and incremental changes to existing files of the target endpoint.
Before a new or updated app layer is applied, the Mirage server takes a CVD snapshot so that it can roll back if any post-update problem arises.
Before and during app layer download, the system verifies that enough disk space is available to proceed with the operation.
The same interfaces are used to apply or modify app layers 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.
Prerequisites
Verify that endpoint centralization is completed for that CVD and its content is protected in the server. You can revert to the previous CVD state.
Verify that the software to be deployed by the app layer does not conflict with locally installed applications. See Correct Software Conflicts By Using a Transitional Base Layer.
App layer assignment requires a base layer to be present on the endpoints.
Procedure
Results
This completes the administrator procedure.
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.