A manufacturer is rolling Secure Client out to plant laptops and wants endpoint experience data from that same rollout. Which approach fits?
Select an answer to reveal the explanation.
Short Explanation
The sensor belongs in the laptop image you are already rolling out, not in a side project. You deploy the Endpoint Agent through the Secure Client rollout so endpoint visibility arrives with it. A spreadsheet, turning Secure Client off, or a second collector that does not share the view breaks that plan.
Full Explanation
Endpoint visibility was requested as part of the Secure Client rollout, so the Endpoint Agent needs to arrive with that client rather than through a parallel effort. Deploying the Endpoint Agent through the Secure Client rollout fits, because the laptops that receive the client also receive the endpoint test vantage the plant asked for, and the results stay with that deployment. A spreadsheet of laptop complaints kept entirely outside the Secure Client rollout records anecdotes after the fact and never measures the endpoint path. Turning Secure Client off and installing a separate endpoint collector that ignores that rollout abandons the deployment that was supposed to carry the agent and substitutes a tool the rollout does not include. A second collector that records endpoint data and does not share the Secure Client view creates a second dataset the Secure Client deployment cannot see, which fails the request to arrive with that rollout. Exam caveat: installing any endpoint collector is not the same as carrying the Endpoint Agent inside the Secure Client rollout the plant is already executing. Operational check: on a pilot laptop that received Secure Client, confirm endpoint test results are present from that same deployment.