Getting StartedReading time 5 minUpdated 2026-09-09

Install and bind the Windows client: first-time setup for parents

Install the AIVI client on the supervised Windows PC, finish initialization, set the parent password and bind it to your parent account — then manage time rules remotely from the web console.

AIVI has two parts: the Windows client installed on the child's PC (enforces lock screen, time slots and process control), and the web control center parents use in a browser (configures rules and remote care). This guide walks through the first-time install and binding.

Install and bind in four steps

  1. 01

    Download and run the installer

    Get aivi_setup.exe from the Download page (the China and international editions share one installer). Run it as administrator; the wizard lets you pick the server site, auto-detected from the system country/region by default. You can also switch later in Settings → Server Site without reinstalling.

  2. 02

    Initialize: sign in or use local mode

    The first launch opens the initialization screen. Register or sign in with email/phone (invite code optional) to enable remote management, or choose local-only mode (no cloud binding; configuration stays in the on-device settings center).

  3. 03

    Set the parent password

    The parent password is the only credential for entering Setup mode, changing rules, temporary unlock and uninstalling. Choose something your child cannot guess and store it safely. It cannot be recovered online — a forgotten password requires reinstall or contacting support.

  4. 04

    Configure rules and return to Guardian mode

    Configure Time Management and App Management in Settings, then click Apply Now to return to Guardian mode. From then on the PC locks automatically on schedule; parents can see the device at /dashboard and manage it remotely (account and active plan required).

How to confirm the binding

  • The client home screen shows Remote Management: Connected at the bottom, with the membership name appended once bound.
  • The device card appears in the web console (/dashboard) with the correct device name and online status.
  • The device name is reported by the client heartbeat roughly every 10 seconds; if a placeholder shows right after binding, wait one heartbeat cycle.

Related guides