Device QuickTasks
These look obsolete, as there's no such drop-down list anymore, but maybe there's something to rescue.
Quick Tasks
Some tasks must be executed by using the device quicktask dropdown list, which can be located at the toolbar in the inventory section.
To launch quicktask for device(s), you must first select target device(s), and then select quicktask from the list.
After selection press the Execute button to confirm quicktask process.
Device quicktask-menu marked with red rectangle.
Most of the quicktasks contain possibility to add operations to queue without launching the device management session.
This way it's possible to collect operations to wait for the next notification (which launched device management session)
and process all those operations at the same time.
There's a special case when following device security operations are executed: Lock device, Unlock device and Wipe device.
They will be added in front of the device management queue and therefore processed immediately when next session is initialized.
Note:
When processing quicktasks for multiple devices at the same time, you should be aware that all selected devices might not contain support for every tasks.
Therefore when multiple devices are selected, some quicktasks might not be available.
Quicktask: Application management
Application management -quicktask provides the way to install applications in the device.
Application management section view
Application management dialog contains a table of applications that are compatible with currently selected device(s).
Remember that device compatibility must be added in the application management described in the chapter Applications → Edit application compatibility.
Application table contains four columns:
Log column
Used to open application related log dialog, which can be used to check application related history events.
If there is exclamation ( ! ) -mark with blue background next to Log-link,
it highlights that history contains log-entries which can be viewed.
Application column
This contains the application name and version.
Description
This is description of the application.
URL
Download URL, which will be used when application installation is executed.
Notice that some applications may use short-URL (shorter version of URL) when using SMS-installation.
Additional options:
Skip if preinstalled on device
When this option is enabled, application table will not show applications that are marked as pre-installed on the device.
For example many Nokia devices may have Mail for Exchange -application pre-installed, and therefore it might not be necessary to install it twice.
Don't install immediately, only add to task queue
If you want to add task to queue list without sending a notification (session initializing) command to device, this must be enabled.
Application will then be installed during the next device management session. Note that this operation does not work with Send install SMS.
Buttons:
Send Install SMS
It sends SMS-message containing the selected application download link to the device(s).
Install (normal)
Install selected application via OMA DM connection and activate application immediately.
Install (hidden)
Install selected application via OMA DM connection and leave application inactive.
Reveal (hidden)
Activate inactive application via OMA DM -connection.
Uninstall
Uninstall application that has been previously installed via OMA DM connection.
Uses OMA DM connection to process uninstall operation.
Does not work with SMS-installed applications.
Quicktask: Send initial settings to device (With instructions)
This is the master mobile device provisioning task. It senses the capabilities of the device to be provisioned.
This task sends out a couple of text messages to the device.
First there are one or two pre-provisioning informational text messages.
Next step has no less than three different choices. The following table covers the choices.
Device native capability | Action taken |
[1] Full OMA DM capability example: any late Symbian OS device | OMA DM settings and security policies are sent, OMA DS (SyncML) settings are sent, device inventory taken |
[2] Full OMA DS capability, no OMA DM example: Nokia Series 40 devices | OMA DS (SyncML) settings are sent |
[3] No OMA DM, nor OMA DS example: Windows Mobile, many Java ME devices | Informational text message is sent, which has a URL link to the internet web page with more detailed service setup instructions |
Default code for opening the settings message is 1234.
Third step is one or more post-provisioning text messages with additional information.
Last step is a text message with user private service settings. These settings are required if the user wants to sync PIM data with Mozilla Thunderbird, Microsoft Outlook, or similar program.
The settings are also required for logging in to service Web UI.
Reminder which pops up when sending settings to WSDM-devices
When sending initial settings to WSDM devices, you should first install client application on the device by using the Install client button.
WSDM Client is a special application type that needs special parameters in application management section.
To see how to add WSDM client into application database see chapter Devices → Applications → Managing Applications → Special application type: WSDM client.
After client has been installed, settings can be send to device. Note that there are currently two different ways to send settings to device.
One is to send settings via SMS message which works only on WSDM clients that have support for SMS-management. Windows Phone OS devices or devices without phone connection do not support this feature.
Send installation code must be used instead. Send installation code is used to start the WSDM client on the device. Note that both of these options need user interaction to be accomplished.
Note:
It is recommended not to use this task when doing mass provisioning.
It is much more efficient to use the without instructions version.
Note:
If the device is not allocated to any user, it is impossible to send working settings to case [2] devices.
The settings will be otherwise working, but username and password will be missing.
Note:
This task might not be visible when service using OTAP. Use No instructions version instead.
Quicktask: Send initial settings to device (No instructions)
This task is the quick version of the above full one. It only sends the actual settings to the device.
Please refer to the table above. This task is the preferred mass provisioning task.
Quicktask: Restart device
Restart the device. As with PCs, many times some intermittent problems are fixed just by rebooting the device.
Sometimes this might be a software vendor suggestion after an application installation.
Quicktask: Lock device
All provisioned devices that have advanced security operations integrated can be remotely locked.
It is important to have the correct security code in device’s settings.
Note:
Locking a device will send a random-generated, long lock code to the device to prevent unlocking it from the device itself.
You can then only unlock the device from the service.
Quicktask: Unlock device
All provisioned devices that have advanced security operations can be remotely unlocked.
It is important to have the correct security code in device’s settings.
Note:
Unlocking a locked device will send the lock code that is registered in the portal (default 12345) to the device and then unlocks it.
If you lock the phone by hand, the unlock code you need to open the device is the one registered in the service.
Quicktask: Wipe device to factory settings
All provisioned devices can be remotely wiped and reset to factory default settings.
This operation will remove everything from the phone, so it must be used with caution.
Quicktask: Activate all settings
This task is the “bread and butter” task. It is the most common task to be executed.
Whenever there are device settings which are changed on the Web UI, the settings are activated (sent out to the device) with this task.
Quicktask: Activate some settings
While you can activate all settings at one time with Activate all settings quicktask, this task allows you to decide which settings will be updated.
Activate some settings is used by selecting target settings in the list and launching device update by using the Execute button.
Quicktask: Send free form SMS
Send a freeform SMS to the device. This feature might not be enabled for all organizations.
Send free form SMS message dialog.
To send free form SMS message to the device(s), type text into textarea (notice the 160 character limit) and use the Send -button.
It's also possible to send message as a Flash message.
Quicktask: Send web account info SMS
Task for sending web account credentials (username, password, organization and web ui url) for the user via SMS-message. Notice that this operation will reset current password of the user.
Quicktask: Send sync account info SMS
Task for sending synchronization account credentials for the user via SMS-message. The username in this message is the concatenated version of ‘organization.username’.
This concatenated version is used with SyncML client authentication, including the mobile device and any third party clients.
For Web UI login, the ‘organization’ and ‘username’ has to be typed into separate fields on the browser.
Quicktask: Capture full OMA-DM tree
Capture as full OMA DM tree from the device. This is used for fault management, diagnostic, and software development purposes only.
OMA-DM tree contents can be seen in Inventory status dialog.
After diagnostic settings capture has been successfully completed, it's possible to view the results via Device Editor → Inventory status → Device → Diagnostics.
It's possible to compare results of different diagnostics capture entries by selecting multiple items (diagnostics entries) from the list.
In multi-selection mode it's possible to notice the changes that have been done in the OMA DM -tree between selected captures.
Red tree nodes/leafs
Something has been removed.
Violet tree nodes/leafs
Something has been changed.
Blue tree nodes/leafs
Something has been added.
You can also download the entries by selecting a entry from the list, and clicking the ”Download dmTree-xxxxxx...” button at the top of the right table.
This will download / open (depending on the browser) the whole DM-tree containing all values that have been captured from the device.
Warning:
While device OMA DM tree might contain huge amount of leafs and nodes, this operation might take some time.
Also be noticed that this operation will make lot of data traffic between server and the device.
Quicktask: Fetch device diagnostics information
Get device inventory status (hardware, software, firmware versions, local UI language setting) and record it in service database.
Warning:
If some settings are specified in the device editor, they should be activated before using Fetch device diagnostics information quicktask.
Otherwise changes will be overridden by current settings of the device.
Quicktask: Remove device management & data sync
Performs decommission to device(s). Connects device(s) via device management connection and removes / nullifies all service related settings on device.
Exception is the access point, which cannot be disabled because it's used during the session.
Quicktask: F-Secure Mobile Security
When device has F-Secure Mobile Security application installed, it's possible to do quicktasks that are related to it.
This means that you can control application over device management connection.
F-Secure Mobile Security quicktask dialog
When you enable the selection Only add task to queue, don't execute it right away option, the tasks are not executed immediately.
They are pushed into the DM-queue to wait for the next device management session.
Operations can be used by clicking the related button.
Here are the descriptions for each button:
Start F-Secure Mobile Security
Start the F-Secure Mobile Security anti-virus client service.
It checks for incoming and outgoing data on the background and notifies you if something unwanted is noticed.
Stop F-Secure Mobile Security
Stop the F-Secure Mobile Security anti-virus client service. This task should not be activated unless the client is making the phone unresponsive, or if it interferes with something you need to do.
Stopping the client means that the incoming and outgoing packages are not checked in the background.
Virus database update (F-Secure)
Attempts to update the virus database for the F-Secure Mobile Security. Up-to-date virus database should be checked every day, as new viruses come every now and then and they can be really devastating.
Full virus scan (F-Secure)
Launch a complete virus scan on the device. While this may take some time, it is suggested that a full virus scan is done regularly to make sure there are no viruses on the phone. These viruses may destroy personal or credential data on the device, so they should be dealt with.
Activate F-Secure Mobile Security license
This will try to activate license for the application. Check application management section F-Secure Mobile Security for more details how to define the license for the application.
Note:
On some cases, like in Full virus scan task, F-Secure Mobile Security will be started if not already running.
Track
Sometimes it's useful to track device actions in real-time. Track is an operation that can be used to track device specific actions in real-time.
To start tracking the device(s), first select device(s) to track and then use the Track button or use mouse context menu (right mouse button) On-going activity log.
This will open a new window for tracking.