ReadykeyPROUnlimitedversion64500ReleaseNotes by cU9tSd8U

VIEWS: 41 PAGES: 17

									ReadykeyPRO® Unlimited
    Version 6.4.500


     Release Notes




           1
1.   ReadykeyPRO Unlimited (6.4.500) ................................................................................................................................................... 5
  1.1.      Supported Operating System Requirements Now Enforced ................................................................................................... 5
  1.2.      Upgrades ................................................................................................................................................................................. 5
     1.2.1.    Universal Time Conversion Utility Must be Run on All Systems After Upgrade ............................................................. 5
     1.2.2.   Badge Design Programming with List Builder Lists Will Not Function in BadgeDesigner After Upgrade from
              ReadykeyPRO Unlimited Version 5.12.012 or Earlier ...................................................................................................... 5
2. Versioning Information ...................................................................................................................................................................... 5
  2.1.      Current Access Series (RKP) Firmware and Special Application Versions ........................................................................... 5
  2.2.      Minimum System Hardware Requirements ............................................................................................................................ 5
  2.3.      Supported Operating Systems ................................................................................................................................................. 6
     2.3.1.    Windows XP Professional with Service Pack 3 ................................................................................................................. 6
     2.3.2.    Windows Server 2003 Standard, Service Pack 2 or R2 Service Pack 2 ............................................................................. 6
     2.3.3.    Windows Vista with Service Pack 2 .................................................................................................................................. 6
     2.3.4.    Windows Server 2008 with Service Pack 2 ....................................................................................................................... 6
     2.3.5.    Windows Server 2008 R2 .................................................................................................................................................. 6
     2.3.6.    Windows 7 ......................................................................................................................................................................... 6
     2.3.7.    Service Packs and Critical Patches ..................................................................................................................................... 6
  2.4.      Security Utility........................................................................................................................................................................ 7
  2.5.      Supported Database Systems .................................................................................................................................................. 7
     2.5.1.    Microsoft SQL Server 2005 Express SP3, 32-bit and 64-bit ............................................................................................. 7
     2.5.2.    Microsoft SQL Server 2005 SP3, 32-bit and 64-bit ........................................................................................................... 7
     2.5.3.    Microsoft SQL Server 2008 Express SP1, 32-bit and 64-bit ............................................................................................. 7
     2.5.4.    Microsoft SQL Server 2008 SP1, 32-bit and 64-bit ........................................................................................................... 7
  2.6.      Supported System Components .............................................................................................................................................. 7
     2.6.1.    Internet Information Services (IIS) .................................................................................................................................... 8
  2.7.      VMware Platforms .................................................................................................................................................................. 8
  2.8.      Supported Third-party Components........................................................................................................................................ 8
  2.9.      Antivirus Software Applications ............................................................................................................................................. 8
  2.10.     Supported Web Browser ......................................................................................................................................................... 8
  2.11.     Supported Terminal Services .................................................................................................................................................. 9
  2.12.     OPC Versions ......................................................................................................................................................................... 9
  2.13.     End of Life Products ............................................................................................................................................................... 9
     2.13.1. VeriSoft server and client................................................................................................................................................... 9
     2.13.2. Emergin WirelessOffice ..................................................................................................................................................... 9
     2.13.3. Ultra Scan........................................................................................................................................................................... 9
     2.13.4. Biometric Container (iCLASS/DESfire) smart card applications and card formats .......................................................... 9
     2.13.5. Identix ................................................................................................................................................................................ 9
     2.13.6. Digitize Receivers, Inc: System 3000, 3500, 3505 ............................................................................................................ 9
     2.13.7. HASP parallel dongles ....................................................................................................................................................... 9
     2.13.8. Printers ............................................................................................................................................................................... 9
     2.13.9. Encoder .............................................................................................................................................................................. 9
3. New Features ..................................................................................................................................................................................... 9
  3.1.      General .................................................................................................................................................................................... 9
     3.1.1.    Support for Device Notes ................................................................................................................................................... 9
     3.1.2.    Reports ............................................................................................................................................................................... 9
     3.1.3.    License Administration Login and Password are Encrypted.............................................................................................. 9
     3.1.4.    Advanced Power Reporting and Configuration ................................................................................................................. 9
  3.2.      Access Control ...................................................................................................................................................................... 10
     3.2.1.    Interlock Support.............................................................................................................................................................. 10
     3.2.2.    Device Discovery Console Enhancements ....................................................................................................................... 10
     3.2.3.    Printers and Encoder Support for MAG Cards ................................................................................................................ 10
     3.2.4.    Encoders Supported for Encoding Onity Card Data Using the Lenel (iCLASS) Smart Card Format ............................. 10
     3.2.5.    Reader Groupings are Now Supported............................................................................................................................. 10
     3.2.6.    Strike Follower ................................................................................................................................................................. 10
     3.2.7.    Support for Disabling Intrusion Commands from Alarm Monitoring.............................................................................. 10
     3.2.8.    Support for Galaxy Dimension Intrusion Panels .............................................................................................................. 10
     3.2.9.    Alarm Acknowledgement ................................................................................................................................................ 11
     3.2.10. Alarm Aggregation .......................................................................................................................................................... 11
     3.2.11. Runaway Detection .......................................................................................................................................................... 11
  3.3.      Visitor Management ............................................................................................................................................................. 11
     3.3.1.    Support for Driver’s License Scanning ............................................................................................................................ 11

                                                                                                    2
     3.3.2.    Enhancements to the Documentation ............................................................................................................................... 11
  3.4.      Identity Management ............................................................................................................................................................ 11
     3.4.1.    Support for LG Iris iCAM Encoding ............................................................................................................................... 11
     3.4.2.    Ability to Remove Biometric Data ................................................................................................................................... 11
     3.4.3.    Badge Status Deactivate ................................................................................................................................................... 11
     3.4.4.    Support Added for Fargo DTC400e Printer ..................................................................................................................... 11
     3.4.5.    ScanShell SDK 9.37.4 Now Available on Supplemental Materials Disc ......................................................................... 11
     3.4.6.    Full support for Bioscrypt 4G enrollment and verification readers .................................................................................. 11
