Samsung devices still prompt to install Hexnode after factory resetSolved

Hi @mees,

For Samsung devices, a Hexnode enrollment prompt after factory reset is usually triggered by an external zero-touch or enrollment assignment rather than by the app remaining on the device.

The first place to verify is Samsung Knox Mobile Enrollment:

1. Sign in to the Samsung Knox portal.
2. Go to Knox Mobile Enrollment > Devices.
3. Locate the affected Samsung devices.
4. Select the devices and choose Actions > Unassign profile, or delete the devices if they are no longer being managed through Knox.
5. Factory reset the devices again and start setup after the Knox assignment has been removed.

If the devices are still assigned to a Hexnode profile in Knox Mobile Enrollment, they will continue to pull the Hexnode enrollment flow during setup after connecting to the internet.

Regards,
Sienna Carter
Hexnode UEM

I already checked Knox Mobile Enrollment and the devices are no longer assigned there. They’ve also been factory reset again. The weird part is that the Hexnode prompt appears only after I sign in with the Google account during setup.

Hi @mees,

If the prompt appears specifically after signing in with the Google account, the trigger is likely coming from Google Workspace Android management settings rather than Samsung Knox Mobile Enrollment.

An administrator can check this in the Google Admin Console:

1. Open the Google Admin Console.
2. Go to Devices > Mobile & endpoints > Settings > Setup.
3. Open Third-party integrations.
4. Disable the option Enable third party Android mobile management if Hexnode is no longer being used as the Android EMM for that Google Workspace tenant.
5. Factory reset the Samsung devices again and complete setup.

This setting can redirect Android devices associated with the Google Workspace account to a configured third-party MDM during setup. If the Hexnode portal is no longer active, the device may still be pushed toward Hexnode because the Google Workspace integration is still enabled.

Before disabling it, make sure the organization is not still using Hexnode or another third-party EMM for Android management, since this can affect other Android enrollments tied to the same Google Workspace tenant.

Regards,
Sienna Carter
Hexnode UEM