Skip to content

Desktop Connections ​

Remote Access, Remote Desktop, Hyper-V consoles, and Quick Support use the selected Relay to connect the operator's browser and the device over HTTPS/WSS. Intel AMT KVM and SOL have separate connection requirements.

An available Relay with the required permitted use and free channel capacity is required to start a desktop session. Managed endpoints use the Relay assigned through their service routing. Quick Support uses one of the Relay services included in the distributed client.

If the Relay connection is interrupted, the viewer shows Reconnecting while it attempts to recover the same session. Input pauses during the interruption. Traffic resumes after both participants reconnect and confirm the recovered secure channel. If recovery expires, start or reconnect the viewer as described on the feature's page.

Picture quality ​

Picture quality and update rate adapt automatically to the connection. On slower connections, fine detail can take longer to sharpen after activity stops.

Remote Access and Quick Support can use window outlines while dragging when connection performance is limited. This remains in effect until the last viewer disconnects, when the previous dragging preference is restored. Wallpaper and animation preferences are preserved.

Trust ​

See Architecture for the desktop connection trust model.

For Quick Support, obtain the client and invitation from the intended support organization and check the operator before approving access.

Ports and firewall requirements ​

The standard deployment uses TCP 443:

SourceDestinationPort and protocolRequired for
Operator's browserOrdyn application and selected RelayOutbound TCP 443, HTTPS/WSSSign-in, session setup, and desktop transport
Managed AgentAssigned Edge and selected RelayOutbound TCP 443, HTTPS/WSSAuthorization, session control, and desktop transport
Quick Support clientConfigured Relay servicesOutbound TCP 443, HTTPS/WSSInvitation authentication, session control, and desktop transport

Managed Agents keep using their assigned Edge for control and do not require direct access to the Ordyn application server. Neither the browser nor the device needs inbound network access for a desktop connection.

For Remote Desktop, the Agent connects to the RDP listener on the same Windows device using its locally configured port (TCP 3389 by default). The browser does not connect to that port. Do not expose or forward RDP port 3389 for Ordyn access.

For a Hyper-V console, the device-side connection ends at the Hyper-V host Agent. The guest does not need inbound RDP access or a network connection to the operator's browser.

See Relay network requirements for the service infrastructure connections.