7PMDM Server x - SymbianS60 Client Guide. 7P Mobile Device Management. Doc.Rel: 1.4 / Doc.Nr.: n/a

Transcription

1 7PMDM Server x - SymbianS60 Client Guide 7P Mobile Device Management Doc.Rel: 1.4 / Doc.Nr.: n/a

2 Table of Contents 1 Objectives and Target Groups Objectives: Third-Party Materials Integrity of device OS Text conventions Hyperlink navigation Home hyperlink Description of the warning flags Additional documentation MDM Client Installation Symbian MDM Client install and activation User receives a SMS text message User opens the SMS text message User installs application User accepts installation application MDM Client activation MDM Client activation PIN MDM Client activation; selecting access point MDM Client console Accessing the MDM Client MDM Client s menu structure Application Management AppStorage (Application storage) Mandatory applications Apps (Applications) to be uninstalled Applications to be stopped Memory status Backup settings Initiate backup... Error! Bookmark not defined Backup status Connection settings Connect to server PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 2 / 48 ^Home

3 Activate the MDM Client Set interval settings Select access point settings Online settings... Error! Bookmark not defined. Advanced features Set TARM Trust Restart MDM Client Stop MDM Client File transfer log Activity details Reset data... Error! Bookmark not defined. User settings Privacy settings GPS info Network info MDM security code Debug logging Change security code Shortcut key in use About the MDM Client Exit the MDM Client Remove (uninstall) the MDM Client Manual uninstall of the MDM Client Example - Application Management Blacklist Create the device message (Symbian only) Add a Symbian application to the MDM server Deploy and install an application to the device Verify that the application is installed on the Symbian device Add the application title to the a MDM server "Blacklist" Configure the Symbian device with the Blacklist (policy) Frequency (of Operation) Conditions (of Operation) Actions (to be performed when conditions met) Verify Blacklist is operational PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 3 / 48 ^Home

4 Table of Figures Figure 1 MDM Client and Activation SMS message Figure 2 Open MDM Client open download URL link Figure 3 Selecting the MDM Client Figure 4 Install the MDM Client application Figure 5 MDM Client information message Figure 6 Inserting the Activation PIN Figure 7 Selection of Access points presented to user Figure 8 MDM Client Applications screen Figure 9 MDM Client notification screen Figure 10 MDM Client: AppStorage Figure 11 Example of a local App Store Figure 12 Applications to be uninstalled Figure 13 Memory status Figure 14 Initiate backup.... Error! Bookmark not defined. Figure 15 Backup items to be performed.... Error! Bookmark not defined. Figure 16 Backup tasks saved.... Error! Bookmark not defined. Figure 17 Backup status Figure 18 Connect to server Figure 19 MDM Client activation Figure 20 Address and password of MDM server.... Error! Bookmark not defined. Figure 21 Set connection interval Figure 22 Connection interval values Figure 23 Connection select access point Figure 24 Three access points Figure 25 Select access point Figure 26 Access point 1 configured Figure 27 Offline/online status.... Error! Bookmark not defined. Figure 28 Set MDM Client offline?... Error! Bookmark not defined. Figure 29 Restart the MDM client Figure 30 Stop MDM client Figure 31 Service not active Figure 32 Activity details Figure 33 Activity detail notifications Figure 34 Reset data.... Error! Bookmark not defined. Figure 35 Reset data confirmation.... Error! Bookmark not defined. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 4 / 48 ^Home

5 Figure 36 MDM client restart successful.... Error! Bookmark not defined. Figure 37 Privacy settings Figure 38 Insert valid security code Figure 39 Select privacy data.... Error! Bookmark not defined. Figure 40 Enable GPS information Figure 41 Enable network information Figure 42 Enable security code data Figure 43 Enable debug mode Figure 44 Change security code Figure 45 New security code Figure 46 Verify new security code Figure 47 Current version number Figure 48 Exit the MDM Client Figure 49 Settings icon Figure 50 Application manager icon Figure 51 Installed applications icon Figure 52 MDM Client application list Figure 53 MDM client uninstall Figure 54 MDM client uninstall confirmation Figure 55 MDM client uninstall warning Figure 56 MDM client removal indication Figure 57 Symbian message Figure 58 Add a Symbian application Figure 59 Install an application on Symbian device Figure 60 Check application installed on device Figure 61 Create an application blacklist Figure 62 Deploy blacklist operation to device Always Figure 63 Run application - expected results List of tables Table 1 Text convention... 6 Table 2 MDM Client menu structure PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 5 / 48 ^Home

