You can include a custom post-base layer script in the base layer capture. This script perform certain actions required after a base layer update, such as installing software that must be run on the individual endpoint, or updating or removing hardware drivers that might already exist on the endpoint. You can also use a post-base layer script following a layer provisioning operation.
About this task
Software required to be run on the individual end point can include hardware-specific software that is compatible with only certain endpoints.
The client installation includes a default sample script that does not perform post-base layer script actions.
The client continues to run the post-base layer script at every startup, until the first upload following the base layer update is finished. This ensures that the state of the CVD on the server includes the result of the post-base layer script. This process is also done for every enforce base layer operation.
The script must include the relevant checks and conditional clauses so that any parts that require one-time execution are not run again.
The post-base layer script file and auxiliary files used or called by the script are captured as part of the base layer and distributed to the endpoints. Verify that the auxiliary files are placed in the same directory as the script or another directory that is captured in the base layer.
- After a base layer update operation, create a file called post_core_update.bat under the %ProgramData%\Wanova\Mirage Service directory.
After a layer provisioning operation, create a file called post_provisioning.bat under the %ProgramData%\Wanova\Mirage Service directory.
- Edit the file on the reference machine to perform the required post-deployment actions on the endpoint.
To monitor the execution of the post-base layer script, the client reports events to the central management service if the script returns an error value other than zero.