Endpoint strategy
WindowsWindows.
If your users connect to Windows-based cloud desktops, virtual desktops or remote applications, keeping Windows on the endpoint often delivers the most direct, compatible and future-ready experience.
XPC builds on that advantage by turning the Windows endpoint into a simple, controlled gateway to the services your users need — without replacing the Windows platform underneath.
Linux connecting to Windows? Possible. But not always first, fastest or fullest.
The simple idea
When the destination is Windows, the endpoint should not fight the journey
The broker or cloud platform may change. The remote operating environment is still overwhelmingly Windows. A Windows endpoint talking to a Windows service is often the shortest path to full compatibility, timely feature access and fewer surprises — because Windows is usually the platform Microsoft supports first and most completely.
Azure Virtual DesktopWindowsMicrosoft's own desktop and app delivery service.
Windows 365WindowsCloud PCs that are, by definition, Windows.
CitrixWindowsOften brokering Windows desktops and Windows published applications.
Omnissa HorizonWindowsFrequently used to deliver Windows desktops and applications.
RDP / Remote Desktop ServicesWindowsInherently Windows-centric by design.
When the destination is Windows, Windows is the most natural place to start.
Strategy
Why keeping Windows on the endpoint can be the smarter strategy
None of this says Windows is always right. It says that when the destination is Windows, the endpoint has a shorter path to compatibility and new capability.
Windows-first compatibility
Microsoft's newest endpoint and remote-workspace capabilities are naturally designed around Windows first. When the workload is Windows, the endpoint is running the platform those clients are built for.
Faster access to new capabilities
Improvements to performance, media handling, device redirection, security and desktop experience commonly reach supported Windows clients early in the rollout.
Less waiting for parity
Linux and macOS clients are separate implementations with their own release cycles. Parity often arrives — but timing, scope and architecture can vary by vendor and version.
Fewer cross-platform compromises
A Windows-to-Windows path removes one operating system from the equation when the workload, policies and support model are already Microsoft-centric.
Better fit for enterprise support models
Windows endpoints work naturally with Windows drivers, peripheral support, endpoint agents, patching and the management tools your team already runs.
XPC lets you keep this advantage
Rather than replacing Windows with a different endpoint operating system, XPC simplifies what the user sees while preserving the Windows platform and its compatibility benefits.
Endpoint alignment
One platform in the path, or two?
Both paths reach the same Windows workspace. The difference is how many endpoint platforms have to stay aligned with it.
WindowsWindows
The shortest path.
Windows endpoint
XPC in front, Windows underneath
Windows workspace
AVD, Windows 365, Citrix, Horizon, RDS
- Native alignment
- Latest client capabilities
- Windows drivers and peripherals
- Enterprise Windows tooling
Other OS → Windows
It can work — but there is another platform in the middle.
Linux or macOS endpoint
Separate endpoint platform
Windows workspace
The same Windows destination
- Platform-specific client
- Separate support cycle
- Feature parity may vary
- Timing depends on vendor roadmap
The closer your endpoint is to the platform being delivered, the fewer translation problems you invite.
First in line matters
The endpoint client matters more than it looks
A remote desktop is not simply a picture being sent across the network. Modern remote-workspace clients increasingly participate in the session, and the operating system underneath decides which of those capabilities are available — and when.
The more sophisticated the remote workspace becomes, the more the endpoint platform matters.
- Media and video processing
- Microsoft Teams calling and meetings
- Cameras and microphones
- Graphics acceleration
- Multiple monitors and display technologies
- USB, smart cards and peripherals
- Printing
- Authentication
A real-world example
Microsoft Teams optimisation for virtual desktops
Microsoft's newer Teams VDI architecture uses a media engine called SlimCore to move much of the Teams media processing out of the virtual desktop and onto the endpoint. Microsoft's own documentation lists supported Windows endpoints — including Windows LTSC thin clients — and supported macOS versions. It also illustrates roaming between a Windows endpoint using the newer architecture and a corporate-managed Linux thin client that supports the older WebRTC optimisation.
Windows endpoint
Supported Windows versions, including Windows LTSC thin-client builds, can use the newer SlimCore-based optimisation.
macOS endpoint
Supported macOS versions are now covered by the newer architecture as well, subject to client and version requirements.
Linux thin client
Depending on the client and platform combination, these environments can still rely on the older WebRTC optimisation architecture.
The question is not simply “can it connect?”. The better question is which endpoint puts you in the strongest position for what comes next.
Capabilities vary by client, platform and version. Refer to current Microsoft documentation for the authoritative support matrix.
Where this matters most
Windows destinations, whichever platform delivers them
Azure Virtual Desktop
A Windows endpoint is naturally aligned with Microsoft's own desktop delivery platform. Formerly known as Windows Virtual Desktop.
Windows 365
When users access Windows Cloud PCs, keeping Windows at the edge usually simplifies the compatibility story.
Citrix delivering Windows
Citrix may broker the session, but the remote workload is still commonly Windows — so Windows endpoints remain highly relevant.
Omnissa Horizon delivering Windows
Where Horizon delivers Windows desktops or applications, a Windows endpoint remains a strategically strong fit.
RDS / RDP
The most native client and platform alignment here is still Windows to Windows.
Browser and Windows-centric business apps
Even where access is browser-delivered, the surrounding tooling, peripherals and management are often already Windows.
Architecture
XPC does not replace the connection technology. It simplifies access to it.
XPC does not try to become Citrix Workspace, Windows App, the Horizon Client or the WorkSpaces client. Those stay specialist clients on the Windows endpoint. XPC controls how users reach them.
User
One simple screen with only the approved connections.
XPC
Simple, controlled interface, configured from XPC Portal.
Windows endpoint
The platform stays in place, with everything IT already runs on it.
- Drivers
- RMM
- Security
- Patching
- Peripherals
- Native clients
- Browser
- Authentication
Connection client
The specialist client keeps doing its own job.
- Windows App
- Citrix Workspace
- Horizon Client
WorkSpaces client- RDP
- Browser
Remote workspace
Whichever platform delivers the session.
- Azure Virtual Desktop
- Windows 365
- Citrix
- Omnissa Horizon
- RDS
- Other approved services
Keep Windows. Simplify the endpoint.
XPC keeps the Windows advantage — and removes the Windows clutter
The traditional objection to Windows as a thin-client endpoint is fair: a normal Windows desktop gives users far more than they need. XPC changes that equation without changing the operating system.
What the user no longer sees
- Start menu and desktop clutter
- Settings and Control Panel
- File Explorer wandering
- Unapproved local applications
- System interfaces and notifications
- Ways to drift away from the workspace
What your IT team keeps
- Windows compatibility and drivers
- Native remote-workspace clients
- Your RMM and remote support
- Endpoint security and application control
- Patching, Windows Update and BitLocker
- Printers, peripherals and monitoring agents
One consistent experience
Different users. Different services. One endpoint experience.
An office worker, a home-based colleague and the IT administrator supporting them all start from the same simple XPC screen. Behind it, the workspace platform can change without changing what users see or how the endpoint is managed.
XPC in front. Windows underneath. Your workspace behind it.
Fair comparison
This is not about saying Linux or macOS are “bad”
A specialist Linux thin-client operating system can offer a small footprint, appliance-style management, tightly controlled configuration and a reduced Windows-specific attack surface. For organisations that specifically want to remove Windows, those can be compelling advantages. macOS clients for major remote-workspace platforms are also very capable, and Microsoft, Citrix and Omnissa continue to invest in them.
But every non-Windows endpoint introduces another platform whose client implementation, packaging and release schedule must stay aligned with a Windows-based environment. Sometimes parity arrives quickly. Sometimes an optimisation uses a different architecture, or a Windows-only component becomes the exception that matters.
So if the services your users depend on are fundamentally Windows-based, it is reasonable to ask whether the endpoint should also stay in the Windows family for the most direct compatibility path. XPC simply offers a different trade-off: keep Windows compatibility underneath, and remove Windows complexity from the user experience.
FAQ
Questions we are asked about endpoint platform choice.
If the destination is Windows, keep the endpoint ready for Windows.
XPC helps you keep the compatibility benefits of Windows while replacing the user-facing desktop with a simpler, controlled experience built for remote workspaces and cloud access.