View Categories

File Sync with Custom Intent

1 min read

File Sync with Custom Intent allows administrators to deploy OEM-specific configuration files (e.g., XML from Zebra StageNow or Honeywell EZConfig) directly to devices and trigger them automatically using broadcast intents. This ensures consistent application of vendor settings such as WiFi, roaming, or hardware features without requiring manual intervention on each device.


Key Benefits #

  • OEM Compatibility – Deploy and apply vendor-specific XML configuration files (e.g., Zebra, Honeywell) seamlessly through Autonoedge.
  • Automated Configuration – Use broadcast intents to trigger device settings without requiring manual user action.
  • Consistent Deployment – Ensure standardized configuration across large device fleets with minimal effort.
  • Flexible Triggers – Configure sync schedules (e.g., every boot, every X hours) to maintain policy enforcement.
  • Secure File Delivery – Host configuration files in Autonoedge Cloud or limit access to LAN-only for added security.


File Sync with Intent Usage (OEM) #

  1. Create the configuration file using the device vendor’s tool:
    • Zebra: StageNow or EMDK → exports .xml
    • Honeywell: EZConfig or Power Tools → exports .xml
  2. Example Zebra XML path:
    /sdcard/zebra_config/config.xml
  3. Example Honeywell XML path:
    /sdcard/honeywell/config.xml
  4. Save the XML with a clear, version-controlled name (e.g., zebra_wifi_config_v2.xml).

Step 1 – Upload the XML via Autonoedge File Sync #

  1. In the Autonoedge console, go to File System > Files.
  2. Choose Add by Link or Upload to host the XML.
  3. Set LAN Access Only if the file should only be accessible inside the corporate network.
  4. Example file link:
    http://files.internal.com/zebra_config/config_v2.xml

Step 2 – Configure File Sync in Profile #

  1. Go to Profiles and select or create a device profile.
  2. Open the File Sync section.
  3. Add the XML file to sync:
    • Source: the link or uploaded file
    • Destination Path on Device:
      • Zebra: /sdcard/zebra_config/config.xml
      • Honeywell: /sdcard/honeywell/config.xml
  4. Set sync trigger (e.g., “Every boot” or “Every X hours”).
  5. Save the profile.

Step 3 – Send Custom Intent to Apply Configuration #

  1. Navigate to Profiles > Feature Control > Broadcast Intents.
  2. Create a new custom broadcast intent:
    • Zebra Example:
      • Zebra ImportProfilePath:/storage/emulated/0/download/roam.xml
    • Honeywell Example:
      • am broadcast -a com.honeywell.ezconfig.intent.action.IMPORT_XML --es path /sdcard/honeywell/persist/DeviceConfig.xml --include-stopped-packages --receiver-include-background

  3. Save and assign the intent to the same profile.
  4. The intent will silently trigger the configuration file once synced.


Best Practices & Tips #

  • Use Version Control: Name XML files clearly with versions (e.g., zebra_wifi_config_v2.xml) for easier tracking and rollback.
  • Test Before Rollout: Validate XML and intent commands on a small test fleet before large-scale deployment.
  • Verify File Paths: Double-check source and destination paths for each OEM to avoid failed configurations.
  • Align Intents with Profiles: Ensure broadcast intents are assigned to the same profile as the synced file.
  • Leverage LAN Restriction: Use LAN Access Only for sensitive configuration files to limit exposure outside corporate networks.
  • Document Configurations: Keep a record of uploaded XML files, intents, and profiles for auditing and troubleshooting.