How XPC works
A focused Windows endpoint experience for Citrix and RDP.
XPC places a purpose-built access interface in front of Windows. Users see the remote connections and endpoint controls they need. IT retains control of everything underneath.
Six stages
From install to steady state.
- 01
Install XPC on the Windows endpoint
XPC is deployed alongside the customer's existing software and management agents.
- 02
Register the endpoint
The XPC-Cloud-Connector authenticates the endpoint to the appropriate tenant in XPC Portal.
- 03
Assign an XPC Configuration
Administrators group endpoints into configurations that define the XPC experience and available connection options.
- 04
Choose the appropriate operating mode
Use Shell Mode for the most controlled user experience or Init Mode where broader endpoint compatibility is required.
- 05
Present approved Citrix and RDP connections
XPC launches the customer-installed and customer-managed connection clients.
- 06
Maintain Windows with existing IT tools
RMM, remote support, patching, endpoint security, drivers, services, and other corporate agents continue operating underneath.
Responsibility
One endpoint. Two management responsibilities.
XPC Portal and your existing IT platform work in parallel. Neither replaces the other.
XPC Portal manages
- Tenant and XPC configuration
- Endpoint registration and XPC status
- Connection presentation
- XPC Live and XPC Suspended state
- Shell/Init selection
- Citrix/RDP readiness reporting
- Authorised return to the normal Windows shell for maintenance
Your IT platform manages
- Windows
- Citrix Workspace and RDP configuration
- Updates and patches
- RMM and remote support
- Antivirus, EDR, and application control
- Drivers and peripherals
- Corporate services, agents, and plugins
Positioning
Closer to a controlled Windows shell than a new OS.
XPC is not a new operating system, and it is not a conventional Windows kiosk locked to a single application. It is a controlled Windows shell experience that presents users with the specific remote connections and endpoint controls the customer approves.
Because Windows remains in place underneath, the customer keeps the driver, agent, peripheral, service, and management ecosystem it already operates.
FAQ
