A government agency wants endpoint experience from staff laptops, while lobby kiosks run an operating system other than Windows, Mac, or Room OS. What is the sound rollout?
Select an answer to reveal the explanation.
Short Explanation
A badge reader built for staff doors will not magically scan a freight gate. You put Endpoint Agents on the staff devices that run Windows, Mac, or Room OS, and you treat the other kiosk operating system as its own problem. One closet probe, a WAN Insights page with no endpoint, or an image that omits the agent does not collect that laptop experience.
Full Explanation
Endpoint Agents are the collector for user devices on the operating systems this design covers: Windows, Mac, and Room OS. Staff laptops on those systems get the agent. Lobby kiosks on a different operating system are a separate collection problem, not a reason to pretend one vantage point is every endpoint. One Enterprise Agent in a closet is a network probe; asking it to cover both the laptops and the kiosks leaves the laptop experience unmeasured and still does not put an endpoint collector on an unsupported kiosk. A WAN Insights view with no agent installed on any user device can speak to WAN and SaaS paths and does not report from the staff device. Imaging every laptop and kiosk while leaving the Endpoint Agent out produces machines that never join the endpoint tests, including the laptops that could have run the agent. Exam caveat: unsupported operating systems do not expand what an Endpoint Agent can install on; they change the tool you choose for that fleet. Operational check: inventory staff devices by operating system, deploy the agent on the Windows, Mac, and Room OS population, and record a different method for the kiosks.