Appearance
Quick Support
Quick Support lets Remote Access Operator help someone on a Windows device without enrolling or installing an Agent. It uses the organization's Quick Support executable and a temporary invitation code.
An available licensed Remote Access connection is required. Quick Support shares capacity with managed Remote Access and requires no endpoint license.
Start support
- Open Operations → Quick support and generate an invitation.
- Give its ten-digit code to the person requesting help. The invitation lasts five minutes and permits one authentication attempt.
- The person opens your organization's client, enters the code, and checks the operator identity before allowing the connection.
- Open the session's viewer to begin support.
Use a fresh invitation after a failed attempt. Obtain both the client and invitation through your organization's trusted support process.
During support
Clipboard text sharing is optional. Picture quality adapts automatically to the connection; see Desktop Connections.
The person receiving support can use Stop sharing or close the client to end the session. The operator can use End session. Closing only the viewer leaves the approved session available; reopen it to continue.
If viewer recovery fails, use Reconnect. A lost client connection can end sharing when recovery expires; start a new session if that happens. Sessions last at most 24 hours.
Windows access
A normal launch controls the current user's desktop and cannot control elevated applications or UAC screens. When administrative access is needed, choose Relaunch as admin before connecting and complete the Windows administrator prompt.
Windows policy can still prevent UAC screen access. The person at the device must handle those prompts locally when required.
Administrator downloads
Use Service Operator to prepare distribution:
- Enable Quick Support on the participating Relays and configure their public HTTPS addresses.
- Upload a compatible Windows Quick Support release bundle under Releases.
- Configure optional privacy-policy and imprint links in Administration → Settings → Quick Support.
- Download the prepared executable and distribute it to users.
Download and redistribute the client after changing services, Relay addresses, or document links. Use a release compatible with the deployed support services.
Distribute A Permanent Download Link
Publish the selected release through a cache node's Published downloads. Relay and document-link changes refresh that client automatically while preserving the selected release and URL. The link may be temporarily unavailable during replacement.
A public download does not grant support access; invitation and consent are still required. See Desktop Connections for network requirements.