6 1 Objectives and Target Groups 1.1 Objectives: The aim of this document is to describe to customers of SEVEN PRINCIPLES AG the key features of the Symbian 7P Symbian MDM Client application. It describes the installation process of the MDM Client, using both Mobile networks (i.e. devices with an active SIM card and data plan) and Wi-Fi only compatible devices. The installation is followed by a description of the activation process which allows the MDM Client to successfully communicate with a designated MDM Server. The section entitled "MDM Client console", details the settings and functionality available to the MDM Client. This includes a full disclosure of the MDM Clients "Privacy Settings". This manual reflects the current functions of the 7P MDM Symbian Client. Any updates or feature enhancements made to the product will be promptly reflected in future releases of this document. Target groups: This document was created specifically for the customers of SEVEN PRINCIPLES AG. 1.2 Third-Party Materials All third-party trademarks are the property of their respective owners. 1.3 Integrity of device OS The MDM server relies on the integrity of the devices OS to forward information to the MDM server by the device proprietary messaging OS, or via the MDM client acting with the device messaging OS. In the unfortunate event that a device OS is compromised or has been corrupted in any way, the information passed to the MDM server may be corrupt, impeded or non-existent. The handling of such a situation is beyond the scope of the 7P MDM server. 1.4 Text conventions The following conventions are typically adhered to in the construction of this document. Convention Description Key names Keys that are pressed simultaneously are linked by a plus sign (+): e.g. Press Ctrl + Alt + Del The word Enter indicates you type something and then press the Return or Enter key. enter Bold Used to distinguish certain words from others within the text Italics Used to distinguish certain words from others within the text Table 1 Text convention 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 6 / 48 ^Home

7 1.5 Hyperlink navigation Hyperlinks are used to allow detailed examination of information. For example, if an Operation (named SIM change test) has been deployed to the device, a status message would be included in the device history. Selecting the "SIM change test" hyperlink will open the Operation > SIM change test allowing closer examination. Selecting the browsers "back" button will return the administrator to the device history log. When hyperlinks are available, selecting the hyperlink will either: Navigate the administrator to the origin of the link, for example, a configuration statement To further functionality, for example, as with the displaying of GPS records Utilising the back facility of the browser may return the administrator to the original page. It is always advisable, due to the dynamic nature of the updating data, for the administrator to restart their query with the vertical menu buttons. 1.6 Home hyperlink A hyperlink (^Home) is inserted into the bottom right-hand side of the footer which when pressed will return the reader to the beginning of the document and is only active in PDF format. 1.7 Description of the warning flags This document may contain warnings and safety recommendations of the following meaning: Attention: May have undesired consequences Caution: Operational functionality may be impeded Further attention may be required when implemented General information 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 7 / 48 ^Home

8 1.8 Additional documentation The following additional documentation is available from your 7P representative or service provider: 7PMDM_Client_Android_v5.07.0x_EN 7PMDM_Client_iOS_v5.07.0x_EN 7PMDM_Client_SymbianS60_v5.07.0x_EN 7PMDM_Client_WindowsPhone_v5.07.0x_EN 7PMDM_Client_Files2Go_v5.07.0x_EN 7PMDM_Spec_LDAP_v5.07.0x_EN 7PMDM_Spec_MSCompanyHub_v5.07.0x_EN 7PMDM_Spec_SSP_v5.07.0x_EN 7PMDM_Spec_AppWrapping_v5.07.0x_EN 7PMDM_Spec_Files2Go_v5.07.0x_EN 7PMDM_Spec_CSVImport_v5.07.0x_EN 7PMDM_Manual_InstallGuide_v5.07.0x_EN 7PMDM_Delivery_RelNote_v5.07.0x_DE 7PMDM_Delivery_RelNote_v5.07.0x_EN 7PMDM_Delivery_ReleaseBulletin_v5.07.0x_EN 7PMDM_Delivey_FeatureList_v5.07.0x_EN Revision details have been omitted from the documentation list as the most current version will be available from your 7P representative or service provider 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 8 / 48 ^Home

