START A DISCUSSION
Login START A DISCUSSION
back Back

MotoOEM Config- ThinkShield version discrepancy

expand collapsive

Hello,

I’m facing an issue with Moto OEMConfig App Configurations on a group of Motorola G Power 2021 phones (app version: v13.03.0320). The app shows ‘ThinkShield for Mobile 01.00.000’, and some features require ‘ThinkShield for Mobile v13.03.000 or higher’. Despite attempting to resolve the problem by resaving the policy and associating it with the targeted devices multiple times, the configurations were not successful.

I need to configure these devices as the new candidates are joining the organization. There’s uncertainty about whether the ThinkShield version is the reason. Any insights or suggestions would be appreciated.

2 January 2024

All Replies

  • Hexnode

    3 January 2024

    Leonard

    Moderator

    Hi @Sarah, thank you for reaching out to us!

    The functionality of each setting in the configurations list depends entirely on the ThinkShield version of the device.

    @Sarah, could you please provide details on which configured setting is not getting pushed to the device? Also, check the ThinkShield version in Settings > About phone > Android version > ThinkShield for mobile.

    Cheers!

    Leonard

    Hexnode UEM

    3 January 2024

  • Hexnode

    5 January 2024

    Leonard

    Moderator

    Hi @Deborah. Thanks for reaching out on Hexnode Connect!

    Make sure to add the Moto OEMConfig application from Managed Google Play to the app inventory before configuring and associating it with your target devices.

    Follow these steps to configure the app configurations for Moto OEMConfig:

    1. Login to your Hexnode portal.

    1. Navigate to the Policies tab.
    2. Select an existing policy or create a new one by clicking New Policy.
    3. From Android > App Management, select App Configurations, and click Configure.
    4. Click on Add new configuration. Select the Moto OEMConfig app.
    5. Configure the app. Click Done.
    6. Go to Policy Targets.Associate the Policy with the target Devices/ Device Groups/Users/User Groups/Domains.
    7. Click Save.

    Cheers!

    Leonard

    Hexnode UEM

    5 January 2024

  • Hexnode

    8 January 2024

    Leonard

    Moderator

    Hi @Sarah

    The Disable Safe Mode setting is effective for ThinkShield for mobile v13.02.000 or higher. For fully managed devices with a Work Profile, ThinkShield for mobile v13.03.000 or higher is required.

     

    However, the setting will not be effective due to the incompatible ThinkShield version on the device, even though you have the required app version.

    Let us know if you face any further constraints.

    Cheers!

    Leonard

    Hexnode UEM

    8 January 2024

Not what you're looking for? Try asking the Help Community replies

Not what you're looking for?

Try asking the Help Community replies

Trending Topics

Unable to set up BitLocker on the device using BitLocker policy

Invalid credentials error when syncing Google Contacts via CardDAV

Is there a developer mode for hexnode browser

Prevent multiple Hexnode browser windows

Hexnode + ZScaler (device ownership) for mobile devices

Confirm action

×

This action cannot be reverted

Confirm

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .