Supported by: ALL
The server path is the URL by which the DME client can reach the DME server. This is the external DME server address, including the port number. /nam_xml must not be added to it (this was a requirement in previous versions of DME). This value must be correct, otherwise your DME clients will not be able to connect to the DME server after the first synchronization. It is highly recommend to lock this setting so users cannot change it. This setting is locked on the devices by default. The server path is usually provisioned to the device along with the client software using OMA DM or SMS push. See also Send server path.
Supported by: ALL (if they have a phone module)
This is the phone number for the device. This value naturally cannot be set in the default or group settings on the server. It is either entered by the user when installing the DME client or later by entering the number in Settings on the device, or it is registered by the server during OMA DM or SMS push installation of the DME client and subsequently synchronized to the client.
If no phone number is registered for the device in the client, the client will send an SMS to the server's SMS modem, which responds with the number from which the SMS was sent. This number is then synchronized to the server at the next sysinfo sync. The phone number must be set in order for SMS-based features, including DM actions, to work correctly on the device. Please note that for the device to discover its own phone number, the SMS modem phone number must be registered on the server (Server > Server configuration > SMS modem). See SMS modem for more information.
Supported by: 
If this setting is On, the DME client will launch immediately after start or reboot of the device. Recommended value: On.
If Lock device when logout in the Security group of settings is enabled, this setting must be enabled also (does not apply to the Basic MDM client).
Supported by:
By default, the GPRS connection times out after 1 minute for cost reasons, but you can choose to never close the connection. Recommended value: After 1 minute to reduce data costs and save battery lifetime. This setting does not affect network push, which runs on a different connection.
Supported by:
If this setting is On, the client logs incoming and outgoing traffic for use in Traffic statistics (see Analyzer). If On, make sure this feature does not conflict with local data protections laws.
Supported by:
If this setting is Off, the device will not perform background synchronization when using a roaming network. Background synchronization covers scheduled synchronization, e-mail and PIM pull, and SMS push notification. If Manual sync. when roaming is On, the user will still be able to synchronize manually.
The roaming status of the device is stored on the server. The first background sync performed while roaming will therefore be carried out normally, but will also inform the server that the device is roaming, effectively cutting the device off from further background synchronization. This means that the server is unable to detect that the device is back in the home network, unless the user performs a manual sync. When using this cost-saving feature, it is important to instruct the users to perform a manual sync when they return to their home network.
Supported by:
If this setting is Off, the user will not be able to perform manual synchronization when using a roaming network. When roaming, a user trying to perform a manual sync will see a message saying that synchronization is not allowed when roaming.
The device uses information from the SIM card when checking if it is currently roaming. As soon as the phone is no longer roaming, the user is able to synchronize manually again. Performing a manual sync will also inform the server that the device is no longer roaming, which is necessary for re-enabling background sync. See also Background sync. when roaming.
Supported by:
If this setting is On, the client will help the user switch to an operator among the choices made in the list of mobile operators. This only applies to Windows Mobile clients. If this setting is Off, or on other platforms than Windows Mobile, it is up to the user to switch to the preferred operator. See Preferred operators for more information.
Supported by: 
In this field you can specify the action of the secondary device action button when the Desktop is shown. The following choices are available:
- Lock: This is the default setting. Pressing the secondary action button locks DME and shows the Login screen.
- Hide: If you select this option, pressing the secondary action button will hide (minimize) DME without logging out the user.
Supported by:
In this field you can specify the action of the device action buttons when the Login screen is shown. This setting does not apply to iPhone. The following choices are available:
- Exit: This is the default setting. Pressing the secondary action button exits the DME application.
- Hide: If you select this option, pressing the secondary action button will hide (minimize) DME without logging out the user. Note that by selecting this, both the Exit action and the Login action are moved to the primary action button, which is then called Options.
Supported by:
If this setting is On, the user can select the DME application as the program to be launched when he or she presses the Mail one-touch button 
on the Symbian device.
Supported by:
With this setting, you can choose to show a notification with the number of new e-mails in DME. The notification pops up on the Nokia homescreen when a new e-mail arrives. When the user clicks the navigation key (or taps the notification area - 5th edition only), DME opens or is brought to the foreground. If the user presses any other key (or taps outside the notification area - 5th edition only), the notification disappears, and the user can continue working with the phone.
You can choose among the following options:
- Enabled: The notification is shown for approx. 30 seconds every time the user goes to the homescreen. This means that the notification will reappear whenever the user navigates to the homescreen from another application; when the phone wakes from screensaver mode; or when the user presses any button after the notification has disappeared by itself (that is, after 30 seconds). The notification will be removed when the user opens DME and reads any of the new e-mails.
- Show once: The notification only appears once - when the user clicks (or taps) something to make the notification disappear, it will not reappear until a new e-mail arrives.
- Disable: The homescreen integration feature is disabled.
Supported by:
In this field you can specify the primary, secondary, and tertiary access point used to connect to the DME server. It is recommended to enter the fastest and/or cheapest access point as the primary access point, such as WLAN, and let it fall back to GPRS as a secondary access point. Note that if you fill in these fields, you must be certain that all the Symbian devices that use this property have the access points in question installed.
Supported by:
With this setting you can specify which action the DME client for iOS (3.5.6 and later) should perform after launch or after resuming from minimized state. To provide the fastest check for server commands after startup of the client, set this to E-mail sync.. This requires that the notification framework has a schedule for e-mail scans - otherwise the option System info sync. is faster. Please note that in version 3.5.6 of the DME client, the value None is interpreted as a System info sync..
Supported by:
The first time a feature is enabled for a client device, this action will be performed. For instance, if you enabled calendar sync. on a device where this was previously disabled, then the action selected here will be run for the client's calendar the first time the client connects to DME. Note that the client user will not be asked about this - therefore, you should use the Wipe option with caution!
- Wipe: The first time the client connects to synchronize a resource of a certain type (calendar, contacts, etc.), the client is commanded to wipe any existing data on the device. For instance, if you synchronize contacts for the first time, all your existing contacts will be deleted first. The user is not asked about this.
Use this option with care. You can use the Wipe mode if you want to make sure that only company data is stored on the phone.
- Merge: The first time the client connects to synchronize a resource of a certain type (calendar, contacts, etc.), the client is commanded to merge any existing data on the device. For instance, if you synchronize contacts for the first time, all your existing contacts on the device will be sent to the server as creates first. The server will then detect and remove duplicates, and then synchronize the result. The user is not asked about this.
This is the recommended setting.
Note that the device will always wipe or merge the available data store. In the case of Calendar and Contacts, personal items will not be affected if the device uses Secure mode.
Supported by:
If this setting is On, you can view e-mails in full HTML on supported clients (version 4.1 and above). The advantage of HTML is of course that the users receive richer content on their devices. The drawback is added data transfer volume. DME strips tags that may present a risk from the HTML, such as script tags, embed tags, etc.
Please note that on Domino, this feature only works when running Notes session mode. Furthermore, the feature works best when Domino 8.5.3 Feature Pack 1 or 2 is installed on the DME connector (64 bit). Feature pack 3 interprets HTML differently, and this will yield unexpected results on the device.