Hello @harold ,
For Windows app deployments, Hexnode UEM uses the success criteria configured in the app repository to confirm whether the application was installed successfully. If the success criteria does not match what Windows reports locally, the app can remain Pending or show as Failed even when some Proofpoint components appear in the Proofpoint console.
A few important points for this type of deployment:
- Windows identifiers are different from macOS identifiers. Apple Team IDs or macOS bundle-related identifiers cannot be used as Windows success criteria.
- If using App Identifier as the success criteria, manually install the app on an enrolled Windows test device, then go to Manage > Devices > select the device > Applications. Use the exact identifier shown for the correct Proofpoint component.
- Security agents may install multiple components, such as an updater, service, or helper utility. If the identifier belongs to a secondary component instead of the main installed agent, Hexnode may still report the app as missing.
- For EXE deployments, Exit Code 1603 usually means the installer itself failed. This is often caused by incorrect or incomplete silent install parameters. For Proofpoint-style agents, the silent install command may require vendor-provided tenant-specific values, such as tenant ID, token, server URL, cluster URL, or other deployment arguments.
If the app identifier method is unreliable for this installer, try using File Path as the success criteria and point it to a file that is created only after the main agent is installed successfully.
Regards,
Simon Scott
Hexnode UEM
What's new 
9 Views
