Install

This section covers everything that has to be installed before you can help anyone: the Blink server (only if you run Blink on premises), its certificates, the Access agent on the computers you look after, and the support tool your customers run for a one-off session.

Before you start

Check supported systems: which computers Blink runs on, and what the network has to allow.

Your Blink server (on premises only)

Install Blink on your own server: server and storage requirements, DNS name, ports, data, first start and the recovery kit.
Set up certificates: Let’s Encrypt from the console, your own certificate, and the built-in one.
Back up and restore the server: what to back up, and how to bring a server back on new hardware.
Upgrade the server: move to a new server version safely.

Access agent (unattended computers)

Create an enrollment key: the key that lets an agent join your organization.
Install the Access agent on Windows: signed installer, command line for scripted rollouts, or straight from a support session.
Deploy the Access agent with your RMM tool: ready-made scripts and steps for NinjaOne, Datto RMM, N-able, ConnectWise, Kaseya, Atera, Syncro, Intune, Configuration Manager, Group Policy and more, and how to switch from your old remote access tool.
Keep agents up to date: how updates reach your computers and what the console shows.
Uninstall the Access agent: remove it from a computer and clean up the console.

Support tool (one-off sessions)

Run the support tool: what your customer downloads and runs, on Windows and Mac.
Allow Blink on a Mac: the macOS privacy settings Blink needs to see and control the screen.

When everything is installed, carry on with Configure or Use Blink. If something does not work, see Troubleshooting or .

Question about this page?

Ask the AI assistant. It starts from this page, then searches the rest of the docs.

Documentation

For AI tools

IZT

Contact IZT