InputGuard

Deployment

Windows deployment

Deploy InputGuard to Windows devices by assigning the Chrome extension through your normal channel, then running an enrollment script from your organization’s deployment profile.

Overview

Windows devices are deployed with an enrollment script you download from the portal. Extension installation is separate, so the script does not own Chrome-wide install policy.

  • Install or assign the InputGuard Chrome Web Store extension through your normal browser or device-management channel.
  • Run the enrollment script to give the device a stable identity, capture hostname and OS, and write InputGuard managed configuration.
  • Restart Chrome or reload chrome://policy so the extension reads the managed configuration.

The script writes only InputGuard’s extension-specific managed configuration. It does not write ExtensionSettings or ExtensionInstallForcelist.

Organization deployment

Install or assign the InputGuard Chrome extension through your normal browser-management channel. InputGuard enrollment scripts then configure the installed extension and enroll devices into your organization.

Deploying through MDM?

Push the enrollment script through Jamf, Microsoft Intune, Kandji, Mosyle, RMM, or your existing endpoint automation. See MDM deployment.

Download the script

Enrollment scripts are generated per organization from a deployment profile in the portal, so there is nothing to download here — you get the Windows script from your own workspace.

  1. 1

    Open Deployment in the InputGuard portal

    Go to the Deployment page in your workspace.
  2. 2

    Create or select a deployment profile

    A profile carries your organization’s enrollment settings and can be reused across devices.
  3. 3

    Open Deploy and download the script

    Open the profile’s actions (⋮) menu, choose Deploy…, then select Download enrollment script under Windows. You get a direct script download such as inputguard-enroll-<profile>-windows.ps1.

Extension installation is separate

Install or assign the published Chrome Web Store extension before running the script. The script configures InputGuard for your organization but does not install or force-install the extension.

Install on a device

On the Windows device:

  1. 1

    Install or assign the Chrome extension

    Use the Chrome Web Store, Google Admin, your MDM, Group Policy, RMM, or existing Chrome policy.
  2. 2

    Run the enrollment script

    From an elevated PowerShell session run: powershell -ExecutionPolicy Bypass -File .\inputguard-enroll-<profile>-windows.ps1. It creates or reuses a stable device identity, captures hostname and OS, and writes the device-specific managed configuration.
  3. 3

    Reload Chrome policy

    Restart Chrome (or open chrome://policy and click Reload policies) so the managed configuration takes effect.

Verify enrollment

After running the enrollment script, open the portal and go to the Devices page. The Windows device should appear in the device list, confirming it registered with your organization. Once it is listed, you can assign policy to it.

Not showing up?

Give enrollment a moment to complete, then refresh the Devices page. See Device enrollment for how registration works.