Configure the registration in Intune for devices without Android user (AOSP) belonging to the company

Access Problem solving + support in the Microsoft Intune administration center for:

AOSP Android

On November 11th, 2022, Elo will release a new OS Update for Android 8.1 AOSP Devices. This update includes feature enhancements and bug fixes that will improve the performance and usability of Android 8.1 AOSP Devices. This update will be available for download on the Eloview Cloud Portal As a Dropdown Ota. Please reach out to your elo support contact for any additional question or to get access to a direct download of this update.

• Added the Ability to Restric Content Downgrade from Eloview Portal.
• Added Support for 802.11x Credentials Using Network Configuration Template.
• Resolved an Issue where the Full Report Generated Showed Account Default Content Under the Currently Playing Application Instatead of the Actual Content Being Played.
• Resolved an Issue where Background of Eloview Webapps Weren’t Displaying Correctly.
• Resolved an Issue Whore Some Activity Logs Showed Multiple Instances of Reinstallation of Contents.
• Resolved an Issue where Devices Played Default Content With Daylight Saving Time Changes.
• Resolved an Issue where daylight Saving Time to Standard Time Caused A Delay in Scheduled Content.
• Resolved an Issue Where Some Contents Were Downgrad Based on Previously Scheduled Content.
• Resolved an ISSUE WHERE IN SEME VIRTUAL KEYBOARD CASES APPARED ON THE SCREEN AFER REBOOTS.
• Resolved an Issue where there was a broadcast leak withn Elo test Application Causing Device to Get Stuck.
• Resolved an Issue where Devices Were Flashing A White Screen when Updated to 3.56.20.
• Improvements on Apis of Eloviewhome SDK for the Below:
  • Added support to auto allow usb permissions.
  • Added restrictions to limit navigation bar and status bar changes for devices in eloview mode.
  • Added the Ability to Enable/Disable Navigation Bar.

  AS Always, your Devices Will Never Prompt for An Update or Auto-Update. Once the update is available, Devices can be updated from:

  • Eloview Portal
  • Eloviewhomesdk

  Configure the registration in Intune for devices without Android user (AOSP) belonging to the company.

  Configure the inscription to Microsoft intune for devices without user belonging to the company and built on the Android Open Source Project (AOSP) platform (AOSP). Intune offers an aircraft management solution Android (AOSP) For corporate Android devices that are:

  • Not integrated into Google Mobile Services
  • Intended to be shared by several users
  • Used to accomplish a specific set of tasks at work

  The devices registered in Intune with this management mode are automatically configured with Microsoft Authenticator and Company Portal. These devices are registered in intune without user account, are not associated with a specific user and are configured with the shared device Azure Adure Adure Adure during registration.

  When the shared device mode is activated, these devices allow unique authentication and disconnection between users in participating applications. Thanks to company portal’Installation, users also obtain a unique disconnection from applications integrated into the software development kit (SDK) in Intune, even for applications that do not yet participate in shared device mode.

  Required configuration

  To register and manage AOSP devices, you must have:

  • A Microsoft Intune active client
  • A supported device.

  You must also:

  • Define Microsoft Intune as Authority for Management of Mobile Devices (MDM) in your client you must only do it once, during the first implementation of intune for the management of mobile devices.
  • Assign valid licenses to all users of realwear devices. For more information, see Microsoft Intune License Management.

  Create an registration profile

  Create an registration profile to activate registration on devices.

  Intune also generates a token in the form of a simple text, but it cannot be used to register devices.

  1. Connect to the Microsoft Intune administration center and select Devices>Android>registration> Android devicesbelonging to the company and without user.
  2. Choose Create And fill the required fields.
  3. Name : Type a name you will use when assigning the profile to the dynamic apparatus group.
  4. Description : add a profile description (optional).
  5. Jeton expiration date : date on which the token expires. Intune applies a maximum of 90 days.
  6. SSID:identifies the network to which the device will connect.

  Note the details of Wi-Fi are necessary because the realwear device does not have a button or an option allowing it to automatically connect to other devices.

  • Pre-party key:pre-party key used for authentication to the network.

  Access registration token

  Once you have created a profile, Intune generates a necessary token for registration. To access the token:

  1. Go to User devices belonging to the company.
  2. In the list, select your registration profile.
  3. Select tokens.

  Another way to find the token is:

  1. Go to User devices belonging to the company.
  2. Look for your profile in the list, then select the menu More (. ) which is next to this.
  3. Select Display the registration token.

  The token appears as a QR code. When installing the device, when invited, analyze the QR code to register the device in Intune.

  You can also export the JSON file from the registration profile. To create a JSON file:

  1. Go to User devices belonging to the company.
  2. In the list, select your registration profile.
  3. Select Export the token>.
  • The QR code contains all the identification information provided in the simple text profile to allow the device to authorize itself correctly with the network. This is compulsory, because the user will not be able to attach a network from the device.
  • Since you manage the device via intune, you must ignore the realwear configuration for the first time. QR intune codes are the only thing you need to configure the device.

  Replace the token

  Generate a new token to replace the one approaching your expiration date The replacement of a token does not affect the devices already registered.

  1. Connect to the Microsoft Intune administration center.
  2. Select THE>Android devicesRegistration>AndroidProperty>of business, devices without user.
  3. Choose the profile to use.
  4. Select A>token token.
  5. Enter the new token expiration date. Tokens must be replaced at least every 90 days.
  6. Select OK.

  Revoke the token

  Revoke a token to expire it immediately and make it unusable for example, it is appropriate to revoke a token in the following cases:

  • You have accidentally shared the QR token/code with an unauthorized third party.
  • You have done all the registrations and no longer need the QR token/code.

  The revocation of a token does not affect the devices already registered.

  1. Connect to the Microsoft Intune administration center.
  2. Select THE>Android devicesRegistration>AndroidProperty>of business, devices without user.
  3. Choose the profile to use.
  4. Select A>token revoke>Yes

  Create a group of devices

  You can create Groups of assigned devices Or Groups of devices Dynamics in Intune. For more group information, consult adding groups to organize users and devices.

  Groups of dynamic devices are configured to automatically add and delete devices depending on a set of rules and parameters. For example, you can group devices by registration profile name.

  To create a group of Dynamic AVure AVE devices for devices registered with a registration profile without Android business user (AOSP), you can perform the following steps.

  1. Connect to the Microsoft Intune administration center and choose Groups>All groups>New group.
  2. In the panel Band, Inform the compulsory fields as follows:
     • Group type : Security
     • Name of the group : type an intuitive name (for example “factory devices n ° 1”)
     • Type of belonging : Dynamic device
  3. Choose Add a dynamic request.
  4. In the panel Dynamic belonging rules, Inform the fields as follows:
     • Add a dynamic belonging rule : Simple rule
     • Add devices where : nom_profil_inscription
     • In the middle zone, choose Is equal to.
     • In the last field, enter the name of the registration profile you created.

  For more information on the rules of dynamic belonging, consult Dynamic belonging rules for groups in Azure Ad.

  Sign up devices via a QR code

  After installing and assigning the Android registration profiles (AOSP), you can register devices via the QR code.

  1. Turn on your new device or reset to factory settings.
  2. When the device invites you, analyze the QR code of the token.

  To access the token in Intune, select Devices>Android Android registration of business devices, devices >without >user. Select your registration profile, then Select tokens.

  1. Follow the prompts on screen to complete the registration and registration of the device. During the configuration, Intune installs and automatically opens the applications necessary for registration. These applications are as follows:
     • Microsoft Authenticator application
     • Microsoft intune application
     • Intune company portal application

  To use JSON to register devices, see the instructions provided by the device manufacturer.

  After registration

  Application updates

  The Microsoft Intune application automatically installs application updates available for itself, Authenticator and Company Portal. When an update becomes available, the Intune Farm application and installs the update. The application must be completely closed to install the update.

  Manage devices remotely

  The following remote actions are available for Android devices (AOSP):

  • Reset
  • DELETE
  • Remotely lock
  • Reset the secret code
  • To restart

  You can act on a device at a time. For more information on the location where to find remote actions in Intune, see delete devices using deletion, deletion or manually unsubscribe from the device.

  Once you have restored an Android device (AOSP), the device remains in the state Pending until it is fully restored to its default factory settings. Intune it then deletes it from the list of devices. When you delete a device, it is immediately deleted from the list of devices, without pending state, and factory reset occurs during the next check.

  Problem resolution

  Show the version of Microsoft Intune and Microsoft Authenticator Applications

  To find out which version of the Microsoft Intune or Microsoft Authenticator application is installed on a device:

  1. Access Devices And select the device name.
  2. Select Discovered applications.
  3. Look for your application, then search for the number version in the version of the application version.

  Troubleshooting + support

  Access Problem solving + support in the Microsoft Intune administration center for:

  • See the list of Android devices (AOSP) registered by a user
  • Activate the troubleshooting of Android devices (AOSP) in the same way you can help other user devices.

  Share application newspapers with Microsoft Corporation

  If you have any problems with the registration or the Microsoft Intune application, you can use the intune application to download and send application newspapers to Microsoft Corporation. After submitting newspapers, you will receive an incident ID to share with your Microsoft Corporation technical support.

  Known limitations

  The known limitations are as follows when you work with AOSP devices in Intune:

  • You cannot apply certain types of passwords via compliance profiles and device restrictions. Password types are as follows:
    • Password required, without restriction
    • Alphabetical
    • Alphanumeric
    • Alphanumeric with symbols
    • Low biometric
    • Intune for Cloud of the public sector (Cloud of the Public Community) High and Department of Defense (D0D)
    • Intune managed by 21vianet

    Next steps

    • Create an Android device configuration strategy (AOSP) to limit the parameters on devices.
    • Create an Android device compliance strategy (AOSP).
    • For more information on the implementation of AOSP, see the source required for Android (opens the source of Android source).