expressaccess 1.1 (Build 120) Release Notes

Transcription

1 expressaccess 1.1 (Build 120) Release Notes January 18, 2008

2 Table of Contents OBJECTIVE AND SCOPE... 3 ADDITIONAL DOCUMENTATION... 3 HEALTHCAST CONTACTS... 3 YOUR COMMENTS... 3 COPYRIGHT INFORMATION... 3 RELEASE INFORMATION... 4 SUPPORTED HARDWARE AND SOFTWARE... 4 NEW FEATURES AND ENHANCEMENTS... 4 ISSUES FIXED (TERMINAL SERVICES ENVIRONMENTS)... 6 KNOWN ISSUES (TERMINAL SERVICES ENVIRONMENTS)... 6 ISSUES FIXED (CITRIX ENVIRONMENTS)... 6 KNOWN ISSUES (CITRIX ENVIRONMENTS)

3 Objective and Scope The objective of this document is to provide information about expressaccess version 1.1, including supported platforms (hardware and software), features/enhancements, fixes, and known issues. Additional Documentation For additional expressaccess documentation, see the following: expressaccess 1.1 Administration Guide: how to setup and use expressaccess HealthCast Website ( additional company information HealthCast Contacts HealthCast, Inc, 5777 North Meeker Ave, Suite 103 Boise, ID Corporate: (208) Sales: (610) Support: (208) ; Your Comments We welcome your feedback and suggestions to improve this document and our products. Please send an to Thank you. Copyright Information Citrix is a trademark of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. AIR ID is a registered trademark of RF IDeas, Inc. ( HealthCast, expressaccess and exactaccess are registered trademarks of HealthCast, Inc. 3

4 Release Information Product Name: expressaccess (EA) Release Name: expressaccess 1.1 Build Number: 120 Version Number: Release Date: January 18, 2008 Supported Hardware and Software The following is a list of all supported hardware and software for expressaccess 1.1. Please note that expressaccess may be deployed in a number of different configurations. Please contact your HealthCast representative to determine the optimal design for your organization. Client Operating System: Windows XP SP2 Wyse V90 XP embedded thin client HP 5720 thin client Terminal Services: Microsoft Terminal Services support requires Remote Desktop Client version 6.0. This software must be installed on the client desktop prior to installing expressaccess in RDP mode. Citrix : Citrix ICA client version 9.15 and earlier and 10.X are not supported. This software must be installed on the client desktop prior to installing expressaccess in ICA mode. Proximity Card Readers (optional): RF IDeas pcprox model: RDR-6082AKU RF IDeas AIR ID model: RDR-7082AKU (for iclass cards) RF IDeas pcprox model: BSE-PCPRXH-USB Proximity sensor (optional): RF IDeas pcprox - Sonar Windows Installer: Version 3.0 and above New Features and Enhancements 4

5 The following new features and enhancements are included in expressaccess version 1.1: Feature/Enhancement Login Screen (#1802) Timeout Feature (#1065) Check CAPS LOCK Message (#1067) Credentials Cleared Upon Unsuccessful Login (#1052) Accessing Locked/Disabled Account (#1801) Description The login screen has been updated. The two (2) minute login time limit has been disabled if there is any activity (i.e. mouse, keyboard) on the computer. After an unsuccessful login attempt, the resulting error message prompts the user to verify CAPS LOCK has not been activated on the computer. In addition, if CAPS LOCK is on when the user enters their password, a tool tip-style message will also appear. After an unsuccessful login attempt, both the username and password fields are cleared. When attempting to access a locked or disabled account, the resulting error message indicates the account is locked or disabled rather than a generic invalid login message. Only disabled and locked Windows account message functionality is mirrored and supported in EA 1.1. Other account control messaging features such as login hours and logon to specific workstations are not supported. Domain Password Change (#1121) Enhanced Prox Card functionality (#1200) Remote Upgrade Deployment Feature (#1201) RDP version 6 Support (#1737) iclass Reader/Card Support (#1629) Incorrect credentials message updated (#1804) A user may now change his/her domain password when it has expired, or is about to expire. (expressaccess will prompt for this change). When using a proximity card (optional), expressaccess now allows for self-registration, password saves, and tap-in/tap-out functionality. expressaccess now allows for remote upgrade deployment via tools such as SMS, Altiris, and Tivoli. Previous versions do not need to be uninstalled before running the upgrade. RDP version 6 is now supported in expressaccess and is the only version supported in this release. iclass proximity card readers are now supported in expressaccess (see above supported hardware section). If a user s authentication fails because of incorrect credentials, the resulting message has been updated 5

6 to be more helpful so that the user can correct the issue. Issues Fixed (Terminal Services Environments) The following issues were occurring in the expressaccess product when used in Terminal Services environments. These issues have been fixed in expressaccess 1.1: Build.120 fixes: Password expiration not reading domain setting (#2138): The password expiration setting is now being read from the logged in user s domain rather than the workstation setting. Passwords never set to expire prompted for password reset (#2130): Accounts with passwords set to never expire are now being read properly; no password expiration message is seen. Build.119 fixes: Proximity Card Not Populating Username (#123): When using a proximity card (optional), expressaccess 1.1 now populates the username field upon first card swipe. Known Issues (Terminal Services Environments) The following are known issues for this release when used in Terminal Services environments. These issues have been logged in HealthCast s internal issue-tracking system. The number assigned to the issue is listed, along with a brief description of the issue. If additional information, including a workaround, is available, that is also provided. No known issues Issues Fixed (Citrix Environments) The following issues were occurring in the expressaccess product when used in Citrix environments. These issues have been fixed in expressaccess 1.1: Build.120 fixes: Password expiration not reading domain setting (#2138): The password expiration setting is now being read from the logged in user s domain rather than the workstation setting. Passwords never set to expire prompted for password reset (#2130): Accounts with passwords set to never expire are now being read properly; no password expiration message is seen. 6

7 Build.119 fixes: Proximity Card Not Populating Username (#123): When using a proximity card (optional), expressaccess 1.1 now populates the username field upon first card swipe. NumLock State Inconsistent (#1207): expressaccess 1.1 now consistently maintains the Num Lock state when connecting and disconnecting to the remote desktop server. Known Issues (Citrix Environments) The following are known issues for this release when used in Citrix environments. These issues have been logged in HealthCast s internal issue-tracking system. The number assigned to the issue is listed, along with a brief description of the issue. If additional information, including a workaround, is available, that is also provided. Issue #130 Improper display on Citrix if using different screen resolutions: If a user starts a remote desktop session, disconnects, and then reconnects to the existing session on a workstation that has a different screen resolution from the initial workstation, the screen will not be displayed properly. Steps to Reproduce: 1. Start a new remote desktop session on a workstation that has a high screen resolution (i.e X 768). 2. Disconnect the session, leaving it active on the server. 3. Move to a different workstation with a lower screen resolution (i.e. 800 X 600). 4. Login as the same user. Result: The user is reconnected to their existing session; however, it retains the screen resolution established on the first workstation. This means it may not be possible to see the entire remote desktop. This issue also occurs when going from a workstation with a low resolution to a workstation with a high resolution. In this case, the user will see the entire remote desktop, but it will be smaller than full screen. Issue #1 Small white bars appear above, below and to the sides of the remote desktop: Steps to Reproduce: 1. Configure expressaccess client to not show the title bar. 2. Login to establish a remote desktop session. Result: The remote desktop session will have small white bars that appear on the top, bottom, and sides. It is, however, visible and usable. 7