Mideye endpoint setup guide: install to protected sign-in
This guide is for the administrator who sets up the Mideye endpoint on a Windows computer. Follow the pages in order. At the end the computer asks for a second factor at every sign-in, and you have a tested way back in. Each page lists what you need, the steps with the exact labels in Mideye Configuration, how to verify the result, and what to do when it fails. Use a test computer or a virtual machine first, and keep a second administrator session open until you have tested.
Core path
Section titled “Core path”- Before you begin: choose the backend and check what you need.
- Install: run the MSI and restart Windows 11.
- Connect one backend, either:
- Connect Mideye Cloud: client ID and secret, Touch on the phone, no server to run; or
- Connect Mideye Server: your own Mideye Server, an Authentication API endpoint and a pinned certificate.
- Break-glass: a break-glass account and code, your way back in.
- Turn protection on: arm the computer, test the first sign-ins, and let it activate.
- Remote Desktop: check that RDP asks for the second factor too.
Set up break-glass before you turn protection on. Activation needs a break-glass account.
Optional features
Section titled “Optional features”Add these after the core path, or before you turn protection on if users need them from the first day.
Hardware tokensSign in with a code from a hardware token or a YubiKey.
Assisted LoginA named approver confirms the sign-in, by phone or with codes.
Authenticator appUsers enrol an app at the sign-in screen and use it offline. Mideye Server only.
Join FleetManage many computers with one policy.
After setup
Section titled “After setup”- Logs and events: where to look when something fails.
- Upgrade and uninstall.
- Mideye Configuration reference: every page and field.

