ID EXPRESS

Server and Client Software

Release Notes (RN): Version: 01.03

Prepared for:

External Distribution

Prepared by:

Bo Liao

Rodrigue Nyamaswa

Original Release Date:

07/6/2015

Version: 01.03

Release Date:09/15/2018

Confidentiality Notice:

This document contains engineering data that is sensitive toStanley Security Solutions (SSS).

ID EXPRESS

Server and Client Software

Release Notes (RN): Version: 01.03

Table of Contents
ParagraphPage
1Overview
2Known Issues
3Revision 2.2.6 – 07/06/2015
4Revision 2.2.5 – 03/04/2015
5Revision 2.2.4 – 12/18/2014
6Revision 2.2.2 – 2/22/2012
7Revision 2.2.0 – 6/31/2011

Page 1

ID EXPRESS

Server and Client Software

Release Notes (RN): Version: 01.03

1Overview

This document describes the individual revision information that has occurred for ID EXPRESS Server and Client Software Version 01.02 and01.01.

2Known Issues

IPv6 is not working, due to max length allowed in software currently is 30, which should be 39 (8*4+7). As of 03/10/2015.

ID Express Server needs to do ‘web cache’ clean after server installation, if the GUI and Transaction Report has repeated Kiosk Logo appeared in the header.

3Revision 2.2.6 – 07/06/2015

  1. Feature:
  1. ID Express Server Installation Upgrade from older version, can have the ID Expresss Server Configuration File being relocated to C:\ProgramData\Stanley, an AppData directory, which is more ideal for application-specific data.
  1. Feature:
  1. ID Express Server Configurator can still open and use the Configuration File which has been used by older version of ID Express.
  1. Feature:
  1. If the ID Express installation for both server and client (i.e. kiosk) side is an Upgrade Installation(i.e. Installation on top of previous old version), the installation will automatically detect older version and uninstall it and installing the newer version.
  1. Feature:
  1. The Welcome message on the Welcome page can show up whatever the application user type in for this message the ID Express Server Configurator.

4Revision 2.2.5 – 03/04/2015

  1. Feature
  2. The Kiosk WatchDog can power cycle the Encoder when the WatchDog kicking start the IDExpress Kiosk program.
  3. Feature
  4. The Encoder will be power cycled by U451 at Windows startup, this is done by Kiosk client installation writing a task, ResetEncoder_byUSBm451, to Task Scheduler, so that when Windows is restarted after installation, this new Task in Task Scheduler will run U451 to reset the Encoder.
  5. Feature
  6. Allow the user password length changed from 20 to 64.

5Revision 2.2.4 – 12/18/2014

This revision resolved 7 items:

  1. Feature
  2. RM Track # 1466: Add Ipv6 Support to IDExpress.
  3. Feature
  4. RM Track # 1988: LDAP Auth Failed > Custom Message is not linked to SignIn page. Implemenation of the message in the case of LDAP Auth Failure was missing.
  5. Feature:
  6. RM Track # 1989: Custom Page with ID Express after successful transaction. Different logic in the case of Timeout vs button click in the past, client requested the timeout to mirror the Clear button click logic.
  7. Feature:
  8. RM Track # 1990: Custom Page with ID Express after failed transaction. Different logic in the case of Timeout vs button click in the past, client requested the timeout to mirror the Clear button click logic.
  9. Feature:
  10. RM Track # 1991: Keyboard needs to expand to be easier to use. Keyboard previously only occupied a set width. Will now expand to the the available width of the screen, excluding about 5% of each side.
  11. Feature:
  12. RM Track # 1998: Recent Windows 7 Update caused COM Control issue. A recent Windows 7 Update has caused the COM control to not load properly, causing issues in the system. Resolution is changing a few Windows settings, which are included in the installation and documented here:

HKLM\SOFTWARE\Microsoft\.NETFramework\EnableIEHosting