9 2 MDM Client Installation This section describes the Over-the Air (OTA) delivery of the 7P MDM Client application. It includes a description of the steps that has to be performed by the user of the Symbian Mobile device to ensure the correct installation of the 7P MDM Client. This chapter consists of the following sub-chapters: 2.1 Client OTA installation 2.2 Client automatic activation 2.1 Symbian MDM Client install and activation When the System Administrator adds a new Symbian user to the MDM Server, a SMS text message is sent to the new user's device from the MDM Server during the device or user registration process. The message, received by the user, typically contains: Free text (a message to the user, entered by the administrator). A download link (URL to locate the MDM Client application). Activation PIN. Default security parameters. Access point details (optional). Encoded activation information (for use only by the MDM client). 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 9 / 48 ^Home

10 2.1.1 User receives a SMS text message When a system administrator adds a new user to the MDM Server, a SMS text message, containing a URL and activation details are sent to the user's device. Figure 1 MDM Client and Activation SMS message. Refers to the URL web link to a downloadable MDM Client application. (MTIzNCxodHR.MQ==) Contains encrypted information which is consumed by the MDM Client on installation User opens the SMS text message On receipt of the SMS message, the user would be expected to open the included download link. Figure 2 Open MDM Client open download URL link. The link will direct the user to a predetermined web site. The web site automatically detects the model and manufacturer of the user's device. An appropriate MDM Client is presented to the user for installation. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 10 / 48 ^Home

11 2.1.3 User installs application Figure 3 Selecting the MDM Client The following message is displayed: "MDM Client will be installed in 5 seconds. Please, close the browser after installation. If client version is not detected, you will be redirected to install the MDM Client manually." After downloading the installation package, the user must agree to start the Install of MDM Client: by selecting the file to install User accepts installation application Detailed information about the installation package version number is displayed. Click the OK button to continue. Figure 4 Install the MDM Client application. When the OK button is selected, the installation process will commence. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 11 / 48 ^Home

12 2.2 MDM Client activation After the successful installation, the MDM client will start automatically (within 30 seconds). An information message is displayed and the MDM client is known to be in the "waiting for activation" state. Figure 5 MDM Client information message MDM Client activation PIN The user would have received an activation Personal Identification Number (PIN number) from the system administrator. The activation PIN could typically be as simple as "1234". The activation PIN confirms the identity of the MDM client to the MDM server. The user must enter the provided activation PIN into the MDM Client. Figure 6 Inserting the Activation PIN. When the activation PIN is entered, click OK. The MDM Client will now connect with the MDM Server, connecting through the predetermined access point that was designated in the encrypted portion of the original SMS message. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 12 / 48 ^Home

13 2.2.2 MDM Client activation; selecting access point The system administrator may include a reference to an installed access point on the user's device. If the activation message does not include access point information, then the MDM Client will prompt the user to select a destination(s) or access point(s) that will be used by the MDM Client to connect to the MDM Server. Figure 7 Selection of Access points presented to user. In the selection list, destinations are listed on the top, and individual access points are listed after them. It is recommended to use the Internet destination. After confirmation of the access point the MDM Client tries to establish a connection, using the selected access point, with the MDM Server. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 13 / 48 ^Home

14 3 MDM Client console This section describes the structure and options available to the user of the MDM Client. This section is illustrated with current screen shots to aid in the user's navigation of the MDM Client. This chapter consists of the following sub-chapters: 3.1 Accessing the MDM Client. 3.2 The MDM Client's menu structure. 3.3 Application management. 3.4 Backup settings. 3.5 Connection settings. 3.6 Advanced settings. 3.7 User settings. 3.1 Accessing the MDM Client To access the 7P MDM Client, the user must navigate to: Start Applications Installed Applications 7P MDM Client, and select the MDM Client icon. Figure 8 MDM Client Applications screen. When the MDM client application is opened, (by navigating through to application list), the MDM Client notification screen is displayed. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 14 / 48 ^Home

15 The MDM client notification screen indicates the current status of the MDM Client service. It also informs the user when the MDM client last connected with the MDM server (last connection), the calculated time that the MDM client will try to connect with the MDM server (next connection times), and the time that the last successful backup (if executed) was performed. Figure 9 MDM Client notification screen. The user exits the MDM client application by selecting "Exit" button, which returns the user to the devices application screen. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 15 / 48 ^Home

