DEPLOYMENT GUIDE

From a download to a verified endpoint.

A practical sequence for client setup, protected license enrollment, Windows and Mac installation and a documented first connection.

Plan your evaluation Explore downloads

Pilot workflowCurrent availability

Angular monitors and laptops connected around a navy gateway cube — Original editorial illustration · Conceptual architecture

ON THIS PAGE01 / Define the pilot before distributing an installer 02 / Establish client ownership, users and groups 03 / Create and distribute protected enrollment input 04 / Choose the build and finish the local platform steps 05 / Verify readiness in the client workspace 06 / Close the test with recovery and access cleanup

CHAPTER 01

Define the pilot before distributing an installer

A deployment brief should name the client organization, the people who will administer it, the owned test devices and the workflows the pilot will evaluate. Record the operating systems and processor architectures so the download choice is explicit. Include recovery responsibility, expected network conditions and the criteria that make a device ready for support. CyberCursor separates the web portal for administration and observation from the installed controller for interactive screen, terminal and file work. Choose a small group that represents the environment rather than immediately treating every endpoint as a target. The published Windows and Mac builds are pilot installers; release signing, macOS notarization and fresh production endpoint acceptance remain separate gates. Define how your team will evaluate those requirements before relying on the rollout operationally.

CyberCursor workspace interface illustration with fictional Northstar IT devices — Product illustration · Fictional device and organization data

CHAPTER 02

Establish client ownership, users and groups

The platform owner provisions the client and its owner account, while the client administrator handles endpoint operations. Complete the assigned account’s password and authenticator setup before installation. Create a small group structure that maps to a site, department or test ring, then assign management users only where they need remote access. Temporary outside support should use an endpoint share with an appropriate expiry rather than a broad permanent assignment. Review the different permissions for remote control, file operations and terminal commands. Super Admin does not operate client endpoints in the current hierarchy. With ownership established, the deployment team has a clear place to create enrollment keys and inspect results. Keep a record of the named client owner and the person responsible for reviewing each pilot device.

CyberCursor groups interface illustration with fictional Northstar IT devices — Product illustration · Fictional device and organization data

CHAPTER 03

Create and distribute protected enrollment input

A client administrator with recent MFA can create the primary client key or a key for an existing group. Choose the group key when new endpoints should enter that group automatically; choose the primary key when grouping will happen later. Deliver the credential only through the authorized deployment process. For bulk Windows setup, use the documented protected JSON input file containing the key and agent name, and pass its path to the installer rather than exposing the key directly in command arguments. The installed Mac setup workflow can also read protected input under administrator authority. Your deployment system must remove temporary input after successful setup. Confirm the company’s endpoint allowance separately: the reusable key authorizes enrollment, while active plan and subscription limits remain independently enforced.

Management portal

Fleet overview, performance, inventory, groups, licenses and administrative context. File listings are read-only.

Desktop controller

Windows and Mac apps for interactive screen access, terminal commands and bounded file modifications.

Endpoint agent

Identity, reports and authorized actions on the owned computer. Availability depends on endpoint readiness and OS permissions.

CHAPTER 04

Choose the build and finish the local platform steps

Download the controller for the operator’s computer and the endpoint agent for the computer that will be managed. Windows x64 is for Intel and AMD PCs; Windows ARM64 is for Windows on ARM. On Mac, choose Apple silicon for M-series devices or Intel for older Intel-based Macs. Compare the installer with the published SHA-256 value and follow your organization’s pilot software process. Windows assisted endpoint setup includes key and agent-name fields. Mac enrollment takes place in CyberCursor Endpoint after package installation, and initial Screen Recording and Accessibility permissions must be granted locally. The endpoint and controller are separate components with independent versions. A successful download or package-content check is not the same as a working installed service, so continue through authenticated contact and device reporting.

Conceptual architectural operations screens — Original editorial illustration · Conceptual architecture

CHAPTER 05

Verify readiness in the client workspace

After installation, confirm that the endpoint appears once in the intended client and group with the chosen agent name. Compare its reported manufacturer, model, serial, architecture and operating system with local facts. Wait for fresh authenticated monitoring and validated remote-provider connectivity before attempting direct access. Open CyberCursor Remote using the production portal address, sign in with the appropriate role and test the intended view or control path on the owned endpoint. File and terminal acceptance should be recorded separately, using disposable data and short harmless commands. Offline demo samples have no installed agents and cannot demonstrate live monitoring or remote control. Keep the first report, local identity checks and actual endpoint outcomes together so the pilot decision is based on the installed environment rather than the website’s illustration.

01 / PLATFORM

Super admin

Organizations, clients and high-level administration.

02 / ORGANIZATION

Client & managers

Assigned endpoints, groups, enrollment keys and operational workflows.

03 / DELEGATION

Time-limited guest

Explicitly shared endpoints with a scoped expiry, rather than whole-client access.

CHAPTER 06

Close the test with recovery and access cleanup

A rollout acceptance record should include interruption and cleanup, not only the happy path. Test an offline device, verify that last-known reporting is labeled correctly and confirm that interactive operations are unavailable when the endpoint cannot respond. Remove a disposable management assignment or expire a guest share and inspect the access result. Revoke a test enrollment key to confirm that new setup stops without assuming that existing endpoints are removed. Record how an incomplete installation will be recovered and who will uninstall or revoke a test machine when the pilot ends. Preserve useful evidence without retaining unnecessary private files or credentials. Send the platform mix, deployment tool and proposed acceptance checks to connect@cybercursor.com if you want help preparing a controlled evaluation or identifying the next rollout gate.

Layered glass infrastructure and a shield-shaped security object — Original editorial illustration · Conceptual architecture

EVALUATION NOTES

Questions to take into your pilot.

Operational details matter as much as the interface.

What are the two installation components?

CyberCursor Remote runs on the operator’s Windows computer or Mac. CyberCursor Endpoint runs on each managed Windows or Mac computer.

Do I need an endpoint ID and password for pairing?

The current product flow uses a client or group license key plus an agent name. Remote permission still follows the operator’s authenticated account scope.

Can Mac permissions be skipped during setup?

No. Initial Screen Recording and Accessibility setup follows macOS controls. The pilot does not bypass those operating-system permissions.

What proves that a deployment is ready?

Verify client/group ownership, device identity, fresh reports and the actual required endpoint workflows. Installer completion alone is insufficient.

Continue exploring.

Connect this workflow to the rest of your endpoint workspace.

RESOURCESPILOT

Build your next endpoint workspace.

Start with a conversation about your fleet, your workflows, and a controlled pilot.

Talk to CyberCursor Get the desktop app