macOS policy association shows Partial Success: User token could not be fetchedSolved

Hi @ethan_,

This status usually appears when the policy contains configurations that must be applied to the macOS user profile, but Hexnode is unable to fetch the user token for the currently active user session.

For macOS user-level policy configurations, make sure the user is logged in with the same account that was used to enroll the Mac or the MDM-enabled account created during enrollment. If the policy includes only device-level configurations, the device profile association can still succeed while the user profile association shows as failed.

You can also verify whether the configuration profile was installed on the Mac from System Settings > General > Device Management. If the expected profile is listed there, the device-level policy payloads have been deployed successfully.

Regards,
Sienna Carter
Hexnode UEM

I noticed an old Privacy Preferences Policy Control setting for the Hexnode UEM app in the policy. Is that still required? We also had a similar entry for Hexnode UEM Helper.

Hi @ethan_,

A Privacy Preferences Policy Control configuration is not required for the Hexnode UEM app or Hexnode UEM Helper as part of the standard macOS policy deployment. If those PPPC entries were added in an older policy and are no longer needed for any specific workflow, they can be removed from the policy.

After removing unnecessary user-level or obsolete payloads, re-associate the policy and check the association status again. The device profile should continue to apply normally, and the Partial Success message should no longer appear if there are no user-profile payloads that require a missing user token.

Regards,
Sienna Carter
Hexnode UEM