16 3.2 MDM Client s menu structure Main menu Submenu Description Message(s) Device settings App. management AppStorage Mandatory apps Apps to be uninstalled Apps to be stopped Memory status Shows message sent to the MDM client from the MDM server. If no messages exist, then the menu is hidden. Enforces Bluetooth policy. If no policy exists or there is no policy violation then the menu is hidden. Opens browser to server defined location (normally ). If no link is defined then menu is hidden. Shows mandatory applications that should be installed and/or running. If no application is defined then menu is hidden Shows blacklisted applications that will be uninstalled. Shows blacklisted applications to be stopped. If no application is defined then menu is hidden. Shows the available memory for application. Backup Backup status Shows backup status. Connection Connect to server Forces a connection with MDM Server. Activate Set interval Select access point Activates the MDM Client with the MDM Server settings. Sets the connection interval for the MDM Client connection attempts to the MDM server. Selects which access points the MDM client will use when connecting. Advanced Set TARM trust A deprecated setting, maintained for consistency. Allows the setting of TARM Trust (needed for configuring Autolock via OMA DM). If it is set then menu is hidden. The setting of TARM Trust is now supported by the MDM server. Restart MDM Client Stop MDM Client File transfer log Activity details Restarts the MDM Client. Stops the MDM Client. Also all MDM background processes are killed. Shows the file transfer log. Shows the connection attempts and any errors that have occurred. User settings Privacy settings Privacy settings for sending GPS location and user data. Can be accessed by specifying MDM security code. Change security code Shortcut key in use Allows the user to change MDM security code. If checked then MDM Client will connect to the server when user presses and holds Home key for more than 5 sec. About Shows MDM client version (Currently 4.0.2). Table 2 MDM Client menu structure. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 16 / 48 ^Home

17 3.3 Application Management Application management refers to an internet location, specified by the system administrator that could contain custom built applications AppStorage (Application storage) Go to Options -> App. management > AppStorage. Figure 10 MDM Client: AppStorage An internet browser opens to the MDM server provided link, which usually is Figure 11 Example of a local App Store. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 17 / 48 ^Home

18 3.3.2 Mandatory applications Go to Options -> App. management -> Mandatory apps. Displays the mandatory applications that should be installed and/or running on the user's device. If no applications are defined then the menu is hidden Apps (Applications) to be uninstalled Go to Options -> App. management -> Apps to be uninstalled. Displays blacklisted applications to be uninstalled. If no applications are found, the following message will be displayed. Figure 12 Applications to be uninstalled. Press OK button to return to the MDM Client main screen Applications to be stopped Go to Options -> App. management -> Apps to be stopped. Displays all blacklisted applications that will be stopped. If no applications are defined, then this menu is hidden. A black listed application is defined by the system administrator. The MDM Client is updated of blacklisted applications through a policy rule generated by the MDM Server. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 18 / 48 ^Home

19 3.3.5 Memory status Go to Options -> App. management ->Memory status. Figure 13 Memory status. The memory status displays the amount of memory available for applications. RAM RAM memory available for applications data. Flash Internal phone memory available for applications data (C: drive). Mass Internal mass memory. Card Free space that is available on external flash card. If no card is present then 0/0 is displayed. Press "Done" to return to MDM Client main screen. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 19 / 48 ^Home

20 3.4 Backup settings The Backup settings allow the user to select which elements of their personal information will be backed up to the MDM Server Backup status Go to Options -> Backup -> Backup status. Through the Backup status, the user can see the details of the last backup session performed on the device. Figure 14 Backup status. Once the "Backup status" button has been selected, the backup status page is displayed on the user's device. The user can select from the following: Contacts Calendar Notes Bookmark SIM contacts SMS folders If a successful backup was executed, then a timestamp and number of items (in brackets) will be shown. If a backup was not executed, then no timestamp or number of items will be displayed. Press "Done" to return to MDM Client main screen. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 20 / 48 ^Home

21 3.5 Connection settings The connection settings sections contains commands and instructions that can be used to alter the frequency and access point the MDM Client uses to connect to the MDM Server Connect to server Go to Options -> Connection -> Connect to server. The "connect to server" forces the MDM Client to connect with the MDM server. Figure 15 Connect to server. A notification that the MDM client will attempt to connect to the MDM server is displayed Activate the MDM Client Activate is the process which allows the MDM client to successfully connect, authenticate and communicate with a designated MDM server. If this is the first activation on the device, then the MDM Client will show the Access point screen, allowing the user to select an appropriate access point(s) (see Select access point settings). If the MDM server address is modified and the connection to the new server fails, then the MDM client will default to the previously known MDM server address. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 21 / 48 ^Home

