A “Not Optimized” status in Teams is not, by itself, proof that the endpoint is defective. Check whether the precise Teams, Horizon Agent, Horizon Client, and endpoint combination supports the intended optimization mode. This guide focuses on that compatibility decision for environments that still use Tera2 PCoIP zero clients.
Correction — September 12, 2026: The earlier article described a deployment with 100% of users affected and host CPU exceeding 90%, without an attributable test record. Those numbers and the claim of a universally proven hardware replacement fix have been removed. No measured deployment results are asserted below.
Distinguish remote display from media optimization
A device being able to display a Horizon desktop does not establish that it can run the endpoint component needed for Teams media optimization. HP documents the Tera2 PCoIP zero-client platform; use its exact model and firmware when checking support, rather than treating every product called a zero client as equivalent.
Omnissa's Teams optimization guide is the reference for the supported implementation and troubleshooting workflow. Optimization requirements evolve. A generic statement that all Windows, Linux, macOS, or thin-client devices support every Teams feature is not a substitute for the version and feature requirements.
Compatibility record to complete before changing hardware
| Layer | Record | Question to resolve |
|---|
| Application | Teams version, installation type, reported media mode | Which optimization architecture is being used? |
| Virtual desktop | Windows build, Horizon Agent version and installed features | Does this image support and enable that architecture? |
| Endpoint | Manufacturer, model, OS or firmware, Horizon Client where applicable | Can this exact endpoint run the required media component? |
| Session | Selected protocol, effective policies, device permissions | Is the feature available in this actual session? |
| Business requirement | Camera, microphone, screen sharing, accessibility needs | Are all required features supported, not just audio? |
Use a supported comparison endpoint
With an approved test account, connect to the same pool using an endpoint explicitly supported for the required optimization mode. Record the media status and run a short agreed call scenario. Keep the desktop image and application version constant. If the status changes, endpoint compatibility or configuration becomes a stronger lead; that alone does not establish a particular hardware defect.
If both endpoints remain unoptimized, investigate the Agent installation, policy, application configuration, and documented prerequisites before buying replacements. If only the Tera2 path lacks support for the required component, document that specific compatibility gap and test a supported alternative before proposing a fleet migration.
Measure the outcome, not just the label
Record call setup, microphone and camera behavior, screen sharing, CPU observations on the desktop and endpoint, and any disconnects. Identify what was measured and over what interval. Do not infer a host-wide capacity reduction from one successful call. Repeat the workflow after reconnect and verify the required peripherals and user controls.
Decision and rollback
Separate three outcomes: a configuration correction on a supported platform; an unsupported combination requiring a different endpoint or application path; or an unresolved failure needing vendor logs. A firmware update is not automatically a missing media engine, and a modern thin client is not automatically compatible.
Pilot changes with the desktop and endpoint owners. Keep the previous approved endpoint configuration available, verify management and security requirements, and roll back if the replacement breaks peripheral access or other business applications. Request a written compatibility answer from the supplier when the published matrix does not cover your exact combination.
Related troubleshooting guides
Comments
Post a Comment