Windows EXE app deployment stuck in Pending because App Identifier success criteria is missingSolved

Yes, an incorrect or missing success criteria can cause this behavior. For Windows EXE app deployments, Hexnode needs a valid success criteria value to confirm that the app was installed successfully. If the app installs on the device but Hexnode cannot match it against the configured App Identifier, the deployment may remain in Pending until it times out or may eventually show as failed.

To verify the installation state, you can run a Scan for apps action on the Windows device:

• Manage > Devices > select the device > Actions > Scanning & Monitoring > Scan for apps.

If the application is installed and reported by Windows, it should appear under the device’s Applications tab. The value shown there can be used to identify the correct app entry.

That makes sense. I had entered something like the product name as the success criteria. Is the Windows App Identifier usually a readable name, or is it more like a number/code? Also, we already have a macOS policy for the same app. Can I use the identifier from that policy for Windows?

The Windows App Identifier is usually an alphanumeric identifier reported by Windows for that installed application. It may not be the same as the product name you entered manually. The macOS identifier should not be reused for Windows. macOS values such as Apple Team Identifiers, bundle identifiers, or system extension identifiers are specific to Apple platforms. Windows does not use those values for app detection. To get the correct Windows App Identifier:

1. Manually install the Proofpoint DLP agent on one enrolled Windows test device.
2. In Hexnode, go to Manage > Devices and open that device.
3. Open the Applications tab.
4. Search for the Proofpoint application.
5. Copy the exact App Identifier shown for the Windows app.
6. Go to the Apps section, open the Proofpoint app entry, and paste that value into the Success Criteria / App Identifier field.

Alternatively, the vendor’s Windows deployment documentation may list the product code or installer identifier that can be used.

I ran into something similar with another EXE-based security agent. The app was actually installed, but Hexnode kept showing Pending because I had used the display name instead of the identifier from the Applications tab. After updating the success criteria with the exact Windows identifier and scanning the device again, the deployment status updated correctly.

Got it. So the macOS Team ID is not relevant here, and I need to pull the Windows identifier from the enrolled test device or confirm it with the vendor. That clears it up.