4. Known Issues/Updates ..................................................................................................................................................................... 12
  4.1.      General .................................................................................................................................................................................. 12
     4.1.1.    License Bits Removed from the ReadykeyPRO License ................................................................................................. 12
     4.1.2.    Installation Includes Non-essential Sentinel Services ...................................................................................................... 12
     4.1.3.    Modifying or Repairing ReadykeyPRO ........................................................................................................................... 12
     4.1.4.    Database Installation Utility Error with SQL Server 2008 Express 64-bit....................................................................... 12
     4.1.5.    Temporary Files Remain After Installation Has Completed ............................................................................................ 12
     4.1.6.    World Time Zone Default Data Updated ......................................................................................................................... 13
     4.1.7.    Flash Player Removed from Supplemental Materials Disc .............................................................................................. 13
     4.1.8.    Web Application Server Not Recommended with Windows XP, Windows Vista, or Windows 7 .................................. 13
     4.1.9.    Browser-based Application Security ................................................................................................................................ 13
     4.1.10. Column Heading Tooltips Disabled for Windows XP ..................................................................................................... 13
     4.1.11. Windows Public Profile Not Supported with Security Utility ......................................................................................... 13
     4.1.12. ACS.INI File Cannot be Edited by Administrator Group Member .................................................................................. 13
     4.1.13. Bulk User Tool Now Part of Installation.......................................................................................................................... 13
     4.1.14. Error 1905. Module C:\Program Files\ReadykeyPRO\msvbvm50.dll Failed to Unregister ............................................ 13
     4.1.15. FormsDesigner Field Style Border and Inside Edge not Functioning Properly ............................................................... 13
     4.1.16. Drop-down Fields Can Be Configured for PIV and FASC-N in FormsDesigner ............................................................ 13
     4.1.17. Installation Guide neglects to inform installer on how to enable the Application Server role for .NET Framework on
               Windows Server 2008 R2 ................................................................................................................................................ 13
  4.2.      Access Control ...................................................................................................................................................................... 14
     4.2.1.    Incorrect wiring of the LG Iris ICU4000 WIB board may cause damage to hardware .................................................... 14
     4.2.2.    Open Supervised Device Protocol Reader Tamper Switch Monitoring ........................................................................... 14
     4.2.3.    Strike Field States Cutoff on Close .................................................................................................................................. 14
     4.2.4.    Conflict Possible for Aux Output 1 .................................................................................................................................. 14
     4.2.5.    Turnstile Mode Issues Access Granted/Door Used When First Person is in Turnstile and Second Person Presents Badge
                ......................................................................................................................................................................................... 14
     4.2.6.    Low Battery and Tamper Reporting for Schlage Wireless Locks .................................................................................... 14
     4.2.7.    OSDP Reader May Have Incorrect LED Display ............................................................................................................ 14
     4.2.8.    Downstream Encryption Key Download Will Fail if any I/O Modules Are Offline ....................................................... 14
        4.2.9. Area Access Manager (Browser-based Client) Returns a Server Error for a Cardholder if a Field is Added to the
               Cardholder Form .............................................................................................................................................................. 14
     4.2.10. Area Access Manager Browser-based Client Reports Not Supported with Windows Authentication on Windows Server
               2008 or Windows Vista .................................................................................................................................................... 14
     4.2.11. Integrated Intrusion LCD Display of Event History Adds Spurious Event for Alarms with Door Set for Entry Delay .. 14
  4.3.      Identity Management ............................................................................................................................................................ 15
     4.3.1.    Magicard Tango2e Must Use Driver V1.41 ..................................................................................................................... 15
     4.3.2.    ScanShell 1000N Scanner Not Supported with Microsoft Vista ...................................................................................... 15
     4.3.3.    DigiOn24 iCLASS Credentials Encoding Reliability ...................................................................................................... 15
  4.4.      Visitor Management ............................................................................................................................................................. 15
     4.4.1.    Visitor Management Browser-based Client Applications Not Supported with Windows Server .................................... 15
     4.4.2.    After Adding List Builder Items, IIS Must be Restarted .................................................................................................. 15
     4.4.3.    Sign-in Locations Must be Modified ............................................................................................................................... 15
     4.4.4.    Supported Date Format .................................................................................................................................................... 15
     4.4.5.    Searching is Based on the Visitor Last Name .................................................................................................................. 15
     4.4.6.    After Using Basic Search to Find a Visitor, it is Not Possible to Perform the Same Search Again ................................. 15
     4.4.7.    Advanced Search Results are Based on the Last Entry When Two or More of the Same Search Criteria are Selected .. 15
     4.4.8.    Limited Support for Group Visits .................................................................................................................................... 15
     4.4.9.    Group Visit Limitation of 75 Visitors .............................................................................................................................. 15
     4.4.10. When Deleting a Large Group Event, the System May Experience a Slight Wait Time ................................................. 15
     4.4.11. Visitors Can Sometimes be Saved Without Filling in All Required Fields ..................................................................... 16
     4.4.12. A Visitor Management Host User Should Not be Linked with Directory Accounts Associated with Different
               Cardholders ...................................................................................................................................................................... 16
     4.4.13. Login with the Correct User Name and Password Fails if Access to the System is Disabled .......................................... 16

                                                                                                     3
     4.4.14.  A Change in User Permissions Requires Recycling the Application Pool ....................................................................... 16
     4.4.15.  Cardholder Permission to Delete Visits is Required to Remove Visitors from an Event................................................. 16
     4.4.16.  E-mails Do Not Have the Scheduled Time or Visit Key if the Event Was Created in System Administration, ID
              CredentialCenter, or Visitor Management ....................................................................................................................... 16
     4.4.17. A Host and Their Delegate Should be Assigned the Same Segment ............................................................................... 16
     4.4.18. In BadgeDesigner, the Visit Times Indicate that They are UTC When They Are Not .................................................... 16
     4.4.19. Front Desk Has the Error, “The HTTP Request is Unauthorized with Client Authentication Scheme 'Negotiate'. The
              Authentication Header Received from the Server Was 'Negotiate,NTLM'.” ................................................................... 16
     4.4.20. Access Control Badges Retain Previous Access Levels When Reassigned ..................................................................... 16
     4.4.21. Error Messages that Result From Not Having JavaScript Are Not Localized ................................................................. 16
     4.4.22. The Service Trace Viewer Tool is Needed to View the Visitor Management Tracing File ............................................. 16
     4.4.23. Minimum Module Width and PDF417 Correction Are Not Supported ........................................................................... 16
     4.4.24. Only TrueType Fonts Are Supported for Badge Printing ................................................................................................ 16
5.   Copyright and Trademark Notice..................................................................................................................................................... 17




                                                                                           4
1. ReadykeyPRO Unlimited (6.4.500)
This document provides an overview of the features, enhancements and changes available in this release. Installation instructions are
available in portable document format (PDF) on the ReadykeyPRO disc in the ..\Program Files\ReadykeyPRO\doc\ folder.
ReadykeyPRO Unlimited (6.4.500) from this point forward will be referred to as ReadykeyPRO Unlimited.

