Public-health non-persistent VDI desktops need Carbon Black Cloud protection and must still launch the published EHR client. What is the right setup?
Select an answer to reveal the explanation.
Short Explanation
Non-persistent desktops are copies of one mold. Put the sensor and EHR permission on the golden image, then let a VDI sensor group hand every clone the same policy.
Full Explanation
Non-persistent VDI still receives Carbon Black Cloud policy through a sensor group; permissions for the published EHR client belong on that image-scoped policy. Skipping sensors, toggling prevention on every clone, or substituting NSX Guest Introspection as the allow list leaves clones unprotected or inconsistently excepted. Bake the group assignment and permission into the golden image.