Windows deployment

Windows devices are deployed with a deployment package you download from the portal. Each package is a ZIP containing two artifacts plus a README:

• A managed registry policy (inputguard.reg) that carries your organization’s static configuration — and, in production, force-installs and locks the extension.
• A generic enrollment script that gives the device a stable identity, captures hostname and OS, and writes the device-specific managed configuration.
• A README with the exact steps for this platform.

The administrator workflow is the same on every platform: install the profile or policy, then run the enrollment script. The user never visits the Chrome Web Store or installs anything manually.

Deployment packages are generated per organization from a deployment profile in the portal, so there is nothing to download here — you get the Windows package 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 package

   Open the profile’s actions (⋮) menu, choose Deploy…, then select Download deployment package under Windows. You get a ZIP with the registry policy, the enrollment script (inputguard-enroll.ps1), and a README.

Unzip the package on the Windows device, keeping both files together, then:

1. 1

   Import the registry policy

   Double-click inputguard.reg, or run reg import inputguard.reg — or push it through your management tooling. In production it also force-installs and pins the extension.
2. 2

   Run the enrollment script

   From an elevated PowerShell session run: powershell -ExecutionPolicy Bypass -File .\inputguard-enroll.ps1. It creates (or reuses) a stable device identity, captures hostname and OS, and adds the device fields to the policy.
3. 3

   Reload Chrome policy

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

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.