Install the Mideye endpoint on Windows with the setup wizard

This page is for the administrator who installs the endpoint on one computer with the setup wizard. The install changes nothing at sign-in: Windows keeps its own sign-in until you turn protection on. For many computers, see Join Fleet.

Before you begin

• The MSI, mideye-credential-provider-<version>-x64.msi, and local administrator rights. See Before you begin.
• No older Mideye Credential Provider installed.
• For Fleet mode: the onboarding file made in Fleet (Nodes, Add computers).

Steps

1. Copy the MSI to the computer and run it as an administrator.
2. On the first page choose the mode. Local is selected by default.
   • Local: standalone. You configure the computer in Mideye Configuration. Choose this for this guide.
   • Fleet: managed by Mideye Fleet. A second page asks for the full path of the onboarding file. The file holds the join key, so you copy the file instead of typing the key. Delete the file after the install.
   • Admin: the tools and Group Policy templates only, no service. For an administrator’s workstation.
3. Leave Install Mideye Configuration (graphical tool) ticked. It is not offered on Windows Server Core; use mideye cp there.
4. Press Install.
5. On Windows 11, restart the computer when the wizard asks, before you turn protection on. Windows Server does not need a restart.

The installer checks everything before it changes anything. If it refuses, a box titled “Mideye Credential Provider Setup” shows the reason, followed by “Nothing was installed.”

Verify

• Mideye Configuration is in Start, All apps, Windows Tools. Windows asks for administrator approval when you open it. Its first page, Overview, shows protection OFF.
• The service MideyeBroker is running in Services.
• Event Viewer, Application log, source Mideye Credential Provider: event 4011 names the version and the mode.
• The sign-in screen still shows only the normal Windows sign-in. The Mideye tile appears when you turn protection on.

Troubleshooting

• “Nothing was installed.” with event 1112: the usual causes are an older Mideye Credential Provider that is still installed, and an onboarding file that cannot be read.
• No Mideye Configuration on Windows Server Core: it is never installed there. Use mideye cp.
• Upgrade, repair and uninstall: see Upgrade and uninstall.
• More in Troubleshooting.

Next: Connect Mideye Cloud or Connect Mideye Server.