Group Policy deployment
For Active Directory environments, push the MSI through Group Policy Software Installation. No custom code: the standard MSI deployment workflow applies.
Prerequisites
- A domain controller with GPMC installed
- An SMB share readable by domain computers, for example \\server\Software
- PermitUSB.msi placed in the share
- An enrollment token from the dashboard
Steps
- Open Group Policy Management Console (gpmc.msc)
- Create or edit a GPO scoped to the OU containing the target machines
- Computer Configuration, then Policies, Software Settings, Software installation
- Right-click, New, Package. Browse to the MSI on the share and choose Assigned
Passing TENANT_TOKEN via GPO
GPO Software Installation does not pass MSI properties directly. Two options:
MST transform
Recommended for production. Create a transform with orca.exe setting the Property table’s TENANT_TOKEN, SERVER and optional ENDPOINT_GROUP, then attach the .mst on the Modifications tab of the package.
Startup script
Simpler for small environments. A PowerShell startup script that runs the install on first boot:
msiexec /i \\server\Software\PermitUSB.msi /qn TENANT_TOKEN="<token>"Verification
After the next gpupdate and reboot cycle, target machines run the install at boot. Newly enrolled hostnames appear on the Endpoints page within about 30 seconds of first boot.
Something missing or wrong here? Tell us. Documentation gaps get filled fast.