NetMotion Mobility XE

Version 6.70
April 2006

Introduction to NetMotion Mobility XE

This document contains information that will help you install and configure the NetMotion Mobility XE software, and describes known issues with this release.

A successful Mobility XE installation and configuration depends on the network hardware and software environment in which it is deployed. Please review this entire document, with special attention to known issues, before installing the Mobility XE software.

For the latest news and support information pertaining to the Mobility XE release, including any updates to these release notes, please see the NetMotion Wireless web site at www.netmotionwireless.com/support/.

Contents:

Installing NetMotion Mobility

The NetMotion Mobility Quick Start Guide outlines the basic procedures for installing or upgrading the Mobility server and Mobility client software, and establishing an initial connection.

For detailed consideration of NetMotion Mobility deployment in a production environment, see the NetMotion Mobility System Administrator Guide.

What's New in NetMotion Mobility XE Version 6.70

For more detailed information about Mobility XE features, visit the NetMotion web site at www.netmotionwireless.com, or see the NetMotion Mobility System Administrator Guide.

System and Product Requirements

The number of mobile devices a Mobility server can support depends on client usage patterns and server processing power. For a discussion of scalability issues, see the NetMotion Mobility System Administrator Guide.

The Mobility server requires the following:

The Mobility warehouse requires the following:

The Mobility client for Windows 2000, Windows XP, or Windows XP Tablet requires the following:

The Mobility client for Windows CE requires the following:

To integrate Mobility XE into a wireless network environment, you must have at least one of the following:

Other installation and configuration requirements:

NetMotion Mobility XE Documentation

NetMotion Mobility includes:

Version Compatibility

The security and feature enhancements in Mobility XE affect the compatibility of this version with earlier releases:

Upgrading from NetMotion Mobility or Mobility XE version 6.0x

Mobility XE version 6.70 servers will coexist with older Mobility servers in a server pool; you do not need to upgrade all servers in a pool at the same time. If your Mobility warehouse is collocated with a Mobility server, upgrade the other servers in the pool before you upgrade the collocated server.

Warning: Do not add a Mobility XE version 6.01 or older server to a pool that includes Mobility XE version 6.5, 6.6, or 6.7 servers. The older server will not function normally, and will display "Object class violation" errors in the event log.

It is good practice to perform a full backup of the server 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 schema is ever corrupted.

Upgrades to Mobility XE version 6.70 from NetMotion Mobility v5.01 or earlier releases require new Mobility XE licenses. Licenses issued for earlier releases are not valid for the shipping version of Mobility XE, and devices will not be allowed to connect until valid licenses have been applied. Please contact your sales representative for Mobility XE licenses.

After upgrading a Mobility client, the client can connect only to the Mobility server address specified in the Configuration dialog box in NetMotion Client Properties, or provided through DHCP. If you are upgrading your Mobility client from a location where it can only connect to the Mobility server using an external address, specify the external address in the Configuration dialog box in NetMotion Client Properties. When the client establishes an initial connection, it receives the list of all addresses for the Mobility server and can use any of the server's addresses for subsequent connections.

If you are upgrading a Mobility server from version 5.01 and you are using NAT or port forwarding to access the server, you must configure the external server addresses in the Mobility XE console or your clients will receive the following error message: "This client is configured for a Mobility server address that is not in the External Server Address list. Contact your administrator to configure this setting in the Mobility Console." See the online help for more information.

After upgrading a version 6.0 Mobility XE server to version 6.70, some settings that had not been modified before upgrading may display an override icon. The settings will be carried over correctly from the previous version.

Known Issues

Installation

Mobility warehouse installation may fail if you try to install the warehouse on a machine to which you are connected using Terminal Services.

Mobility server

If Symantec Antivirus version 9.0.1 is installed on a Mobility server, memory requirements of the antivirus software will significantly decrease the number of client connections the server can support. To maintain maximum Mobility server capacity with this antivirus product, see Technical Note 2144.

The default values for the Window Size - Receives and Window Size - Transmits settings on the Server Settings and Client Settings pages of the Mobility console is increased from 16 frames in NetMotion Mobility XE to 32 frames in Mobility XE version 6.5. If you have overridden the default values for these settings on a Mobility XE server, the values you have set will be preserved on upgrade.

If you specify an Activity Log - File Name Prefix server setting longer than six characters, the prefix is not added to the activity log file name. Also, a file name prefix ending in an underscore character is not handled correctly.

Do not install the Mobility server or Mobility warehouse on a network domain controller.

