Assigning preferences and security settings to devices

There are different ways to assign settings that determine how users work with the HCL Traveler server. You can use the built-in set of default device preferences and security settings that HCL Traveler provides, which is simpler. Or you can create a HCL Traveler policy settings document, which provides greater flexibility and control but is more complex to configure.

Before you begin

If you are using a HCL Traveler policy settings document, the template of the address book on the HCL Traveler server should be at the latest Domino 901 pubnames.ntf template to ensure all the available tabs and settings are available.

Note: HCL Traveler defined device security settings apply to Exchange ActiveSync devices (Apple devices, Blackberry 10, Windows Phone) unless otherwise noted. However, the device preference settings (Sync settings, filter settings, and device settings) do not apply. If a device using ActiveSync cannot be identified, Traveler attempts to apply the settings for Apple devices.
Note: HCL Traveler defined device security settings apply to BlackBerry 10 devices that are configured for direct connection to HCL Traveler (and not activated on a BlackBerry Enterprise Service 10.) For BlackBerry 10 devices that connect to HCL Traveler using BlackBerry Enterprise Service 10, the BES10 managed security policies take precedence, and the HCL Traveler Exchange ActiveSync policy settings will be ignored.
Note: HCL Verse for Android and iOS clients support being configured by third party Enterprise Mobility Managers (EMM). EMM supplied settings take precedence over Traveler settings (unless supplied settings are locked). It is recommended that all settings be managed via the EMM and not through the Traveler server or Traveler policies. For more information, see Managing Android Verse using Android Enterprise and Managing Verse for IOS using AppConfig.