ReadykeyPRO clients purchased from Bosch no longer ship with the ReadykeyPRO software DVD. ReadykeyPRO installation and
supplemental DVDs are now available for download directly from the Bosch ReadykeyPRO Info Center. To download the
ReadykeyPRO software, visit the Bosch ReadykeyPRO Info Center: http://www.boschsecurity.us/en-us/readykeypro. Download the
ReadykeyPRO software and create a master DVD for all of your client installations.

1.1.       Supported Operating System Requirements Now Enforced
The installation or upgrade of ReadykeyPRO Unlimited will be blocked on any operating system version not specifically listed as
supported in section 2.3, Supported Operating Systems.
To install ReadykeyPRO Unlimited, upgrade to a supported operating system and service pack.

1.2.     Upgrades
Direct upgrades can only be performed two major releases behind the release you’re upgrading to. Therefore, if you are upgrading to
ReadykeyPRO software version 6.4 you must have 6.1. If you have anything older, you must first upgrade to 6.1 before upgrading to
6.4.

Important: Please review each of the following items carefully to determine whether additional steps are needed for your particular
upgrade.

          1.2.1. Universal Time Conversion Utility Must be Run on All Systems After Upgrade
The Universal Time Conversion (UTC) Utility is used to collect World Time Zone information to be used to convert local dates and
times in the system to the new standard UTC time. Standard ReadykeyPRO reports have been converted to use UTC time which
allows users in multiple time zones to see the same data but in their local time. For systems that are being upgraded, any custom
reports and/or custom DataExchange and DataConduIT scripts will need to be updated to account for this change and work properly.
For more information, refer to the Upgrade Guide.

Note: If you have previously run the UTC Utility after a previous upgrade, you should not need to run the utility again.

         1.2.2. BadgeDesign Programming with List Builder Lists Will Not Function in BadgeDesigner After
               Upgrade from ReadykeyPRO Unlimited Version 5.12.012 or Earlier
Any badge layout programming configured in BadgeDesigner that uses controlling fields with List Builder lists will not function after
an upgrade from ReadykeyPRO Unlimited Version 5.12.012 or earlier. This may cause the badge design for newly printed badges that
use any UDF drop-down fields configured with List Builder to be incorrect. To resolve this issue, run the Program Badge Repair
Utility located at \Program Files\ReadykeyPRO\ProgramBadgeRepairUtility.exe after running Database Setup to upgrade your
database.

2. Versioning Information

2.1.      Current Access Series (RKP) Firmware and Special Application Versions
          RKP-500/1000/2000 ISC Version v3.120
          RKP-2210/2220/3300 ISC Version v1.118
          RKP-1100/1200 Series 1 Version v1.04
          *RKP-1100/1200 Series 2 Version v1.31
          RKP-1320 Series 1 Version v1.13
          *RKP-1320 Series 2 Version v1.40
          RKP-1300 Series 1 Download not supported
          *RKP-1300 Series 2 Version v1.40
*Important: Before downloading the firmware in this release to downstream Bosch access control boards, please ensure that DIP
switch or jumper 8 is in the OFF position. Failure to take this step will result in an inability to communicate to these boards until the
switch or jumper position is corrected, and may therefore affect normal operation of your system. By default, boards are shipped with
DIP switch or jumper 8 in the OFF position.

2.2.      Minimum System Hardware Requirements
            Pentium IV 1 GHz Processor
            2 GB RAM

                                                                    5
            DVD-ROM
            USB Port
            1024x768 color display
            6 GB of available space

2.3.       Supported Operating Systems
The following products have been approved with the listed operating systems and system service packs. All new systems shipped from
Bosch will include at least these service pack versions. OPERATING SYSTEM REQUIREMENTS ARE NOW ENFORCED.
Installations attempted on other operating systems will not run.

Note: ReadykeyPRO is a 32-bit application that can be run on some 64-bit systems. 64-bit systems are only supported as listed in this
section.

Please contact ReadykeyPRO Technical Support with any questions regarding compatibility.

        2.3.1. Windows XP Professional with Service Pack 3
Windows XP Professional is approved for all ReadykeyPRO server and client operations.
Windows XP is not recommended for use as the Web Application Server (LS Application Server service) because the number of client
connections to IIS is limited in this operating system.
Windows XP 64-bit is NOT supported.
Windows XP SP3 is supported for communication with HID Edge Devices.
Windows XP SP3 will be called Windows XP, from this point forward, in the ReadykeyPRO Unlimited Release Notes.

        2.3.2. Windows Server 2003 Standard, Service Pack 2 or R2 Service Pack 2
Windows Server 2003 64-bit is NOT supported.
Windows Server 2003 R2 SP2 Standard Edition is supported for communication with HID Edge Devices.
Windows Server 2003 Standard, SP2 or R2 SP2 will be called Windows Server 2003, from this point forward, in the ReadykeyPRO
Unlimited Release Notes.

         2.3.3. Windows Vista with Service Pack 2
Windows Vista 64-bit is NOT supported.
Windows Vista is not recommended for use as the Web Application Server (LS Application Server service) because the number of
client connections to IIS is limited in this operating system.
Windows Vista is not supported for communication with HID Edge Devices.

        2.3.4. Windows Server 2008 with Service Pack 2
Windows Server 2008 SP2 32-bit and 64-bit are supported.
Windows Server 2008 SP2 Standard Edition, 32-bit is supported for communication with HID Edge Devices.
Windows Server 2008 Standard and SP2 will be called Windows Server 2008, from this point forward, in the ReadykeyPRO
Unlimited Release Notes.

        2.3.5. Windows Server 2008 R2
Windows Server 2008 Standard is approved for all ReadykeyPRO server and client operations.
Windows Server 2008 R2 64-bit is supported.
Windows Server 2008 Standard and will be called Windows Server 2008 R2, from this point forward, in the ReadykeyPRO Unlimited
Release Notes.

        2.3.6. Windows 7
Windows 7 Professional and Ultimate are approved for all ReadykeyPRO server and client operations.
Windows 7 is not recommended for use as the Web Application Server (LS Application Server service) because the number of client
connections to IIS is limited in this operating system.
Windows 7 Professional and Ultimate 32-bit and 64-bit are supported.
Windows 7 Professional and Ultimate will be called Windows 7, from this point forward, in the ReadykeyPRO Unlimited Release
Notes.

          2.3.7. Service Packs and Critical Patches
Please visit the ReadykeyPRO Info Center for a complete and up to date list of approved Microsoft Service Packs and Critical Patches
(MS Patches section): http://www.boschsecurity.us/en-us/readykeypro. The Bosch Security Patch Policy located on the Web site
details the specific conditions and frequency of certification for Microsoft Windows Critical Updates.


                                                                  6
