Important: the agent identifies users through Microsoft Entra ID. Once installed, it silently signs the user in with their Entra account and matches that account's email to a Corma user. That means GPO deployment only works on devices that are Hybrid Entra joined, with users' AD accounts synced to Entra ID through Entra Connect. On devices joined to Active Directory only, the agent installs but can't identify anyone, and no data shows up in Corma.
Prerequisites
A domain admin account, or an account that can create and link GPOs
Devices that are Hybrid Entra joined, with users synced through Entra Connect
An Entra admin with the
Global AdministratororApplication administratorrole, for the consent stepA network share that every target computer account can read
Optional: access to your antivirus admin console, to allow-list the agent
Step 0: Connect Microsoft Entra in Corma
Go to Corma > Connectors > Microsoft and make sure the connector is connected (see the Microsoft Entra ID article). If it isn't, Step 1 fails.
Step 1: Grant consent to the Corma Agent app
Open the admin consent URL (the same one as in the Intune article) and sign in as an Entra admin.
Check "Consent on behalf of your organization" and accept.
To confirm, go to Entra > Enterprise applications and search for "Corma Agent".
Step 2: Put the MSI on a network share
Download the MSI (link in the Intune article; currently
corma-os-agent-v1.0.56.msi).Copy it to a shared folder, for example
\\fileserver\Software\Corma\.Give
Domain Computersread access on both the share and the NTFS folder. GPO installs run as the computer account (SYSTEM), not as the user.
Step 3: Create the GPO and link it to an OU
Open Group Policy Management (
gpmc.msc) as administrator.Right-click Group Policy Objects > New, and name it
Corma-OS-Agent.Right-click the OU that contains the target computers > Link an Existing GPO… >
Corma-OS-Agent.
Step 4: Assign the MSI
Right-click
Corma-OS-Agent> Edit.Go to
Computer Configuration>Policies>Software Settings>Software installation.Right-click > New > Package…, and select the MSI through its UNC path (
\\fileserver...), not a local path.Choose Assigned, then click OK.
GPO installs MSIs silently, so you don't need a/qnswitch.
Step 5: Recommended policy settings
Under Computer Configuration > Policies > Administrative Templates > System > Logon, enable Always wait for the network at computer startup and logon. Without it, the install can be skipped on fast-boot devices.
Step 6: Apply and verify
On a test device, run
gpupdate /forceand restart. Software installation runs at startup.Check that
C:\Program Files\Corma\Agentexists.Sign in as a regular user. Within 48 hours, the user should show the OS agent as Connected in Corma (Users, or Devices > OS agent column).
To troubleshoot, run
gpresult /h report.htmland see the debugging steps below.
Optional: allow-list the agent
If you use an AI-powered antivirus, approve Program Files\Corma\Agent.
Managing updates
To roll out a new version, add the new MSI to the same GPO, then in its Upgrades tab select the previous package and choose "Uninstall the existing package, then install the upgrade package".
Debugging
Check the device's join state with dsregcmd /status: AzureAdJoined, DomainJoined and AzureAdPrt must all be YES. Then check the agent logs:
Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='Corma Monitoring Agent'} -MaxEvents 20 | Format-List TimeCreated, MessageIf a user's Entra email doesn't match their email in Corma, they won't be identified.
Data can take up to 48 hours to appear in Corma after deployment: about 24 hours for the agent to install and send its first report, then about 24 hours for Corma to process it. Wait 48 hours before troubleshooting.
If the result is "No events were found that match the specified selection criteria", the agent has logged no errors. Either it is running correctly, or it is not running at all. Check that the
C:\Program Files\Corma\Agentfolder exists on the device, then contact your Corma point of contact.
