OnGuard Cumulative Hot Fix 3.0 Release Notes

Lenel Systems International, Inc. 1212 Pittsford-Victor Road Pittsford, New York 14534 Tel 585.248.9720 Fax 585.248.9185 www.lenel.com OnGuard 6.4.500 Cumulative Hot Fix 3.0 Release Notes Table of Contents Versioning Information... 2 1 Current Access Series (LNL) Firmware and Special Application Versions... 2 2 Current Security Series (NGP) Firmware... 2 3 Current ILS Firmware... 2 4 Current Digital Video Firmware... 2 Known Issues... 3 1 Digital Video... 3 Resolved Issues... 4 1 General... 5 2 Access Control... 10 3 Intrusion Detection... 15 4 Identity Management... 24 5 Visitor Management... 25 6 Digital Video... 26 7 Enterprise... 31

Versioning Information The following firmware versions have been updated and are included with this hot fix. 1 Current Access Series (LNL) Firmware and Special Application Versions LNL-1100-U, LNL-1200-U, LNL-1300-U, LNL-1320-U Version 10.13 2 Current Security Series (NGP) Firmware NGP: 1.02.026 Note: Refer to the NGP Firmware 1.02.026 Release Notes file included with this hot fix. 3 Current ILS Firmware Lock Firmware: Control Module (ACU): 3.0.0.21 Prox Reader: 3.0.0.1 iclass Reader: 3.0.0.2 MIFARE Reader: 3.0.0.14 WLM NA: 0.9.21358 WLM EU: 0.9.21366 PDA Application: 2.0.3.8 WAP Firmware: WWM NA: 0.9.21358 WWM EU: 0.9.21366 WMC Ethernet Firmware: 2.0.21791 WMC Wi-Fi Firmware: 2.0.21791 4 Current Digital Video Firmware Remote Monitoring Firmware Version 6.4.500 Hot Fix 2.6 2012 Lenel Systems International, Inc. 2

Known Issues 1 Digital Video 1.1 SkyPoint compatibility note (OG-23310) When upgrading to OnGuard 6.4.500 Hot Fix 3.0, SkyPoint 2.0 must be used. OnGuard 6.4.500 Hot Fix 3.0 is not compatible with earlier versions of SkyPoint. 1.2 Attention SkyPoint customers using Remote Monitor SkyPoint customers using Remote Monitor must upgrade Remote Monitor to 6.4.500 Hot Fix 2.6 in order to be compatible with SkyPoint 2.0. 1.3 Attention customers using SkyPoint 2.0 (OG-22626) The first connection to NetEVS will take up to 20 40 seconds. Streaming video, viewing recorded video, and getting a recipient list will result in this delay the first time one of these functions is performed. The next time any of these functions is performed, the response time should improve. If none of these functions are performed for 15 minutes, the delay will be observed again the next time one of the functions is performed. The same initial delay will also be observed for these functions when using a NetDVMS that is configured with an Auxiliary Server (SkyPoint Base). These delays will not be observed when using a NetDVMS that is not configured with an Auxiliary Server. 1.4 Launching SkyPoint from Alarm Monitoring displays error message (OG-26346) Launching the SkyPoint application from Alarm Monitoring will display an error message. Any preferences saved in the SkyPoint options dialog within Alarm Monitoring will not be used and the application will open in Full Screen. The workaround for this is to open the SkyPoint application through the program shortcut and configure the screen configuration from the client setup dialog. A resolution in a future service release for OnGuard 2010 (6.4.500) is not expected at this time. This issue is not present in OnGuard 2012 (6.5). 1.5 Unable to receive Communication Lost event from RC-E Recorder (OG-24126) RC-E recorders will always appear to be online. If a RC-E recorder goes offline, there is no indication that the devices from which the RC-E is recording are no longer recording/available. This is a recorder limitation. 1.6 NetDVMS: Restoring the network connection does not give "Video Source Signal Lost" alarm (OG-24376) When using a NetDVMS or RC-C recorder with an Axis Encoder, there is a scenario in which camera status will not be reported properly in Alarm Monitoring. If the video cable that connects an analog camera to the Axis Encoder is disconnected while the Axis 2012 Lenel Systems International, Inc. 3

Encoder is offline or powered down, the camera will appear to be online in Alarm Monitoring when the Axis Encoder is brought back online or powered up. This is a recorder limitation. 1.7 Unable to play recorded video from RC-E Cameras continuously for more than one hour, Video stopped before one hour (OG-24439) Recorded video from RC-E cameras will not continuously play for more than one hour. It stops after playing for an hour. This is a limitation on the recorder and will be addressed in future releases. 1.8 Receiving incorrect "Responding" event from RC-C two minutes after Axis Encoder is disconnected (OG-24479) When using a NetDVMS or RC-C recorder with an Axis Encoder, if the Axis Encoder is disconnected, Alarm Monitoring will correctly indicate the lost connections to the corresponding cameras. Approximately two minutes later, Alarm Monitoring will briefly (and incorrectly) identify those cameras as having been reconnected. Within a few seconds, the correct (disconnected) status will once again be reflected. This is a recorder limitation. Resolved Issues The release notes below are for items from 6.4.500 Hot Fix 2.1 3.0. To view release notes for items prior to 6.4.500 Hot Fix 2.1, refer to the Release Notes on the Lenel Web site: http://www.lenel.com/support/downloads/onguard. (You will need your Lenel login to gain access to this site.) This hot fix is only intended to correct the problems described below and should be applied only to systems that are determined to be experiencing these problems. Please evaluate your need for this fix before installing it. It is strongly recommended that this hot fix only be installed by customers who have an immediate need to correct one or more of these problems. When applying this hot fix, it must be installed on every server and workstation running OnGuard 2010 6.4.500 software in this system. Failure to do so may result in serious system failure. This hot fix can only be applied after your system's database has been upgraded to OnGuard 2010, version 6.4.500. 2012 Lenel Systems International, Inc. 4

