How to find mandatory apps, active policies, and failed deployments on Windows devices?Solved

Participant
Discussion
4 days ago Oct 20, 2026

I’m taking over as a new IT admin and trying to review our Windows devices in Hexnode. I need to find out which apps are being forced onto devices, which policies are currently applied, and where to check if an app or policy deployment failed. What is the best place to start?

Replies (5)

Marked SolutionPending Review
Hexnode Expert
4 days ago Oct 20, 2026
Marked SolutionPending Review

Hi @liam_vance , Welcome to the Hexnode Community.

For Windows devices, you can review required apps and active policies from both the policy view and the device view.

To check required apps from a policy:

  1. Go to Policies.
  2. Open the policy you want to review.
  3. Click Manage > Modify.
  4. Navigate to Windows > App Management > Required Apps.

This section lists the applications enforced by that policy.

To check what is applied to a specific device:

  1. Go to Manage > Devices.
  2. Open the Windows device.
  3. Go to the Policies tab to see the active policies applied to that endpoint.
  4. Go to the Applications tab to view installed apps and deployment status.

In the Applications tab, use the Customize Columns option, represented by the pencil icon, to add useful fields such as Status, Version, and Installation Type. This helps identify whether an app is installed, pending, failed, or marked as a required app.

To review apps across all enrolled devices:

Go to Reports > Application Reports > All Applications. This gives an organization-wide app inventory and installation overview.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
4 days ago Oct 20, 2026
Marked SolutionPending Review

This helps. I also noticed there seems to be only one main policy in use, plus a default Windows compliance policy. Is the device-level Policies tab the best way to confirm what is actually active?

Marked SolutionPending Review
Hexnode Expert
4 days ago Oct 20, 2026
Marked SolutionPending Review

Yes @liam_vance . The Policies tab on the device summary page is the best place to confirm what is currently applied to that specific endpoint.

A default compliance policy may appear in some environments, but the important thing is whether the policy is associated with the device and active. Open the device record under Manage > Devices, then check the Policies tab. Any policy listed there is the policy you should inspect for enforced configurations such as restrictions, app requirements, network settings, or compliance-related settings.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
4 days ago Oct 20, 2026
Marked SolutionPending Review

What should I check if an app or policy shows as failed on a Windows device? Can I tell why it did not push?

Marked SolutionPending Review
Hexnode Expert
4 days ago Oct 20, 2026
Marked SolutionPending Review

Hi @joseph_jay ,

Start with the device’s Action History.

Go to Manage > Devices, open the affected Windows device, and select the Action History tab. This shows the status of commands sent to the device.

Common statuses include:

  • Success: The command was processed successfully.
  • Pending: The device is offline or not connected to the internet.
  • In Progress: The device has received the command and is processing it.
  • Failed: The command failed. Hover over the failed status or failure icon to view the specific error reason.

If the failure needs deeper investigation on the Windows device, check these local log locations:

  • Hexnode Agent logs: C:\Hexnode\Hexnode Agent\Logs
  • Hexnode Installer logs: C:\Hexnode Installer\Logs
  • Hexnode Updater logs: C:\Hexnode\Hexnode Updater\Logs

You can also generate a Windows MDM diagnostic report from the device:

  1. Open Settings > Accounts > Access work or school.
  2. Select the MDM account.
  3. Click Info.
  4. Under Advanced Diagnostic Report, click Create report.

For Windows MDM-related event logs, check:

Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider

These locations are useful for understanding why a Windows app or policy deployment failed.

Regards,
Isabel Lora
Hexnode UEM

Save