Best Practice for Loading Device Profiles

Follow these tips and best practices for loading device profiles, especially in large deployments.

  • Do not load more than ten VoiceConsole device profiles per node. A single server installation should have no more than 10 pending device profile loads across all sites at any one time.
  • Adjust the MAX_CONCURRENT_DOWNLOADS setting. (VoiceConsole On Prem deployment customers only).
    • MAX_CONCURRENT_DOWNLOADS is specified in the VoiceConsole database table voc_system_properties. It defaults to a value of 1.
    • This value is applied per node when configured in a clustered environment.
    • A VoiceConsole service restart is required when changing this setting.

    Use care when setting this value greater than 5. Consult technical support if performance is affected. Honeywell recommends that this setting not be set above 10.

  • Consider the server-to-site bandwidth. The speed of the network between the Honeywell server and mobile devices impacts the download speed of the device profiles.
  • Refer to the recommended wireless network settings. These recommended settings can improve wireless performance.
  • Consider using the Device Profile Load Job. This job can be ran automatically or manually during a time of low usage.
  • Ensure good naming conventions for hostnames.
    • Do not use an internal TLD (top level domain) – such as a domain ending in .local or .lan.
    • Use a FQDN (Fully Qualified Domain Name) with a proper TLD such as .com or .net.
  • Consider timing of shift starts. Ensure that all shift starts and other task data is available or make sure that there is sufficient time between loading device profiles to not affect shift start with operator, voice, and task package downloads.
  • Do not load a profile multiple times to a device or devices.
  • Monitor for stuck devices. If a device appears to be stuck waiting for a profile load, remove the device from view within VoiceConsole and let it re-appear after a device restart.
    • This clears all pending action items and configuration for a device.