Configuration
Overview
Once devices are enrolled and on the target firmware, they can be configured from your MDM in three ways:
- MDM settings: The standard Android Enterprise policies built into every MDM, such as Wi-Fi networks, certificates, passcodes, restrictions, and kiosk (lockdown) mode.
- OEMConfig: Datalogic-specific settings that Android Enterprise doesn't cover, such as scanner, keyboard, power, and dock settings, managed through the Datalogic OEMConfig app.
- Scan2Deploy: A profile created in Scan2Deploy Studio and applied by the Scan2Deploy Agent on the device. Your MDM sends the profile data to the agent instead of a barcode being scanned. A Scan2Deploy profile is either:
- Barcode Only: All of the profile data fits in the barcode data. Nothing needs to be hosted.
- Host Profile: The profile (
.tarfile) is hosted by Scan2Deploy Studio, pushed to the device by your MDM, or hosted on a server. Supports every Scan2Deploy action, including app installs, Datalogic Launcher, and Enterprise Browser.
Most deployments combine them: MDM settings for the device policies, OEMConfig for Datalogic settings, and Scan2Deploy only for configuration that neither of the others can provide.
Don't configure the same setting with more than one method, such as a Wi-Fi network in both your MDM and a Scan2Deploy profile. The most recently applied value wins, and the MDM may reapply its own value later. Settings that are available in your MDM or OEMConfig should be configured there.
Comparison
| MDM settings | OEMConfig | Scan2Deploy (Barcode Only) | Scan2Deploy (Host Profile) | |
|---|---|---|---|---|
| Configures | Android Enterprise policies | Datalogic device settings | Wi-Fi, app enable/disable, scanner and device settings, scripts | Every Scan2Deploy action |
| Set up in | MDM console | MDM console | Scan2Deploy Studio | Scan2Deploy Studio |
| Delivered by | MDM agent | OEMConfig app | Intent with the profile data | Intent with the profile data, plus the .tar file |
| Kept in sync | Yes, the MDM reapplies and reports the policy | Yes, the MDM reapplies and reports the configuration | No, applied once | No, applied once |
| Hosting required | No | No | No | Yes, from Scan2Deploy Studio, on the device, or on a server |
When to use each
MDM settings
Use MDM settings for anything that is part of Android Enterprise. These policies work the same way on every Android device, are reported in the MDM console, and are reapplied by the MDM if they change. Typical examples:
- Security: Root (CA) and client certificates, passcode and authentication, factory reset protection, system update policy, and single sign-on
- Restrictions: Kiosk (lockdown) mode for dedicated devices, app allow and block lists, feature control (camera, Bluetooth, USB file transfer, screenshots, factory reset), web filter, browser proxy, and phone calls
- Connectivity: Wi-Fi networks, including enterprise (EAP) networks, APN, and VPN
- Apps and device: Managed Google Play apps and their managed configurations, device inactivity, date and time, wallpaper, bookmarks, and email
See MDM Settings for what each is used for on Datalogic devices.
OEMConfig
Use OEMConfig for Datalogic settings that Android Enterprise doesn't cover, such as:
- Scanner settings: symbologies, wedge, formatting, and good read feedback
- Key remapping, power, dock, and display settings
- Datalogic network and security settings
- Arrow FOTA firmware updates
Like MDM settings, OEMConfig is configured in the MDM console and reapplied by the MDM. See the OEMConfig settings reference for every available setting.
Scan2Deploy
Use Scan2Deploy when you already have a Scan2Deploy profile from staging devices by barcode, or need a feature that is only available in Scan2Deploy, such as:
- Datalogic Launcher, Enterprise Browser, QuickBoard, and Advanced Keyboard configuration
- Visual Formatter, Snap OCR, and file uploads
- Installing local APKs and updating the Datalogic Mobility Suite
Scan2Deploy profiles are applied once and are not tracked by the MDM. To change a setting, update the profile in Scan2Deploy Studio and send it to the devices again.
Choose Barcode Only when the profile only uses the actions it supports (see Action Selection); the profile data is sent in a single intent and nothing needs to be hosted. Choose Host Profile for any other action.
Where to configure in each MDM
| MDM settings | OEMConfig | Scan2Deploy (Barcode Only) | Scan2Deploy (Host Profile) | |
|---|---|---|---|---|
| SOTI MobiControl | Policies > Profiles, as configurations in an Android Enterprise profile | Policies > Profiles, as an OEM Config configuration in an Android Enterprise profile | Send Script with the SOTI MobiControl intent copied from Scan2Deploy Studio | Packages, with the intent as a post-install script, assigned in a profile |
| Microsoft Intune | Devices > Configuration, as Android Enterprise template profiles | Devices > Configuration, as an OEMConfig profile | Launch Activities in the OEMConfig profile | Launch Activities in the OEMConfig profile, with the .tar file hosted on a web server |
| SureMDM | Profiles > Android | Profiles > Android, as an OEMConfig Policy profile | Jobs, as a Run Script job with the SureMDM intent copied from Scan2Deploy Studio | Jobs, as a Composite Job with a File Transfer job and a Run Script job |
| Workspace ONE | Resources > Profiles & Baselines > Profiles, as Android profiles | Resources > Apps > Native, as the application configuration of Datalogic OEMConfig | Devices > Provisioning > Product List View, as a product with a Run Intent action | Devices > Provisioning, as a Files/Actions component with the .tar file and a Run Intent action |