7P MDM Server Admin Quick Start 7P Mobile Device Management

Transcription

1 7P MDM Server Admin Quick Start 7P Mobile Device Management Rel: / Doc.No.:7PMDM_ServerAdminQuickStart_EN

2 1 Prerequisites Cloud instance login and language selection Basic navigation layout Basic navigation Command navigation Create a basic user hierarchy and groups Add a test user account Configure the MDM server default messages Configure the MDM server ios messages Configure the ios Organisational information Adding user information Manually add users Add users using the CSV import utility Add users automatically using LDAP sync Custom Parameters The MDM server uses Custom Parameters in three ways: Add devices Automatically through an Operation command Using the Self Registration Portal Manual addition of user device Choose a Platform MDM ID (IMEI) Device name Device phone number for enrollment Activation parameters Activation PIN Samsung KNOX Private IMSI Enrollment type Enroll via Enroll via SMS Save without enrolling P_QuickStartAdminGuide_ _EN.docx Page 2 / 28

3 3.6.4 Private IMSI Manual manipulation of user device To user To device pool Enrollment and Android devices Enrollment and ios devices Enrollment and WF8 devices Enrollment and Windows Mobile devices Enrollment and Symbian S60 devices Appendix A Configure the settings General options Configure the MDM client settings Check the Device connection settings Check the MDM client installation settings Check and configure the device connection intervals Check the location of the MDM Server ios client Check and configure the MDM server ios download page Add Mobile carrier information P_QuickStartAdminGuide_ _EN.docx Page 3 / 28

4 Table of Figures Figure 1 Successful login Figure 2 Server navigation Figure 3 Hierarchy and groups... 7 Figure 4 Self Provisioning Portal welcome screen Figure 5 Add device button Figure 6 Add new device data Figure 7 Mandatory enrollment fields Figure 8 Assign device to device pool Figure 9 Assign device to user Figure 10 Device assignment confirmation Figure 11 Android device data Figure 12 Add new ios device data Figure 13 Add newwp8 device data Figure 14 Add new WinMobile device data Figure 15 Adding new S60 device P_QuickStartAdminGuide_ _EN.docx Page 4 / 28

5 1 Prerequisites This document assumes the following have been configured and tested by the supplier of the MDM server: Administrators account SMTP communication configured and tested SMS communication configured and tested MDM Client web page MDM Client server address and password This document also assumes that the administrator has been formally briefed in the capabilities of the MDM server by a trained 7P MDM specialist who has highlighted the ascending order of events contained in this document that will guarantee a successful deployment of their MDM solution In this section we will show how to perform the following tasks Login to the Cloud instance of their MDM server Change the UI language Understand document navigation and syntax Create a basic user hierarchy and groups Add a test user account Add a generic test device Once the above tasks are complete, the administrator will be able to add users and devices within a predetermined hierarchy and send each configured device an (Wi-Fi only devices) or a SMS text message. 1.1 Cloud instance login and language selection On a new installation, the MDM administrator user name and password will be defined in the software distribution package. Once the credentials have been successfully inserted, and the "login" button pressed, the initial login screen will be replaced by the MDM server "home page". Figure 1 Successful login. The MDM version number will always be displayed in the "footer" of every page, for example v Once logged into the MDM server select the required language from the pull down menu located at the top right hand side of the initial login screen. You may choose from the following: English, German, Spanish, Finnish, or Danish. 7P_QuickStartAdminGuide_ _EN.docx Page 5 / 28

6 The language selection may be changed at any time and will be saved automatically 1.2 Basic navigation layout The MDM server navigation is achieved by selecting a main "header" subject (pictured in gold) of Dashboard, Organization, Infrastructure, Operations, Reports and System settings which will open an associated web page. Each opened web page will reveal it's vertical topic elements (pictured in blue). Each topic element will have detailed configuration panel associated with it. Figure 2 Server navigation Basic navigation Navigation through the various headers, topic, and panel is short formed in this document in the following way: Navigate to System settings > Base > Tenants will instruct the administrator how to locate the "Tenants" configuration panel within the MDM server. Command navigation Command navigation consists of a command tagged onto the navigational direction: Select the Organization > Hierarchies & groups > Add a new hierarchy will instruct the administrator how to locate the "Add a new hierarchy" command within the MDM server. 1.3 Create a basic user hierarchy and groups Navigate to Infrastructure > Hierarchy & groups > Add a new Hierarchy 7P_QuickStartAdminGuide_ _EN.docx Page 6 / 28

