How does publisher rule approach while deploying windows app work in practice?Solved

Participant
Discussion
6 months ago Jan 14, 2026

How would the Publisher rule approach work in practice? Do we need to run commands on every end-user device to get the publisher name, or should we build this from one reference machine?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
6 months ago Jan 14, 2026
Marked SolutionPending Review

Hello,

Thanks for reaching out to Hexnode Connect.

You do not need to collect publisher details from every end-user device. The best practice is to use a single reference machine (like an IT test laptop or VM) where the required applications are installed.

You can identify the exact Publisher value on that Windows reference machine by following these steps:

  1. Open Run, type secpol.msc, and press Enter.
  2. Navigate to Application Control Policies > AppLocker > Executable Rules.
  3. Right-click Executable Rules and select Create New Rule.
  4. Proceed through the wizard until you reach the Publisher section.
  5. Browse and select the application executable. Windows will display the exact publisher string for that executable.

You can then copy that complete Publisher string and use it when creating your corresponding Windows app rule in Hexnode.

One important note: Hexnode applies these rules through Microsoft’s AppLocker CSP. Once enforced, AppLocker acts as a “deny-by-default” system for that rule category. Make sure you account for all your other required applications (using additional allow rules or suitable wildcards) before pushing the policy, otherwise legitimate desktop apps may be inadvertently blocked.

I hope this helps or resolves your issue. Feel free to reach out if you have any more doubts or need further assistance.

Best regards,
George,
Hexnode UEM

Save