Product Documentation

Creating Symbian Configuration Profiles

Oct 20, 2015

Symbian devices configuration in Device Manager is done by sending OMA Device Management commands to the devices. The list of supported commands can be found from the Nokia Developer web site. A search for the "OMA Device Management" keywords in the document section of web site will return a number a documents describing Device Description File (DDF) for features that can be controlled using OMA-DM.

OMA DM will allow control of Symbian devices by:

  • Defining Wi-Fi or GPRS Access Points.
  • Defining Mail for Exchange parameters.
  • Encrypting device and/or SD cards.
  • Customizing devices.
  • Configuring VoIP parameters.

That list is not an exhaustive list of what can be configured on Symbian devices and the features may depend on the device model. For instance, device encryption was supported on S60 3.2 devices only on the E-Series devices.

Device Manager supports <Alert>, <Add>, <Replace> and <Exec> OMA-DM commands.

The following example will display the message "Management in progress..." on the user device during 30 seconds.

<Alert> 
  <CmdID>_cmdid_</CmdID> 
  <Data>1100</Data> 
  <Item> 
    <Data>MINDT=30</Data> 
  </Item> 
  <Item> 
    <Data>Management in progress...</Data> 
  </Item> 
</Alert>

The structure of an OMA-DM command must always contain a command ID. In this case, the command ID is interpreted on the fly. It is then replaced by the placeholder "_cmdid_". The following example will configure the Mail for Exchange client.

<Replace> <CmdID>_cmdid_</CmdID> <Item> 
<Target><LocURI>./MailForExchange/Server</LocURI></Target> 
<Data>webmail.mycompany.com</Data> </Item> 
<Item> 
<Target><LocURI>./MailForExchange/UseDefaultPort</LocURI></Target> 
<Data>True</Data> </Item> <Item> 
<Target><LocURI>./MailForExchange/UseSSL</LocURI></Target> 
<Data>True</Data> </Item> <Item> 
<Target><LocURI>./MailForExchange/ToNapID</LocURI></Target> 
<Data>BearerManagementSNAP/SNAP4097</Data> 
</Item> <Item> 
<Target><LocURI>./MailForExchange/Roaming</LocURI></Target> 
<Data>2</Data> </Item> <Item> 
<Target><LocURI>./MailForExchange/UserName</LocURI></Target> 
<Data>$user.samaccountname</Data> </Item> 
<Item> 
<Target><LocURI>./MailForExchange/Domain</LocURI></Target> 
<Data>$user.domainname</Data> </Item> 
<Item> 
<Target><LocURI>./MailForExchange/Email/Addr</LocURI></Target> 
<Data>$user.mail</Data> </Item> <Item> 
<Target><LocURI>./MailForExchange/Schedule/OffPeakSchedule</LocURI></Target> 
<Data>1</Data> </Item> </Replace> 

Note that this is an example; you can configure many more options in the Mail for Exchange client. The example shows that several commands can be chained in the same command block. User attributes can be used by using $user.attributename macro. Those macros will be replaced on the fly by the actual user data.

Special configurations can be created to enforce configuration on Symbian devices. Those configurations will have the following format.

<Exec> <CmdID>_cmdid_</CmdID> <Item> 
<Target> <LocURI>am_policy</LocURI> 
</Target> </Item> </Exec> 

The <LocURI> parameter can be set with the following values:

  • am_policy / am_policy_del: This will set or remove the application management policy enforcement to control application installation and removal.
  • ap_policy / ap_policy_del: This will set or remove the Access Points policy management enforcement.
  • custo_policy / custo_policy_del: This will set or remove the device customization policy management enforcement.
  • ds_policy / ds_policy_del: This will set or remove the Data Synchronization policy management enforcement.
  • email_policy / email_policy_del: This will set or remove the Email policy management enforcement.
  • im_policy / im_policy_del: This will set or remove the Instant Messaging policy management enforcement.
  • wlan_policy / wlan_policy_del: This will set or remove the WLAN Access Points policy management enforcement.

To create a new Symbian configuration profile, on the Policies tab, click New configuration in the Configurations section of Symbian.

To use the schedule wizard to configure connections for Symbian devices

  1. On the Policies tab, click Configurations and then on the New Configuration menu, click Scheduling.
  2. In the Scheduling dialog box in Device Manager, enter a name for the configuration and optionally, a description.
  3. In Scheduling configuration parameters, select the following options:

    • Do not define connection policy. The device will not reconnect unless the user clicks Connection in Device Manager.
    • Keep connection permanently live. If the connection is permanent, Device Manager on the mobile device will attempt to reconnect automatically to the server running Device Manager after a network connection loss and will monitor the connection by transmitting control packets at regular intervals. This configuration is not recommended because it consumes more battery charge and generates more network traffic.
    • Define a permanent and/or occasional connection schedule within a given time range. Keep the connection live during the following time range:

      • Define a period in which the device will stay connected to the server. Device Manager on the device will attempt to reconnect to the server running Device Manager after a network connection loss and will monitor the connection by transmitting control packets at regular intervals.
      • Force one connection during the time range below. The connection will automatically shut down once updates have taken effect. This option forces a scheduled, one-time connection to the server, in particular to check for availability of new deployments. To avoid a connection peak at the beginning of the selected range, the relevant devices will connect randomly during the defined range. Device Manager on the device will only reconnect after a network connection loss if an operation was in progress. The server running Device Manager will likewise terminate the connection after an inactive period.
        Note: Both of the preceding options include an option to see the schedule to the local device clock or to UTC time.