Gordon Welling
Admin Group
Manager Technnical Support Services
Joined: 11-December-2003
Location: Canada
Posts: 507
|
| Posted: 15-September-2006 at 12:13pm
|
|
|
How to Upgrade the Omni Mobile Client from 1.x to 2.x
Our testing
has confirmed that version 1.x clients will still be able to connect to
the 2.x Omni Mobile server. Users should be able to continue to use
Omni Mobile without interruption (other than during the upgrade
process). The client versin should only be updated to to 2.x if the server has been upgraded. To update the server, please follow the Omni Mobile Server upgrade instructions in this post.
While the version 1.x client will continue to work
after the server upgrade, the enhanced features provided by Omni Mobile
2.x will not become available to users until they upgrade the device
client. It is highly recommended that the Omni Mobile client on all
devices is upgraded to version 2.x that comes with the most current
omnimobile.zip download file.
Upgrading the Client
The 2.x client includes a new Appforge Crossfire client that must be upgraded first. The correct 1.x to 2.x client upgrade steps are:
- On your device logout of the Omni Mobile client and ensure that it is not running in memory. (Important - do not proceed until you have completely shut down the client.)
- Uninstall the Omni Mobile client from the device.
- On
your device, install the latest release of the Appforge Crossfire client onto
your device using the procedures described in the applicable Quick Start Guide or the User Guide (you will not have to reprovision the account).
- On your device, install the latest release of the Omni Mobile client using the same method used in step 3.
- Important - Before using the new client on the device, the user must connect to WebAccess and select the "Update" button on any of the Omni Mobile policy configuration pages. This will cause database to be updated to support the new functions that are enabled in the Omni Mobile version 2.x client. It is not necessary to make any changes to any values for the update to occur.
- On your device, run Omni Mobile and log in.
Note
- For Palm OS devices, just install the latest 2.x client over the existing
1.x client. The Appforge Crossfire client is built into the Omni Mobile
client and upgrade automatically.
New Omnimobile-Desktop.exe
The 2.x client uses a new Account Creator (omnimobile-desktop.exe) to create PDB files. Once you upgrade to 2.x clients, PDB files must be created using the omnimobile-desktop.exe utility contained in the latest omnimobile.zip download file.
Do not Reuse PDB Files
With Omni Mobile 1.x it was possible to reuse PDB files created by omnimobile-desktop.exe. With Omni Mobile 2.x, device tracking and management has been added to the server. Everytime a set of PDB files are created by omnimobile-desktop.exe, they are registered to the server and can only be used on one device for a single instance.
Once the user logs in using a set of PDB files for their account, the PDB files cannot be reused again. Once PDB files have been copied to the device, delete them from the host computer to ensure that they will not be reused. Reusing a set of PDB files will cause all policy and data updates to cease on all devices that the same PDB files have been provisioned on.
Edited by Aldo Zanoni on 31-January-2007 at 4:20pm
|
Omni Web Forum : GroupWise for PDAs and Smart Phones ~ Omni Mobile : Omni Mobile Clients for GroupWise Synchronization
Topic: TIP: Upgrade Client from 1.x to 2.x