Read through this information carefully since it addresses BOTH OPERATING SYSTEMS AND DATABASES.
For all instances, Bosch STRONGLY RECOMMENDS enabling the uninstall option when installing the service pack. There have
been rare instances where communications and database activity have been affected by the installation of a service pack. When these
situations have occurred, uninstalling the service pack resolved the issues.
Bosch also STRONGLY RECOMMENDS backing up your database before performing any service pack installation.

2.4.    Security Utility
Windows Firewall is supported by use of the Security Utility; other third-party firewalls are not supported.

Note: “Windows Security Utility” was renamed “Security Utility”. The Start menu shortcut, user interface, and documentation have
been updated to reflect this change.

The Security Utility allows ReadykeyPRO Unlimited users to take advantage of the capabilities of Windows. The utility must be run
to ensure that the ReadykeyPRO software will continue to function properly. The utility automatically adjusts all settings that affect
the ReadykeyPRO software. It also displays the current system settings, as well as a list of actions required for normal operation of
Bosch software installed on the local computer.

Note: The Security Utility does not open database communication ports.

The Security Utility runs automatically during ReadykeyPRO, Remote Monitor, and Device Discovery Console installations. It must
also be run manually as a maintenance procedure after any of the following changes have been made:
          Windows updates
          Windows service pack changes
          Windows security setting changes

2.5.     Supported Database Systems
For an up-to-date list of tested database systems, refer to the compatibility charts on the ReadykeyPRO Info Center:
http://www.boschsecurity.us/en-us/readykeypro.

Note: When creating or modifying an ODBC connection on a 64-bit operating system, the location where the ODBC Data Sources are
configured is different than on 32-bit operating systems:
          For 32-bit operating systems: Click Start, then navigate to Settings > Control Panel > Administrative Tools > Data
              Sources.
          For 64-bit systems: Navigate to C:\windows\SysWOW64 and run the odbccad32.exe file.

          2.5.1. Microsoft SQL Server 2005 Express SP3, 32-bit and 64-bit
          2.5.2. Microsoft SQL Server 2005 SP3, 32-bit and 64-bit
Note: SQL Server 2005 requires .NET 2.0 as a prerequisite.
          2.5.3. Microsoft SQL Server 2008 Express SP1, 32-bit and 64-bit
Note: Microsoft SQL Server 2008 Express Service Pack 1 is now installed with ReadykeyPRO for systems that do not have a database
installed.
          2.5.4. Microsoft SQL Server 2008 SP1, 32-bit and 64-bit
Note: Microsoft SQL Server 2008 R2 is NOT supported.

2.6.      Supported System Components
            Scan Shell SDK version 9.40.11
            MDAC (REQUIRED)
            Windows XP: MDAC 2.81
            Windows Server 2003: MDAC 2.82
            Windows Vista and Windows Server 2008: MDAC 6.0c
            DirectX (REQUIRED)
            Windows XP and Windows Server 2003: DirectX 9c
            Windows Vista, Windows Server 2008, and Windows 7: DirectX 10
            MSXML 6 (REQUIRED) - MSXML 6 is installed automatically with ReadykeyPRO.
            Adobe Flash Player 9 or later (REQUIRED for Visitor Management Host)
            Microsoft Silverlight 2.0 or later (REQUIRED for Visitor Administration)
            Microsoft .Net 3.5 SP1 (REQUIRED) - Microsoft .Net 3.5 SP1 is installed automatically with ReadykeyPRO when
             installing using the setup.exe file. To shorten the ReadykeyPRO installation time, install Microsoft .Net 3.5 (available on
             the Supplemental Materials disc) prior to installing ReadykeyPRO.

                                                                   7
Note: If the Microsoft .Net 3.5 SP1 installation fails during the ReadykeyPRO installation on Windows Vista or Windows Server
2008, you must run the System Update Readiness Tool available from Microsoft: http://support.microsoft.com/kb/947821. To prevent
this issue, verify that the Windows Update service is turned on.

         2.6.1. Internet Information Services (IIS)
IIS is REQUIRED for the Web Application Server.
          Windows XP and Windows Server 2003: IIS 5 and 6 (Windows XP is not recommended for the Web Application
              Server)
          Windows Vista and Windows Server 2008: IIS 7 (Windows Vista is not recommended for the Web Application Server)
          Windows Server 2008 R2: IIS 7.5
The following minimum settings are required for the browser-based applications to function properly:
          Common HTTP Features
              o Static Content
              o Default Document
              o Directory Browsing
              o HTTP Errors
              o HTTP Redirection
          Application Development
              o ASP.NET
              o .NET Extensibility
              o ISAPI Extensions
              o ISAPI Filters
          Security
              o Windows Authentication
              o Request Filtering
          Management Tools
              o IIS Management Console
              o IIS 6 Metabase Compatibility
              o IIS 6 WMI Compatibility

2.7.     VMware Platforms
            VMware ESX Server and ESXi Server 3.5.x and 4.0.x for all ReadykeyPRO services and database server with software-
             based license only
            VMware Server 1.0.x and 2.0.x on ES and ADV systems with SQL Express only
            VMware Workstation 6.5.x

Note: VMware is supported for ReadykeyPRO standard systems.

2.8.     Supported Third-party Components
            Crystal Reports XI (11 and 11.5) Release 2
            Adobe Reader 9.3

2.9.    Antivirus Software Applications
Bosch does not certify any antivirus software to be used with ReadykeyPRO.

Note: The \LicenseServerConfig\Licenses folder on the License server should also be excluded, since it will sometimes corrupt the
license file.

         McAfee Virus Scan
        McAfee Virus Scan can be recommended, but is not tested or certified at Bosch and is installed at the user’s risk.

         Symantec Endpoint Protection
        Symantec Endpoint Protection is used internally at Bosch and can be recommended, but is not certified.

         Trend Micro OfficeScan Corporate Edition version 8.0
        Trend Micro OfficeScan can be recommended, but is not tested or certified at Bosch and is installed at the user’s risk.

2.10.    Supported Web Browser
            Internet Explorer 7.0 or 8.0 (REQUIRED for License Administration and browser-based applications)


                                                                  8
2.11.    Supported Terminal Services
ReadykeyPRO Unlimited will support Terminal Services. This support is a licensed feature. Please contact ReadykeyPRO Technical
Support with any questions regarding compatibility.
         Citrix is not supported within Windows XP or Windows Vista

2.12.     OPC Versions
             OPC Data Access 2.0
             OPC Alarms and Events 1.0

2.13.     End of Life Products
The following products have discontinued support:
         2.13.1. VeriSoft server and client
         2.13.2. Emergin WirelessOffice
         2.13.3. Ultra Scan
         2.13.4. Biometric Container (iCLASS/DESfire) smart card applications and card formats
         2.13.5. Identix
         2.13.6. Digitize Receivers, Inc: System 3000, 3500, 3505
         2.13.7. HASP parallel dongles
