Environment
- Carbon Black Cloud Sensor: 2.0.x - 3.3.x
- Microsoft Windows: All Supported Versions
- Virtual Desktop Infrastructure (VDI) using Primary Images
- Non-Persistent clones of the Primary Image
Objective
Resolution
Linked Clones
- VDI primary images having a sensor installed using the VDI=1 command switch for non-persistent clones should not be turned on again
- If the VDI primary image is turned on for any reason, including to perform system updates, application installs, or sensor upgrades then the sensor should be re-installed
If the sensor is uninstalled or de-registered from a primary image, any clones deployed from this image that are running will stay operational. Newly deployed clones will no longer register. Use the newly created primary image for deployment going forward.
Instant Clones
- When using a VDI primary image with the option VDI=1, the primary will appear as a clone in the console the next time it is turned on. This will make it subject to Auto-Deregistration of VDI Sensors option
- Disable the Auto-Deregistration of VDI Sensors option if the VDI primary image is turned on for any reason so that the sensor is not de-registered on the running parent image
- If a new parent image is published the VMs in each assignment will be synced with the new primary image as users log out of their sessions for the old parent image
The cloning process creates a running parent image from the VDI primary image that is never turned off, so both the primary image and running parent will share the same sensor device id. If the sensor is uninstalled and/or re-installed on the VDI primary image, the sensor will be de-registered on the running parent image as soon as the primary image connects to the Carbon Black Cloud backend. This will likewise affect any clones attached to that parent from being able to register with the Carbon Black Cloud backend.
Additional Notes
- A new command line feature is available available in the 3.4.x.x sensor release and higher which will allow a VDI primary image that has been turned on to be re-registered without requiring a sensor re-install
- When using a VDI primary image with the option VDI=1, the next time the image is booted the sensor honors the VDI=1 selection and treats the system as a non-persistent VDI clone
- If this clone is then updated / manipulated and then re-saved as a VDI primary image it will appear as a clone in the console. This will make it subject to Auto-Deregistration of VDI Sensors option
- Once this newly created VDI primary image (which is registered with the backend as a clone) reaches the Auto-Deregistration window it will be de-registered
- Any clones spawned from this VDI primary image after this point will not be able to register as the primary image is no longer registered (authorized to communicate with the cloud)
- Below is a step-by-step example procedure that can be used to create multiple VDI primary images for non-persistent (Linked) VDI clones
Primary Golden Image Prep:
- Boot the currently Existing Primary Golden Image (EPGI)
- Perform maintenance operations / application installations
- Remove the existing sensor (3.1 in this case)
- If image has tamper protection enabled – disable it prior to attempting removal
- Any existing non-persistent clones that were deployed from this (EGPI) that are currently running will remain running and registered.
- Any non-persistent clones deployed from this current (EPGI) CAN NOT be deployed again as the sensor has been de-registered and child clones will not be able to register
- Reboot the machine (general best practices)
- Verify removal of sensor (services / executables / web console)
- Verify proper operation of the system and confirm no other pending installs / updates are being performed
- Shutdown (EPGI)
- Mark / Annotate this state without a sensor as the Primary Golden Image (PGI)
Secondary / Tertiary / Quaternary / … Image Prep:
9. Create a clone of the PGI without sensor installed for each sensor version pro re nata
10. Boot each new Clone Primary Image (CPI)
11. Rename each (CPI) to a different host name - recommend an easily identifiable naming convention (XXXXXPGI, XXXXSEN310, XXXXSEN320, …)
12. Reboot
13. Verify proper operation of the system and confirm no other pending / installs updates are being performed.
Sensor Install:
14. Boot each previously created (CPI)
15. Install sensor version of your choice using these instructions
16. Verify successful installation / registration via web console
17. Give the image some time to complete post installation activities
18. Shutdown and save each (CPI)
19. Do not turn on (CPIs) again.
Working With Clones:
20. If there is a need to update the primary for all images go back to step one and select one of the existing (CPIs) as the reference point.
21. Do not turn on (CPIs) again.
Related Content
