Hi @boris,
For this setup, you can prepare most of the configuration before the tablets arrive.
For the app:
- On Hexnode UEM portal, go to Apps > Add Apps > Managed Google Apps.
- Search for and approve the required Play Store app.
- Navigate to Policies > New Policy > Android.
- Use the App Permissions policy to pre-configure runtime permissions such as Camera, Storage, Location, etc. These can usually be set to Allow, Deny, or Prompt.
- Use the App Configuration policy only if the app developer supports Android Managed Configurations. If the app does not expose managed configuration keys, there may be no app parameters to configure in Hexnode.
For the kiosk policy:
- On Hexnode UEM console, go to Policies > New Policy.
- Open Android > Kiosk Management > Single App.
- Configure the kiosk with the approved Managed Google Play app.
- Review the available kiosk settings, including status bar, peripheral controls, exit options, and app launch behavior.
- Save and associate the policy with the tablet devices or a tablet device group.
For separating scanners and tablets, you do not necessarily need a separate enrollment profile. If your Hexnode plan and workflow allow multiple enrollment profiles, you may create one, but it is also fine to enroll the tablets using the existing Android Enterprise enrollment flow and place them into a separate device group. Then associate tablet-specific policies with that group.
For Samsung tablets, activate Samsung Knox during enrollment if prompted. This allows Hexnode to apply Samsung-specific management capabilities on supported devices.
The black screen during Remote View can happen on Android 15 and later due to Android’s screen sharing protection mechanisms. Certain system screens, app content, or sensitive UI elements may be hidden from remote viewing for privacy and security.
To access the relevant Android setting, Developer Options must first be allowed on the managed device. Android Enterprise enrollment can block users from enabling developer settings by default. Under Policies tab, navigate to Android > Advanced Restrictions > Allow Settings., and enable Developer Mode. After that, exit kiosk mode temporarily if required and enable Developer Options on the tablet. Then open Settings > Developer options and look for the screen sharing protection setting. On many devices, it appears under the Apps section as “Disable screen share protections,” but the exact name can vary by manufacturer and Android build.
Once that protection is disabled, Remote View should be able to display app content that was previously hidden. However, some secure system screens, including parts of Developer Options or other protected settings pages, may still appear blank during a remote view session because Android blocks capture of secure content.
Regards,
Sienna Carter
Hexnode UEM