Unable to create user accounts remotely on macOS devicesSolved

Participant
Discussion
4 days ago Mar 05, 2026

We’re running into an issue while trying to create new user accounts remotely on our managed Mac devices. The action keeps failing even though we’re using the correct administrator credentials. 

Another thing we noticed is that the Last check-in time shown in the portal seems outdated for many of these Macs. These devices are actively being used, but the timestamp in the portal doesn’t reflect that. 

Has anyone come across something similar? Could the outdated check-in time be related to the account creation failure? 

Replies (5)

Marked SolutionPending Review
Hexnode Expert
3 days ago Mar 06, 2026
Marked SolutionPending Review

Yes, the two observations are very likely related. 

Remote actions such as creating user accounts depend on active communication between the device and the Hexnode UEM server. For macOS devices, this communication is triggered through Apple Push Notification Service (APNs). If the device has not checked in recently or is unable to receive push notifications, the action may not reach the device. 

To troubleshoot this, you can try the following steps: 

  1. Verify APNs connectivity on the network used by the Mac device. 

  1. Ensure the device has a stable internet connection. 

  1. Restart the device, as this can restore the APNs connection. 

  1. From the Hexnode portal, perform a Scan Device action to refresh device information. 

  1. Open the Hexnode UEM app on the device and trigger a manual sync. 

Once the device successfully syncs with the server, the Last check-in time in the portal should update, and remote actions should start processing normally. 

Marked SolutionPending Review
Participant
3 days ago Mar 06, 2026
Marked SolutionPending Review

That’s helpful, thanks. I tried opening the Hexnode UEM app on one of the affected Macs and triggered a manual sync, and the Last check-in time updated immediately in the portal. 

However, I noticed that the sync didn’t work on the first attempt. It failed once and then worked on the next try. Is that expected? 

Marked SolutionPending Review
Hexnode Expert
3 days ago Mar 06, 2026
Marked SolutionPending Review

Intermittent sync failures are not typical, but they can occur if the device temporarily loses connectivity with the APNs service or the network connection fluctuates. 

Since the Last check-in time updated after the manual sync, it indicates that the device was not actively communicating with the server earlier.  

If you encounter this behavior consistently across multiple devices, it would be worth checking: 

  • Network restrictions that may affect APNs connectivity 

  • Firewall rules that might block required Apple services 

  • Stability of the network used by the devices 

If needed, you can also try repeating the manual sync on the affected devices to re-establish communication. 

Marked SolutionPending Review
Participant
3 days ago Mar 06, 2026
Marked SolutionPending Review

I ran a manual sync again on the affected Mac and retried the account creation action. This time it went through without any issues, and the new user account was created successfully. 

Looks like the device just needed to sync with the server again. 

Marked SolutionPending Review
Hexnode Expert
3 days ago Mar 06, 2026
Marked SolutionPending Review

Great to hear that the issue is resolved. 

Since the action succeeded after the device synced with the server, the failure was most likely caused by delayed communication between the device and the Hexnode UEM server, which depends on APNs and stable network connectivity. 

If you run into similar situations again, triggering a manual sync from the Hexnode UEM app can help restore communication quickly. 

Save