If the Mobility server will participate in a domain in which any domain controllers run on a Windows 2000 system, install Service Pack 2 or later on all domain controllers to avoid authentication and security issues.

Do not install the Mobility XE server on the same computer as a multicast listening application. The application will not appear to receive multicast packets.

Mobility warehouse

Do not rename the machine on which the Mobility warehouse is installed.

There is a known conflict between the Sun ONE console application and the ATI video driver version 5.30.1.b02. Attempting to start the Sun ONE console locks the system, requiring a reboot. If your system is using this driver, uninstall it and use the Microsoft driver for your display.

Mobility client (any platform)

If Mobility XE is deployed in an NT4 domain, users with Mobility client devices will not be able to change their network passwords through the Mobility client. Use the Windows password change facility.

Mobility XE version 6.01 was the last release to include updates for the following Mobility client platforms:

Mobility clients on these platforms will be able to connect to a version 6.70 Mobility server, but will not be able to implement features added after v.6.01. Future releases will not include new features or bug fixes for Mobility clients on these operating systems.

Mobility client for Windows 2000 or Windows XP

When you boot a Mobility client device into Safe mode with networking, the Mobility client may be unable to connect to a Mobility server.

Microsoft recommends that you stop network card services before ejecting a card (or undocking a laptop). Mobility clients on Windows 2000 or Windows XP may successfully maintain the network connection if you eject a network interface card without stopping the card services, but will display an error message. You may also lose NetBIOS drive mappings.

Warning: Do not change network interface cards on a Windows 2000 or Windows XP device when the device is suspended. The operating system does not support this procedure, and may leave your system in an unstable state.

MSN Messenger file transfers may not persist through suspend/resume events. Allow the file transfer to complete before suspending the mobile device, or re-start it when the client reconnects to the Mobility server.

Mobility XE does not support the Fast User Switching feature in Windows XP. If you enable this feature on a Mobility client, your system may become unresponsive. To recover, restart the computer in Safe Mode, disable Fast User Switching, and restart the computer.

A Mobility client with open mapped network drives may generate multiple error dialog boxes if the network drives become temporarily unavailable, as would happen if you suspend and then resume the mobile device with mapped drives displayed on the desktop in Windows Explorer. Click OK to dismiss the error dialog boxes, then refresh the folder contents.

The Mobility client for Windows 2000 supports interface-assisted roaming detection for any interface cards that have Windows XP-compatible drivers. In addition, it will use the hardware interface for out-of-range detection for interface cards using Windows 2000 drivers. All other subnet roaming detection on a Windows 2000 client is beaconing-based.

Mobility Client for Windows Mobile

Mobility client devices running Windows Mobile cannot perform DES or 3DES encryption. If you specify either of these options, Windows Mobile clients will be unable to connect to the Mobility server.

When installing the Mobility client software over an earlier version, the previous user name and domain may not display correctly in the logon box. They will display correctly after the user re-enters the user name and domain.

For Windows Mobile devices, decreasing the Failover - Connected Timeout client setting to 30 seconds may improve failover performance.

After resetting the Mobility client device, the domain name may not appear in the logon dialog box and it may seem that it is not possible to move the cursor to the domain field. The cursor does not appear when the field is empty, but you can enter the domain name as usual. You can also select the most recently used domain name from the drop-down list.

Rarely, a Windows Mobile 2003 Second Edition device will not display the Mobility XE logon dialog box after the device is reset. To display the logon dialog box, reset the device a second time.

Mobile devices on Cingular Wireless may be pre-configured with a local proxy server. This proxy server must be disabled for the Mobility client to operate correctly. To modify local proxy configuration, on the Start menu of the device, select Settings. Select the Connections tab, and then select the Connections icon. Under the Connection heading, select Edit my proxy server. Clear the check box marked "This network uses a proxy server to connect to the Internet". Select OK (twice) and then close Settings.

Microsoft networking (NetBIOS) file transfers may not persist through roaming, suspend/resume, or out-of-range events. Allow the file transfer to complete before roaming, suspending the mobile device, or moving out of range. If a file transfer is interrupted, re-start it when the client reconnects to the Mobility server.

Redirecting the NetMotion Event Log file to compact flash prevents the Mobility client software from loading. To correct this problem, save the log file in a folder on the Windows Mobile device. By default, the NetMotion Event Viewer log file is stored in the Windows folder.

NetMotion Mobility XE v6.70
© 1999-2006 by NetMotion Wireless, Inc.