Also, be sure the ReadMe instructions are executed in correct processor-bit directories. For example, there are different settings for 64bit vs 32bit on the Security settings (CASPOL script will run in installer now). There is a new step (5) to ensure proper configuration when .NET 4.5 is installed already.

  1. Feature:
  2. Registry Access on 64bit machines vs 32bit machines. Noticed some issues accessing registry in 64bit machines vs 32bit machines and now are building all components the same where possible. In one single situation, the Launcher application must build separate 32 and 64 bit versions, however, the Client Configuration tool will make the determination which one to use when the change is made to launch Kiosk at startup.
  1. Feature:
  2. Move Kiosk.Config to AppData Directory. Previous placement was in c:\windows\system32\ which is not ideal for application-specific data. If config file is found there, it will be moved to an AppData directory, whose path is different depending on OS.

For Windows 7/8: C:\ProgramData\Stanley\Kiosk.Config

For Windows XP: C:\Users\AllUsers\Application Data\Stanley\Kiosk.Config

  1. Feature:
  2. Hidden Buttons on Web Pages. Noticed the hidden buttons showing up on the web pages that were previously not showing, seems to have been due to a Windows Update. Applied different hiding logic for these buttons.
  1. Feature:
  2. View Audit Log Information from Server using IPv6. Was an issue when server was utilizing IPv6 and the determination of whether the server was the local machine or not.
  1. Feature:
  2. Post.aspx page encountered an error when Prox Cards were enabled without a device attached. An error was being ignored and caused the Post page to remain. Add exception handling for this error so that navigation can continue.

6Revision 2.2.2 – 2/22/2012

  1. RM Track #1124
  2. Problem: IDExpress doesn’t display user room number assignment after issuing a badge.
  3. Resolution: A checkmark has been added to IDExpress server config to enable displaying room assignment after a badge is issued.
  4. RM Track #1130
  5. Problem:Transaction History Reports stop working after enabling SSL.
  6. Resolution: Transaction History Reports are displayed with SSLON or OFF.
  7. RM Track #1316
  8. Problem: Occasionally, the ID Express takes up so much system resources rendering the BASIS database unavailable.
  9. Resolution: ID Express system resource usage is no longer rendering BASIS database unavailable.
  10. RM Track #1318
  11. Problem: ID Express keeps the cards inserted by users if the encoder fails to validate the card during the encoding process.
  12. Resolution: The ID Express will only keep cards that were pulled from the hopper and then failed the encoding process. Otherwise, all inserted cards will be dispensed regardless of encoding success or failure.
  13. RM Track #1127
  14. Problem: kiosk client repeatedly disconnects and reconnects to the server.
  15. Resolution: Kiosk client will maintain a connection to the server as longer as there is a solid network connection between the two.

7Revision 2.2.0–6/31/2011

  1. RM Track #585
  1. Problem: Occasionally, the ID Express application permanently loses connection to the encoder and as a result the system fails to issue badges
  2. Resolution: A watchdog was implemented to detect this condition and restart the ID Express application and reestablishes connection to the encoder.
  1. RM Track #586
  1. Problem: If a Maintenance Required Error is generated, the system cant recover unless the application is closed and restarted.
  2. Resolution: The system constantly attempts to handle Maintenance Required Error when ever it occurs. If the issue is fixed, the ID Express resumes normal operation without having to restart the system.
  1. RM Track #752
  1. Problem: Client kiosk image allows the monitor to turn off after 20 minutes of inactivity. This lenders the system unusable.
  2. Resolution: New client image keeps the monitor On regardless of activity.
  1. RM Track #753
  1. Problem: Client occasionally crashes during operation.
  2. Resolution: Error handling was implementing to restart the ID Express application if an exception occurs.
  1. RM Track #754
  1. Problem: If a kiosk is configured to issue temp cards and a user unsuccessfully attempts more than 3 times to get a card the client hangs.
  2. Resolution: The ID Express now will return to the main screen after a timeout.
  1. RM Track #757
  1. Problem: Custom logo images don’t show in server configuration tool.
  2. Resolution: ID Express displays custom logos if they are setup in the system
  1. RM Track #759
  1. Problem: The verification field at the client is case sensitive yet it shouldn’t be.
  2. Resolution: The verification field is no longer case sensitive.

Page 1