HASP parallel hardware keys (dongles) are no longer supported. If you still are using a HASP hardware key, you need to contact
Bosch to have your HASP dongle replaced before upgrading.
         2.13.8. Printers
Support has been discontinued for the following printers:
          Datacard Magna
          Dymo 330 and 440
          Evolis Pebble
          Nisca 5100, 5200, and 5310
          Zebra 420 and 420i
         2.13.9. Encoder
Support has been discontinued for the following encoder:
          Nisca PR5301 magnetic stripe encoder for the Nisca PR5300 and PR5310 card printers


3. New Features

3.1.      General
         3.1.1. Support for Device Notes
A device notes field has been added for access panels, readers, fire, receivers, and intrusion detection. It is limited to less than 2000
characters. The information entered in this field will be displayed for the device in Alarm Monitoring.

         3.1.2. Reports
The following updates have been made to reports:
          A new Notes field has been added to the Access Panels and Hardware Panels reports.
          The reader Name field has been expanded to 96 characters and reports have been updated to accommodate the new
              length.
          The "Access Denied Events" and "Access Denied Events, by Reader" reports now include the following events:
              o Interlock Area Busy
              o Cannot Open Door: Interlock Area Busy
              o Exit Request Denied: Interlock Area Busy
              o DURESS - Interlock Area Busy

          3.1.3. License Administration Login and Password are Encrypted
The License Administration login and password are encrypted when they are passed to the License Server. The hash will not be the
same data even with the same logon credentials on different systems. This is a requirement for U.S. government DIACAP
certification.

         3.1.4. Advanced Power Reporting and Configuration
Configurations are available per panel for charging parameters, warning and cutoff voltages, and battery testing. Specific events are
also provided.
                                                                  9
3.2.      Access Control
          3.2.1. Interlock Support
Interlocked areas can be configured, allowing only one door to be opened at a time within the area. This is available with the RKP-
2220. It can only be enabled for local anti-passback and is unavailable for global anti-passback.

         3.2.2. Device Discovery Console Enhancements
             Support for Lantronix Devices
Integrated Lantronix Device Server, support Discovery, Ping, Get Version, Reboot Device and Change IP Address.

           Support for Bosch Access Control panels
Bosch Access Control panels (RKP-2220), support Discovery, Ping.

             Device Type capability
Display different icon by Device Type. Use Device Type as condition of Group functionality and Sort functionality.

          Device Filter capability
Add Filter functionality, discover and display devices according to the selection of Device Type and Brand.

          Save Credentials capability
Add Save Credentials functionality, save the Credentials that changed by user on the local machine, and use them when the certain
device is discovered next time.

          Use of Bonjour
Use of Bonjour is currently not officially supported and issues may result. If issues occur while Bonjour is enabled, disable Bonjour
before running the Device Discovery Console.

         3.2.3. Printers and Encoder Support for MAG Cards
The following printers and encoders are supported for use with MAG cards:
          Fargo HDP5000 printer equipped with an ISO magnetic encoder, using driver version 2.0.0.5 or later
          Magicard Rio/Tango 2e card printer equipped with an ISO magnetic encoder, using driver version 1.3.4.0 or later
          A MSR206 magnetic stripe encoder can be used for encoding Onity card data.

         3.2.4. Encoders Supported for Encoding Onity Card Data Using the Lenel (iCLASS) Smart Card Format
