Product Documentation

To provide custom terms and conditions for enrollment

Oct 20, 2015
If your company has specific policies governing connections to the corporate network, you can deliver custom terms and conditions files to users of iOS and Android devices. During device enrollment, users are presented with the terms and conditions and must accept them to enroll their devices. Declining the terms of use cancels the enrollment process.
  1. Ensure that your custom terms and conditions file is available in .pdf format. Name the file enduserterms.pdf. Only PDF files can be used.
  2. On the Device Manager server, copy the custom terms and conditions file to the \tomcat\webapps\zdm\documents\ directory of the installation.
  3. Using a web browser, navigate to http[s]://serveraddress[:port]/zdm, where serveraddress is the fully qualified domain name (FQDN) or IP address of the Device Manager server and port is the optional port number if you changed the default setting.
  4. Log on to the Device Manager web console using an account with administrative permissions.
  5. Click the Files tab and then in the left pane click New file.
  6. Navigate to and select the custom terms and conditions file you want to import.
  7. Select Terms & Conditions PDF to use the imported file for user acceptance of terms and conditions.
  8. Select the Default Terms & Conditions PDF check box to use the imported file as the default document for users who are members of multiple groups with different terms and conditions documents.
  9. Optionally, enter a description that will help you to identify the document and then click Import.

    The document is stored in the Device Manager database.

Once you have uploaded the file, you must add it to a deployment package to deliver the file to users during enrollment. Typically, the file is added to the iOS or Android base package that is deployed to users when they enroll. However, if you configure additional packages for deployment during device enrollment, you can also add the file to these packages. For more information about deployment packages, see Creating Deployment Packages