School-lab non-persistent VDI desktops refresh from a golden image each night. How should the CB Defense sensor be deployed so it survives that cycle?
Select an answer to reveal the explanation.
Short Explanation
Non-persistent labs are like a stack of laminated hall passes—you print from a master, you do not Sharpie a unique ID on the master and photocopy it. Use the VDI/golden-image sensor prep so each clone registers fresh. Installing after login vanishes at refresh, and cloning one live sensor ID collides in the console.
Full Explanation
Non-persistent desktops require the Carbon Black Cloud VDI or golden-image procedure so the sensor is prepared on the master and each clone obtains a unique identity at first boot. A one-off install inside a disposable session is lost on refresh. Cloning a production sensor ID causes duplicate-device collisions. NSX distributed IDS is not a substitute for the endpoint sensor on VDI pools.