Please make sure you stop all LS and Lps product services and close all running product applications before you continue. This hot fix addresses and resolves various OnGuard 2010 version 6.4.500 issues as one hot fix. This hot fix includes and supersedes all previous incremental or cumulative hot fixes. All of the following issues listed below are addressed by this hot fix. This hot fix must be reapplied whenever the system is modified or repaired with the OnGuard installer. If after evaluation of your needs for this hot fix you determine that installation is necessary, proceed with the installation. Installation Instructions: On all OnGuard 2010 servers and clients: 1. Close all OnGuard applications and then stop all OnGuard LS and Lps services. 2. Install OnGuard 6.4.500 Hot Fix 3.0. 3. Run Database Setup on each OnGuard server. a. A valid license is needed. b. Database Setup does not need to be run on OnGuard clients. 4. Start the OnGuard LS and Lps services. 5. Restart IIS. 1 General 1.1 Error during upgrade or uninstall (OG-15997) This hot fix resolves an issue that caused the following error message to appear during an upgrade or uninstall: Error 1905. Module C:\Program Files\OnGuard\msvbvm50.dll failed to unregister. 1.2 Flexnet license not working (OG-17164) This hot fix resolves an issue that caused the Flexnet license to stop working and show up as inactive in License administration. 1.3 When passing in time properties to an incoming DataConduIT message queue, the UTC offset is ignored and set to -240 minutes (OG-21836) This hot fix resolves this issue. 2012 Lenel Systems International, Inc. 5

1.4 When Modifying a Scheduled Action that has an Expiration Date of One Time After it has Expired, it Shows the Next Run Time as Never (OG-21933) This hot fix resolves an issue in which when there is an existing schedule that is reoccurring and it has expired, modifying it to one time, it will show never as the next run time. The scheduled action does not execute at the appropriate time since the next run time could not be calculated. 1.5 Global I/O cannot be executed with remote license server (OG-23427) This hot fix resolves an intermittent issue in which Global I/O could not be executed with a remote license server. 1.6 Report Error and Incorrect Daylight Savings Time (DST) start and end dates (OG-22415) This hot fix resolves an issue that caused an error message in reports due to incorrect Daylight Savings Time (DST) start and end dates calculated by OnGuard. The following message appeared when generating a report: A time range cannot be used on this report and will be ignored. 1.7 Software Connection Error - Panel Offline Unless Communication Server is run as authenticated user (OG-22419) This hot fix resolves an issue in which there is a software connection error and the panel is offline unless the Communication Server is run as an authenticated user. 1.8 Cannot Update Audio Instructions or Notifications in Windows 7 (OG-22469) This hot fix resolves an issue in which audio instructions or notifications could not be updated in Windows 7. 1.9 Issue regarding Database Setup prompt for client installations (OG-22567) This issue has been resolved. 1.10 Grant/Deny pop-up threads from Global I/O can cause Linkage Server to close unexpectedly (OG-22577) This hot fix resolves an issue that caused the Linkage Server to close unexpectedly. 1.11 Scheduled actions intermittently have their next run time set to 'never' causing them to not run again (OG-22449) This hot fix resolves an issue that caused scheduled actions to intermittently have their next run time set to 'never' which caused the scheduled actions to not run again. 2012 Lenel Systems International, Inc. 6

1.12 NULL Insert Issues When Restoring Alarm Acknowledgements (OG-22609) This hot fix resolves an issue that caused NULL insert issues when restoring Alarm Acknowledgements. 1.13 Some reports do not work when run against an Oracle database (OG-22615) This hot fix resolves this issue. 1.14 VideoViewer (Browser-based Client) Cab file not installing the OnSSI Certificate (OG-22625) This hot fix resolves this issue. 1.15 Alarm acknowledgement history records containing new lines are not correctly archived (OG-22644) This hot fix resolves incorrect archiving of alarm acknowledgement history records containing eight (8) or more tabs followed by new lines in the Notes field. 1.16 PIV import does not work (OG-22661) This hot fix resolves an issue in which clicking [Import] after entering a PIN does nothing. 1.17 Incorrect status/intermittent failures are reported by DataExchange server when linked configuration has no data to process (OG-22688) This hot fix resolves an issue in which incorrect status/intermittent failures were reported by DataExchange server when linked configuration had no data to process. 1.18 Database Setup fails with Oracle using Windows Authentication (OG-22700) This hot fix resolves an issue in which Database Setup fails with Oracle using Windows Authentication. 1.19 Reports lock tables while running (OG-22820) This hot fix resolves an issue that caused reports to lock tables while running which may have affected the ability to acknowledge alarms, log events to the database, etc., for the duration of report execution for long running reports. 1.20 Improper sentence in license agreement (OG-22855) This hot fix resolves an issue in which there was an improper sentence in the license agreement. 1.21 Support needed for the Notifier 3000 fire panel (OG-22874) This hot fix includes support for the Notifier 3000 fire panel. The Custom Solutions Fire Integration (CS-DEV-FIRE) license is required. The following ACS.INI file setting is required for the panel to work: [Notifier] 2012 Lenel Systems International, Inc. 7

