13 Replies Latest reply on Jan 31, 2019 5:24 PM by Azzam Affan

    OEMConfig

    Matt Dermody

      I've noticed that the newest Nougat build for the WT6000 has added support for OEMConfig, which is exciting news.

       

       

      But then I realized that the WT6000 only has AOSP versions of Android and my understanding was that OEMConfig was a management feature specific to GMS devices enrolled into an EMM like SOTI as an Android Enterprise device. Am I missing something here? Can you enroll AOSP device as a Managed Device with Device Owner or can you only use Device Administrator? What happens on Android Q and beyond when Device Admin becomes increasingly deprecated, will there even be AOSP device options any more?

        • Re: OEMConfig
          Azzam Affan

          Hi John,

           

          Thank you for your questions. 

           

          OEMConfig is not specific to only GMS devices.  It will be available on AOSP devices as well. You can manage AOSP devices as a Device Owner or Device Administrator.  You will need to ensure first that the EMM supports AOSP devices on the specific OS version.

           

          Device Owner is supported on AOSP and have the Device Policy Manager APIs available to take advantage of OEMConfig.  However, Google Play services APIs are not available on AOSP devices.

           

          AOSP devices can be managed today as a Device Owner and eventually Device Administrator will go away after Q.  Again the Google Play services APIs will not be available.

           

          I hope this answers you and if you need further clarification or answers please do not hesitate to reach out to me.

           

          Azzam 

           

           

           

           

           

          OEMConfig is not specific to only GMS devices.  It will be available on AOSP devices as well.

            • Re: OEMConfig
              Matt Dermody

              It does for the most part, although I'm unfamiliar with Enrolling into an EMM as Device Owner with Android Enterprise without leveraging the Google Setup/Welcome wizard in some shape or form. I'm familiar with the QR and NFC based enrollment as well as the hashtag or MGPA enrollment at the account prompt, but I didn't think there were any other ways to leverage DO than through the setup wizard on a GMS device. That is welcome news that it will also be an option for AOSP, I just am not as familiar with how DO enrollment will look on those devices.

                • Re: OEMConfig
                  Arseniy Osipov

                  Hi John,

                   

                  You can use StageNow for this. There is a CSP to send an intent which will set the selected application as a DeviceOwner.

                   

                  Arseniy

                    • Re: OEMConfig
                      Matt Dermody

                      So assuming we can enroll as Android Enterprise with Device Owner via StageNow, how does the OEMConfig Managed Configuration actually get exposed at the EMM level? My understanding right now is that the only method to utilize Managed Configurations is when distributing apps via Managed Google Play. How would this be possible on the AOSP only WT6000?

                        • Re: OEMConfig
                          Azzam Affan

                          OEMConfig exposes managed configurations that can be set by the EMM via XML.

                           

                          Managed Configurations are permissions given to Device Owner and are not limited to app distribution only.  Using OEMConfig in Device Owner mode on AOSP devices is supported.

                           

                          The EMM can use the Play Store copy to capture the managed configurations that are presented to the IT admin.  Once the IT admin has made their changes, the managed configurations can be pushed to the device(s) and then applied by the DO agent.

                           

                           

                           

                            • Re: OEMConfig
                              Matt Dermody

                              I am looking to better familiarize myself with the components involved with OEMConfig in order to better prepare myself for migrating from DA to DO in the future. I have started to experiment and am running into somewhat of a stumbling block. I am trying to add OEMConfig to my listed of Managed Apps as part of a test Managed Google Play account for the enterprise I have binded/bound(?) to a SOTI instance and I can’t find OEMConfig in the list. As I understand it, this is the mechanism through which we can pull the managed configuration schema for the app.

                               

                               

                              I have performed this process with similar applications in order to distribute Managed Configurations. For example here are the managed configurations available for Cisco Anyconnect VPN client after adding the application as a Managed App.

                               

                               

                               

                              What am I missing here? Is OEMConfig not yet on the Play Store?

                                • Re: OEMConfig
                                  Adam Arruda

                                  Hi Matt,

                                   

                                  Zebra is preparing to officially launch our OEMConfig support in the market in the near future.  We have been actively working with our partners, like SOTI, to get them up to speed on what we are doing and how they can support it.  I do know SOTI is working on this, and does plan to support OEMConfig, however I dont have an exact timeline on when they plan to bring it to market. 

                                   

                                  For DA-DO migrations, we do have a porting process that Google has approved, that will allow an EMM to move an agent from DA to DO, without needing to FR the device. Again, this is something we've shared with our partners, and they are actively working on it, as they too see the growing need as more customers look to move to DO.

                                   

                                  It may be best to touch base with your SOTI rep, as they may be able to provide further clarity around timelines for these two features.

                                  1 of 1 people found this helpful
                                    • Re: OEMConfig
                                      Matt Dermody

                                      Thank you for clarifying Adam! I am very excited about the OEMConfig option and thought it might be ready for primetime since it has been included in a lot of recent LG builds. It is one of the most compelling reasons to move to DO from DA in a COSU environment that I have seen to date. I am also relieved to hear there will be another approved method for migrating from DA to DO that doesn't require a complete Factory Reset of a device. I have been planning to leverage DA for a long as possible but had the dilemma with the SD660 based devices releasing on O as to whether I should preemptively enroll them as Android Enterprise Work Managed devices with DO and deal with the limited number of management APIs compared to DA or continue using DA and then deal with a Factory Reset and re-enrollment when it became time to upgrade them to P and beyond. Given this news it sounds like we might be okay leveraging DA with O devices and then converting them from DA to DO through this pending porting process before upgrading them to P.

                                       

                                      Thanks!

                                        • Re: OEMConfig
                                          Adam Arruda

                                          Matt, I was re-reading your comments and something I wanted to clarify which may be helpful.

                                           

                                          If you enroll with a DO agent, all the MX XML management will still exist on the device (N & O bother support XML and OEMConfig), if that was your worry.  So when deciding between DA and DO on 660 devices, you should have the same API availability.  The difference will come with P devices, where only DO+OEMConfig will work, as the support for DA, as well as XML will  be gone.

                                           

                                          Hope that helps.

                                          1 of 1 people found this helpful
                                            • Re: OEMConfig
                                              Matt Dermody

                                              Revisiting this topic as I prepare for this inevitable switch from MX to "ZMC" distributed through OEMConfig. Here are some additional thoughts and questions that come to mind.

                                              • We often leverage the EMMTK support for MX to execute profiles and configurations that I don't see how they would be supported by OEMConfig. For example we may use an AppMgr profile to install an APK so that the permissions can be automatically granted to that app instead of prompting the end users on Marshmallow and higher devices. An EMM like SOTI can easily distribute and install an APK through its Package Building process but if we want to add any custom handling for that APK then we'll use a post-install script call to mxconfig on an AppMgr based profile. How will such a process be executed once the EMM support for MX is deprecated?
                                              • Model specific settings. How will OEMConfig work with model specific MX/ZMC settings (eg. P3 key mapping on a WT6000, heater and power output on a VC80x, etc. ). Will each device model have their own version of OEMConfig hosted in the Play Store or will there only be one Zebra OEMConfig? Will we need to create separate distributions of OEMConfig ZMC for each device model or will we be able to have a universal deployment wherein non-device related configurations can be safely ignored by the device if applied. (Eg can the VC80x ignore the WT6000 specific configurations and vice-versa if applied the same OEMConfig ZMC.
                                                • Re: OEMConfig
                                                  Azzam Affan

                                                  Hi Matt,

                                                   

                                                  Thank you and you bring up some good points.

                                                   

                                                  • MX is not being deprecated but the XML interface that we provide EMMs will be, however this will not happen in the near future.  We are discussing what you mentioned internally, and it will eventually have to be done via OEMConfig. Here is a diagram with the flow:

                                                   

                                                  OEMConfig.png

                                                   

                                                  • Regarding model specific settings, there will be only one super set OEMConfig.  The same OEMConfig will work on all device models.  As you mentioned if there are device specific settings that are applied that cannot be fulfilled (your example) the setting will be applied and OEMConfig will accept it, however if it is not supported by the device it will not be applied.  Only those settings that are supported will be applied.

                                                   

                                                  Hope this is clear and it makes sense.

                                                    • Re: OEMConfig
                                                      Matt Dermody

                                                      I just thought of another MX + EMM integration scenario that would be extremely frustrating to lose. Right now we use the LicenseMgr CSP based MX to activate TouchWarehouse or Zebra Enterprise Browser licenses with the License Manager on the device. Each environment gets a unique MX XML file containing the License Manager sections and the specific Activation ID and license server source for the activation. This is distributed to the devices and executed as MX XML by EMM providers like SOTI. How will such a licensing process be handled with OEMConfig with ZMC once the traditional MX XML delivery method is deprecated? Would we be expected to manually license every device or use StageNow barcodes instead? If so that's a relatively unacceptable tradeoff. I would hope that we'd be able to input License Manager AIDs into the OEMConfig Managed Configurations at the EMM server level. Please tell me this scenario has already been considered!

                                                        • Re: OEMConfig
                                                          Azzam Affan

                                                          Hi Matt,

                                                           

                                                          Yes we have considered the majority of non DO DPM actions that were previously accomplished via XML.  As long as the EMM correctly consumes the OEMConfig Schema and generates the Data Driven UI, they will be able to accomplish this without the need to submit XML.  Here is the specific portion in the schema that needs to be implemented:

                                                           

                                                          {

                                                                            "entry": [   "Activate License","Return License","Return All Licenses","Refresh License","Delete Server" ],

                                                                            "restrictionType": "choice"

                                                                            ,"description": "Specify a Zebra Mode licensing action to be performed"

                                                                            ,"entryValue": [ "Activate","Return","Reset","Refresh","DeleteLicenseSource"   ]

                                                                            ,"title": "Zebra Licensing Configuration - License Action"

                                                                            ,"key": "zebraLicenseAction"

                                                          }