Upgrading From Mobility XE Version 6.x to 6.70

Technical Note 2147

Last Reviewed 24-Apr-2008
Applies To
Mobility XE versions 6.00 through 6.61
 Printer-friendly version

Summary

Please pay careful attention to all the instructions and information in this tech note. In order to ensure a successful upgrade you must follow these instructions exactly.

Mobility XE version 6.70 contains many additions and changes to both the clients and server, which are detailed in What's New.

Important: After version 6.70 was released, Sun released Patch 4 for the Mobility XE warehouse (Sun Java™ System Directory Server 5.2). Since Patch 4 contains critical bug fixes and optimizations, NetMotion Wireless strongly recommends that you apply the patch either before or immediately after upgrading your Mobility server(s). If you are upgrading to version 6.70 as a step towards upgrading to version 8.0, you must apply Patch 4 before your upgrade to 8.0 can complete. To determine if your warehouse has already had Patch 4 applied, and for instructions on applying the patch, see Tech Note 2195.

Upgrade tips

• See the version 6.70 readme for a description of known issues with this release.

• Upgrades from Mobility XE version 6.00 and higher do not require new Mobility XE licenses. (Upgrades from 5.01 and earlier, however, do require them—contact your sales representative.)

• The Mobility XE Warehouse has not changed since version 6.00: select Server Only during setup.

• It is good practice to perform a full backup of the warehouse before you upgrade the first server in a pool, and another after you upgrade the last server in the pool. This will allow you to recover if the data are ever corrupted. For instructions on backing up the warehouse, see Tech Note 2129.

• After you have successfully upgraded all your Mobility servers to version 6.70, you must reinitialize your primary warehouse only. See Tech Note 2222 for instructions.

• Generally we recommend upgrading your Mobility server(s) first, then upgrading your clients as you have time. However, both the Mobility 6.70 clients and server are backwards compatible with Mobility 6.00 and 6.01, so it's safe to upgrade the clients first if you need to.

• Mobility 6.70 uses FIPS-compliant encryption libraries, but you must have at least Mobility 6.61 installed on both the server and the clients for FIPS compliance. A setting in Mobility 6.70, Security—FIPS Required, can be used to block non-FIPS-compliant (pre-6.60) clients from connecting. This setting is turned off by default on the server upgrade, enabling older clients to connect until you have a chance to upgrade them. For full FIPS compliance, upgrade all of your clients to 6.70 and re-enable this setting.

• If you are using Policy Management and your Mobility server is more current than your clients (the versions are out of synch), the newer policy features will not be available for those clients. You have two choices regarding older clients:

  • To prevent older clients from connecting if they've been assigned a Policy they don't support, select Policy—Disconnect if client incompatible in the Mobility console, Server Settings (this is the default). This option is useful when a Policy is being used for security purposes and you don't want users connecting without it, for example if clients are being blocked from reaching certain network resources.

  • If Policy—Disconnect if client incompatible is not selected, the older client is allowed to connect, but the server does not send the incompatible policy.

• If you have more than one Mobility server and do not want to interrupt client connect during the upgrade, you can take a server offline a day or so before upgrading it. This allows clients to naturally migrate to the other server the next time they connect. After you've upgraded one server you can bring it back online and take your other server offline to repeat the process. See Tech Note 2191 for complete instructions.

• WARNING: Do not add Mobility XE version 6.0x servers to a pool that includes a version 6.50 or higher server. Doing so corrupts the Mobility warehouse schema.
  Adding a version 6.70 server to an existing Mobility server pool updates the Mobility warehouse schema. After the warehouse schema has been updated to version 6.70, you cannot add new Mobility XE 6.00 or 6.01 servers to the pool without corrupting the warehouse. If you must replace one of your Mobility XE 6.0x servers (for example, when recovering from a crash), and you have already added a version 6.70 server to the pool, contact technical support for help in restoring the Warehouse schema.

• The Mobility server(s) must be rebooted after the upgrade. This will disconnect any active client sessions, however they should automatically reconnect after the server comes back up.

Operating System Support

Mobility XE version 6.70 clients are available for the following client operating system platforms:

• Windows XP (SP1 & SP2)

• Windows 2000

• Windows Pocket PC 2003

• Windows Pocket PC 2003 Second Edition (SE)

• Windows Pocket PC 2003 Phone Edition

• Windows CE 4.2

Version 6.70 client software is not available for the following client operating system platforms:

• Windows 98

• Pocket PC 2002

• Pocket PC 2000

• Windows CE 3.x

Mobile devices running any of these operating systems can run Mobility XE version 6.01 client software and connect to a version 6.70 server, although many of the new features available in version 6.70 will not be available.

Related Information

Please comment on this technical note.