TotalReadTimeout=100 In addition, a custom script needs to be run in order to add the Notifier 3000 option into System Administration. Contact Technical Support for the custom script. 1.22 Linkage server gradually leaks memory due to License expiration check mechanism (OG-22900) This hot fix resolves an issue that caused the linkage server to gradually leak memory due to a license expiration check mechanism. 1.23 Issue Code is limited to the range of 0-99 when adding a badge using DataConduIT (OG-22506) This hot fix resolves an issue in which the range of the issue code, when adding a badge using DataConduIT, is limited to 0-99. 1.24 When Querying for Lnl_LoggedEvents the SegmentID Value is always <empty> (OG-22760) This hot fix resolves an issue in which when querying for Lnl_LoggedEvents, the SegmentID value was always <empty>. 1.25 Timezone intervals do not refresh properly when selecting timezone via System Tree (OG-23031) This hot fix resolves an issue that caused timezone intervals to not refresh properly when selecting timezone via the System Tree. 1.26 Linkage Server fails to process Cardholder software events (OG-23038) This hot fix resolves an issue that caused the Linkage server to fail to process Cardholder software events. 1.27 DataExchange can Stop Responding if the Specified Badge Type is Not Properly Resolved During Import (OG-23167) This hot fix resolves an issue that caused FormsDesigner to stop responding when running a DataExchange script that was assigning Access Levels to a Badge. This issue seemed to occur if there was an existing Badge record with a nonexistent Badge Type. 1.28 DataConduIT Queries Can Fail with Date and Time Filters in Non-US- English Formats (OG-23203) This hot fix resolves an issue that caused DataConduIT queries to fail with date and time filters in non-us-english formats. 1.29 Time zone update for the Egypt region (OG-23241) This hot fix includes a time zone update for the Egypt region. 1.30 License Agreement missing the word "to" (OG-23505) This hot fix resolves an issue in which the License Agreement was missing the word, to. 2012 Lenel Systems International, Inc. 8

1.31 ID Allocation skipping badge ID when cancelling "change badge status" dialog (OG-23520) This hot fix resolves an issue in which ID Allocation was skipping badge ID when cancelling "change badge status" dialog. 1.32 'Global I/O Linkages' report - missing device links for Intercom Station (OG-23542) This hot fix resolves an issue that caused the Global I/O Linkages report to have missing device links for the Intercom Station. 1.33 Alarms screen in System Administration is slow at customer site due to their configuration (OG-23591) This hot fix resolves an issue that caused the Alarms user interface to be slow, and scrolling from record to record would also take a long amount of time. 1.34 Violation of primary key constraint (OG-23747) This hot fix resolves an issue in which there was a violation of the primary key constraint when a new database was created and DBsetup was run. 1.35 Communication Server calculation of active timezone is incorrect when a holiday type is assigned to a timezone interval (OG-24037) This hot fix resolves an issue in which the Communication Server calculation of active timezone is incorrect when a holiday type is assigned to a timezone interval. 1.36 DataConduIT - Modifying a BadgeID via DataConduIT does not delete the badge from a panel (OG-24040) This hot fix resolves an issue in which modifying a BadgeID via DataConduIT did not delete the badge from a panel. 1.37 Cardholder changes at the region are not communicated to the parent node hardware during Cardholder record upload (OG-24137) This hot fix resolves an issue in which Cardholder changes at the region are not communicated to the parent node hardware during Cardholder record upload. 1.38 Alarm Monitoring closes unexpectedly when accessing the right-click menu for a device that is not defined in System Administration (OG-24524) This hot fix resolves an issue that caused Alarm Monitoring to close unexpectedly when accessing the right-click menu for a device that is not defined in System Administration. 2012 Lenel Systems International, Inc. 9

1.39 Reports: Alarm Panel Inputs Contact Normally Open field is not showing a value (OG-24715) This hot fix resolves an issue in which the Contact Normally Open field is not showing a value in the SA/'Panel Alarm Input' Report for Alarm Panel Inputs configured in the SA/Alarm Panel Input form. 1.40 December 2011 Microsoft time zone updates (OG-24776) This hot fix includes the December 2011 Microsoft time zone updates. 1.41 KioskClickOnce\Config and FrontDeskClickOnce\Config folders missing in combined Standard and Enterprise 6.4.500 Hot Fix 2.0.18 releases (OG-24932) This hot fix resolves an issue in which the KioskClickOnce\Config and FrontDeskClickOnce\Config folders were missing in combined Standard and Enterprise 6.4.500 Hot Fix 2.0.18 releases. 1.42 DataConduIT - Cannot create badge when "Automatic" is selected on Cardholder Options > Badge ID Allocation (OG-25397) This hot fix resolves this issue. 1.43 After upgrade, Web applications cannot be run (OG-25573) This hot fix resolves this issue. 2 Access Control 2.1 Readers are Missing for Access Level when Multiple Users Try to Modify Access Level Record at the Same Time (OG-22251) This hot fix resolves an issue in which when multiple users tried to modify the same access level simultaneously, readers were missing for the access level. 2.2 Need to pair the "Burglary Alarm" and "Burglary Alarm Restored" alarms within Alarm Monitoring (OG-22761) This hot fix includes the pairing of the "Burglary Alarm" and the "Burglary Alarm Restored" alarms within Alarm Monitoring. The "Burglary Alarm Restore" and "Burglary Restore" alarms will now replace a previously reported Burglary Alarm. 2.3 Area Access Manager (Browser-based Client): Non-SA user cannot add badge to access level (OG-22674) This hot fix resolves an issue that caused a non-sa user to not be able to add a badge to an access level using Area Access Manager (Browser-based Client). 2012 Lenel Systems International, Inc. 10

2.4 Extended open time limited to a value of 255 for first card unlock (OG-22687) This hot fix resolves an issue that caused extended open time to be limited to a value of 255 for first card unlock. 2.5 Unable to load Alarm Acknowledgment Activity History for Receiver Accounts (OG-22502) This hot fix resolves an issue in which Alarm Acknowledgment Activity History could not be viewed for Receiver Accounts. The Activity History text box displayed the following message: Unable to load acknowledgment history from the remote server at... 2.6 Performance issues when loading Alarm Monitoring with several video devices configured (OG-22530) (OG-24679) This hot fix resolves an issue that caused performance issues when loading Alarm Monitoring with several video devices configured. 2.7 Unable to add more than 32 Access Levels per Badge (OG-22811) This hot fix resolves an issue in which no more than 32 access levels per badge could be added. 2.8 Alarm Monitoring: Multiple Events are generated for all Readers when modifying a single reader (OG-22788) This hot fix resolves an issue in which multiple events are generated for all readers when modifying a single reader. 2.9 Universal I/O boards intermittently go offline/online (OG-22840) This hot fix resolves an issue in which Universal I/O boards intermittently go offline/online. 2.10 1320U/1300U (Universal I/O) panels unable to read PIV mag with Weigand out data (OG-22879) This hot fix resolves an issue in which 1320U/1300U (Universal I/O) panels were unable to read PIV magnetic with Weigand out data. 2.11 Global APB Timed Penalty (OG-22881) This hot fix resolves an issue in which time penalty still applies to granted access and denied access caused by true Anti-Passback. 2.12 Global APB lacks immediate enforcement when used on a server not in GMT (OG-22882) This hot fix resolves an issue that caused Anti-Passback to not be enforced immediately for a new badge if the server time was not in GMT. Now, Global APB works correctly on a server in UTC. 2012 Lenel Systems International, Inc. 11

2.13 Basis Offline Locks reporting FailedRPCs (OG-22963) This hot fix resolves an issue in which Basis Offline Locks were reporting FailedRPCs. 2.14 Maximum Active Badge Enforcement Issue (OG-22735) This hot fix resolves an issue that caused the ability to add two active badges while the maximum was set to one. This occurred when the application was opened in two instances and with the same user login. 2.15 Integra readers are counted incorrectly against Onity Integra license (OG-22777) This hot fix resolves an issue in which Integra readers are counted incorrectly against the Onity Integra license. 2.16 Enhancement: Increased Number of Intrusion Zones for OAAP Intrusion Integrations (OG-22958) This hot fix includes an increase in the number of intrusion zones that can be configured in System Administration from 512 to 2048, for OAAP intrusion integrations. 2.17 LNL-1320-U with FW 10.11 stays offline when downstream from LNL- 8000 panel (OG- 23059) This hot fix resolves an issue in which LNL-1320-U with FW 10.11 stays offline when downstream from LNL-8000 panel. 2.18 Reader Form - Setting tab: Checkbox "Do Not Activate Strike On REX" needs to be disabled when "Main panel controls REX processing" is not checked (OG-23066) This hot fix resolves an issue in which the checkbox "Do Not Activate Strike On REX" does not disable the strike, unless the "Main panel controls REX processing" is checked. 2.19 Lenel Universal I/O boards do not read PIV and Prox cards properly (OG-23079) This hot fix resolves an issue that caused the Lenel Universal I/O boards to not read both PIV and Prox cards properly. 2.20 When scrolling through readers, the up/down arrow keys do not work (OG-23192) This hot fix resolves an issue in which scrolling using the up/down arrow keys did not work. This occurred in the Readers screen of Access Control > Readers and Doors. 2.21 Reports: The Alarm Panel Inputs Report is showing the incorrect total inputs (OG-23202) This hot fix resolves an issue in which the Alarm Panel Inputs Report was showing the incorrect total inputs. 2012 Lenel Systems International, Inc. 12

2.22 Alarm panels cannot be configured under integrated OAAP access panels (OG-23248) This hot fix resolves an issue in which Alarm panels cannot be configured under integrated OAAP access panels. 2.23 Badge count in Capacity tab is not correct (OG-23430) This hot fix resolves an issue that caused the Badge count in the Capacity tab to not be correct. 2.24 Global APB: New Badges Do Not Get Moved Into Anti-Passback Areas from Access Granted Events (OG-23527) This hot fix resolves an issue that caused new badges to not get moved into Anti-Passback areas from Access Granted events. Now, badges are moved into Anti-Passback areas correctly. 2.25 System Administration stops responding when trying to save the configuration (OG-23722) This hot fix resolves this issue. The Reader settings are now able to be updated with the Alarm screen open (in edit and view modes). 2.26 Incorrect error message when executing a Custom Function (OG-23843) This hot fix resolves an issue that caused an incorrect error message to display when executing a Custom Function. When executing a Custom Function for a Bosch panel or OAAP Intrusion panel that supports 'Execute Custom Function' the message that is displayed is now formatted properly. 2.27 When Access Levels assign in Area Access Manager, Badge Last Change field does not update (OG-24035) This hot fix resolves an issue in which when Access Levels assign in Area Access Manager, Badge Last Change field does not update. If Access Levels modify in System Administration the same field is updated. 2.28 Communication Server not passing badge changes to hardware (OG-24038) This hot fix resolves an issue in which the Communication Server is not passing badge changes to the hardware. 2.29 Capture Image in Alarm Monitoring and Video Viewer does not work via the menu selection (OG-24049) This hot fix resolves an issue that caused Capture Image in Alarm Monitoring and Video Viewer to no longer work via the menu selection. 2012 Lenel Systems International, Inc. 13

2.30 ILS Wireless panel can add more than 32 locks (OG-24317) This hot fix resolves an issue in which the ILS Wireless panel could add more than 32 locks. 2.31 Unable to add ILS Magnetic Data to Track 3 of Magnetic Card Format while adding new magnetic card format (OG-24345) This hot fix resolves an issue that caused the inability to add ILS Magnetic Data to Track 3 of the Magnetic Card Format while adding a new magnetic card format. 2.32 Alarm Monitoring does not exit properly when Windows session ends (OG-24543) This hot fix resolves an issue that caused Alarm Monitoring to not exit properly when the Windows session ends. 2.33 Onity/Integra CT30 access level definitions do not work after Segmentation is enabled (OG-24882) This hot fix resolves an issue in which Onity/Integra CT30 access level definitions do not work after Segmentation is enabled. 2.34 SMux Provider: Physical connection is not usable errors when acknowledging alarms (OG-24883) This hot fix resolves an issue that caused SMux Provider: Physical connection is not usable errors when acknowledging alarms. 2.35 DataConduIT - Cannot create a badge when the Badge Type's ID Allocation = "import from card" (OG-25075) This hot fix resolves an issue in which a badge cannot be created when the Badge Type's ID Allocation = "import from card". 2.36 In Alarm Monitoring - Edit menu items are duplicated for custom added menu items (OG-25090) This hot fix resolves an issue in which Edit menu items are duplicated for custom added menu items. 2.37 System Administration stops responding if a user with no Field/Page Permission Group accesses Badge Types (OG-25105) This hot fix resolves an issue in which System Administration stops responding if a user with no Field/Page Permission Group accesses Badge Types. 2.38 Need to implement searching of global I/O groups within System Administration (OG-25742) This hot fix includes the implementation of searching of global I/O group within System Administration. 2012 Lenel Systems International, Inc. 14

3 Intrusion Detection 3.1 LCD name for Alarm Inputs is not displayed correctly after it is modified (OG-21819) This hot fix resolves an issue in which the LCD name for Alarm Inputs was not displayed correctly after it is modified. 3.2 Reader Report Cardholder Exit/Entry Shows Nothing for NGP Readers (OG-22452) This hot fix resolves an issue that caused reader report Cardholder Exit/Entry to show nothing for NGP readers. The date/time report, Cardholder Time and Attendance also showed nothing. 3.3 If the number of inputs allowed on an NGP alarm panel is reduced no validation is performed to see if inputs exist that will become out of range (OG-22477) This hot fix resolves the issue. Now the user is not allowed to reduce the number of inputs for the NGP alarm panel if inputs already exist that exceed the reduced value. Instead a warning message displays and the modification will not be allowed. 3.4 Cannot add the maximum number of areas supported by NGP, can only add at most 64 areas (OG-22525) This hot fix resolves an issue in which the maximum number of areas supported by NGP cannot be added. Only up to 64 areas could be added. 3.5 NGP: It is possible to enable SIA/CID communications and save a blank (empty) Account number when Contact ID is selected as the reporting format (OG-22536) This hot fix resolves an issue in which it was possible to enable SIA/CID communications and save a blank (empty) Account number when Contact ID was selected as the reporting format. 3.6 NGP: Incorrectly displaying a message about the maximum number of outputs reached when modifying an alarm panel (OG-22537) This hot fix resolves an issue in which a message was incorrectly displayed when modifying an alarm panel. 3.7 NGP: It is possible to configure the NGP In and Out Reader with no Area Entering (OG-22560) This hot fix resolves an issue in which it was possible to configure the NGP In and Out Reader with no Area Entering. 2012 Lenel Systems International, Inc. 15

3.8 NGP LCD Keypad serial number field is editable when multi-select is turned on (OG-22561) This hot fix resolves an issue in which the NGP LCD Keypad serial number field is editable when multi-select is turned on. 3.9 NGP: Spelling error in message (OG-22562) This hot fix resolves an issue in which there was a spelling error in a message that displayed when Number of invalid PINs was empty or blank on the Invalid Access tab. 3.10 Tab order is incorrect when editing an NGP alarm output (OG-22568) This hot fix resolves an issue in which the tab order is incorrect when editing an NGP alarm output. 3.11 Area settings for In Reader and Out Reader are empty with setting In Reader Area to Outside Area (OG-22570) This hot fix resolves an issue in which the Area settings for In Reader and Out Reader are empty with the setting In Reader Area to Outside Area. 3.12 NGP: Serial Number edit box is enabled when configuring 2 LCD Keypads for an NGP panel (OG-22571) This hot fix resolves an issue in which the Serial Number edit box is enabled when configuring 2 LCD Keypads for an NGP panel on the Readers and Doors screen. 3.13 With OnGuard 2010 (6.4) Technology Update or OnGuard 2010 (6.4) Hot Fix 2.0, generating the Module Details report or NGP Panels report when using an NGP panel connected to an Oracle database results in a "Failed to retrieve data from the database" warning (OG-22616) This warning only occurs when running the reports from the NGP Reports tab on the Reports form. This issue is resolved in OnGuard 2010 (6.4) Hot Fix 3.0. 3.14 NGP does not report change of state when input point is supervised (has EOL) and the circuit type is set to Not-Supervised on Alarm Input form (OG-22771) This hot fix resolves an issue that caused NGP to not report change of state when the input point is supervised (has EOL) and the circuit type is set to Not-Supervised Alarm Input on the Alarm Input form. 3.15 Intrusion Mask Group Enhancements: 24 hour alarm filter and Entry Delay (OG-22815) This hot fix includes the following enhancements: Intrusion Mask Group Filter: When the intrusion mask group is disarmed and a 24 hour alarm is activated, non-24 hour alarms (except for Door Forced Open alarms) are prevented from coming into Alarm Monitoring if Mask Group Filtering is enabled in the ACS.INI file. To 2012 Lenel Systems International, Inc. 16

activate Mask Group Filtering, the following must be set in the ACS.INI file under the [CommunicationServer] heading: [CommunicationServer] EnableIntrusionMaskGroupFiltering=1 Intrusion Mask Group Entry Delay: When Entry Delay times out, a Mask Group Alarm is created and contains the device (input name of entry point) that triggered the delay. 3.16 NGP Dual Interface Door Controller communication can become unstable (OG-22546) This hot fix resolves an issue that caused NGP Dual Interface Door Controller communication to become unstable. 3.17 GMT World Time Zone for NGP panel does not recognize DST for scheduled unlocks (OG-22647) This hot fix resolves an issue that caused GMT World Time Zone for the NGP panel to not recognize DST for scheduled unlocks. (NGP panels need to have their firmware upgraded to version 1.01.130 to receive this fix.) 3.18 Keypad Time on a NGP panel is incorrect when selecting Venezuela time zone (OG-22653) This hot fix resolves an issue that caused the time displayed on the keypad to be incorrect if the Venezuela time zone was selected. The time displayed on the NGP keypad was off by a half hour. (NGP panels need to have their firmware upgraded to version 1.01.130 to receive this fix.) 3.19 NGP: If you use a year greater than 2037 for badge or access level activation/deactivation dates it will make the badge/access level permanent on the panel (OG-22694) This hot fix resolves an issue in which if you use a year greater than 2037 for badge or access level activation/deactivation dates it will make the badge/access level permanent on the panel. 3.20 OnGuard does not send down the configuration of the 'Disarm always requires PIN' NGP LCD Keypad setting properly (OG-22850) This hot fix resolves an issue that caused OnGuard to not send down the configuration of the 'Disarm always requires PIN' NGP LCD Keypad setting properly. (NGP panels need to have their firmware upgraded to version 1.01.130 to receive this fix.) 3.21 Output 1 and 2 on NGP-1100 will only activate when outputs 1 or 2 of the VBUS connected 1208 are activated (OG-22853) This hot fix resolves an issue in which Output 1 and 2 on NGP-1100 would only activate when outputs 1 or 2 of the VBUS connected 1208 were activated. 2012 Lenel Systems International, Inc. 17

3.22 NGP panel can eventually stop reporting events to Alarm Monitoring (OG-22866) This hot fix resolves an issue that caused the NGP panel to report many events to OnGuard, and eventually reach a threshold that resulted in future events not being reported to OnGuard. This occurred if a NGP panel was running for a long time. (NGP panels need to have their firmware upgraded to version 1.01.130 to receive this fix.) 3.23 NGP: Need to change the alarm name 'End of Emergency', the current name is not a proper description for this alarm (OG-22890) The event and alarm name has been changed to 'Emergency Off'. 3.24 NGP Panel does not transmit to Central Station When Areas are Armed or Disarmed (OG-22934) This hot fix resolves an issue that caused the NGP panel not to transmit to the Central Station when Areas were Armed or Disarmed. 3.25 NGP Local I/O will not work when using the 2200 or 2220 (either access or intrusion) panel models (OG-22935) This hot fix resolves an issue that caused NGP Local I/O to not work when using the 2200 or 2220 panel models. 3.26 Behavior for Door Alarm versus Door Tamper Reporting (OG-22936) This hot fix includes changes in behavior for event reporting of door alarms. OnGuard will send a Door Contact Tamper Active alarm in the case of a true tamper condition that occurs on the Door. However, in the case of a door alarm condition (that is, intrusion based alarm related to Entry Doors for areas) OnGuard will send Alarm Active. Both events will include the name of the door in the Device column in Alarm Monitoring. The restore events will also come in properly for the occurrence of both of these alarms. There will also be additional text reported up with these alarms. Door Contact Tamper Active will have the text Door Tamper displayed as part of the additional alarm text. Alarm Active will have the text Door Alarm as part of the additional alarm text. You can view this text by selecting the alarm, right clicking, and then choosing the View Additional Text menu item. 3.27 Applying updates to NGP Central Station Setup Report (OG-22938) This hot fix includes updates to the NGP Central Station Setup Report. The existing NGP central station setup report needs to be modified by browsing to the updated report and clicking OK. This will update the report on the system. 3.28 NGP: Supervised inputs can show "active" status instead of "fault" when they are opened or shorted (OG-23081) This hot fix resolves an issue in which supervised inputs can show "active" status instead of "fault" when they are opened or shorted. 2012 Lenel Systems International, Inc. 18

3.29 NGP Download causes Communication Server to stop responding (OG-23151) This hot fix resolves an issue in which the NGP download caused the Communication Server to stop responding when more than 14 inputs were linked to one output. 3.30 Disarm always requires PIN panel behavior does not work (OG-23402) This hot fix resolves an issue that caused Disarm always requires PIN panel behavior to not work properly. (NGP panels need to have their firmware upgraded to version 1.01.130 to receive this fix.) 3.31 Global I/O with NGP - nothing is being sent to the Linkage server until it is restarted (OG-23419) This hot fix resolves an issue that caused Global I/O with NGP to not work properly. 3.32 Enhancement: Increased Number of Intrusion Areas and Doors for OAAP Intrusion Integrations (OG-22858) This hot fix includes an increase in the number of intrusion areas that can be configured in System Administration from 32 to 128, for OAAP intrusion integrations. It also includes an increase in the number of intrusion doors that can be configured in System Administration from 8 to 256, for OAAP intrusion integrations. 3.33 Enhancement: Increased Number of Intrusion Zones for OAAP Intrusion Integrations (OG-22958) This hot fix includes an increase in the number of intrusion zones that can be configured in System Administration from 512 to 2048, for OAAP intrusion integrations. 3.34 Enhancement: Increased Number of Offboard Relays for OAAP Intrusion Integrations (OG-23020) This hot fix includes an increase in the number of offboard relays that can be configured in System Administration from 200 to 512, for OAAP intrusion integrations. 3.35 Guardall: Fire Alarm restored from the keypad, shows Burglary Restored in Alarm Monitoring (OG-23078) This hot fix resolves an issue in which when a Fire Alarm is restored from the keypad, it shows Burglary Restored in Alarm Monitoring. 3.36 New NGP User Report (OG-23111) An NGP Users report has been added, which includes Name (First and Last), NGP Panel User ID, Cardholder Badge ID, and both Phone Numbers. This report is useful for identifying more information about the user who an event has been generated for, and may be sent to a central station. 2012 Lenel Systems International, Inc. 19

3.37 Execute Custom Function Option is Now Available for Intrusion Panel Integrations (OG-23128) The Execute Custom Function is now available for Intrusion panel integrations. The Execute Custom Function option is available from the intrusion panel context menu in Alarm Monitoring. In order to enable this option in the context menu, an additional element needs to be specified within the panel capabilities XML and loaded to the database. The element name is <ExecuteFunction> and must be specified as true in order to load the Execute Custom Function menu item on the intrusion panel context menu from Alarm Monitoring. When selecting the Execute Custom Function menu item a dialog will be displayed. The dialog allows the end user to enter a keypad and function number. The range of acceptable values is: Keypad number: 0 63 Function number: 0 255 3.38 Downloading NGP Firmware will produce a "Panel restart due to power failure" alarm (OG-23256) The name of the event was changed to "Panel restart" instead of "Panel restart due to power failure". The "Panel restart" event can be received when the power is disconnected from the panel or during the firmware upgrade. 3.39 More than 64 alarm panels can be added to NGP-3320i, even though the Maximum Capacity of Alarm Panels under Capacity Tab is 64 (OG-23312) This hot fix resolves an issue in which more than 64 alarm panels can be added to the NGP-3320i, even though the Maximum Capacity of Alarm Panels under the Capacity Tab is 64. 3.40 When a reader is removed from the NGP panel, the reader is still displayed on the keypad (OG-23343) This hot fix resolves an issue in which when a reader is removed from the NGP panel, the reader is still displayed on the keypad unless a database download is performed. 3.41 Guardall Px/Qx/Rx panel lost communication (OG-23347) This hot fix resolves an issue in which a Guardall Px/Qx/Rx panel lost communication. Marking the panel offline-online reestablished the communication. 3.42 Cannot edit some of the alarms for an NGP panel on the Alarm Definitions form (OG-23360) This hot fix resolves an issue that caused the inability to edit some of the alarms for an NGP panel on the Alarm Definitions form. 2012 Lenel Systems International, Inc. 20

3.43 Reader/Door Mask/Unmask events are not unmasking in Alarm Monitoring (OG-23368) This hot fix resolves an issue in which Reader/Door Mask/Unmask events are not unmasking in Alarm Monitoring. 3.44 User is unable to Arm or Arm Stay in Alarm Monitoring on NGP default area (OG-23372) This hot fix resolves an issue in which the user was unable to Arm the default area in Alarm Monitoring. The following error message appears: Area "Default Area" arming failed. Reason area alarm active. Would you like to force arm the area. The same error message was generated when the user selected Arm Stay. 3.45 OnGuard does not remove Keypad arming area settings properly from the NGP panel (OG-23378) This hot fix resolves an issue in which OnGuard does not remove Keypad arming area settings properly from the NGP panel. 3.46 Configured Global Outputs using NGP access panel are not activated in Alarm Monitoring (OG-23398) This hot fix resolves an issue in which configured Global Outputs using an NGP access panel are not activated in Alarm Monitoring. 3.47 User can add more than 64 offboard door interfaces with different serial numbers (OG-23411) This hot fix resolves an issue in which the User can add more than 64 offboard door interfaces with different serial numbers. Also, an incorrect value is displayed for "Maximum Capacity" for door interfaces. 3.48 Incorrect arm message when arm area with door tamper (OG-23429) This hot fix resolves an issue that caused an incorrect arm message. 3.49 OnGuard is not reporting 'Pod Trouble' alarms that occur on the NGP panel (OG-23455) This hot fix resolves an issue that caused OnGuard to not report Pod Trouble alarms that occurred on the NGP panel. 3.50 NGP: The "Device" is not identified in Alarm Monitoring during "Duress Alarm" (OG-23477) This hot fix resolves an issue in which the device name is not presented in Alarm Monitoring during a Duress event. 2012 Lenel Systems International, Inc. 21

3.51 Maximum number of Downstream Devices under Capacity tab is 96, but more than 96 downstream devices can be added (OG-23500) This hot fix resolves an issue that caused more than 96 downstream devices to be able to be added even though the Capacity tab stated 96. 3.52 NGP does not save proper configuration changes when sorting by one of the columns (OG-23528) This hot fix resolves an issue that caused NGP to not save the correct configuration changes sorting by one of the columns. 3.53 Door circuit setting is changed to "Not Supervision, Normally Closed" when modifying the "Request to exit circuit" setting (OG-23565) This hot fix resolves an issue in which the actual Door circuit setting is changed to "Not Supervision, Normally Closed" when modifying the "Request to exit circuit" setting. 3.54 NGP panel download fails if onboard alarm panel output configured to be activated by timezone (OG-23686) This hot fix resolves an issue in which the NGP panel download fails if the onboard alarm panel output is configured to be activated by timezone. 3.55 User cannot add 1024 alarm inputs for NGP panel in System Administration (OG-23726) This hot fix resolves an issue in which the user cannot add 1024 alarm inputs for the NGP panel in System Administration. The following message appears: Cannot add an alarm panel to this access panel since the maximum allowed (64) have already been added. 3.56 Badge count in Capacity tab does not refresh automatically (OG-23782) This hot fix resolves an issue in which the badge count in the Capacity tab does not refresh automatically. 3.57 Guardall Px/Qx/Rx - The arming/disarming pop-up menu is not displayed when you right-click an area (OG-24006) This hot fix resolves an issue that caused the arming/disarming pop-up menu to not be displayed when you right-click an area for a Guardall Px/Qx/Rx panel. 3.58 Galaxy GD520 alarms for Keypad, RIO, and Central unit do not get reported uniquely (OG-24071) This hot fix resolves an issue that caused Galaxy GD520 alarms for the Keypad, RIO, and Central unit to not get reported uniquely. 2012 Lenel Systems International, Inc. 22

