Adding a contacts account

To enable the iOS MDM device user to synchronize data with the CardDAV server, add the CardDAV account. Synchronization with the CardDAV server enables the user to access the contact details from any device.

To add the CardDAV account of the iOS MDM device user:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.

    Complete the following steps within 15 minutes. Otherwise, you may face an error when saving changes to the policy.

  4. In the policy Properties window, select the Contacts section.
  5. Click the Add button in the CardDAV accounts section.

    The CardDAV account window opens.

  6. In the Description field, enter a description of the user's CardDAV account. You can use macros from the Macros available drop-down list.
  7. In the Server address and port field, enter the name of a host or the IP address of a CardDAV server and the number of the CardDAV server port.
  8. In the Main URL field, specify the URL of the CardDAV account of the iOS MDM device user on the CardDAV server (for example: http://example.com/carddav/users/mycompany/user).

    The URL should begin with "http://" or "https://".

  9. In the Account name field, enter the account name for authorization on the CardDAV server. You can use macros from the Macros available drop-down list.
  10. In the Password field, set the CardDAV account password for authorization on the CardDAV server.
  11. To use the SSL (Secure Sockets Layer) data transport protocol to secure the transmission of contacts between the CardDAV server and the mobile device, select the Use SSL connection check box.
  12. Click OK.

    The new CardDAV account appears in the list.

  13. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, CardDAV accounts from the compiled list will be added on the user's mobile device.

Page top