NetMotion Mobility XE

NetMotion Mobility XE

Version 8.0
April 2008

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.

The latest news and support information pertaining to the Mobility XE release, including any updates to these release notes, are available on the NetMotion Wireless web site at www.netmotionwireless.com.

Contents:

What's New in NetMotion Mobility XE Version 8.0

Installing NetMotion Mobility XE

System and Product Requirements

NetMotion Mobility XE Documentation

Known Issues

What's New in NetMotion Mobility XE Version 8.0

New features in Mobility XE version 8.0 include:

A Network Access Control (NAC) module that lets you control which mobile devices are allowed to connect to the Mobility server, based on their compliance to system health and configuration rules

Enhanced support for real-time applications, including improved call and video quality in environments with high packet loss, high latency, and jitter

Numerous minor enhancements and bug fixes, including better handling of network driver errors that previously halted data flow on Mobility clients

For more detailed information about new and enhanced Mobility XE features, visit the NetMotion web site at www.netmotionwireless.com/products/whatsnew.aspx.

Installing NetMotion Mobility XE

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

For detailed consideration of Mobility XE deployment in a production environment, see the NetMotion Mobility XE 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 XE small deployment server system requires:

Processor: x86-compatible Pentium 4® processor, 2.0 GHz (minimum).

Operating system: Microsoft Windows Server 2003 R2 (Service Pack 2), Microsoft Windows Server 2003 (Service Pack 2), or Microsoft Windows 2000 Server (Service Pack 4).

RAM: 2 GB, minimum.

Disk space: 2 GB free, minimum.

Browser (with JavaScript™ enabled): Internet Explorer® v7, Internet Explorer v6, Firefox® 2.0.

The Mobility XE small deployment server system installs both Mobility server and Mobility warehouse on one machine. It is intended for pilot programs and small deployments with under 400 users.

A stand-alone Mobility server requires:

Processor: x86-compatible Pentium 4, 2.0 GHz (minimum).

Operating system: Microsoft Windows Server 2003 R2 (Service Pack 2), Microsoft Windows Server 2003 (Service Pack 2), or Microsoft Windows 2000 Server (Service Pack 4).

RAM: 2 GB, minimum.

Disk space: 1GB free, minimum.

Browser (with JavaScript enabled): Internet Explorer v7, Internet Explorer v6, Firefox 2.0.

For RSA SecurID® user authentication: RSA® Authentication Agent version 6.0 or higher.

A stand-alone Mobility warehouse requires:

Processor: x86-compatible Pentium 4, 2.0 GHz (minimum).

Operating system: Microsoft Windows Server 2003 R2 (Service Pack 2), Microsoft Windows Server 2003 (Service Pack 2), or Microsoft Windows 2000 Server (Service Pack 4).

RAM: 2 GB, minimum.

Disk space: 3 GB free for a pool of four or fewer Mobility servers. 5 GB free for a pool of five or more Mobility servers.

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

Operating system: Microsoft Windows Vista (Business, Enterprise, or Ultimate Edition), Microsoft Windows XP (Service Pack 2), Microsoft Windows XP Tablet PC Edition® (Service Pack 2), or Microsoft Windows 2000 Professional (Service Pack 4).

Disk space: 10 MB free.

Mobility XE online help requires a web browser that supports HTML 4.0, JavaScript 1.2, and CSS1 or higher.

The Mobility client for Windows Mobile® or Windows CE requires the following:

Processor: StrongARM 1100 or compatible processor (e.g., XScale).

Operating system: Microsoft Windows Mobile 6.0 (Classic, Standard, or Professional), Microsoft Windows Mobile 5.0 for Smartphone or Pocket PC, Microsoft Windows Mobile 2003 for Pocket PC, Microsoft Windows CE version 5.0, or Microsoft Windows CE version 4.2.

See Technical Note 1515 for a current list of tested device types and processors.

Storage memory: 3 MB free on Windows Mobile for Pocket PC devices, or 7 MB free on Windows Mobile for Smartphone.

ActiveSync® installation requires ActiveSync v. 4.1 or greater.

Network requirements:

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

A wireless LAN adapter installed on a mobile device and wireless access points installed on the wired network.

A wireless WAN device installed on a mobile system and available wireless WAN service (for example, an account with a service provider).