7 Figure 3 Hierarchy and groups Select the "Add a new hierarchy" button and enter "Support" in the pop up field provided, then "Save" "Support" hierarchy added "North" subgroup added Select the "Support" label, the "operation on selected node" pane is revealed, select" Add a new subgroup". Insert the name of the new group, "North", then "Save" A basic hierarchy has now been created, "Support" with a subgroup called "North". 1.4 Add a test user account Navigate to Infrastructure > Users and devices > Add user The previously created Hierarchies and groups are clearly visible. No users have been entered into the MDM server at this point in time. Select "Add user", the form is revealed add the user's details to the form. A valid address must be used. 7P_QuickStartAdminGuide_ _EN.docx Page 7 / 28

8 The "Add device" button will be displayed Complete the form, using the "Apple ios" device. It is essential at this stage to insert a valid mobile telephone number and valid address. Once inserted, select "Save without enrolling" the information will be saved into the MDM server database but the enrollment mechanism will not be started. A device has been successfully added to a new user. 1.5 Configure the MDM server default messages Navigate to Settings > Messages > Default messages The default messages contain standard phrases that are used daily in the operation of MDM servers by many customers. The MDM server will allow the administrator to personalise the messages to complement a corporate profile 1.6 Configure the MDM server ios messages Navigate to Settings > Messages > Default ios messages Again, like default messages, the default ios messages contain standard phrases that are used daily in the operation of MDM servers by many customers. The MDM server will allow the administrator to personalise the messages to complement a corporate profile 7P_QuickStartAdminGuide_ _EN.docx Page 8 / 28

9 1.7 Configure the ios Organisational information Navigate to Settings > Messages > ios Organisational information The "Display account information" reveals the information that the controlling organisation has registered with Apple Corporation Inc. The account information is returned to the MDM server as part of the DEP protocol. 7P_QuickStartAdminGuide_ _EN.docx Page 9 / 28

10 2 Adding user information In this section we will show how to perform the following tasks Manually add users Add users using the CSV import utility Add users automatically using LDAP sync Unique user information Custom Parameters The size of the installed user base usually determines the method used to add user information to the MDM server. Smaller users may use either the manual input method or utilise the CSV import utility, whilst larger user bases would use either the CSV import utility or LDAP sync. 2.1 Manually add users Manually adding a user to the MDM server is identical to the already described "Adding a test user" (See Add a test user account) 2.2 Add users using the CSV import utility The "CSV import" tool allows the administrator to select a pre - populated CSV file from their local computer which will be imported into the MDM server database. Before the data is committed to the MDM server database, specific integrity checks are executed on the importing data to ensure the data is correctly formed. For details in the preparation of a CSV file ready to import many users into the MDM server (see Error! Reference source not found. of this document). 2.3 Add users automatically using LDAP sync For details in testing and configuring the LDAP sync function of the MDM, refer to the Manual LDAP EN. When a valid LDAP configuration is implemented, the "Sync with LDAP" button becomes visible on the "Users and Devices" window. If the administrator then selects "Sync with LDAP" the MDM server will synchronise the user account information with the LDAP server. If users have been added by other means, and are not contained within the LDAP server the new users will be added to the existing user base. 2.4 Custom Parameters Custom parameters allow the efficient utilization of both the MDM Server and MDM Server configuration distribution process. Custom parameters are identical in creation, format and configuration. The primary function of a custom parameter is to substitute user configuration values (e.g. Exchange username) with assigned Custom Parameter assignments used in MDM server templates, configurations and scripts. If, for example, the administrator wishes to deploy "Exchange settings" to 1,000 users through a configuration template, most of the detail found in the configuration is common, except for the values of "Exchange username" and "Exchange password". Custom parameters can be defined as type "default", where the values assigned to the custom parameter are visible, or type "password" where the values are encrypted and displayed as "******", hiding the true values. 7P_QuickStartAdminGuide_ _EN.docx Page 10 / 28

