- About the Registry Collection for Windows Mobile
The Registry collection is used to configure the Windows Mobile or Windows CE registry base of the mobile devices, thus allowing for a single point for device registry management. Device Manager includes a series of step-by-step wizards, allowing for rapid setup and deployment of registry configurations.
In addition to configuring both new and existing registry values, either for the operating system or installed third-party applications, you can manage the Device Manager client configuration options. This allows for multiple client backup settings, and control over network connectivity, and is included with a dedicated wizard.
A set of registry keys can only exist in a configuration. You can create different settings and then deploy them selectively to some or all of the mobile devices in the fleet. You can create a new registry configuration either manually or via the wizard. The configuration wizard includes pre-configured options for the following applications:
Device Manager uses registry keys to store its own data in each mobile device. You can configure these options by using the Device Manager Options wizard.
Device Manager configuration backup. Device Manager client settings can be stored on the removable memory card in the mobile device. If a mobile device has to be hard reset, it will automatically retrieve the settings required to reconstruct the configuration, such as Device Manager agent, registry keys, Device Manager-related security certificates, and network configuration. For devices with more than one memory card, you can also configure a backup to a specific card.
Connect to these networks. Device Manager is authorized, if necessary, to activate connections as defined in Network Management on the mobile device:
The operating mode depends on the status of the mobile device's current network connection at any given time:
|Authorized and Active connection||If the server running Device Manager is accessible through this network, the Device Manager agent connects to the server running Device Manager.|
|Unauthorized but Active connection||The mode is the same as for Authorized and Active connection.|
|Authorized and Inactive connection||The Device Manager agent will activate the connection and then connect to the server running Device Manager.|
|Unauthorized but Active connection||The Device Manager agent will not attempt to activate the network connection.|
It is preferable to create a special group, such as UninstallGroup, on the Users tab to uninstall Device Manager and then create a package of Device Manager option registry keys containing the uninstall option. You can then deploy this package to UninstallGroup on the Deployment tab. Thereafter, you can add a user to the UninstallGroup in order to uninstall Device Manager from the remote device.
This feature allows for Windows Mobile devices to be forced to connect back to the server running Device Manager when either a call or SMS from a preconfigured number is received by the device. To enhance security, a keyword must be included within the SMS message. This is particularly useful if a device is lost or stolen, and needs to be remotely disabled or wiped.
To use this feature, in the Connect On SMS reception / Connect on Call dialog box, select to either connect to server when receiving a SMS message or phone from a specific number.
Using the MS Exchange configuration for MS Outlook wizard in Device Manager, you can configure mobile email settings easily and automatically across your entire fleet of devices. These settings will generate the appropriate registry keys to synchronize with an Exchange server:
On the General tab, elect the appropriate device operating system type because different configuration options are available depending on the operating system release. For instance, tasks synchronization is available for Windows Mobile 6 devices but not for Windows Mobile 2003 or Windows Mobile 5.
If you create an Exchange tunnel, the value you enter in Server address has to be the same as the value you enter in Specify a local alias on the Tunnel tab, if you specified an alias. The server running Device Manager manages and optimizes the data stream and communication between the Exchange server and the mobile device.
In the Deployment tab, you can also configure rule to avoid deploying a specific package (say "XYZ") when roaming. In this case, if the Block all cellular connections managed by Device Manager option has been selected, all packages except "XYZ" will still be deployed even in roaming situations.
In the Tunnel tab, a given application tunnel can be forced to block all data traffic when roaming. For example, if the Block all cellular connections except the ones managed by Device Manager option has been selected, the "CRM_App" data traffic will still be blocked although it is managed as a Device Manager tunnel.