22 Go to Options -> Connection -> Activate. All MDM servers have a unique URL and password. The URL informs the MDM client where to connect to the MDM server, and the password, which when entered into the MDM client is presented to the MDM server for authentication. Figure 16 MDM Client activation. Once these parameters are inserted, click the OK button. The MDM server can hide this menu item to prohibit users modifying the connection settings Set interval settings Allows the MDM client connection interval to be defined. Go to Options -> Connection -> Set interval. Figure 17 Set connection interval. The set interval screen will appear. This screen is used to specify the timed interval that the MDM Client will use when attempting to connect to the MDM Server. The user can select either a predefined interval ranging from 5 minutes to 1 day, or use the MDM server defined interval which is specified by the MDM Server. By default, the "Defined by server" interval is set. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 22 / 48 ^Home

23 Figure 18 Connection interval values. The MDM server can hide this menu item to prohibit users from modifying the connection settings. Click OK button to force connection with MDM Server Select access point settings Go to Options -> Connection -> Select access point. Figure 19 Connection select access point. The select access point screen will appear. This screen is used to select the access points and define their order of priority. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 23 / 48 ^Home

24 Symbian S60 devices and above will allow the configuration of three access points per MDM client. Figure 20 Three access points. The access points should be considered as: Access Point 1 Home WLAN Access Point 2 Work WLAN Access Point 3 GSM ( with active data SIM card) When the MDM Client initially attempts a connection with the MDM Server it will select Access point 1. If the connection fails, then the next access point, Access point 2, is used; this action is repeated until a connection is established. Press Select button to select the access point for example Access point 2. Figure 21 Select access point 2 Select the access point or destination. In the list provided, destinations are grouped first, and individual access points follow after them. It is recommended to use the destination as this allows phone to automatically try to establish internet connection using all the access points that this destination contains. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 24 / 48 ^Home

25 Figure 22 Access point 2 configured. Press the OK button to return to MDM Client main screen. If a connection has been attempted on all access points without success, an error is reported on the notification screen of the MDM Client and the connection will be retried at a later random time. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 25 / 48 ^Home

26 3.6 Advanced features The Advanced features contain controlling elements of the MDM Client. If allowed by the MDM Server, the user can for example stop, start and restart the MDM Client Set TARM Trust Go to Options -> Advanced -> Set TARM Trust. The 7P MDM Nokia client application, FrOMA, must be installed on the device before attempting to set the TARM Trust. After selecting the menu item, the user is shown an informative text, warning them that the process might be time consuming and that the code that they must enter when prompted is This command can be achieved by using the MDM server command function and is only listed for continuity. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 26 / 48 ^Home

27 3.6.2 Restart MDM Client Go to Options -> Advanced -> Restart MDM Client. The Restart MDM Client restarts the MDM Client. Figure 23 Restart the MDM client. An information screen indicating that the MDM client was restarted successfully is displayed. It may take some time before the MDM application is fully up and running. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 27 / 48 ^Home

28 3.6.3 Stop MDM Client Go to Options -> Advanced -> Stop MDM Client. Figure 24 Stop MDM client. The Stop MDM Client "terminates the operation of the MDM Client and all of its processes. Press the "Yes" button to stop MDM Client. Figure 25 Service not active. The Service is not active message will appear. The MDM server can hide this menu item to prohibit users modifying the connection settings. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 28 / 48 ^Home

29 3.6.4 File transfer log Go to Options -> Advanced -> File transfer log. Figure 26 File transfer log details. When the MDM server sends commands to transfer file(s) to/from the device, additional setting Log on client can be set. The user can then see in the file transfer log the list of files that have been transferred Activity details Go to Options -> Advanced -> Activity details. The Activity details "screen shows the connection attempts and any errors that have occurred. Figure 27 Activity detail notifications. The Activity details screen displays time stamped information messages regarding the connection and communication of the MDM client to the MDM server. Typically, any message emanating from the MDM client is BLUE in colour. When the MDM server acknowledges receipt and replies to the message, then the original blue coloured message will turn BLACK, indicating a successful handshake. All error messages are coloured RED. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 29 / 48 ^Home

