Documentation / Installation

Install the MindShield SQL Agent

A controlled installation prepares the Windows host, registers the agent service and establishes the foundation for activation and SQL Server discovery.

Last reviewed: July 2026Public product guidance

Before you begin

Confirm that the host is authorized for protection and that the person performing installation has local administrative rights. Record the intended customer, organization, device name and SQL Server instances before making changes.

Preparation checklist
  • Supported 64-bit Windows host.
  • Reliable outbound HTTPS access to the approved MindShield API endpoint.
  • Sufficient local or approved backup storage.
  • Approved SQL Server service identity and permissions plan.
  • Valid activation information supplied through an authorized channel.

Install the agent

  1. Obtain the approved installer from MindShield support or your authorized partner.
  2. Verify the installer filename, release channel and checksum when one is supplied.
  3. Run the installer as an administrator.
  4. Review the installation directory and locked API endpoint.
  5. Select the detected SQL Server instances intended for setup review.
  6. Complete installation and allow the installer to create the Windows service.
Controlled distribution

Do not use an installer received through an unverified link or copy an already-installed agent directory from another computer.

Validate the Windows service

Open Windows Services and confirm that MindShieldAgent exists, uses the approved service identity, has startup type set to Automatic and is running. A running service confirms process startup only; it does not prove activation, API connectivity or SQL Server permission.

Complete post-installation checks

  • Confirm the agent can reach the production API over HTTPS.
  • Complete license activation and device registration.
  • Confirm the correct device appears in the authorized dashboard scope.
  • Review discovered SQL Server instances for duplicates or stale entries.
  • Test permissions before selecting databases for a policy.