Enable Screen Sharing on a Rented Mac Mini

Published November 11, 2026 • Figment editorial team

What a Mac rental actually gives you

Short answer: on modern macOS (12.1 and later) you cannot enable Screen Sharing with a shell command alone. The kickstart helper that ships with Remote Management can only deactivate the service; turning Screen Sharing or Remote Management on now requires the Sharing pane in System Settings or an MDM configuration profile. That reshapes what "enable screen sharing on a rented Mac Mini" means in practice — it is a conversation with the provider first, then a short checklist in System Settings, then an SSH tunnel.

Before signing anything, confirm these four points in writing with the rental provider:

Is Screen Sharing (or Remote Management) already enabled on the delivered image?
Does the account you receive have administrator rights so you can toggle sharing yourself?
Is inbound SSH available on the host, on which port, and from which source addresses?
How do you reach a macOS desktop the very first time — a provider web console, an already-active VNC/ARD endpoint, or neither?

Figment publishes three relevant tiers that you can request at /mac-hosting. The $29/month virtual Intel macOS plan is reached through a browser console only: there is no inbound SSH and no exposed guest VNC port. The physical i3 Mac is $49/month, and physical M-series Macs start from $95/month. Physical plans are provisioned on request, and the exact chip, RAM, disk, administrator account, macOS version, and inbound-SSH policy are agreed in the quote. Submit requirements at /mac-hosting/start.

If your rental is a browser-console VM, stop here. The VM already draws its desktop in the browser; installing a second VNC server on it would not be reachable from the public internet and is not supported. Everything below is for a physical Mac rental where the provider has explicitly quoted administrator access and inbound SSH.

Apple's current guidance for turning Screen Sharing on or off is a System Settings workflow, not a kickstart one. You need an interactive desktop session for the first toggle — either via the provider's console or a pre-enabled ARD/Screen Sharing endpoint the provider ships with.

Once you have a desktop, open Apple menu → System Settings → General → Sharing, then:

If Remote Management is on, turn it off — Remote Management and Screen Sharing cannot run simultaneously.
Click the information button next to Screen Sharing and switch it on.
Under Allow access for, choose Only these users and add the single operator account you will connect as. Avoid All users on a rental; that setting admits every local account, including service users you may not control.
Decide whether to enable VNC viewers may control screen with password and set a password. Without that toggle, only Apple's own Screen Sharing client (on another Mac) can authenticate. Third-party clients on Windows and Linux rely on this VNC-compatibility path.
Click Done.

Native Apple Screen Sharing and legacy VNC are not the same protocol. macOS speaks an extended RFB dialect that Apple's Mac client negotiates (higher colour depths, clipboard sync, and drag-and-drop). The VNC-compatibility toggle falls back to plain RFB so RealVNC Viewer, TigerVNC, and Remmina can connect. That compatibility authentication is the DES challenge/response defined in RFC 6143 §7.2.2, which truncates the shared secret to eight bytes. Treat the VNC password as a weak factor: short, unique to this host, and only usable over an encrypted tunnel.

Enable Remote Login (SSH) in the same Sharing pane if the provider did not pre-enable it, and scope its Allow access for list to the same operator user. Apple documents this toggle in Allow a remote computer to access your Mac.

Expect macOS to prompt for Screen Recording and Accessibility consent the first time a remote viewer attaches to the operator account. Those prompts are account-scoped and cannot be dismissed from the command line; approve them in System Settings → Privacy & Security on first connect.

Connect from Windows or Linux over an SSH tunnel

With SSH and Screen Sharing both on, forward port 5900 through the encrypted channel. From Windows (PowerShell, which ships with OpenSSH on Windows 10 and 11) or any Linux terminal:

ssh -N -L 5901:localhost:5900 operator@YOUR_HOST

Leave that terminal running. Point the VNC client at localhost:5901:

Windows: RealVNC Viewer or TigerVNC. Server localhost:5901. Password is the one you set in the Screen Sharing pane.
Linux: vncviewer localhost:5901 (TigerVNC) or Remmina with the VNC plugin against the same address.

If the first handshake fails, verify from the Mac side that the listener is bound locally before touching any firewall:

sudo lsof -iTCP:5900 -sTCP:LISTEN

You should see screensharingd on *:5900 or localhost:5900. If nothing is listening, Screen Sharing is not actually on; return to the Sharing pane. Do not ask the provider to open 5900 inbound on the perimeter — the SSH tunnel keeps the port private and makes the public VNC question moot.

Rental checklist and troubleshooting

Use the following checklist as a short artifact to paste into your first email to a prospective provider. Every item is something that can quietly block the setup above:

Administrator account on the delivered image, with the user name you will reference in "Only these users"
Named macOS version (ask specifically; do not assume Tahoe or Sequoia)
Inbound SSH confirmed, with port and allowed source addresses
Console path to the desktop for the first toggle, or a pre-enabled Screen Sharing/ARD endpoint
Statement of whether Screen Sharing is pre-enabled or must be toggled by you
Perimeter firewall policy and whether the provider manages an ACL you cannot change
Written statement of what the provider will not change on the image (for example audio, GPU passthrough, or arbitrary DMG uploads)

Troubleshooting the common failures:

VNC client says authentication failed. The compatibility password is truncated to eight bytes; re-set it to an eight-character secret.
Black screen or grey background after login. First connect from the provider console and approve Screen Recording for the operator account in Privacy & Security, then relaunch the viewer.
Session drops when idle. Consult the installed caffeinate(8) manual page with man caffeinate, then run caffeinate -dims & inside your SSH session. For a persistent policy, open System Settings → Battery (or Energy Saver on Intel desktops) and disable automatic sleep on power.
Reboots. Screen Sharing comes back as a launch daemon, but SSH tunnels do not; re-run the ssh -N -L command after the Mac restarts.
Nothing listening on 5900. Either Screen Sharing is off or Remote Management is on; only one of the two can be active at a time.

Figment positions the $29 virtual Intel macOS plan for browser-only desktops and the $49 and from-$95 physical tiers for workflows that need inbound SSH, administrator rights, and your own Screen Sharing configuration. Agree the specific hardware, macOS version, and access model in the quote, then request provisioning at /mac-hosting/start.

Related guides: