V6.3 /V6.31 SR1 versus V6.3 ==================== - Fix: Autoupdater - Autoupdater would sometimes crash. This is fixed. - Fix: Sync Service - Sync Service would not process single User Group Changes. This is fixed. - Fix: System User - System User Module would sometimes freeze. This is fixed. - Fix: Data Tier Interfacing - The DeleteCard procedure had a a schema bug. This is fixed. - Fix: Data Tier Interfacing - The SyncPerson procedure had a a schema bug. This is fixed. - Fix: Batch Import - A string / value pair was missing from the database on new installs. This is fixed. - Fix: Sync Service - Sync Service would not process single User Group Changes. This is fixed. - Fix: Lock Program - Low Battery threshold was changed to allow for a longer warning before the lock dies. - Change: Lock Program - Anti-passback was changed to relock on door close instead of opening - Change: Access Keycards - Access Keycards now allows for UserIDs up to 20 characters long - New Feature: Access Keycards- Support for new KDE Encoder - New Feature: Autoupdater - Support for new KDE Encoder V6.3 /V6.31 versus V6.2 ==================== NOTICE: v6.3/6.31 can ONLY upgrade 6.2/6.21, 6.1 SR1/6.11 SR1 or 5.5 SR15 / 5.51 SR15. No other upgrade path is valid. Upgrade any pre 5.5 SR15 system to 5.5 SR15 first. Upgrade any 6.1 system to SR1 first. NOTICE: WINDOWS 7 - If Windows prompts you to "Reinstall in Compatibility Mode" for System Setup or System User module (or any other module), ANSWER WITH: "THIS PROGRAM INSTALLED CORRECTLY." KNOWN ISSUE: WINDOWS AERO - The System User and Unlock Code Modules do not show a glass frame. KNOWN ISSUE: SQL 2008 R2 - 64 bit SQL 2008 R2 cannot create a linked server to Sybase and therefore cannot upgrade 5.5 SR15. The upgrade must be done in a 32 bit environment. KNOWN ISSUE: SERVER 2008 R2 - Sometimes the installer will crash with a "tmp" file error. This is generally a permsions issue that can be resolved by manually creating a database named "PERSONA" and then running the installer again. KNOWN ISSUE: System Users - System Users sometimes "hangs" when saving a user. Close/re-open module to try again. KNOWN ISSUE: System Setup - Saving settings sometimes displays a SQL error. The settings WERE saved. The bug occurs when the module attempts to display the change. Close / reopen the module. - Fix: Sync Service - The Sync Service did not poll changes to start/end dates or turnover threshold without a restart. This is fixed. The Sync Service now checks settings at each run. - Fix: Sync Service - Non-interfaced Additional Campus Doors and User Group doors were removed from a predefined record. This is now fixed. - Fix: Sync Service - The Sync Service was not maintaining (cleaning) the response table. This is now locked to 100,000 rows. - Fix: Track 3 Replace Svc - The Track 3 replace service could sometimes update extraneous rows in the 3rd party database. This is fixed. - Fix: Import Module - The Import Module might create multiple predefined cards. This is fixed. - Fix: Stored Procedures SDK - SyncPerson & SyncCardHolder fixed in SDK - Fix: T3 Replace Service - The T3 replace service might sometimes touch each record in the host on each run. This is fixed. - Change: Import Module - A path to find the log file is now displayed after the import runs. - Change: Batch Import - Batch Import Module is included with base license now so as to configure patterns for import. - New Feature: Import Module - The classic Import Module (available to all users) no longer requires an "Access Pattern" field. The system will assign an access pattern based on valid Building & Room. V6.2 /V6.21 versus V6.1 SR1 ==================== NOTICE: v6.2/6.21 can ONLY upgrade 6.1 SR1 or 5.51 SR15. No other upgrade path is valid. NOTICE: WINDOWS 7 - If Windows prompts you to "Reinstall in Compatibility Mode" for System Setup or System User module (or any other module), ANSWER WITH: "THIS PROGRAM INSTALLED CORRECTLY." KNOWN ISSUE: WINDOWS AERO - The System User and Unlock Code Modules do not show a glass frame. KNOWN ISSUE: SQL 2008 R2 - 64 bit SQL 2008 R2 cannot create a linked server to Sybase and therefore cannot upgrade 5.5 SR15. The upgrade must be done in a 32 bit environment. KNOWN ISSUE: SERVER 2008 R2 - Sometimes the installer will crash with a "tmp" file error. This is generally a permissions issue that can be resolved by manually creating a database named "PERSONA" and then running the installer again. - Fix: Access Keycards - Switching from autoupdater to serial encoder did not always work properly. This is fixed. - Fix: API - ShowUnlockCode did not show future codes, only the code for now. This is fixed. - Fix: Autoupdater - The Autoupdater service could frequently crash. This is fixed. - Fix: Autoupdater - Autoupdater did not always encode Additional Campus Doors properly. This is fixed. - Fix: Autoupdater - Issues found in 64 bit Windows. This is fixed. - Fix: Future Unlock Codes - Override codes were not saved properly (wrong year). This is fixed. - Fix: Installer - The installer for Campus 1000 v6.1 did not properly install the perseng.msg file. This is fixed. - Fix: Installer - PERSONA services did not depend on MS SQL service which could sometimes provoke an issue at reboot if SQL did not come up before the PERSONA services. This is fixed. - Fix: Installer - Registry not updated in some cases by 6.1. This is fixed. - Fix: Installer - The installer might crash with certain issues in the environment. The installer is now more bulletproof. - Fix: Reports - Reports Module would display errors when viewing events from more than one lock. This is fixed. - Fix: Reports - Lock event reports in 6.1 would show the internal lock designation (not the human readable door name). This is fixed. - Fix: Sync Service - Sync Service compares were case sensitive. Sync Service now ignores case. "ADAMS HALL" is equal to "Adams Hall" - Fix: Sync Service - Sync Service could sometimes assign more than one card to the same access pattern. This is fixed. - Fix: Sync Service - Default Start / Stop times were not always used when the import failed to find valid dates in the import data. This is fixed. - Fix: Track 3 Replace Svc - The service could not update fields in an Oracle database. This is fixed. - Change: Installer - The installer now fully supports SQL 2008 and 2008 R2 with the above known issue during upgrades. - Change: Reports - Autoupdater device name is now included in the system event report when a card is encoded. - Change: Sync Service - Safety net to avoid large (unintended) card turnover. The Batch Import configuration module now includes a feature to limit the number of cards that can be deleted in a single session. Anything over this threshold will return an error to the CHAResponse table and process nothing. This fixes cases where data import errors (incomplete files, broken database links, etc.) would provoke a mass delete of all cardholders followed by an immediate re-add. - New Feature: Import Module - The Import Module can now import a Track 2 number. - New Feature: Bluetooth - LockLink 3.2 has released with Campus 1000 v6.2. Locklink 3.2 is backward compatible to ALL PERSONA Campus 1000 releases v1.0 and higher. No changes were made to Campus 1000 to accommodate the Bluetooth device. V6.1 SR1 /V6.11 SR1 versus V6.1 *SR1 IS PASSWORD PROTECTED. CONTACT SUPPORT FOR THE PASSWORD TO INSTALL* ====================== - Fix: Sync Service - Support 2y/4y formats - Change: Locklink - Support automatic lock program selection based on system options - Fix: Lock Program 22r - Fix 2y/4y bug. V6.1 /V6.11 versus V5.5 SR14 ====================== WINDOWS 7 COMPATIBILITY NOTE: If Windows prompts you to "Reinstall in Compatibility Mode" for System Setup or System User module (or any other module), ANSWER WITH: "THIS PROGRAM INSTALLED CORRECTLY." - WINDOWS AERO KNOWN ISSUE: The System User and Unlock Code Modules do not show a glass frame. - Change: Database Engine - Database engine migrated to MS SQL (compatible with MS SQL 2005 and MS SQL 2008 as of this writing). Vastly improved performance on Sync Services. - Fix: Add/Remove Prgs - #547. Add/Remove programs list properly maintained. Old entries cleared out by 6.1 installer. - Fix: Sync Service - NO PIN logic changed to fix issue with some NO PIN cards encoded as Normal - New Feature: Access - Added "Verify Track 2" option to module. Operator can now read a Track 2 Keycards value from a keycard to look up a record. if the record is not found, the actual track 2 data is shown along with any formatting applied by PERSONA. This will be useful when troubleshooting AutoUpdaters. - New Feature: API - #1630. New View defined: OfflineLocksets. - Change: Sync Service - #1629. Additional Access becomes "additive." A new (predef) card created for a user that has an existing keycard will work to keep any Additional Access (User Groups and Additional Campus Doors) that was on the cardholder's previous keycard. This works to keep manually assigned groups tied to a card even when importing changes. Any non-interfaced Additional Access will be carried over from the predefined card (if it exists) or the issued card. Interfaced privileges still rely on the interface's rules of behavior. - Change: Access Keycards - #1637. Room Change Wizard disabled when encoder is an autoupdater. Timing of Room Change Wizard vs AutoUpdater Reclaim is too hard to deal with perfectly at this time. - Change: Access Keycards - #1643. Changed title of Access Keycards History window to be more meaningful. - Change: Access Keycards - Access Keycards now enumerates and uses any available COM port (not just COM 1-4). - Change: Utility - Removed concept of APIUser since MS SQL supports wider authentication methods. - Change: AutoUpdater - #1660. \logger file support removed. - Change: Batch Import - #1618. Removed txt file support, modified to be a configuration tool for Sync Services only. - Changes (general) - Numerous minor UI and performance enhancements over v5.5 SR14 V5.5 SR15 /V5.51 SR15 versus V5.5 SR14 *SR15 IS PASSWORD PROTECTED. CONTACT SUPPORT FOR THE PASSWORD TO INSTALL* ====================== - Fix: Access Keycards - Fix: AutoUpdater - Fix: Sync Service - Support 2y/4y formats - Fix: Sync Service - Error fixed when the only changed field for a record was the User Timetable. - Fix: Sync Service - Error fixed that resulted in User Groups not being imported correctly in all cases. - Change: Locklink - Support automatic lock program selection based on system options - Fix: Lock Program 22r - Fix 2y/4y bug. V5.5 SR14 /V5.51 SR14 versus V5.5 SR13 ====================== - Fix: Access Keycards - Error fixed where removing and re-adding a user through Access Keycards could sometimes result in a Sybase error. - Change: Sync Service - Improved (greatly reduced) CPU and Hard Disk usage of the Sync Service as it uses the database engine. - Change: Sync Service - Changed logic of handling the deletion of cards when dealing with records that have access to both interfaced and non-interfaced areas. An example would be a card that uses a non-interfaced Access Pattern but also has an interfaced Additional Campus Door. In SR13, the card might get deleted or otherwise operated on. Now, the Access Pattern governs whether or not the card can be deleted. See full documentation for complete details. - Fix: AutoUpdater - The AutoUpdater from 5.5 SR13 might encode data to an expired track 3. V5.5 SR13 /V5.51 SR13 versus V5.5 SR12 ====================== - New Feature: Sync Service - Windows Service that monitors CardHolderAccess and RealTime tables for interface activity. Presents an easy method to link PERSONA to a campus's systems. Acts on inserts into these tables to create keycards. Replaces and expands upon functionality previously found in the Batch Import Module. New features include the ability to interface all PERSONA features such as User Groups, Additional Campus Doors, Timetables, etc. All cardholder features can now be interfaced in batch or real time. - New Feature: T3 SyncSvc - Windows Service that links PERSONA's data to a card production database. Sends track 3 card images to a 3rd party database for later encoding by a card printer. - New Feature: Stored Proc - API to drive changes into PERSONA via stored procedure calls. This is fully documented in the complete SDK. - New Feature: API User - SR 13 installer creates a database username and password for a host system to connect with to drive the interface. - New Feature: Real Time - Replacement for the TCP/IP VingCard VC3000 protocol that allows for real-time driving of the PERSONA encoders through the data tier of the system. - New Feature: Batch Import- Can now flag User Groups and Additional Campus Doors as available to interface. - New Feature: Batch Import- Can now configure link to PERSONA Campus Online system. Allows Sync Service to be the single point of input for any interface to PERSONA. - New Feature: System Setup- New Lock Access Suite Utility allows the user to easily configure Access Patterns for "suites." A Suite is a bedroom lock that is behind one or more other PERSONA locks. - New Feature: System Setup- Locks Copy Properties button allows the user to copy all settings from one lockset to many other locksets. This greatly simplifies the configuration of lockset properties such as passage mode, scheduling, gender, etc. - New Feature: System Setup- A new AutoUpdater can be added without restarting the AutoUpdater Service. All changes related to adding, deleting, and changing the role of an AutoUpdater are handled within 30 seconds of making the change in System Setup - New Feature: AutoUpdater/- Access Keycards can encode cards on an TCP/IP AutoUpdater. The operator can Access Keycards now select an AutoUpdater as the encoder used by the client software. The system will handle bringing the AutoUpdater offline and prompting the operator for card insertion. The AutoUpdater is then automatically brought back online. This feature referred to as the "AutoUpdater Pre-empt" feature. - New Feature: Platform - Use of Windows Event Log expanded to log many service related events. - New Feature: Installer - ODBC driver only installer is available for 3rd party host to connect to Sybase. - Change: System Setup - Door names and user groups can no longer contain pipe "|" character. This is now used as a delimiter when importing Access Points. - Change: System Setup - Access Pattern names now include leading zeros for sorting. - Change: System Setup - Modified Lock Access Include Wizard allows the user to include one or many Access Patterns into one or many locksets. This is an improvement over the SR12 Include Wizard. - Change: System Setup - Lock Access Patterns "Wizard" functionality moved to Patterns "Add" - Change: System Setup - Lock Access Delete functionality improved to allow the deletion of one or many Access Patterns from one or many locks. - Change: System Setup - Locks Wizard modification to remove lockset properties. The Wizard is now used only to name new locksets. The ranges of locks can now have specific prefixes and suffixes. - Change: AutoUpdater - Autoupdater now reads track 2 first, then falls back to track 3 if track 2 cannot be found. This will reduce the number of cards rejected by Autoupdater. - Change: VC_NET - Reduced verbosity. Should eliminate errors seen in Citrix. - Fix: System Setup - Fixed tab order on Lock Wizard. - Fix: System Setup - Fixed internal issue with deleting patterns (housekeeping of some tables). - Fix: System Setup - Changing door type from Additional Campus Door to any other door type now checked for consistency. - Fix: System Setup - Lock Access rename Access Pattern display glitch fixed. Display is now updated properly. - Fix: System Setup - Consistency check on Network Encoders parameters save. - Fix: System Setup - Check Settings improvements and fixes. Most notably, the check for locks with > 1200 access patterns had a bug where it would actually check for locks with > 1500 access patterns. So any lock with 1201 - 1499 patterns would have an invalid configuration but would not be caught by this check. This would result in some patterns that would not work in some locks though they looked as though they should. - Fix: System Setup - Sorting of Pattern Names in Lock Access tab is fixed. - Fix: System Users - Sorting of privileges is fixed. - Fix: System Users - Building Master Keycard creation rights were not working properly. This is now fixed. - Fix: Emergency Unlock - Building/Door/Description display fixed - Fix: Batch Import / Sync - Was possible to leave track 3 data "orphaned" in card production database for certain deleted records. Now, in all cases, a deleted PERSONA record has track 3 removed from the card production database - Fix: LockLink - Pattern ID values over 32,767 were being corrupted in the lock data. This would result in new patterns not working in the locks that they should work in. Access Denied, No Rights. - Fix: Installer - Server install onto a machine without ActiveSync would result in an unusable database (LockLink Module not registered). This has been fixed. ActiveSync is not required on the server. V5.5 SR12 /V5.51 SR12 versus V5.5 SR11 ====================== - Fix: Access Keycards - Move validation from "encode" to "save" operation. This prevents a user from predefining a card outside his security scope. This was only an issue in environments with AutoUpdaters, which offer a way to encode this predefined card. Now, the operator can only save a card if he has the proper privilege assigned. - Change: System Events - System event deletion has been made "safer." V5.5 SR11 /V5.51 SR11 versus V5.5 SR10 ====================== - Fix: System User - Username field was limited to 8 characters by version 5.0. This has been changed back to the previous limit from version 4.1 and lower. - Fix: Lock Program 22o - Lock program from SR10 fails to work in the VingCard Remote Reader. This new program includes all fixes from SR10 and will work in all hardware types. - Fix: Future Unlock - Export codes to TXT file would export the wrong field for the door's name. This is fixed. - New Feature: CBACKUP - Sample Backup Script included in the \PERSONA folder for CBACKUP. V5.5 SR10 /V5.51 SR10 versus V5.5 SR9 ====================== - Fix: System Setup - Several fields in the form on the "Lock Access" tab did not behave as expected. Changes were not committed to the database. This is now fixed. - Fix: Lock Program 22n - Sargent P.G Lockcases might experience electronic failure, this is now fixed. - Change: Lock Program - Before this version, if a Stratos Lockcase was disconnected 22n while the lock was fully programmed, the lock would require reprogramming after the lockcase was reconnected. Without reprogramming, the newly connected lockcase would not work until the controller was reprogrammed. This is now changed so the lockcase is initialized each time the motor is run. This allows for service personnel to disconnect and connect lockcases to the LCU without reprogramming the lock. V5.5 SR9 /V5.51 SR9 versus V5.5 SR8 ====================== - Fix: AutoUpdater - AutoUpdater did not work with Track 1. This is now fixed. - Fix: Access Keycards - Adding users would sometimes result in an error reporting a key violation on the "user" table. This has been fixed. V5.5 SR8 /V5.51 SR8 versus V5.5 SR7 ====================== - Fix: Lock Program 22L - Fixed lock behavior that would produce "extra" red lights. 5.5 SR2 introduced reading the card twice - once on the way in and again on the way out. This increases the likelihood of a good read. However, if either read was bad the lock would give the red light and log a misread event even if the other read was good and the door opened. The cardholder would see the door open as expected but would also see a "green/red" or a "red/green" flash as the door unlocked. This "extra red" flash does not keep the door from opening but might confuse maintenance staff, etc. This is now corrected and the red light is never given if the door opens. This is Lock Program version 22L. V5.5 SR7 /V5.51 SR7 versus V5.5 SR6 ====================== - Fix: Access Keycards - Fixed issue where Access Keycards could create a keycard that would Not work properly in Additional Campus, Campus, and User Group Locks. The installer will show any illegal records to the operator for subsequent replacement. - Fix: Installer - Filters messages related to reprogramming locks, downloading data, client/server, etc, based on installer jobs and environment. - Fix: Installer - Installer did not stop AutoUpdate Service properly when upgrading Sybase engine. User was forced to stop manually. This is fixed. V5.5 SR6 /V5.51 SR5 versus V5.5 SR5 ====================== - Fix: Batch Import - Importing with NO PIN would result in keycards that did not work. - Fix: Batch Import - Importing with PIN Always would result in keycards with PIN Normal. - Fix: Batch Import - Import would sometimes not use a vacant access pattern as expected. - New Feature: EXP - Batch Delete included. This is a Custom Report (an EXP) that is launched from the Reports Module and installed into \PERSONA\REPORTS. - New Feature: DB - Included DBPING and DBVALID, two Sybase troubleshooting utilities. Also included a BAT file to execute them with documentation. V5.5 SR5 /V5.51 SR5 versus V5.5 SR4 ====================== - Fix: Database - It was possible to add cardholders that would not populate a table used by the interface. This has been fixed with a database trigger. - Fix: Database - Saving a cardholder without PersonalID would result in a Sybase error. This was introduced in a beta SR5 build and is now fixed. V5.5 SR4 /V5.51 SR4 versus V5.5 SR3 ====================== - Fix: Locklink - SR3 broke the LockLink's Open Door function. This is fixed in SR4. V5.5 SR3 /V5.51 SR3 versus V5.5 SR2 ====================== - Fix: Lock Program 22k,- System did not properly handle the roll-over of the decade. Access Keycards, Invalidation cards in User Group, Additional Campus, and Campus Database Doors would not work for cards that expired after 12/31/2009. V5.5 SR2 /V5.51 SR2 versus V5.5 SR1 ====================== - Fix: Locklink Module - Lock data might not lock out lost cards in all cases with SR1. This is fixed in SR2. - Fix: System Setup - GUI updates for field sizes, some fields were trunctuated. - New Feature - Lock program gives annoying indicator of low battery. Delays cardholder and prompts trouble report. - New Feature: - Card is read on the way in as well as on the way out of the reader. Lock Program 22j The card was only read on the way out in earlier versions. This enhancement increases the ratio of good reads to bad reads. - Change: - The "Open Inhibit" function is now more of a nuisance. The lockset Lock Program 22j will flash repeatedly and delay opening on a low battery warning. The intent is to provoke the cardholder to report the event and have the batteries changed before the lock goes completely dead. - Change: Sybase - Included DLL to allow linked databases. V5.5 SR1 /V5.51 SR1 versus V5.5 / Locklink 3.0 ====================== - New Feature: General - Supports Pocket PC Locklink 3.0 - New Feature: Lock - Lock gives flashing user feedback to button presses Program - Change: LockLink, - Locklink Designation now hidden in system and in Locklink Module. System Setup Locklink Designation is no longer required in the system. - Change: Registry - Install location now stored in HKLM for future use. - Change: Reports - Lock Event report text change. Reports header change (logo). - Change: Keycard Svr - Changed keycard type from "Conference Guest" to "Student." - Fix: Access Keycards - PIN Mode default sometimes ignored - Fix: Access Keycards - PIN Prompt upon card save for subsequent autoupdating Before the PIN prompt would only occur when encoding a card - Fix: Sybase Engine - Sybase SQL engine update to latest build. Fixes some problems with rare system crashes. - Fix: Lock Program - Holding a button down / Button sticking no longer kills 22i batteries. - Fix: Lock Program - Lock will respond with a stuck button where before the 22i lock would appear dead. - Fix: Batch Import - Fixed issue with End time. - Fix: Import - Standard Import Module broken in 5.5 with End Dates all being set to 1899. Fixed in SR1. - Fix: System User - Edit Privilege Groups tooltip fixed. - Fix: Update Interval - Several features related to endtime were fixed from 5.0. Access Pattern Vacant / occupied flags now displayed correctly, among other things. - Fix: PPC - Installing to a non-default location now works. Previous versions required a registry editor to fix up the pocket PC before LockLink could transfer data from the PC. Now the user may install to a non default path but must RUN the pocket PC software to fix up the registry. This is due to a limitation in the installer which will be corrected in later versions with an upgrade to the installer engine. For now it is not able to write a long enough value to the registry, so the application must do it at runtime. - New Feature: PPC - HISTORY.LOG Locklink will retain a history log of "why" a lock was serviced. The technician has the option to check boxes corresponding to reasons for the service ("changed batteries," "cleaned reader," etc.) This log can be analyzed by PERSONA support (and IT staff) for trends. There is no reporting feature built around this yet, a file "history.log" is generated and transferred to the PC on each sync. It is a comma separated file. - New Feature: PPC - COMMENTS.TXT controls the values displayed to the lock service techs which are then saved into the HISTORY.LOG file. It is suggested that you always APPEND to this file and never replace a value. This maintains compatibility with future versions. - New Feature: PPC - Locks displayed as seen in Access Keycards - No "Locklink Designation" exists in the software anymore. The pocket PC displays an alphabetized list of buildings and a filtered rooms list. - Change: PPC - Pocket PC makes a system beep sound after the software completes its startup. Large databases can take some time to initialize in some Pocket PCs. Now there is an audible beep when the process completes. On most systems this will all happen in the same second or two. - Change: PPC - Pocket PC Menu selection name changes: Word "File" for menu launch changed to "Menu." "Program Locks" replaces "Upload" in list. "Read Events" replaces "Events." - Change: PPC - Last date/time of lock programming is retained through software restart. - Change: PPC - User name list is now sorted alphabetically in the pocket pc V5.5/V5.51 versus V5.0 ====================== - New Feature - AutoUpdater - Unattended encoder for updating keycards - Fix: Batch Import - Batch Import More Robust V5.0/V5.01 versus V4.1 ====================== - New Feature - ability to link to SALock’s online TEKControl system so that the two appears as one system with both offline and online functionality - New Feature - Support for Sargent Passport 1000 lockbody - Fix: System Setup - Added ability to set lockbody type in Campus standalone mode V4.1 SR3 /V4.11 SR3 versus V4.1 SR2 ====================== - Fix: Lock Program - Fixed lock behavior that would produce "extra" red lights. 5.5 SR2 introduced reading the card twice - once on the way in and again on the way out. This increases the likelihood of a good read. However, if either read was bad the lock would give the red light and log a misread event even if the other read was good and the door opened. The cardholder would see the door open as expected but would also see a "green/red" or a "red/green" flash as the door unlocked. This "extra red" flash does not keep the door from opening but might confuse maintenance staff, etc. This is now corrected and the red light is never given if the door opens. This is Lock Program version 22L. V4.1 SR2 /V4.01 SR2 versus V4.1 SR1 ====================== - Fix: Access Keycards- Fixed issue where Access Keycards could create a keycard that would Not work properly in Additional Campus, Campus, and User Group Locks. V4.1 SR1 /V4.01 SR1 versus V4.1 ====================== - Fix: Lock Program, - System did not properly handle the roll-over of the decade. Access Keycards, Invalidation cards in User Group, Additional Campus, and Campus Database Doors would not work for cards that expired after 12/31/2009. - New Feature - Lock program gives annoying indicator of low battery. Delays cardholder and prompts trouble report. - New Feature - Card is read on the way in as well as on the way out of the reader. The card was only read on the way out in earlier versions. This enhancement increases the ratio of good reads to bad reads. - Change: Lockset - The "Open Inhibit" function is now more of a nuisance. The lockset will flash repeatedly and delay opening on a low battery warning. The intent is to provoke the cardholder to report the event and have the batteries changed before the lock goes completely dead. - New Feature: Lockset- Lock gives flashing user feedback to button presses V4.1/V4.11 versus V4.0 ====================== - Fix: Batch Import - now polls external database for changes - Fix: Batch Import - now deletes import files after processing them - Fix: Batch Import - Now removes external track3 data when triggered by Access Keycards module - Fix: Batch Import - now starts automatically when command line parameter "/autorun" is used - Fix: Access Keycard - Now triggers a removal of external track3 data when deleting keycards - Fix: Install - Shortcuts now changed from 'VingCard PERSONA' to 'PERSONA' - Fix: Lock program - Invalid lock event, Userid was sometimes overwritten when using deadbolt. - Fix: Lock Events - 'Inhibit Open' text changed to 'Open Inhibit' V4.0/V4.01 versus V3.6 ====================== VingCard PERSONA Campus 1000 V4.0/4.01 is identical to V3.6/3.61 with the following exceptions: - New feature: Added Batch Import module that interfaces with BlackBoard's and DataCard's IDWorks application. - New feature: Open reports, customized SQL queries for reporting and database changes. - New feature: RS-232 serial interface. - Change: PPC locklink now logs user login events. - Change: Lock wizard now has more parameters available. - Change: VCNet registry setting is now stored in LOCAL_MACHINE. - Fix: Access to PPC locklink now given only to users that have access to the locklink module. - Fix: Reports reported false access to additional campus doors. V3.6/V3.61 versus V3.5 ============================ VingCard PERSONA Campus 1000 V3.6/3.61 is identical to V3.5 SR4 with the following exceptions: - New feature: Added possibility to run Escape Return functionality on locks. - Change: Maximum access patterns and invalidated card users in a lock are set from 1500 to 1200. - Change: Changed event text from 'New keycard registered' to 'New keycard predefined'. Less confusing. - Change: Replaced '1/12/1899' type issuetime dates with the text 'None' instead. Less confusing. - Fix: Fixed slow operations when changing dates in Access Keycards module - Privileges tab. Now it only does so when you have decided on the date. V3.5 SR7 /V3.51 SR8 versus V3.5 SR7 ====================== - Fix: Lock Program - Fixed lock behavior that would produce "extra" red lights. 5.5 SR2 introduced reading the card twice - once on the way in and again on the way out. This increases the likelihood of a good read. However, if either read was bad the lock would give the red light and log a misread event even if the other read was good and the door opened. The cardholder would see the door open as expected but would also see a "green/red" or a "red/green" flash as the door unlocked. This "extra red" flash does not keep the door from opening but might confuse maintenance staff, etc. This is now corrected and the red light is never given if the door opens. This is Lock Program version 22L. V3.5 SR7 /V3.51 SR7 versus V3.5 SR6 ====================== - Fix: Access Keycards - Fixed issue where Access Keycards could create a keycard that would Not work properly in Additional Campus, Campus, and User Group Locks. V3.5 SR6 /V3.51 SR6 versus V3.5 SR5 ====================== - Fix: Lock Program, - System did not properly handle the roll-over of the decade. Access Keycards, Invalidation cards in User Group, Additional Campus, and Campus Database Doors would not work for cards that expired after 12/31/2009. V3.5 SR5 /V3.51 SR5 versus V3.5 SR4 ====================== - Fix: Access Keycards Support for new KST model encoders (slim profile, black) V3.5 SR4 versus V3.5 SR3 ======================== VingCard PERSONA Campus 1000 V3.5 SR4 is identical to V3.5 SR3 with the following exceptions: - Fix: Import module gave error message 'Check import settings' and hanged when trying to import records based on personal id's that did not exist. V3.5 SR3 versus V3.5 SR2 ======================== VingCard PERSONA Campus 1000 V3.5 SR3 is identical to V3.5 SR2 with the following exceptions: - Change: Locklink is enabled for using the new LCU; compact lock electronics where both the card reader and the lock 'brain' is in one physical unit. The locklink must be loaded with data after the install to make sure the change is in effect. V3.5 SR2 versus V3.5 SR1 ======================== VingCard PERSONA Campus 1000 V3.5 SR2 is identical to V3.5 SR1 with the following exceptions: - Improvement: When typing in a date or navigating in the calendar view of the startdate or enddate fields in Privileges tab in Access Keycard module, the computer used a lot of time on calculations. Now those calculations only happen when one has decided on which date to use. V3.5 SR1 versus V3.5/V3.51 ============================ VingCard PERSONA Campus 1000 V3.5 SR1 is identical to V3.5/3.51 with the following exceptions: - Change: Building field in Access Keycards-Residence Access is now sorted by name. - Change: Text in Utility-Restore changed. Tells user to contact support before restoring. - Fix: Common end time for cards did not work in some cases. - Fix: Lock events sometimes gave false repeated events. - Fix: Card verification gave wrong user information in certain cases. - Fix: Utility-Backup sometimes left applications in memory when finished. V3.5/V3.51 versus V3.4/V3.41 ============================ VingCard PERSONA Campus 1000 V3.5/3.51 is identical to V3.4/3.41 with the following exception: - The locklink now runs on a PDA (PocketPC). - Added open door by locklink functionality. Doors can be opened with a locklink while running normally and also when lock batteries are dead (by using an external battery pack). - Events can be read from the locklink to the PC and printed out directly to a printer. - Enhanced lock program to use less battery power after disconnecting and reconnecting keypads. V3.4/V3.41 versus V3.3/V3.31 ============================ VingCard PERSONA Campus 1000 V3.4/3.41 is identical to V3.3/3.31 with the following exception: - Keypad only functionality is changed in both system software and lock. Any door can be set up with a 6 digit fixed code and a timezone restriction for that code. Any door can also be set up with a 6 digit changing code that changes according to the user's settings. Exporting codes is no longer restricted to a maximum of 45 days, there is no restriction. Important notes: - All locks must be set up with correct Keypad Only settings before reprogramming all doors. - All locks must be reprogrammed to support the new Keypad only functionality changes. - All locklinks must be updated with the files located in the PERSONA\Locklink directory to support the new Keypad only functionality changes. - Third party systems that use codes exported from PERSONA Campus 1000 V3.3/3.31 must be updated with codes generated from this version after the locks have been reprogrammed. V3.3/V3.31 versus V3.21/V3.21 ============================= VingCard PERSONA Campus 1000 V3.3/3.31 is identical to V3.2/3.21 with the following exception: - New unlock code functionality in both system software and lock. Any door with a keypad can be set up to accept a 6 digit unlock code that changes every hour. Codes can be viewed and also exported to other systems through a text file. V3.2 SR3 ======== VingCard PERSONA Campus 1000 V3.2 SR3 is only meant to be installed on top of V3.2/V3.21, V3.2 SR1 or V3.2 SR2. This version does not need to be installed before other newer versions. This version contains: - Lock program fix for the high current consumption of the keypad temperature sensor after disconnecting and connecting a keypad. V3.2 SR2 ======== VingCard PERSONA Campus 1000 V3.2 SR2 is only meant to be installed on top of V3.2/V3.21 or V3.2 SR1. This version does not need to be installed before other newer versions. This version contains: - When logged on to NT4/W2K with restricted user access any password produced by PERSONA except the backdoor password resulted in an error - fixed. - The PERSONA Keycard Server did not properly handle concurrent access in a high traffic environment. The TCP connection could fail or timeout when receiving several requests at the same time - fixed. - Report modules could crash when running several reports in succession - fixed. - Verifying a deleted keycard displayed wrong user information. This issue was checked, but was not able to reproduce the problem. - Import module could crash when the update was based on PersonalID. This issue was checked, but was not able to reproduce the problem. V3.2 SR1 ======== VingCard PERSONA Campus 1000 V3.2 SR1 is only meant to be installed on top of V3.2 or V3.21. This version does not need to be installed before other newer versions. This version contains: - New lock program that supports new Stratos lockcase and new passagemode functionality. V3.2/V3.21 versus V3.1/V3.11 ============================ VingCard PERSONA Campus 1000 V3.2/3.21 is identical to V3.1/3.11 with the following exception: - The option to install a "Demo" installation has been removed. Anybody wanting a demo installation must now be issued a license code to be able to do the install. V3.1/V3.11 versus V2.2/2.21 =========================== VingCard PERSONA Campus 1000 V3.0/3.01 is identical to V2.1/2.11 with a few exceptions: - During installation you are prompted to select a Campus installation or a General installation. The difference is that the Campus installation uses the same terminology as all earlier version of Campus 1000. Select this installation for installation on universities. The General installation uses a general terminology not specific for universities. - In the Utility module there is a new page, Texts, where you can change some of the words used that is different in the Campus and General installation. You can also swap between General Setting and Campus Setting. It is recommended that you use identical setting for all PCs in the same installation. - The new and improved Enhanced Import Module now handles importing and/or assigning of keycard data, as well as keycard holder/system user information. V2.2/2.21 versus V2.1/2.11 ========================== VingCard PERSONA Campus 1000 V2.2/2.21 is identical to V2.1/2.11 with a few exceptions: - Keycards can now be issued to last up to 4 years (2 years in previous versions). - Short Term Keycards has a time resolution of 1 hour (30 minutes in previous versions). Since the time when a keycard is encoded (the issue time) is the baseline for the keycards start time and expire time those two times will automatically be adjusted against the issue time when the specified start and expire time is not dividable by whole hours. In average half of the short term keycards you encode will have this adjustment. The database is updated, and you have a warning about the adjustment. The adjustment will always be that the start and expire time is 30 minutes earlier than specified. - Online help texts and user manuals are not changed. The maximum duration of keycards is here still 2 years, and Short Term keycards have a resolution of 30 minutes. Upgrade considerations from v1.x: - If you upgrade from previous versions of VingCard PERSONA Campus 1000, all existing keycards work as before. - Only new keycards encoded after the upgrade can have more than 2 years duration. - All keycards you issue the same day as you upgrade can have maximum 2 years duration. - All keycards issued after midnight can have up to 4 years duration. - You must generate new lock data from the LockLink Module and reprogram all locks before new keycards work in the locks as defined in your database. - New keycards issued and used in locks that have not been reprogrammed will not work as defined in the database. The interval between issue time and start time and the interval between start time and expiration time will be reduced to 50%. - It is possible to double the interval between issue time and start time and the interval between start time and expiration time for keycards issued before you upgraded. This can be done with the program ChangeNDF.EXE found in the UTILS directory on the installation CD. When you upgrade from an earlier version the installation program will ask you if you want to run this program. The program will generate a text file describing the modification to the database. After you have used ChangeNDF.EXE you have to generate new lock data from the LockLink Module and reprogram all locks.