30 3.7 User settings The user settings contain elements of sensitive information that can either be sent, or not, to the MDM Server. The MDM Client allows the user of the device to control whether this sensitive information is sent to the MDM Server, or not Privacy settings Go to Options -> User settings -> Privacy settings. Figure 28 Privacy settings. Privacy settings allow the user to restrict the MDM client from sending user sensitive data to the MDM Server. Access to the privacy functions menu is password protected. Figure 29 Insert valid security code. The user has to enter a valid MDM security code (default MDM security code is 12345) to unlock this functionality. Select which information is allowed (or disallowed) to be sent to the MDM server. Press "Done" button to return to MDM Client main screen. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 30 / 48 ^Home

31 3.7.2 GPS info GPS information allows the sending of device location information to the MDM server from the devices built-in GPS hardware. If no GPS device is present, no information will be sent. The GPS information can only be sent to the MDM server if the following conditions are met: The device is capable of receiving GPS data information. The device user has allowed (enabled) the transmission of GPS data. MDM server has requested GPS information from the MDM client. The MDM Client will always try to use assisted technology, then network technology for GPS data gathering. Figure 30 Enable GPS information. If the user, or server set interval, is bigger than 1 minute, then the GPS service is powered off between readings Network info Enables the transmission of network, cell ID, country code, and operator code to the MDM server. Figure 31 Enable network information. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 31 / 48 ^Home

32 3.7.4 Call info Enables the transmission of call ID information either with or without the dialled number to the MDM server. Figure 32 Enable call information MDM security code Allows the transmission of the MDM Client security code to the MDM server. The possible choices are: Figure 33 Enable security code data. Allow sending of the MDM Client security code to the MDM Server. Disallow sending of the MDM Client security code to the MDM Server. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 32 / 48 ^Home

33 3.7.6 SMS information When set, allows the transmission of SMS information to the MDM server. Figure 34 SMS information detail Debug logging Enables or disables the MDM Client s ability to enter "debug logging" mode. This is required when troubleshooting potential problems. Figure 35 Enable debug mode. The possible choices are: Allow sending of the MDM Client security code to the MDM Server. Disallow sending of the MDM Client security code to the MDM Server. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 33 / 48 ^Home

34 3.7.8 Change security code Go to Options -> User settings -> Change security code. This menu item allows the user to change the MDM security code. Figure 36 Change security code. The user has to enter a new security code. A valid MDM security code is a 5 digit numerical value. Figure 37 New security code. Once the value is entered, the MDM Client prompts to verify that the new MDM security code values match: 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 34 / 48 ^Home

35 Figure 38 Verify new security code. If the code entry is verified, the new MDM security code is set. If the default security code is still in use then the user is prompted to change it every time the MDM Client is opened. If the original security code is not then the user must enter the old security code first before changing it Shortcut key in use Go to Options -> User settings -> Shortcut key in use. If checked then the MDM Client will connect to the server when the user presses and holds the Home key for more than 5 sec. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 35 / 48 ^Home

36 About the MDM Client Go to Options -> About. Selecting the "About" option displays the current MDM Client version. Figure 39 Current version number. Press the OK button to return to MDM Client main screen Exit the MDM Client Go to Options -> Exit or press Exit button at MDM Client main screen. "Cancel" closes the MDM Client s user interface. Its background processes, however, will still continue to work and send information to the MDM server. For a complete shutdown of the MDM client the user must use Stop MDM Client menu command (see Stop MDM Client). Figure 40 Exit the MDM Client. When "Cancel" is selected, the user will see that the main MDM client notification screen is displayed. If the user then selects "Exit" the MDM client UI will close, although the MDM client will still report into and receive commands from the MDM server. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 36 / 48 ^Home

37 4 Remove (uninstall) the MDM Client This section illustrates the removal process of the MDM Client. 4.1 Manual uninstall of the MDM Client Uninstalling MDM Client Symbian application Navigate to Menu -> Settings on your mobile device. Figure 41 Settings icon. From Settings Select Application manager. Figure 42 Application manager icon. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 37 / 48 ^Home