3.59 ACS.INI setting that controls the NGP 'Access service menu' and 'Perform service test' permission profile configuration should be removed (OG-24446) This hot fix resolves this issue. 3.60 Guardall Px/Qx/Rx status issue with Arming/Disarming (OG-24538) This hot fix resolves a Guardall Px/Qx/Rx status issue with Arming/Disarming. 3.61 Guardall panel clock can be up to 59 seconds off from the actual time (OG-24823) This hot fix resolves an issue in which a Guardall panel clock can be up to 59 seconds off from the actual time. 3.62 Permission Profiles will not be downloaded to NGP panels correctly in an Enterprise system (OG-25073) This hot fix resolves an issue in which Permission Profiles will not be downloaded to NGP panels correctly in an Enterprise system. 3.63 NGP: The "Area" is not identified in Alarm Monitoring when a "Duress" Alarm is reported (OG-25219) This hot fix resolves an issue in which the "Area" is not identified in Alarm Monitoring when a "Duress" Alarm is reported. 3.64 Guardall Px device translator is filtering out the Set/Unset alarms from being reported to OnGuard (OG-25249) This hot fix resolves an issue in which the Guardall Px device translator is filtering out the Set/Unset alarms from being reported to OnGuard. 3.65 Guardall Px/Qx/Rx Area Status does not display properly in Alarm Monitoring when the panel first comes online (OG-25267) This hot fix resolves an issue in which Guardall Px/Qx/Rx Area Status does not display properly in Alarm Monitoring when the panel first comes online. 3.66 Guardall Px/Qx/Rx debug logging is inconsistent with standard OnGuard logging mechanism (OG-25268) This hot fix resolves an issue in which Guardall Px/Qx/Rx debug logging is inconsistent with standard OnGuard logging mechanism. 3.67 Cardholder Time & Attendance Report Displays Double Entries for NGP 3320i with SDC Module (OG-25636) This hot fix resolves this issue. 2012 Lenel Systems International, Inc. 23

4 Identity Management 4.1 'No Biometric Template Data' alarm in Alarm Monitoring (OG-18857) This hot fix resolves an issue that caused a No Biometric Template Data alarm in Alarm Monitoring. 4.2 OnGuard is not compatible with DigiOn24 MIFARE encoders with firmware version greater than 4.40 (OG-20472) This hot fix resolves an issue that caused OnGuard to not be compatible with DigiOn24 MIFARE encoders with firmware version greater than 4.40. Firmware version 4.92 is supported and validated with this hot fix. For more information, refer to the compatibility charts on the Lenel Web site: http://www.lenel.com/support/downloads/onguard#compatibility-charts. (You will need your Lenel login to gain access to this site.) 4.3 Badge Activate/Deactivate dates are not selected when a Default Badge Type is set in FormsDesigner (OG-22528) This hot fix resolves an issue in which when a default badge type was set for a cardholder or visitor, the Activate/Deactivate dates were not correctly set. This resulted in save errors when the user adding a cardholder or visitor did not have permission to access the Badge tab. 4.4 CSSN ID Number not exposed in FormsDesigner (OG-22635) This hot fix resolves an issue in which when scanning a license or passport that contains an ID that is separate from the license number, the ID was not made available. 4.5 Add support for BIO-4GFXU1H and BIO-4GFXU1 with firmware version 4.1.10 (OG-23239) This hot fix includes support for BIO-4GFXU1H and BIO-4GFXU1 with firmware version 4.1.10. 4.6 Enabled wide character support for the CSSN SDK (OG-22736) This hot fix includes updates to enable wide character support when invoking ScanShell functionality for ID (driver license) and passport scanning. 4.7 Bioscrypt BII_V1100.dll causes intermittent issues within OnGuard applications (OG-22779) This hot fix resolves an issue in which a Bioscrypt BII_V1100.dll file caused intermittent issues within OnGuard applications. 4.8 System Administration may close unexpectedly during Scanshell 1000A import (OG-22836) This hot fix resolves an issue in which System Administration may close unexpectedly during a Scanshell 1000A import after using Forms Designer to remove the Signature and Facial Image fields. 2012 Lenel Systems International, Inc. 24

4.9 Zebra 430i fails to print/encode when data for Track 1 contains lower case characters (OG-23814) This hot fix resolves an issue that caused the Zebra 430i printer to fail to print/encode when data for Track 1 contained lower case characters. 4.10 Memory leak when capturing LG Iris templates (OG-23858) This hot fix resolves an issue in which there was a memory leak when capturing LG Iris templates. 4.11 Digion 24 encoder not available on Create Key Card for OES MIFARE (OG-24173) This hot fix resolves an issue in which Create Key Card was not possible using the Digion 24 for OES MIFARE because the encoder did not appear in the drop-down even when the Digion 24 was defined correctly. 4.12 Custom format not supported for Omnikey proximity card (OG-24775) This hot fix includes the ability to support custom Omnikey proximity card ATR decode formats. The additional functionality parses the Omnikey registry settings as defined in the Omnikey 5125 Registry Settings document. Only the badge ID registry settings are read - the facility code is ignored since only the badge ID is imported. The badge ID length is determined by the number of digits specified in the custom registry settings. The custom mode (ProxFormat = 255) must be set. 4.13 Unable to see the HID Corporate 1000 format in Card Formats (OG-25241) This hot fix resolves an issue in which when setting up a new Weigand card format you are unable to select HID Corporate 1000 under the Special dropdown. 5 Visitor Management 5.1 Incorrect syntax is included in a ClickOnce config file (OG-21306) This hot fix resolves an issue in which there was incorrect syntax included in a ClickOnce config file. 5.2 Personnel, Personal Details Report Does Not Show Information for Visitors (OG-22407) This hot fix resolves an issue that caused the Personnel, Personal Details report to not display the contact information for Visitors. 5.3 Visitor Management does not work when the database contains userdefined fields (OG-22498) This hot fix resolves an issue that prevented Visitor Management from working properly if user-defined fields were used to modify Cardholder, Visit, Badge, or Visitor forms. 2012 Lenel Systems International, Inc. 25