Windows device enrolled after Hexnode Gateway migration but policies not applyingSolved

Hello @sutton ,

Yes, this can be expected immediately after a Windows device is migrated or newly enrolled.

When the Hexnode UEM app is installed and the device completes enrollment, the Hexnode Agent service may still need a few minutes to finish background initialization and establish stable communication with the Hexnode server.

Once enrollment completes, policy deployment is not always instant. The device first performs initial scans and processes the pending action queue. If the action history shows successful Scan Device or Sync User Details actions, that confirms the device is communicating with Hexnode UEM.

To speed up policy deployment:

1. Open the Hexnode UEM app on the Windows device.
2. Click Sync.
3. Wait a few minutes for the queued policy association and related actions to complete.

For newly enrolled Windows devices, allowing around 2–5 minutes after enrollment is usually enough for the initial scan and policy deployment to finish.

Regards,
Simon Scott
Hexnode UEM

Oh, got it. I had clicked Scan Device multiple times from the portal because nothing seemed to happen. Some of those scan actions later showed as Cancelled. Does that indicate a problem?

I don’t think cancelled scan entries are a problem in this case. If multiple manual Scan Device commands are triggered in quick succession, the newer scan request can override or cancel an earlier pending scan. As long as a later Scan Device action completes successfully and the Last Check-in time updates, the device is actively communicating with Hexnode.