38 Once the Application manager has been selected. Select Installed apps. Figure 43 Installed applications icon. Figure 44 MDM Client application list. Find the MDM Client application in the list and continue pressing until the uninstall option appears. Press Uninstall to uninstall application. (You can also uninstall MDM Installer 0x200033BE this is a separate part of the MDM Client.) The MDM server can prohibit users from removing the MDM client. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 38 / 48 ^Home

39 Figure 45 MDM client uninstall. Either "arrow down", or select the "MDM Client". From the Options button, select Uninstall. Figure 46 MDM client uninstall confirmation. A message the MDM client and associated content will be removed from phone. Continue? will appear. Click Yes button to continue removal process. Figure 47 MDM client uninstall warning. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 39 / 48 ^Home

40 The message Unable to uninstall application. Other applications must be closed first. Close now? can appear. Click OK button to close, all needed applications will close automatically. Figure 48 MDM client removal indication. The uninstall progress will begin. A progress indicator will be displayed. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 40 / 48 ^Home

41 5 Example - Application Management Blacklist Description To demonstrate the 7P MDM servers ability to display an information message on the users Symbian device, that an application they have attempted to run is Blacklisted. Create the device message (Symbian only) Add a Symbian application to the MDM server Deploy and install an application to the device Verify that the application is installed on the Symbian device Add the application title to the a MDM server "Blacklist" Instruct the Symbian device of the Blacklist Verify Blacklist is operational The 7P MDM Symbian S60 Client must be installed and activated on the target device. 5.1 Create the device message (Symbian only) Navigate to Settings > Messages > MDM Client > Disable application prompt. Figure 49 Symbian message Insert a suitable informative message that you would like the user to see when they attempt to run a Blacklisted application e.g. "Running this application is not allowed!" Select the "Save" button to commit any changes made to the MDM server, or the "Cancel" button to discard any changes. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 41 / 48 ^Home

42 5.2 Add a Symbian application to the MDM server Navigate to Infrastructure > Applications The "Applications" panel will display previously loaded and available applications by their friendly name. Each resident application may be edited by selecting the friendly name of the application. Selecting the friendly name of an application will reveal the application details. To add a new application to the DMM server, select the "Add" button. You will be asked to insert a friendly name of the new application. When a name has been inserted into the box provided, select the "OK" button. A blank application "Details" will be displayed. For the Symbian application: 1. Select the Symbian filed in the "Package" sub heading and select the "Choose File" button. 2. A file explorer will be opened allowing you to select the location, and name of the application to be installed. Once selected, and "saved", the application will be uploaded into the MDM server. 3. Insert the additional details, for example Version, and select the "Save" button. 4. The application is now available for deployment by any operator of the MDM server. The Symbian S60 application must be loaded into a local file location which can be selected by the MDM server. Download the file FromVNC.sisx ( available from ) onto your local computer. Figure 50 Add a Symbian application Complete the file installation by pressing the green "Save" button. An information pop up will appear informing that the file will be uploaded to the MDM server. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 42 / 48 ^Home

43 5.3 Deploy and install an application to the device Navigate to Users & devices> Select a User > Select a device > Actions > Install application 1. Select the user and users Symbian device that you wish to install the application. 2. Once selected, the device details panel will open 3. Select the "Actions" tab from the device details panel. 4. In the "Action" selection, use the pull down menu to indicate "Install application"; a secondary pull down will appear, from this select the application to install onto the selected device. Figure 51 Install an application on Symbian device 5. Once satisfied that the correct device, the correct Action, and the correct application has been selected, press the "Send" button. The application will be installed onto the device when the device next connects. Only Symbian S60 applications will be shown in the "install applications" pull down when a Symbian device is selected. If the expected application is not visible, check in Infrastructure > Applications ensuring that the application is visible and saved. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 43 / 48 ^Home

44 5.4 Verify that the application is installed on the Symbian device Navigate to Users & devices> Select a User > Select a device > Installations > Apps Figure 52 Check application installed on device 1. Select the user and users Symbian device that you wish to install the application. 2. Once selected, the device details panel will open 3. Select the "Installations" tab from the device details panel, then the "Apps" tab 4. In the applications list, inspect the applications for the deployed application, in this case FromVNC 5. When the application details appear on the application list the application is installed on the device. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 44 / 48 ^Home

