Provisioning is the process of installing software and settings onto the device and getting it working. mSuite includes an over the air provisioning portal that allows a supported wireless device to make a connection and automatically load a customized software build for the connecting user. You can also provision devices by using memory cards, or creating install packages and manually loading these onto the device.
Note: This section only applies to devices that require mSuite client software e.g. Windows Mobile 5 & 6.x, Symbian S60-3*. It does not apply to devices supported by the Exchange ActiveSync (EAS) process (e.g. iPhone/iPod, Palm Pre, Android) since these devices use their built-in EAS client and do not require mSuite client software.
* The mSuite client for Symbian devices is now discontinued. Instead, Symbian devices should use Nokia's 'Mail for Exchange' client which provides similar functionality and is fully supported in mSuite 5.15 and higher as an Exchange ActiveSync (EAS) device.
Over the Air provisioning
How does the Provisioning Portal work?
A standard 'Bootloader' program is downloaded to the device. The Bootloader executes and requests (or was pre-configured with) information about the name or location of your mSuite server. It connects to the mSuite server and prompts the user to logon. If the user authenticates successfully, a software package is downloaded to the user's device. If mSuite client software is already installed, it is removed before the new package is installed.
Administrator initiated method (using SMS text message)
|1.||The administrator sends the user a structured SMS (text) message. This messages contains the URL of the 'Bootloader' download site plus the configuration information needed by the 'Bootloader' to identify and connect to your mSuite server. The recommended text of the message can be found in the mSuite administration console by right clicking on the database name (immediately below 'mSuite Administration Console') then using All Tasks > Generate Provisioning Portal SMS Message. Alternatively, if the user already exists in the mSuite database, expand Administration > User and Groups, right click on Device Users then All Tasks > Generate Provisioning Portal SMS Message then click Next then select the user and click Next again.|
|2.||The user receives the SMS message on their mobile device then clicks the URL in the SMS message which take them to a website where they can download the standard Bootloader program for their device type.|
|3.||The Bootloader runs, connects to the mSuite server and prompts the user to log on.|
|4.||If the user authenticates successfully, all applications deployed to that user are downloaded to their device and installed.|
User initiated method
|1.||The administrator tells the user the 'alias' (if using the CSC) or the hostname/IP address and port of the mSuite server (if using a Local or DMZ Proxy).|
|2.||Using the device's web browser, the user goes to a website where they can select, download a standard 'Bootloader' program. This is available from get.commontime.com or can be hosted on a website of your choosing.|
|3.||The Bootloader runs and the user is prompted to enter the configuration information (as provided by the administrator).|
|4.||The Bootloader connects to the mSuite server and prompts the user to log on.|
|5.||If the user authenticates successfully, all applications deployed to that user are downloaded to their device and installed.|
Migration method (moving from mSuite 4 to mSuite) (applies to Windows Mobile devices only)
|1.||The administrator downloads the Migration application packages (which are based on the Bootloader program) from http://downloads.commontime.com/Migration/MigrationPackage.zip and imports them into the mSuite 4 database using the mSuite 4 administration console. Information about how to import these packages into the mSuite 4 database is included in the zip file.|
|2.||Optionally, the administrator then edits the Bootloader application packages and enters the data for the registry value(s) Alias (if using the CSC) or Host and Port (if using a Local or DMZ Proxy) in HKCU\Software\CommonTime\Cadenza\Provisioning|
IMPORTANT: CSC users must only enter the value for Alias. DMZ or Local Proxy users must only enter the values for Host & Port.
|3.||The administrator deploys the Bootloader application package to the mobile device users.|
|4.||Next time a device management session occurs, the Bootloader application package is downloaded to the device and installed.|
|5.||The Bootloader program automatically executes, connects to the mSuite server and prompts the user to log on.|
|6.||If the user authenticates successfully, all applications deployed to that user (in the mSuite system) are downloaded to their device, the existing version of mSuite is removed and the new version is installed.|
Provisioning via a Local or DMZ proxy
If you are using a Local or DMZ proxy, there is an inbound TCP port configured for the Proxy to listen for incoming connections from devices. If the device's Bootloader program makes a connection to this port, it will be redirected to the Provisioning Portal service.
Provisioning by communicating directly with the CSC
Provisioning when using the CommonTime Switching Center is a similar process. However, in this case, your system is connected to the shared CommonTime Switching Center. This needs to know how to connect the device to your Provisioning Portal. It can determine this from your 'alias' - this was provided to you with your license key and is usually a simple email address.
If you are using the CSC and do not know your 'alias', open the mSuite admin console, right click on the database name (immediately below "mSuite Administration Console") then use All Tasks > Generate Provisioning Portal SMS Message The Alias appears after 'Alias': and before 'cdzprov'
During the process, the user has to authenticate using their credentials. If they cannot do this, the software will not be loaded to the device.
Once authenticated, mSuite recognizes the device type and the user and builds a custom software package and sends it to the device. This package includes all the mSuite software, the policies and any other applications that have been configured for the user.
The following procedure explains how to create a self-extracting package for manual provisioning via a memory card or Web download.
If you are initially provisioning your handheld device, perhaps via a flash memory card or via the Internet, your applications should be built as self-extracting packages. The packages are compressed during creation typically reducing their size by between 50% and 66% for more efficient transfer to the device.
To create a self-extracting package containing all applications and files applied to a user or group of users, do the following:
|1.||In the mSuite Administration Console, under Users and Groups, right-click the name of a user or a group of users.|
|2.||From the pop-up menu select All Tasks > Deployment > Generate Device Package.|
|3.||On the Welcome page, click Next.|
|4.||Click the Browse... button to the right of the Creation path box.|
|5.||Browse to the folder where you would like to save the package and click Open.|
|6.||If necessary, in the File name field, rename the package to be produced.|
|7.||In the Device profile box, select the device type which you would like to create a package for. You should only select one device profile. Click Next.|
|8.||If you selected a Windows Mobile device, the Device Package Options dialog will be displayed. Do the following:|
|9.||If you wish to allow the package to be re-installed automatically after the device is hard-reset, check Install Once; otherwise leave it clear.|
|10.||To delete the package after installation on the device, check Auto-delete; otherwise uncheck it.|
|11.||Click OK. The package will be created at the specified location.|
Each package has two components - a self extracting installer (either .exe or .sisx) and the 'payload' file (.bin).
As part of a provisioning process, the next step is to transfer both parts the self-extracting package to a device, flash memory card, or Internet download page. The executable (.exe or .sisx) and the data file (.bin) must be kept together in the same directory. While you can rename the files, you must ensure that both files have the same name and retain their original file extensions.
After transferring the files to the device, launch the executable.