11 2.4.1 The MDM server uses Custom Parameters in three ways: A system Custom Parameters A "system custom parameter" must be created by the administrator. Once created, the system custom parameter(s) are allocated to user device(s) at any time, to any registered device, by the system administrator. A user Custom Parameter A "user custom parameter" is a "system custom parameter" that is allocated when a new user is registered to the MDM server. Any device (or devices) allocated to that user will then inherit the "user customer parameters" automatically. When inspecting a user's device, through Users and Devices > Device, any configured "user custom parameter" will be identified as "inherited custom parameters". A configuration (template) Custom Parameter The "configuration custom parameters" are an efficient method of utilising system resources when multiple configuration scripts are deployed to multiple users. The following configuration templates, when the listed field is selected, and pulled down, will reveal a Custom parameter that can be selected into the configuration template. Configuration Username Password https https Template Username Password Access Point Autolock Exchange Secure File Container A "configuration custom parameter" is typically used in configuration templates when a value, usually a username or password is substituted by the actual value of the user's username and password combination. 7P_QuickStartAdminGuide_ _EN.docx Page 11 / 28

12 3 Add devices This section explores the way that devices can be added (and manipulated) to the MDM server Automatically through an Operation command Semi-automatically through the SSP (Self service portal) Manually though the administrators console Device manipulation though Device Pool The above methods will be discussed. 3.1 Automatically through an Operation command The MDM server allows administrators to develop a logical command sequence that can be applied to specific devices that comply with specific criteria. Navigate to Operations > Operations > Add The "Not enrolled" condition has no options. The term "Not enrolled" refers to all user device references that are registered with the MDM server that do not have either an activated MDM client, or ios profile. An enrollment SMS or will be sent to all registered users. On receipt, the user must follow the instructions given in either the SMS or message. The "Enroll" operation can be read in the following way: Perform the following only once - "For all devices that match the Condition - Not enrolled perform the Action Enroll by sending the enrollment invitation SMS text message, then the enrollment invitation to the telephone number and address registered in the users detail" 7P_QuickStartAdminGuide_ _EN.docx Page 12 / 28

13 3.2 Using the Self Registration Portal When the user information has been loaded into the MDM server, the administrator can advise the users of the Self registration Portal URL, enabling each user to visit the SRP website, and effectively register their device to the MDM server. Figure 4 Self Provisioning Portal welcome screen. The following information must be loaded by the administrator into the MDM server prior to inviting a user to "selfregister" their device(s). The administrator may load the details in manually, via LDAP, or via a CSV import. First Name Last Name address of user Tenant for user management The MDM server self-provisioning portal uses the address of the user as a uniqueness identifier. It is always preferable that during device registration to utilise the corporate address of the user. Once the information is entered, the administrator displays the URL of the SRP to the required users. The users would then enter the URL of the SRP server into an internet browser and navigate to the given SRP URL. The SRP webpage will automatically set the SRP homepage to the language of the browsing device, if the devices language cannot be matched, then the page will display in the default English language The "home" icon allows the user to restart the SRP process The "Language" icon allows the customer to change the SRP language; choices are English, Deutsch, Dansk and Suomi. The "download" icon will allow the user to download an MDM client directly to the device. If the device is not automatically identified by the download website, the user will be allowed to pick a suitable MDM client for their device from the available list. The user will either select the "ios" button, or the "Android" button depending on their device. Once their choice is selected the following information screen is displayed. If the user information lodged with the MDM server is incorrect, or the user incorrectly enters their details, then, a message stating "User information cannot be found" will be displayed. 7P_QuickStartAdminGuide_ _EN.docx Page 13 / 28