A modem installed on a mobile device and available dial-up service.

Server components should be installed on workgroup or domain machines. Mobility XE does not support servers installed on domain controllers.

For subnet roaming, DHCP services must be available on the network.

Customers running previous Mobility XE versions can safely upgrade to version 8.0 before making their hardware fully compliant with the above requirements. However, hardware should be brought into compliance with the specifications as soon as possible.

NetMotion Mobility XE Documentation

Mobility XE includes:

Online help for all Mobility XE client and server components.

The NetMotion Mobility XE Quick Start Guide, in electronic format (Qstart.pdf).

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

The NetMotion Mobility XE System Administrator Guide, in electronic format (SysAdmin.pdf).

The System Administrator Guide provides an overview of Mobility XE architecture, network design considerations, setup, configuration, maintenance and troubleshooting issues for network administrators who deploy and support Mobility XE software.

Known Issues

Installation

On Pocket PC and Smartphone devices, the Mobility client software may not install successfully on a storage card.

Do not install the Mobility server or Mobility warehouse on a Microsoft domain controller. Mobility XE does not support a Mobility server or Mobility warehouse collocated with a Microsoft domain controller.

Upgrade

In large Mobility XE installations (thousands of users), memory usage issues with a Mobility warehouse older than version 7.10 could affect long-term system stability. New installations of the v7.10 or later Mobility warehouse do not have this problem. To update a Mobility warehouse installation older than v7.10, see Technical Note 2209.

Upgrades from Mobility XE 8.0 Beta to the released 8.0 version will not correctly install help files. To correct this, complete the upgrade and then re-run the setup, and when prompted select the "repair" option.

Mobility server

If Symantec Antivirus version 9.0 or above 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.

A renamed client policy rule may not propagate correctly. Publishing the policy manually from the Mobility console will propagate the change to the subscribed client devices.

Do not connect a Windows Mobile device to a Mobility server via USB. Doing so will cause the server to reject all client connections with a "virtual IP address in use" error.

If the Mobility server is connected to a standby warehouse, you cannot switch from the Warehouse tab to another tab in the Startup Settings utility.

When configuring a Mobility server to use a new primary warehouse, you may not be prompted to restart the computer after authenticating and connecting to the new warehouse. You will need to manually reboot the machine for it to be recognized in the new pool.

Mobility warehouse

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

Mobility client (any platform)

The Mobility icon in the system tray may indicate a different Mobility client status than the Status tab of the NetMotion Mobility Client dialog box. The next change in interface state synchronizes the status display.

Network Access Control policies may not behave as expected if there are multiple security products installed on a Mobility client device.

After entering valid credentials, some Mobility clients may experience an extended delay while the client connects to the Mobility server.

Mobility client for Windows Vista, Windows XP, or Windows 2000

A Mobility client may become unresponsive on a Windows Vista device running the McAfee Security Suite.

On Windows Vista, a Mobility client may be disconnected from the Mobility server if you resume Windows operation immediately after the device hibernates.

A Mobility client on Windows Vista Service Pack 1 may not successfully establish or maintain PPTP or L2TP connections.

Ping may not work as expected on Windows Vista Service Pack 1.

Applications using Microsoft's Peer-to-Peer Infrastructure, such as Windows Meeting Space, require IPv6 support. Although Mobility XE does not tunnel IPv6 traffic, it coexists with the IPv6 protocol by allowing IPv6 traffic only when Mobility XE is bypassed. When the Mobility client is connected to the Mobility server, Mobility XE blocks all incoming and outgoing IPv6 traffic, preventing traffic from bypassing the VPN.

Mobility client for Windows Mobile

On the Cingular 8125 Smartphone, the Mobility client may become unresponsive if the network interface on the server is disabled while the client has an active connection. To connect, disable and re-enable the interface, or soft reset the mobile device.

Certain Windows Mobile 5.0 devices (e.g., the Cingular 8125) may be pre-configured to use a local proxy server. In most cases, this proxy server configuration must be disabled for the Mobility client to operate correctly. To modify the local proxy configuration, on the Start menu of the device, select Settings. Select the Connections tab, and then select the Connections icon. Select Edit (or Set up) 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.

Network applications such as Internet Explorer may occasionally be unable to load a web page or connect to network resources, even when the Mobility client has an active connection to the Mobility server.