Hi @ezekiel,
For Execute Custom Script and other remote actions to run, the Windows device must be active, connected to the internet, and checking in with the Hexnode portal.
If the device has not checked in recently, the action may remain in the pending state because Hexnode cannot deliver the command to the device until communication is restored.
You can verify this from: Manage > Devices > select the device > check the Last Check-in time. You can also review the queued or completed actions from the device’s Action History section.
If the device is offline or has not checked in for a long time, try the following when you have access to the device:
- Ensure the device has a stable internet connection.
- Restart the Windows device.
- Open the Hexnode app on the device.
- Click Sync to manually trigger communication with the portal.
- After the device checks in, retry or wait for the pending Execute Custom Script action to run.
If the MDM profile or Hexnode management profile was removed from the device, the device will no longer check in normally. In that case, the device must be enrolled again before remote actions can be executed.
Regards,
Sienna Carter
Hexnode UEM