14 3.3 Manual addition of user device The device registration/enrollment of a user device may be manually implemented to the MDM server by the administrator. Navigate to Organisation > Users & devices Devices can only be added to a registered user of the MDM Server. When an existing user has been selected, the Add device button will appear in the Users and devices window. Figure 5 Add device button Once the "Add device button" is selected, the "New device data" window is revealed. Selecting a different device from the options will ensure that the correct type of device is registered to the MDM server. The "New device data" information is listed below. Figure 6 Add new device data Samsung enabled KNOX device(s) will have the additional facility to automatically use a KNOX license, enabling the Samsung KNOX container on the target device during activation. 7P_QuickStartAdminGuide_ _EN.docx Page 14 / 28

15 3.4 Choose a Platform The system administrator must select from the following devices: Android Apple ios Symbian 60 WinMob (Windows Mobile) WP8 (Windows Phone8) Unknown Each device has mandatory information that must be provided to enable successful enrollment: Device Android Android ios ios WP8 WinMob S60 MDM ID (IMEI) Device name Device Phone Number Enrollment Activation parameters Download URL Activation PIN Samsung KNOX Private IMSI Private IMSI defined Enrollment type SMS SMS SMS SMS Figure 7 Mandatory enrollment fields. WP8 require both the Device name and MDM ID (IMEI) details to be completed to ensure a successful enrollment. If the MDM ID (IMEI) of the WP8 device is not pre registered, then the device will be added to the users account with the device name of "WindowsPhone" MDM ID (IMEI) The MDM ID (IMEI (International Mobile Equipment Identification) number is typically 15 digits longs and supplied with the original device shipment and is optional for enrollment. The IMEI information field will automatically be inserted by the MDM server once the enrolling device has initially connected. Device name The device name is a friendly name given to the device by the system administrator to help manage and identify specific devices. 7P_QuickStartAdminGuide_ _EN.docx Page 15 / 28

16 Device phone number The device phone number should be included using international dialling format. e.g. Germany " ", Estonia " " and Austria " ". The device phone number is a requirement for the enrollment of Windows Mobile devices, which receives an SMS message as part of its enrollment process. for enrollment The user's enrollment address is a requirement for the enrollment of Android, ios and Windows Phone 8 devices, which receive instructional s as part of their enrollment process. For Android and ios devices, along with enrollment instructions, a picture containing a QR Code, for QR code activation, will be included. Windows Phone 8 devices receive their WP8 username and password contained in their MDM user profile, along with instructions of how to insert the username and password into their Windows Phone 8 device. The for enrollment must be completed with a valid and current address of the prospective MDM server user. Activation parameters The activation parameters define either a URL, allowing the user to download a suitable MDM client for their device, for example, if the device is currently "unknown". Activation PIN The activation PIN, maintained and configured by the administrator allows the user to confirm their association with the MDM server. Samsung KNOX The Samsung KNOX feature, is only pertinent to Samsung KNOX enabled Android devices, allows the administrator to define whether the KNOX facility is enabled, by automatically assigning the use of a KNOX license to the installing device. 3.5 Private IMSI The Private IMSI (International Mobile Subscribers ID) allows the administrator to report the identification of a Private IMSI (SIM card) is intended to be used in the device. Required to negate the action of any configured "SIM change policy". 3.6 Enrollment type Allows the administrator to determine which enrollment method to deploy Enroll via The MDM server administrator can select to send an enrollment (Android, ios and WP8), typically used for Wi-Fi devices. Enroll via SMS The MDM server administrator can select this to send an enrollment SMS message (Android, ios, Windows Mobile and Symbian) 7P_QuickStartAdminGuide_ _EN.docx Page 16 / 28

17 Save without enrolling The MDM server administrator can elect to register the device on the MDM server without enrolling the device. The process of enrollment creates a trust relationship between the device and the MDM server. Private IMSI Each device is allowed a maximum of two extra IMSI cards definitions. These extra IMSI cards are generally referred to as private SIM cards, which allow the user to utilise the company's mobile device whilst consuming data and video through their own private SIM card subscription, for instance, at a weekend. 3.7 Manual manipulation of user device The MDM server action "Assign device" allows the administrator to assign the currently selected device to either another (registered) user, or to the device pool. Figure 8 Assign device to device pool To user The "To user" button, when selected, will produce a pop up that allows the administrator to search for and select a username that they wish to assign the current device to. Figure 9 Assign device to user. From the search results, selecting the name of the user, and selecting the "Ok," button will change the assignment of the device from the present user to the newly selected user. When transferring the device from an existing user to the device pool it is advisable to remove all remotely installed configurations, certificates, applications, and policies from the device. 7P_QuickStartAdminGuide_ _EN.docx Page 17 / 28

18 3.7.2 To device pool At the top right hand side of the device details panel is a group of three buttons which directly affect the deployment and registration of the registered device, one of which is the "Add to pool" button" Figure 10 Device assignment confirmation. On the selection of this button, the device will be assigned to the free device pool. 7P_QuickStartAdminGuide_ _EN.docx Page 18 / 28

19 4 Enrollment and Android devices In this section we will show how to: Manually add an Android device Select either enroll via or SMS Check device has enrolled into the MDM server Navigate to Organisation > Users & devices > Add device > New device data and select the Android platform button. Figure 11 Android device data Once the user's contact and device information is entered correctly, the administrator has the option of either selecting the "Enroll via SMS", "Enroll via ", or "Save without enrolling button". A description of the field contents are as follows: Field MDM ID (IMEI) Device name Description The IMEI of the device A friendly name that will help with device identification Device mobile phone number The device's mobile telephone number in international format e.g. Germany " ", Estonia " ", and Austria " " for enrollment A valid user's address Download URL Enroll via SMS Enroll via Save without enrolling Contains the URL where a suitable MDM client can be downloaded Add the users device through SMS enrollment Add the users device through enrollment Save the presented details without sending either an or SMS enrollment message A mobile number has to be inserted to reveal the "Enroll via SMS" button. The document "7PMDM Android Client" contains a fuller explanation of the enrollment process. 7P_QuickStartAdminGuide_ _EN.docx Page 19 / 28

20 5 Enrollment and ios devices In this section we will show how to: Manually add an ios device Select either enroll via or SMS Navigate to Organisation > Users & devices > Add device > New device data and select the ios platform button. Figure 12 Add new ios device data Once the user's contact and device information is entered correctly, the administrator has the option of either selecting the "Enroll via SMS", "Enroll via ", or "Save without enrolling button". A description of the field contents are as follows: Field MDM ID (IMEI) Device name Description The IMEI of the device A friendly name that will help with device identification Device mobile phone number The device's mobile telephone number in international format e.g. Germany " ", Estonia " ", and Austria " " for enrollment A valid user's address Download URL Enroll via SMS Enroll via Save without enrolling Contains the URL where a suitable MDM client can be downloaded Add the users device through SMS enrollment Add the users device through enrollment Save the presented details without sending either an or SMS enrollment message A mobile number has to be inserted to reveal the "Enroll via SMS" button. The document "7PMDM ios Client" contains a fuller explanation of the enrollment process. 7P_QuickStartAdminGuide_ _EN.docx Page 20 / 28

21 6 Enrollment and WF8 devices In this section we will show how to: Manually add a WF8 device Select either enroll via or SMS Navigate to Organisation > Users & devices > Add device > New device data and select the WP8 platform button. Figure 13 Add newwp8 device data Once the new device information is entered correctly, the administrator has to select either "Enroll via " or the "Save without enrolling" button. A description of the field contents are as follows: Field MDM ID (IMEI) Description The IMEI of the device Device name A friendly name that will help with device identification Device mobile phone number The device's mobile telephone number in international format e.g. Germany " ", Estonia " ", and Austria " " for enrollment A valid user's address The Windows Phone 8 does not require an MDM Client for enrollment. The enrollment process is instigated by the user of the WP8 device, and will succeed if a valid WP8 username and password has been entered when the user was initially added to the MDM server. The document "7P MDM Microsoft Windows Phone 8" contains a fuller explanation of the enrollment process. 7P_QuickStartAdminGuide_ _EN.docx Page 21 / 28

22 7 Enrollment and Windows Mobile devices In this section we will show how to: Manually add a Windows Mobile device Select either enroll via or SMS Navigate to Organisation > Users & devices > Add device > New device data and select the Win Mo platform button. Figure 14 Add new WinMobile device data Once all of the user's contact and device information is entered correctly, the administrator has the option of either selecting the "Enroll via SMS" button, or "Save without enrolling button". A description of the field contents are as follows: Field MDM ID (IMEI) Description The IMEI of the device Device name A friendly name that will help with device identification Device mobile phone number The device's mobile telephone number in international format e.g. Germany " ", Estonia " ", and Austria " " for enrollment A valid user's address Download URL Enroll via SMS Enroll via Save without enrolling Contains the URL where a suitable MDM client can be downloaded Add the users device through SMS enrollment Add the users device through enrollment Save the presented details without sending either an or SMS enrollment message A mobile number has to be inserted to reveal the "Enroll via SMS" button. The document "7PMDM Windows Mobile client" contains a fuller explanation of the enrollment process. 7P_QuickStartAdminGuide_ _EN.docx Page 22 / 28

23 8 Enrollment and Symbian S60 devices In this section we will show how to: Manually add a Symbian S60 device Select either enroll via or SMS Navigate to Organisation > Users & devices > Add device > New device data and select the Symbian 60 platform button. Figure 15 Adding new S60 device. Once the user's contact and device information is entered correctly, the administrator has the option of either selecting the "Enroll via SMS", or "Save without enrolling button". A description of the field contents are as follows: Field MDM ID (IMEI) Device name Device mobile phone number for enrollment Description The IMEI of the device A friendly name that will help with device identification The device's mobile telephone number in international format e.g. Germany " ", Estonia " ", and Austria " " A valid user's address Download URL Enroll via SMS Enroll via Save without enrolling Contains the URL where a suitable MDM client can be downloaded Add the users device through SMS enrollment Add the users device through enrollment Save the presented details without sending either an or SMS enrollment message A mobile number has to be inserted to reveal the "Enroll via SMS" button. The Symbian S60 device has no MDM server functionality. It is only added to the MDM server for asset management. 7P_QuickStartAdminGuide_ _EN.docx Page 23 / 28

24 9 Appendix A In this section we will show how to perform the following tasks Configure SMTP messaging Configure SMS messaging Check SMTP and SMS messaging capabilities Configure the MDM servers General options Configure the MDM client settings Check the Device connection settings Check the MDM installation settings Check and configure the device connection intervals Check the location of the MDM Server ios client Check and configure the MDM server ios download page Add mobile carrier (providers) information Once the above tasks are completed, the administrator will be capable of adding users and devices knowing that their specific message dialogue is used with all installation. 7P_QuickStartAdminGuide_ _EN.docx Page 24 / 28

25 9.1 Configure the settings General options Navigate to Settings > System settings > General options > Edit This set the system error logging level, and is typically only used by the MDM server administrator who has access to the system error log files When the check box is selected, the AppStorage functionality will be enabled on the devices that are enroll to the MDM server. If the administrator uses a hierarchy without defining any sub-groups this is termed a "Standalone" group, and if the user satisfies the membership criteria "Belongs to Location OR Department" then access is permitted When the check box is selected, the SFC (Secure File Container) functionality will be enabled on the MDM server. The Samsung SAFE Enterprise license key is provided by 7P free of charge and should by default be part of the MDM code in the software and is also available on the 7P Cloud MDM instances. This Safe enterprise license is ONLY required when starting to use the new 5.04.xx MDM client that is unsigned by Samsung. The Samsung KNOX license key is only available from SAMSUNG, or a KNOX authorised reseller/distributor in specific regions/countries. 9.2 Configure the MDM client settings Navigate to Settings > Connections > Client settings 9.3 Check the Device connection settings Allow the administrator to control the following attributes for all distributed clients Allow activate will allow the MDM client to activate with the MDM server Allow going offline will allow the device user to select that the MDM client will be "offline" to the MDM system Allow Data reset will allow the user to reset the MDM Client/Server command queue Navigate to Settings > Connections > Device connections The MDM Client connection settings contain important information regarding the MDM client password, and the MDM client URL. This information is required by any user attempting to manually activate a MDM Client. e.g. MDM Server URL: Password: ewbf23 7P_QuickStartAdminGuide_ _EN.docx Page 25 / 28

26 9.4 Check the MDM client installation settings Navigate to Settings > Connections > Client installation settings The "Download URL" will be transmitted to all users wishing to be enrolled via the MDM server "Add device" function. This URL contains the MDM client application location. The "Activation PIN" is required by an enrolling user when they install the appropriate MDM client application onto their device. The "Activation PIN" is essential to the successful enrollment process. The administrator must ensure that the "Activation PIN" is known to all users' wishing to enroll their device into the MDM server. 9.5 Check and configure the device connection intervals Navigate to Settings > Connection settings > Device connection intervals You may change the connection intervals by selecting the "Edit" button make your selection then "Save". 1. The "Interval outside" is the duration of time outside the definition. If From To was 09:00 17:00, and the "Interval outside" was set to 02:00 (2 hours) then the device will connect every 2 hours between 17:00 09:00 2. The "Interval within" is the duration of time within the definition. If From To was 09:00 17:00, and the "Interval inside" was set to 01:00 (1 hour) then the device will connect every 1 hour between 09:00-17:00 3. Use predefined connection times allows the administrator to override the connection schedule by inserting 1, 2 or 3 preferred connection times. 9.6 Check the location of the MDM Server ios client Navigate to Settings > Connections > ios MDM Client With the introduction of architectural improvements with the release of Apple ios 7, it has become necessary to retain two ios MDM clients available for delivery to ios devices. The series 4.x.x ios MDM client which is compatible with all versions of ios, but does not support the ios7 activation method The series 5.x.x ios MDM client, for ios 7 devices only The "ios MDM Client" settings specify the location that the ios device will use to retrieve the 7P MDM clients, either from the AppStore, or In - House via a specified URL. Both clients are available for download, installation and activation for registered MDM server users. 7P_QuickStartAdminGuide_ _EN.docx Page 26 / 28

27 9.7 Check and configure the MDM server ios download page Navigate to Settings > ios settings > Download page Select the "Greeting" language of the ios download page, use the pull down menu to select your required language. Login credentials - If enabled, then only profiles applied to this device will be displayed. address will be used to identify the user. Only enrolments with selected states Done, Error, Sent and Wait will be displayed in the device message log Download page enabled enables files to be downloaded from the specified download page. 9.8 Add Mobile carrier information Navigate to Settings > Base > Providers Providers Add new: Edit: Delete: Save: Allows the addition of a new entry Allows an existing entry to be edited Allows the selected entry to be deleted Allows the edit/changes/additions to be saved 7P_QuickStartAdminGuide_ _EN.docx Page 27 / 28

28 List of changes Version Date Changes Reason Author JC updates Tony Dargis Version release Tony Dargis Author: Tony Dargis File: 7PMDM_Admin Quick Start_EN Version: Date: DocNr: n/a Proprietary Notice: All rights reserved. No part of the document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the written permission of 7P Austria GmbH. The information in this document is subject to change without notice. Schutzrechte: Alle Rechte vorbehalten. Kein Teil dieses Dokuments darf in irgendeiner Form (Druck, Photokopie oder einem anderen Verfahren) ohne schriftliche Genehmigung der Firma 7P Austria GmbH reproduziert oder unter Verwendung elektronischer Systeme verarbeitet, vervielfältigt oder verbreitet werden. Die Firma 7P Austria GmbH behält sich vor, ohne vorherige Ankündigung den Inhalt dieses Dokuments teilweise oder vollständig zu ändern. COPYRIGHT 7P Austria GmbH P_QuickStartAdminGuide_ _EN.docx Page 28 / 28