Odyssey Client Enterprise and FIPS Editions, version 4.51 *********************************************************************** README.TXT May 11, 2006 This file contains important information about system requirements, compatibility with other products, known problems, late-breaking items that are not covered in the manual, etc. *********************************************************************** Contact information: Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 (408) 745-2000 (Main number) (408) 936-1576 (Technical support number) http://www.juniper.net (web home page) *********************************************************************** Operating System Requirements: Odyssey Client Enterprise Edition runs on any of the following: Windows 2000 (Any edition) Windows XP (Any edition) Windows Millennium Edition Windows 98/98SE Odyssey Client FIPS Edition runs on any of the following: Windows 2000 (Any edition) Windows XP (Any edition) Your PC must be running Internet Explorer 5.5 or higher. *********************************************************************** Hardware Compatibility: The Odyssey Client is capable of authenticating with any Wireless Access point or Ethernet switch that supports the 802.1x protocol. The Odyssey Client is capable of performing 802.1x authentication through any wireless adapter card driver that fully supports the 802.11 OIDs defined in NDIS 5.1. The Odyssey Client is capable of performing 802.1x authentication through any wired Ethernet adapter card. The Odyssey Client can authenticate through any Ethernet switch That supports the 802.1X protocol. Wired authentication can use any wired Ethernet adapter card. FIPS mode is available with two association methods: WPA2 and xSec. FIPS mode with WPA2 (RSN) requires a modified NIC driver. If the NIC driver is not compatible you will receive an "Error: FIPS Adapter initialization" indication. Contact Juniper Technical Support for adapter compatibility and driver availability. Use of the xSec protocol (whether in FIPS mode or not) requires an Ethernet switch that implements xSec. xSec works with any 802.11 wireless adapter. *********************************************************************** Installing Odyssey Client: * You must have administrative privileges to install Odyssey Client on Windows 2000 or Windows XP. * To install Odyssey Client double-click OdysseyClient.msi. An installation wizard will guide you through the rest of the installation / upgrade process. On Windows 98 systems, double- click the OdysseyClient.exe file. * Before installing Odyssey Client, close any network adapter properties dialogs. *********************************************************************** New Features in Odyssey Client 4.51: * Single installer for Enterprise Edition and FIPS Edition. Edition is determined by the license key used. * FIPS Edition now includes all Enterprise Edition features. *********************************************************************** New Features in Odyssey Client 4.50 Enterprise Edition: * Option to disable the wireless adapter when a wired network connection is available. * Preferred networks. The administrator can specify networks that will always be selected if in range, pre-empting an existing connection if necessary. * Prompt for user name. Facilitates sharing of computers without separate Windows user accounts. * Simple client certificate selection. Allows pre-configured TLS deployment. Avoids configuration changes when a client certificate expires and is reissued. * Custom prompts in the "Enabling and configuring Odyssey" wizard. These can guide users who must enter non-standard login name formats when initializing Odyssey. * Support for EAP-POTP * Support for EAP-PEAP with inner EAP-TLS *********************************************************************** New Features in Odyssey Client 4.32 FIPS Edition: * FIPS 140-2 Level 1 compliant mode * xSec support *********************************************************************** New Features in Odyssey Client 4.30: * Single sign-on with Smart Card login * Alternate adapter for pre-login authentication *********************************************************************** New Features in Odyssey Client 4.20: * Support for RSA Soft Token *********************************************************************** New Features in Odyssey Client 4.10: * TTLS with client certificate *********************************************************************** New Features in Odyssey Client 4.0: * WPA2 support * CCX2 support * EAP-FAST support * Anonymous outer identity with PEAP * EAP-SIM no longer requires a separate license (Enterprise Edition only) * EAP-SIM and EAP-MSCHAP-V2 can now be configured within EAP-TTLS * Better support for GPO startup scripts and roaming profiles *********************************************************************** New Features in Odyssey Client 3.06: * Option for a machine account to use the Windows computer name and password in TTLS and PEAP profiles. You configure this option in the Odyssey Client Administrator's Machine Account applet. The machine must belong to a Windows 2000 domain or a mixed domain. * Fix for double-byte characters in certain system paths *********************************************************************** New Features in Odyssey Client 3.04: * Hidden option to disable the Wireless Configuration service on Windows 2000. This option requires an edit to the registry, but it can be preconfigured. Please contact technical support if you need to use this option. *********************************************************************** New Features in Odyssey Client 3.03: * Fails more gracefully if you delete the currently active profile. *********************************************************************** New Features in Odyssey Client 3.02: * Change for compatibility with Cisco ACS 3.23 *********************************************************************** New Features in Odyssey Client 3.00: * Enhanced configuration update Administrators can distribute data updates, with or without program updates, that allow much greater control over user configurations. This includes the ability to lock networks, profiles and other records on the user machine. * Permissions Editor Administrators can selectively disable many features on their managed clients. * Novell Client single sign-on Seamlessly connects to an 802.1X network before the Novell Client's first network activity. * Support for 802.11a channels *********************************************************************** New Features in Odyssey Client 2.25: * Script Composer This allows administrators to compose scripts that can automatically update users' configurations. *********************************************************************** New Features in Odyssey Client 2.24: * EAP/PEAP-Token Card support This supports Cisco's use of passwords within this protocol, as well as actual token cards. * EAP-LOGOFF on disconnect from wired adapters This fixes a case where a user may incorrectly inherit some attributes of the previous user. * GINA fast-fail if adapter missing This skips all delays and user interaction if the GINA authentication has no chance of succeeding. Control immediately passes to the Windows login. * Option to disable Odyssey from password prompt This stops future password prompts if you do not wish to use Odyssey at this time. *********************************************************************** New Features in Odyssey Client 2.21: * EAP/SIM support is available as a separately licensed feature *********************************************************************** Known Issues: 1) Under Windows 98, the "Enabling and configuring Odyssey" wizard may put an incorrect value in the "Login name" field of the initial profile. 2) Windows XP disables Fast User Switching whenever a GINA module is added. Consequently, installing the Odyssey GINA module disables Fast User Switching. 3) Some wireless NIC drivers do not completely support ad hoc networks under WPA. This may result in an inability to connect or in delays when connecting or reconnecting. Please contact your NIC vendor if you have problems with ad hoc networks under WPA. 4) If you are using the Odyssey Client Script Composer, do not use double-byte characters in script file names.