The hardware already works. Keep it that way.

Why replacing the endpoint OS is expensive

Move a fleet to a Linux-based thin-client operating system and every attached device returns to the test plan: does the driver exist, does the vendor utility run, is the behaviour identical, who supports it when it is not. That work is often the largest hidden cost of an endpoint migration. Keeping Windows removes it.

• Receipt, label and document printers
• Barcode, RFID and document scanners
• Headsets, handsets and conferencing devices
• Smart card readers, signature pads and specialist devices

Native clients and their plugins

XPC launches the vendor's own client on the Windows PC. That means the client's version, configuration, group policies, plugins and real-time media optimisation components are the ones your platform team already supports — not an approximation maintained by a third party.

Multi-monitor and display behaviour

Display layout, resolution and multi-monitor handling remain the responsibility of the native remote client, so the behaviour users already know does not change when XPC is enabled.

What we do not claim

XPC does not add peripheral capability that Windows or your remote client does not already provide. If a device or redirection feature does not work today on the Windows endpoint, XPC will not change that. The compatibility page states the boundaries plainly.