Remotely
Remotely is a self-hosted remote desktop and support platform for managing enrolled devices and interactive sessions. This page covers agent enrollment, access scope, audit records and removal of stale endpoints.
What Remotely provides
Remotely coordinates remote support sessions between a self-hosted service, an operator console and enrolled agents. It is useful when an organization wants control over the service boundary and device list, but the platform still requires careful account, network and consent management.
Enrollment and operator scope
Enroll one test device first, record the agent identity and confirm which operators can view or control it. Keep support notes separate from secrets, set an expiry or review date for temporary enrollment and remove agents that are retired, duplicated or no longer assigned.
Maintenance note
This page reviews Remotely for self-hosted support, agent enrollment, session review and endpoint lifecycle management. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Remotely to this cloud drive
Baidu Netdisk
Save Remotely to this cloud drive
Remotely self-hosted support guide
Deploy a small test service, enroll one non-critical device and verify operator permissions, session visibility and cleanup before adding more endpoints.
Before you start
- Prepare a service host with a documented backup and update process.
- Define operator roles, device ownership and the approval process for remote control.
- Choose a non-critical test device and keep a local recovery path.
Installation steps
- 01
Configure the service boundary
Install the service, set its host and storage policy, create the initial administrator and confirm that the console is reachable only through the intended access path.
- 02
Enroll one test agent
Install the agent on the test device, record its generated identity and verify the displayed device name, operating system and last-seen status.
- 03
Run and review a support session
Use the least-privileged operator role to start a short session, confirm the consent and audit indicators, then close the session and review its record.
Quick start
- 01
Add review dates
Record owner, purpose and next review date for every enrolled device so temporary support access does not become an untracked permanent endpoint.
- 02
Limit control features
Enable file transfer, terminal or remote control only for roles that need them, and test that a viewer-only operator remains restricted.
- 03
Test agent removal
Retire the test device, revoke its enrollment and confirm that it disappears from active inventory without deleting the audit evidence needed for review.
Usage tips
- Keep the service, operator accounts and agents patched on a planned schedule.
- Avoid placing credentials or private customer data in device descriptions and support notes.
- Review active sessions and last-seen devices regularly, especially after staff or device ownership changes.
Troubleshooting and uninstall
Why is an enrolled device offline?
Check the agent service, outbound network path, device clock and service address, then compare the agent identity with the inventory record before reinstalling it.
Why can an operator see a device but not control it?
Review the operator role, device assignment, consent state and session policy; visibility and interactive control should be treated as separate permissions.
- Revoke the device enrollmentEnd active sessions, mark the endpoint retired in the inventory and revoke its agent identity before removing the local service.
- Remove service and agent dataUninstall the agent or server component through the operating system, preserve required audit records and delete cached secrets only after the retention review.
Frequently asked questions
Is Remotely a public relay service by default?
It is a deployment you operate and configure. The service address, network exposure, operator accounts and agent policy determine the actual access boundary.
Should every enrolled device have full remote-control access?
No. Assign the narrowest role and feature set that supports the task, and use a viewer-only or consent-based workflow when interactive control is not required.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.