45 5.5 Add the application title to the a MDM server "Blacklist" Navigate to Infrastructure> Configurations A list of all previously defined configuration templates will appear in the "Configurations" window panel. Create a new "Application list" configuration by selecting the "Add" button. A "configuration type" pop up will appear. Highlight the "Configuration type > Application list" pop up and insert a memorable name in the field provided, for example SymbianBlacklist Figure 53 Create an application blacklist 1. In the configuration "general" panel, select "blacklist" and "manual" 2. (When the "Manual" list creation mode is selected, further options, such as "Search (Apple)", "Search (Android)" and "Add application" will become available. 3. Select the "Add application" button in the "Application list" section At this point you are allowed to input the selected details of each application that you would like to appear (and be acted upon) in the blacklist. 4. Add the "Name" of the application as seen on the device application details, "identifier" which is unique to the application and the "Platform" to which the application is written for. 5. Multiple application details may be added to this list by selecting the "Add application" button. 6. Once all application detail shave been entered, select the "Save" button to preserve the configuration template. The application list may be added to, by selecting the "Edit" button, "Add application" then "Save". The application list may also be reduced, selecting the "Edit" button, the remove button located adjacent to each application entry, denoted by a "X", then "Save". Once completed, the configuration "SymbianBlacklist" is ready to be deployed to an individual or group of Symbian devices. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 45 / 48 ^Home

46 5.6 Configure the Symbian device with the Blacklist (policy) Navigate to Operations > Operations A list of all previously defined operation templates will appear in the "Operations" window panel. To create a new "Operation" configuration - select the "Add" button. Insert a friendly name of the new Operation into the field provided. When a name has been inserted, select the "OK" button. A blank Operation "Conditions and Actions" template will become available. The "operation" requires three control elements which are determined by the administrator. Figure 54 Deploy blacklist operation to device Always Frequency (of Operation) Adjacent to the friendly name is a pull down menu which allows the administrator to select various "Frequency of Operation" ranging from "Off" to "Scheduled". It is essential that "On every connection" is selected to ensure that the MDM server prevents any blacklisted application from running. With operational blacklists, the Symbian device will inform the MDM server of any application wishing to start. The MDM server then compares the application information with the application information on the blacklist. If the application appears on the blacklist, the application will be blocked from starting on the user's device, and the message created in Create the device message (Symbian only) will be displayed on the user's device Conditions (of Operation) In the "Conditions" drop down, select the following: "Manufacturer is" then select "Symbian" from the available choices, then select "Add" Repeat the selection process from the drop down provided by selecting "Application from blacklist installed" then from the second drop down select the previously configured "SymbianBlacklist", then select "Add." The statement will now appear in the top "Conditions" window. The "Condition" may be removed by selecting the adjacent remove button (big red "X"). 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 46 / 48 ^Home

47 5.6.3 Actions (to be performed when conditions met) In the "Actions" drop down select the following: "Disable application" followed by selecting the check box "Include all applications that are matching the conditions"", then select "Add." The statement will now appear in the top "Actions" window. When the Operation logic is complete, select the "Save" button to commit the operation to the MDM Server. The "Action" may be removed by selecting the adjacent remove button (big red "X"). 5.7 Verify Blacklist is operational On the Symbian device, navigate to the installation files. Locate and run the downloaded Symbian application, or if the application has installed then select the application icon. Once selected, the application will commence execution. Figure 55 Run application - expected results The execution will be terminated by the MDM Client, and an informative message (previously defined) will be displayed to the user. 7PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 47 / 48 ^Home

48 List of changes Version Date Changes Reason Author Version release 1.07 Tony Dargis Corrections #5590 Tony Dargis Added additional steps #5590 Tony Dargis Added front matter Tony Dargis Document updated Tony Dargis Author: Tony Dargis Version: English 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 SEVEN PRINCIPLES, Erna-Scheffler-Straße 1a, Köln. 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 SEVEN PRINCIPLES, Erna-Scheffler-Straße 1a, Köln reproduziert oder unter Verwendung elektronischer Systeme verarbeitet, vervielfältigt oder verbreitet werden. Die Firma SEVEN PRINCIPLES behält sich vor, ohne vorherige Ankündigung den Inhalt dieses Dokuments teilweise oder vollständig zu ändern. COPYRIGHT SEVEN PRINCIPLES PMDM_Client_SymbianS60_v5.07.0x_EN_1.4.docx Page 48 / 48 ^Home