A school wants newly cloned student desktops to be Guest Introspection-ready at first boot instead of waiting for a post-clone Tools install. What should be baked into the golden image?
Select an answer to reveal the explanation.
Short Explanation
Whatever you leave in the golden image is what every clone is born with. Put GI-enabled VMware Tools in the template and the first boot already has the thin agent.
Full Explanation
A school that wants newly cloned student desktops Guest Introspection-ready at first boot must bake VMware Tools with Guest Introspection components enabled into the golden image. Whatever ships in the template is what every clone inherits without a post-clone Tools scramble.
Baking only the Carbon Black uninstaller so clones start without endpoint agents works against readiness. A blank Tools install completed after every clone reintroduces delay and drift. An NSX Edge appliance inside the golden image cannot stand in for guest GI drivers.
Exam caveat: golden-image Tools+GI is the scalable path for clone-ready introspection.
Operational check: update the template with GI-enabled Tools, clone a pilot desktop, verify GI ready at first boot, and lock the image standard before mass cloning for term start.
Golden-image GI Tools make student clones ready at first bell. Validate each image build with an automated GI health probe post-clone, and refuse to publish images that require manual Tools installs during peak enrollment. Keep post-clone GI health probes from the golden-image pipeline with the school image record so the next on-call engineer blocks images that still need manual Tools installs during enrollment rushes.