NetMotion Mobility XE v9.21 Readme
March 2011
Introduction to NetMotion Mobility XE
A successful Mobility XE installation and configuration depends on the network hardware and software environment in which it is deployed. Review this entire document and refer to the list of known issues before installing Mobility XE.
- Prior to this release, the default behavior of Mobility servers was to accept connections only from Mobility clients that were using FIPS-certified cryptographic modules. In v9.21, the default setting is now Off - Warn: if a client connects with a cryptographic module that is not in the approved list, a warning is written to the server event log.
- Simplified deployment: all server and client components of Mobility XE are released together and carry the same version number (9.21).
- Mobility XE version 9.21 includes v7.0 of the Mobility warehouse, though you may have the option of keeping your current warehouse. The warehouse you install depends on the operating system of the computer on which it will run: 7.0, 6.3.1, or v5.2 Patch 4 for Windows Server 2003 R2 (x86), 7.0 for Windows Server 2008 R2 (x64).
- Support for additional antivirus packages.
- New client setting for configuring the behavior of EAP-GTC. You can configure Mobility to connect users automatically after the password change completes, or require users to respond to each authentication challenge separately, as with two-factor authentication.
System and Product Requirements
Mobility XE consists of these software components:
- Mobility server
- Mobility warehouse
- (Optional) Analytics Module: the Mobility reporting server and Mobility reporting database
- A Mobility client that runs on each mobile device
Mobility server pools with a combination of 32-bit and 64-bit servers are supported, provided they are all running v9.21. To install all server components on one computer (for a pilot deployment, or one with no more than 100 clients), choose the Mobility XE Small Deployment Server system. For a production deployment, install the Mobility XE server components on separate computers, adding one or more standby warehouses and additional Mobility servers, depending on the size of your deployment.
Basic Server Requirements
32-Bit Requirements
- Hardware (x86)
- Processor: x86-compatible Pentium 4 dual-core processor (or equivalent), 2.0 GHz (minimum)
- Operating system: Windows Server 2003 R2 (Enterprise or Standard Edition) with SP2 or later
- RAM: 3 GB, minimum
- Disk space: 20 GB, minimum
- Browser (JavaScript enabled): Internet Explorer® 7 or 8, and Firefox® 3.5 or later
64-Bit Requirements
- Hardware (x64)
- Processor: x64-compatible dual-core processor, 2.0 GHz (minimum)
- Operating system: Windows Server 2008 R2 (Enterprise or Standard Edition)
- RAM: 4 GB, minimum
- Disk space: 20 GB, minimum
- Browser (JavaScript enabled): Internet Explorer 8, and Firefox 3.5 or later
The number of mobile devices a Mobility server can support depends on client usage patterns and server processing power. In general, more powerful hardware for both client and server is needed to maintain performance when using encryption, compression, traffic-intensive applications, or faster networks. A computer with additional processors or faster processors will support greater activity by a larger number of users.
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 domain or workgroup computers. Mobility XE does not support servers installed on domain controllers.
- For WLAN subnet roaming, DHCP services must be available on the network.