If you are encoding the Onity data to Book 0, you can use any iCLASS encoder however Rev.B or later is required for Book 1.
          HID (iCLASS) encoder (If you are encoding the Onity data to Book 0, you can use a card printer equipped with the HID
              (iCLASS) PROG encoder Rev.A. The HID (iCLASS) PROG encoder Rev.B can be used for encoding the Onity data to
              either Book 0 or Book 1 however Rev.B or later is required for Book 1.
          DigiOn24 (iCLASS) encoder
          OMNIKEY (iCLASS) encoder

          3.2.5. Reader Groupings are Now Supported
Reader groupings allow you to categorize readers so that you can perform searches from within System Administration to locate
specific sets of readers.

          3.2.6. Strike Follower
An output for a reader can now be overridden so that it is configured to activate and deactivate timed with a door strike. It can be set
for a delay time and/or pulse.

         3.2.7. Support for Disabling Intrusion Commands from Alarm Monitoring
A "Disallow intrusion commands from Alarm Monitoring for all users" option has been added to the General section of the license.
This option configures the system so that intrusion commands may only be performed from the HID command keypads. By default,
intrusion command functionality is available. If you order SWG-1620, the ability to use the intrusion commands will be turned off in
Alarm Monitoring. This is a requirement for DIACAP certification.

        3.2.8. Support for Galaxy Dimension Intrusion Panels
The Galaxy Dimension GD48 and Galaxy Dimension GD520 intrusion panels are now supported, with the following limitations:
        - The Door Control Module (DCM) for Galaxy Dimension panels is not supported.
        - Galaxy audio modules are not supported
                                                           10
         - The Galaxy Ethernet module is not supported for the Galaxy Dimension panels
         - The new Dimension Zone Faulted status is not supported

         3.2.9. Alarm Acknowledgement
In addition to the Main Alarm Monitoring window, alarms can now be acknowledged from the Trace Monitor, Pending Alarms, and
Video Verification windows even if they are no longer present in the Main Alarm Window. The procedure for acknowledging alarms
from these new locations is the same as the Main Alarm Monitoring window procedure.

         3.2.10. Alarm Aggregation
Alarms of the same type can now be combined into one line in Alarm Monitoring for easier viewing. The alarm window columns will
display the most recent alarm info. Actions will still be applied for individual alarms. Aggregation is only applied to the Main Alarm
window; users can still perform a trace to see all alarms. This feature is configured for individual alarm types on the Alarm Definitions
form in System Administration.

         3.2.11. Runaway Detection
The Runaway Detection feature monitors the system for devices that have entered a “runaway” condition characterized by multiple
alarms of the same type coming from a device during a user-defined time interval. Once this state has been identified it will be
indicated in Alarm Monitoring by an alarm and by a change in state in the hardware tree. While in this state, the Communication
Server stops sending the runaway events to Alarm Monitoring stations.

3.3.      Visitor Management
         3.3.1. Support for Driver’s License Scanning
Visitor Management now supports driver’s license scanning. In the Front Desk, visitors can be searched using the last name scanned
from a driver’s license. Scanned data can be used to replace outdated visitor information. This requires the ScanShell 1000 scanner.
However, it cannot be used in conjunction with the SnapShell scanner — only one of these devices should be connected to the
computer at a time. The SnapShell scanner can be used to scan business cards.

         3.3.2. Enhancements to the Documentation
Visitor Management documentation has been improved. A comprehensive table was created containing detailed breakdown of which
permissions are required for each function of the system.


3.4.      Identity Management
         3.4.1. Support for LG Iris iCAM Encoding
The LG Iris iCAM may now be configured to use its internal reader as an encoder.

        3.4.2. Ability to Remove Biometric Data
Users may want to remove biometric data for security purposes. ReadykeyPRO can be configured so that after a successful encoding
of an LG iris template, the biometric data may be removed.

          3.4.3. Badge Status Deactivate
All active badges can be configured to change to another badge status when the deactivate date has passed. It is possible to configure
this system-wide or per badge type.

        3.4.4. Support Added for Fargo DTC400e Printer
Fargo DTC400e printer is now supported for prox badge number import or iCLASS serial number import. The DTC400e with
iCLASS module is supported for serial number import only; the iCLASS badge number will not be imported. A new feature allows
customer-provided cross-reference table to be used to read iCLASS serial number, look up badge number in table, and store badge
number in ReadykeyPRO badge record. Utilizing this workflow requires significant customer-provided scripting. Contacting Bosch’s
ReadykeyPRO Technical Support is highly recommended to aid in implementing this workflow.

        3.4.5. ScanShell SDK 9.37.4 Now Available on Supplemental                   Materials Disc
ScanShell SDK 9.37.4 is now available on the Supplemental Materials Disc.

         3.4.6. Full support for Bioscrypt 4G enrollment and verification readers
ReadykeyPRO now supports Bioscrypt 4G enrollment and verification readers. Through integration with Bioscrypt V-Flex 4G, or V-
Station 4G fingerprint readers, ReadykeyPRO has the ability to seamlessly capture biometric information (fingerprint) and create
biometric templates during the cardholder enrollment process. ReadykeyPRO supports Bioscrypt V-Flex 4G and V-Station 4G for V-
Smart (iCLASS/MIFARE) encoding.

                                                                   11
Through integration with Bioscrypt V-Flex 4G, or V-Station 4G fingerprint readers, ReadykeyPRO has the ability to verify the
identity of the cardholder. The readers shall be able to verify templates that are panel-based and card-based (MIFARE and iCLASS).

4. Known Issues/Updates

4.1.      General
         4.1.1. License Bits Removed from the ReadykeyPRO License
The following items will be enabled by default and will no longer require licensing:
          E-mail Support
          CCTV Support
          Guard Tour
          Video Verify Support
          Program Badge
          Image Effects Gallery
          Cardholder Image Export
          Chromakey/Ghosting
          Maximum Number of Cardholders with Directory Accounts
          Handkey iCLASS Support
          Handkey MIFARE Support
          TWIC (DESFire) Smart Card Application Support
          Integrated Engineering Access Control Support
          Integrated Engineering SmartTOUCH Support
          LDAP Interface Server
          Device Discovery Console

         4.1.2. Installation Includes Non-essential Sentinel Services
The Sentinel Protection Installer run during the ReadykeyPRO installation includes services that are not required. The Sentinel
Protection Server, Sentinel Keys Server, and Sentinel Security Runtime can be safely removed from your system using the Sentinel
Protection Installer from Control Panel > Add or Remove Programs.

         4.1.3. Modifying or Repairing ReadykeyPRO
The method for repairing or modifying a ReadykeyPRO installation has changed. Prior to ReadykeyPRO 6.4.500, the options to
modify or repair a ReadykeyPRO installation were available by going to Windows Control Panel, selecting Add or Remove
Programs, selecting ReadykeyPRO, and clicking [Change]. The Modify and Repair options have been removed from Control Panel.
Instead, you must re-run the ReadykeyPRO installation setup in order to use these options.

If you choose to repair ReadykeyPRO you will need to reset your DSN name, license server name, and any other custom setting made
to the ACS.INI file and/or application.config file. You should back up the ACS.INI file and/or application.config file before doing
any maintenance.

If you are using the repair option when re-installing ReadykeyPRO where either the Application Server or Database Setup features
have been installed then you will receive a warning telling you to back up specific system files. These files are listed in the warning
message and will be different for each installation. Make sure to back up these files or you will lose critical system information
located within the files.

        4.1.4. Database Installation Utility Error with SQL Server 2008 Express 64-bit
The Database Installation Utility may return the following error during installation of a SQL Server 2008 Express 64-bit database:
“An error has occurred reading from the registry.”
To properly install the SQL Server 2008 Express 64-bit database:
    1. Click [OK] to close the error message.
    2. Click [Browse] to specify the Path to copy database files to.
    3. In the Browse dialog, locate the database install directory, then click [OK]. This should be similar to: \Program
        Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA.
    4. Click [OK] to install the database. You should receive a successful message.

         4.1.5. Temporary Files Remain After Installation Has Completed
Some components needed by ReadykeyPRO may leave temporary files on the system root drive after the installation. More
information can be found here: http://support.microsoft.com/kb/950683.

                                                                    12
          4.1.6. World Time Zone Default Data Updated
World time zone default data has been updated according to the changes noted on Microsoft’s Web site:
http://support.microsoft.com/kb/955839

         4.1.7. Flash Player Removed from Supplemental Materials Disc
Flash Player is required for some browser-based applications. It is no longer available on the Supplemental Materials disc and can be
downloaded from: http://www.adobe.com/support/flashplayer/downloads.html#fp10.

          4.1.8. Web Application Server Not Recommended with Windows XP, Windows Vista, or Windows 7
The Web Application Server (LS Application Server service) is not recommended with Windows XP, Windows Vista, or Windows 7.
These operating systems have a limit on the number of clients that can connect to IIS.
Note: The Web Application Server can only be installed using a custom installation; it is not installed by default. If the service is
installed on Windows Vista, you may experience problems when attempting to repair or uninstall ReadykeyPRO.

          4.1.9. Browser-based Application Security
If using browser-based applications, disable parent paths for the Web server for heightened security.

         4.1.10. Column Heading Tooltips Disabled for Windows XP
Tooltips are not available for column headings in ReadykeyPRO running on Windows XP.

         4.1.11. Windows Public Profile Not Supported with Security Utility
The Public Network profile of the Windows Firewall introduced in Windows Vista is not supported with the Security Utility. If you
want to use this profile you must manually make all changes as described in the Security Utility Release Notes. These release notes
are available from the [More Info] button in the Security Utility.

         4.1.12. ACS.INI File Cannot be Edited by Administrator Group Member
By default, the Admin account does not have permission to save the ACS.INI file in Windows Vista, Windows 7, or Windows Server
2008. To work around this issue, add the Admin user to the ACS.INI file security settings and allow full control or run the application
that you use to edit the ACS.INI file (i.e., Notepad) using the “Run As Administrator” option.


          4.1.13. Bulk User Tool Now Part of Installation
The Bulk User Tool has been added to the ReadykeyPRO Installation, and will be installed on every system including custom
installations. The Bulk User Tool is available from the Windows Start menu after installation.

The user logging into Visitor Management Host must be linked to a cardholder. This cardholder must be paired with a user. This is
typically done in System Administration by creating a directory, linking the cardholder with the directory account, then linking the
user to that same directory account. The Bulk User Import Tool is for quickly adding and linking users to their cardholder directory
accounts.

          4.1.14. Error 1905. Module C:\Program Files\ReadykeyPRO\msvbvm50.dll Failed to Unregister
This error may occur when upgrading to ReadykeyPRO Unlimited on Windows Vista. This error can be safely ignored with no side
effects to the installation.

          4.1.15. FormsDesigner Field Style Border and Inside Edge not Functioning Properly
In order to support recently introduced changes to the user interface, the ability to turn off a sunken edge border for a control in
FormsDesigner has been disabled.

         4.1.16. Drop-down Fields Can Be Configured for PIV and FASC-N in FormsDesigner
In FormsDesigner it is possible to specify both PIV and FASC-N configurations for drop-down fields. Only PIV or FASC-N should
be configured, not both. Please choose one to configure. This issue will be addressed in a future release.

         4.1.17. Installation Guide neglects to inform installer on how to enable the Application Server role for
               .NET Framework on Windows Server 2008 R2
The Installation Guide's instructions for SQL Server 2008 tell the user to let the SQL Server 2008 setup install .NET Framework 3.5
prerequisite, but if the user is on the Windows Server 2008 R2 64-bit OS, then it cannot and the user must enable the Application
Server Role instead.


                                                                    13
4.2.      Access Control

        4.2.1. Incorrect wiring of the LG Iris ICU4000 WIB board may cause damage to hardware
Power from the Bosch Reader Interface Module should not be wired to the WIB board. A new diagram has been provided. Consult the
OEM Device Configuration Guide for proper wiring and configuration of LG Iris devices.

When AFC Office when enter is enabled on a lock and Office when exit is not, the lock will only relock (following an entry event)
when either the Relocking timer expires or the Deadbolt ends AFC office mode option is enabled and invoked. When both AFC
Office when enter and Office when exit are enabled on a lock, the lock will also relock when a valid card is used again, following the
entry of exit events.

        4.2.2. Open Supervised Device Protocol Reader Tamper Switch Monitoring
Open Supervised Device Protocol (OSDP) reader tamper switch monitoring now works reliably after Update Hardware Status is
performed.

        4.2.3. Strike Field States Cutoff on Close
For HID Edge devices, the Strike field states Cutoff on close. The actual reader strike output will cutoff on open in all cases.

          4.2.4. Conflict Possible for Aux Output 1
The user interface currently allows configuration of both Tailgate and Pre-alarm mode, both of which use Aux Output 1. These
features should not be used at the same time due to a conflict with Aux Output 1.
Note: Not all pre-alarm configurations require Aux Output 1. The pre-alarm configuration that does use Aux Output 1 should not be
used when using Tailgate or Alarm Shunt.

                        Mode Issues Access Granted/Door Used When First Person is in Turnstile and Second
         4.2.5. Turnstile
               Person Presents Badge
Turnstile Mode now pulses strike even when turnstile status input is asserted.

        4.2.6. Low Battery and Tamper Reporting for Schlage Wireless Locks
To enable low battery and tamper reporting for Schlage wireless locks, the Keypad Type on the reader tab must be set to LNL-2020
w/ Tamper. This setting can also be used with the Schlage WRI wireless reader interface, but this will disable keypad support.

         4.2.7. OSDP Reader May Have Incorrect LED Display
If power is lost to an Open Supervised Device Protocol (OSDP) reader, but power to the Bosch reader interface is maintained, the
LED display pattern may be incorrect until some access activity takes place.

         4.2.8. Downstream Encryption Key Download Will Fail if any I/O Modules Are Offline
If any Series 2 I/O modules (RKP-1300, RKP-1320, RKP-1100, RKP-1200) are offline when the Download Encryption Keys
command is issued from Alarm Monitoring, the command will fail and some or all of the boards will not receive the keys. To work
around this issue, ensure all boards are online or if a board is known to be offline delete it from the system to download keys to the
other boards.

                   Access Manager (Browser-based Client) Returns a Server Error for a Cardholder if a Field is
         4.2.9. Area
               Added to the Cardholder Form
Area Access Manager (Browser-based Client) will return the following server error for a cardholder if a field is added to the
Cardholder form:
“A server error has occurred. Please see your system administrator.”
When a form is updated, IIS must be restarted along with the LS Application Server. If you receive this error, restart IIS and the LS
Application Server.

         4.2.10.Area Access Manager Browser-based Client Reports Not Supported with Windows
               Authentication on Windows Server 2008 or Windows Vista
Reports will not run properly from Area Access Manager (Browser-based Client) with Windows Authentication on Windows Server
2008 or Windows Vista. For these operating systems, only SQL authentication is supported with browser-based reports.

         4.2.11. Integrated Intrusion LCD Display of Event History Adds Spurious Event for Alarms with Door
               Set for Entry Delay


                                                                   14
When utilizing the new Intrusion Mask Groups, an alarm caused by a Door Status event set for "Trigger" point mode will result in an
extra event being displayed in the LCD keypad event history. The extra event will be labeled "256 TYPE ERROR" and have the same
time as the door event, and can be ignored. This issue will be addressed in a future firmware version.

4.3.      Identity Management

         4.3.1. Magicard Tango2e Must Use Driver V1.41
Magicard Tango2e driver V1.42 has a known issue with the installation of magapi.dll. Driver V1.41 is available on the Supplemental
Materials disc and should be used instead.

        4.3.2. ScanShell 1000N Scanner Not Supported with                Microsoft Vista
The ScanShell 1000 scanner is NOT supported in Windows Vista.

          4.3.3. DigiOn24 iCLASS Credentials Encoding Reliability
The reliability of iCLASS credentials encoding using DigiOn24 units has been addressed by firmware v4.92. This firmware only
works on DigiOn24 modules equipped with ROHS HID OEM units. The ROHS units have the word “iCLASS” in gold-colored
lettering, and the non-ROHS units have silver-colored lettering. The firmware can be upgraded by the DigiOn FW Upgrade Utility
(EncoderFirmwareUpgrade(V492).zip), available on the Supplemental Materials disc.

4.4.      Visitor Management

         4.4.1. Visitor Management Browser-based Client Applications Not Supported with Windows Server
Due to the default IE enhanced security settings preventing the use of some browser components, Visitor Management Host and
Administration are not supported on Windows Server 2003 or Windows Server 2008. The IE security settings can be adjusted to
provide support but it is not recommended due to potential insecure IE security setting modifications.

          4.4.2. After Adding List Builder Items, IIS Must be Restarted
List Builder items sometimes do not appear in user-defined drop-down fields. After making changes in List Builder, it is necessary to
restart IIS.

          4.4.3. Sign-in Locations Must be Modified
For visits scheduled in System Administration, ID CredentialCenter, or Visitor Management, the sign-in location does not exist. When
these visits are modified in Host or Front Desk, a sign-in location must be provided.

         4.4.4. Supported Date Format
“Short date, no time” (seen in FormsDesigner) is the only date format supported for date fields in Visitor Management Host.

        4.4.5. Searching is Based on the Visitor Last Name
Performance has been enhanced by limiting basic searching to the visitor’s last name.

         4.4.6. After Using Basic Search to Find a Visitor, it is Not Possible to Perform the Same Search Again
After a search has been performed in Visitor Management Host, the search results must be cleared and criteria must be entered to
conduct a second search, even if it is the same exact search.

         4.4.7. Advanced  Search Results are Based on the Last Entry When Two or More of the Same Search
               Criteria are Selected
When the same search criteria are selected in advanced search, only the last entry will apply to the search.

         4.4.8. Limited Support for Group Visits
When group visits are scheduled through the Front Desk or Host, they will appear in the System Administration, ID CredentialCenter,
or Visitor Management user interface as single visits. However, these single visits cannot be changed through this user interface.

        4.4.9. Group Visit Limitation of 75 Visitors
Group visits are limited to a maximum of 75 invited visitors to ensure reliable performance.

         4.4.10. When Deleting a Large Group Event, the System May Experience a Slight Wait Time
When a large group event is deleted, notification e-mails are sent for the participants. This may require some extended wait time while
the system performs this function.

                                                                   15
           4.4.11. Visitors Can Sometimes be Saved Without Filling in All Required Fields
If a field is required, all users should have permission to view and edit it. When a user does not have permission to view a required
field (configured through the Field/Page Permission Group), it will not be visible in Visitor Management Host; however, saving a
newly added visitor will be possible even though the required field is blank.

         4.4.12. A Visitor Management Host User Should Not be Linked with Directory Accounts Associated
               with Different Cardholders
Directory accounts associated with different cardholders should not be linked to the same user. This will prevent that user from
accessing Visitor Management Host.

         4.4.13. Login with the Correct User Name and Password Fails if Access to the System is Disabled
When the correct user name and password has been typed in and there is a failure to log in, check that the user account has access to
the system. This is configured on the Users > General tab in System Administration or ID CredentialCenter.

         4.4.14. A Change in User Permissions Requires Recycling the Application Pool
Changes made to permissions are not immediately applied for Visitor Management Host. Recycling the application pool in IIS will
allow the correct permissions to be applied.

        4.4.15. Cardholder Permission to Delete Visits is Required to Remove Visitors from an Event
When removing invited visitors from a scheduled event, you must have this delete permission. Even though the event is being
modified, removing a visitor from a scheduled event is equivalent to deleting an event.

         4.4.16.E-mails Do Not Have the Scheduled Time or Visit Key if the Event Was Created in System
               Administration, ID CredentialCenter, or Visitor Management
When an event has been created in System Administration, ID CredentialCenter, or Visitor Management, the notification e-mail does
not have the scheduled time or visit key. Visit events should be scheduled in Visitor Management Host or Front Desk.

         4.4.17. A Host and Their Delegate Should be Assigned the Same Segment
In a segmented system, the host and the delegate must be in the same segment. If they are on different segments, events may appear to
be missing from one or both calendars.

         4.4.18. In BadgeDesigner, the Visit Times Indicate that They are UTC When They Are Not
The database fields, “Visit Time In UTC” and “Visit Time Out UTC” will be printed in the time zone of the visit. They will not be
printed in UTC time.

         4.4.19. Front Desk Has the Error, “The HTTP Request is Unauthorized with Client Authentication
               Scheme 'Negotiate'. The Authentication Header Received from the Server Was 'Negotiate,NTLM'.”
This error typically occurs when attempting to log into the Front Desk on a computer which is on a different domain. Typically, one
security policy is supported (regardless of the IIS setting). The workaround is to create a second service with a different security
policy and second FrontDeskClickOnce deployment site with updated policies and endpoints. For more details, refer to the Installation
Guide. The server should also be added to the Internet Options list of trusted intranet sites.

         4.4.20. Access Control Badges Retain Previous Access Levels When Reassigned
When an access control badge is assigned to a visitor being signed in, it retains the access levels currently configured for the badge.
Signing in/out a previous visitor with the badge does not change the access levels.

         4.4.21. Error Messages that Result From Not Having JavaScript Are Not Localized
Visitor Management requires that JavaScript be enabled in the browser. When it is not, the error message: “This application requires
JavaScript. Contact your administrator,” will appear not localized.

       4.4.22. The Service Trace Viewer Tool is Needed to View the Visitor Management Tracing File
Windows Communication Foundation Service Trace Viewer Tool (SvcTraceViewer.exe) should be used to view the Visitor
Management tracing file (Idvm.svcLog) on the server. This can be obtained from Microsoft’s Web site as part of the Windows SDK.

       4.4.23. Minimum Module Width and PDF417 Correction Are Not Supported
When printing bar codes on badges the minimum module width and PDF417 correction are not supported.

         4.4.24.   Only TrueType Fonts Are Supported for Badge Printing

                                                                   16
Badges for Visitor Management should be designed using TrueType fonts. Other fonts may cause an error when previewing or
printing the badge.

5. Copyright and Trademark Notice
Bosch ReadykeyPRO® Unlimited Release Notes, product version 6.4.500.
Copyright © 2010 Lenel Systems International, Inc. Information in this document is subject to change without notice. No part of
this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
the express written permission of Lenel Systems International, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance with the terms
of that agreement.
Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries. Integral and FlashPoint are trademarks of Integral Technologies, Inc.
Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc. Oracle is a registered trademark of Oracle
Corporation. Other product names mentioned in this User Guide may be trademarks or registered trademarks of their respective
companies and are hereby acknowledged.
Portions of this product were created using LEADTOOLS © 1991-2010 LEAD Technologies, Inc. ALL RIGHTS RESERVED.
ReadykeyPRO includes ImageStream® Graphic Filters. Copyright © 1991-2010 Inso Corporation. All rights reserved.
ImageStream Graphic Filters and ImageStream are registered trademarks of Inso Corporation.




                                                                 17

								
To top