+ All Categories
Home > Documents > Resolved Issues for OnGuard® 7.0 and Service Pack...

Resolved Issues for OnGuard® 7.0 and Service Pack...

Date post: 27-Jul-2018
Category:
Upload: tranque
View: 235 times
Download: 1 times
Share this document with a friend
28
Lenel Systems International, Inc. 1212 Pittsford-Victor Road Pittsford, New York 14534 Tel 866.788.5095 Fax 585.248.9185 www.lenel.com DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 1 Resolved Issues for OnGuard® 7.0 and Service Pack Releases Contents 1. Introduction ........................................................................................................................................3 2. OnGuard 7.0 SP2 Resolved Issues ......................................................................................................3 2.1. Access Control ............................................................................................................................3 2.2. Alarm Monitoring .......................................................................................................................3 2.3. Archiving .....................................................................................................................................3 2.4. Communication Server ...............................................................................................................3 2.5. DataConduIT ...............................................................................................................................4 2.6. DataExchange .............................................................................................................................4 2.7. Digital Video ...............................................................................................................................4 2.8. Enterprise ...................................................................................................................................4 2.9. Linkage Server.............................................................................................................................5 2.10. Login Driver.................................................................................................................................5 2.11. Replicator....................................................................................................................................5 2.12. Reports .......................................................................................................................................5 2.13. Segmentation .............................................................................................................................5 2.14. System Administration ...............................................................................................................5 3. OnGuard 7.0 SP1 Resolved Issues ......................................................................................................6 3.1. Access Control ............................................................................................................................6 3.2. Actions ........................................................................................................................................6 3.3. Alarm Monitoring .......................................................................................................................6 3.4. Archives ......................................................................................................................................6 3.5. Cardholder View .........................................................................................................................6 3.6. Communication Server ...............................................................................................................7 3.7. DataConduIT ...............................................................................................................................7 3.8. DataExchange .............................................................................................................................7 3.9. Digital Video ...............................................................................................................................7 3.10. Global Input/Output (I/O) ..........................................................................................................7 3.11. Licensing .....................................................................................................................................7 3.12. Linkage Server.............................................................................................................................7 3.13. NGP .............................................................................................................................................7 3.14. Replicator....................................................................................................................................8 3.15. Segmentation .............................................................................................................................8 3.16. System Administration ...............................................................................................................8 4. OnGuard 7.0 Resolved Issues .............................................................................................................9 4.1. Access Control ............................................................................................................................9 4.2. Alarm Monitoring .....................................................................................................................10 4.3. Area Access Manager ...............................................................................................................13
Transcript

Lenel Systems International, Inc. 1212 Pittsford-Victor Road Pittsford, New York 14534 Tel 866.788.5095 Fax 585.248.9185 www.lenel.com

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 1

Resolved Issues for OnGuard® 7.0 and Service Pack Releases

Contents 1. Introduction ........................................................................................................................................ 3 2. OnGuard 7.0 SP2 Resolved Issues ...................................................................................................... 3

2.1. Access Control ............................................................................................................................ 3 2.2. Alarm Monitoring ....................................................................................................................... 3 2.3. Archiving ..................................................................................................................................... 3 2.4. Communication Server ............................................................................................................... 3 2.5. DataConduIT ............................................................................................................................... 4 2.6. DataExchange ............................................................................................................................. 4 2.7. Digital Video ............................................................................................................................... 4 2.8. Enterprise ................................................................................................................................... 4 2.9. Linkage Server............................................................................................................................. 5 2.10. Login Driver ................................................................................................................................. 5 2.11. Replicator .................................................................................................................................... 5 2.12. Reports ....................................................................................................................................... 5 2.13. Segmentation ............................................................................................................................. 5 2.14. System Administration ............................................................................................................... 5

3. OnGuard 7.0 SP1 Resolved Issues ...................................................................................................... 6 3.1. Access Control ............................................................................................................................ 6 3.2. Actions ........................................................................................................................................ 6 3.3. Alarm Monitoring ....................................................................................................................... 6 3.4. Archives ...................................................................................................................................... 6 3.5. Cardholder View ......................................................................................................................... 6 3.6. Communication Server ............................................................................................................... 7 3.7. DataConduIT ............................................................................................................................... 7 3.8. DataExchange ............................................................................................................................. 7 3.9. Digital Video ............................................................................................................................... 7 3.10. Global Input/Output (I/O) .......................................................................................................... 7 3.11. Licensing ..................................................................................................................................... 7 3.12. Linkage Server............................................................................................................................. 7 3.13. NGP ............................................................................................................................................. 7 3.14. Replicator .................................................................................................................................... 8 3.15. Segmentation ............................................................................................................................. 8 3.16. System Administration ............................................................................................................... 8

4. OnGuard 7.0 Resolved Issues ............................................................................................................. 9 4.1. Access Control ............................................................................................................................ 9 4.2. Alarm Monitoring .....................................................................................................................10 4.3. Area Access Manager ...............................................................................................................13

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 2

4.4. Badge Printing ..........................................................................................................................13 4.5. Cardholders ..............................................................................................................................13 4.6. Central Station ..........................................................................................................................13 4.7. Client Update ............................................................................................................................14 4.8. Communication Server .............................................................................................................14 4.9. Database ...................................................................................................................................15 4.10. DataConduIT .............................................................................................................................15 4.11. DataExchange ...........................................................................................................................16 4.12. Default Data ..............................................................................................................................16 4.13. Digital Video .............................................................................................................................17 4.14. Discovery Console .....................................................................................................................18 4.15. Elevators ...................................................................................................................................18 4.16. Enterprise .................................................................................................................................19 4.17. FormsDesigner ..........................................................................................................................19 4.18. Guardall ....................................................................................................................................20 4.19. Identity Management ...............................................................................................................20 4.20. Installation ................................................................................................................................20 4.21. Intrusion Detection ...................................................................................................................21 4.22. Licensing ...................................................................................................................................21 4.23. Linkage Server...........................................................................................................................21 4.24. NGP ...........................................................................................................................................21 4.25. Remote Monitoring ..................................................................................................................23 4.26. Replicator ..................................................................................................................................23 4.27. Replication Administration .......................................................................................................24 4.28. Reports .....................................................................................................................................25 4.29. Segmentation ...........................................................................................................................25 4.30. Setup Assistant .........................................................................................................................26 4.31. Supplemental Materials Disc ....................................................................................................26 4.32. System Administration .............................................................................................................26 4.33. Visitor Management .................................................................................................................27 4.34. Web Application Server ............................................................................................................27 4.35. Web Area Access Manager .......................................................................................................27 4.36. Web Service ..............................................................................................................................27 4.37. Web VideoViewer .....................................................................................................................28

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 3

1. Introduction This document contains a list of issues that have been resolved in OnGuard 7.0 and subsequent service pack releases. This document is intended as a supplement to the OnGuard 7.0 SP2 Release Notes.

2. OnGuard 7.0 SP2 Resolved Issues This section contains a list of issues that have been resolved in OnGuard 7.0 SP2.

2.1. Access Control • Access granted to cardholder at reader that is not in an access level assigned to

cardholder (EE5492): This release resolves this issue. Access level assignments work as expected.

2.2. Alarm Monitoring • Alarm Monitoring displays events in an odd format when moving from one remote

connection to another (OG-28963): This release resolves this issue. Alarm Monitoring displays events as expected.

• Alarm Monitoring stops working when performing an alarm acknowledgement (OG-30205): This release resolves this issue. Alarm Monitoring works as expected.

2.3. Archiving • Error occurs while restoring events from an archive (DE9421, EE5402): This release

resolves this issue. Events can be restored from an archive as expected.

2.4. Communication Server • Memory spikes cause Communication Server to stop working (DE5050): This release

resolves this issue. The Communication Server works as expected when several Alarm Monitoring stations are connected to a single Communication Server monitoring the same zone.

• OUT Reader on NGP-1320 loses assigned access levels when upgraded to latest version of OnGuard (DE7079, EE5687): This release resolves this issue. Access levels on OUT Reader on NGP-1320 are retained as expected during an OnGuard upgrade.

• Communication Server and Linkage Server gradually lose functions if temporarily disconnected from the database multiple times (DE7094, EE5522): This release resolves this issue. The Communication Server and Linkage Server work as expected.

• Badges are not downloaded to panels (DE7971): This release resolves this issue. Badges are downloaded to the panels as expected.

• Lenel Error Log flooded with “Internal Logic Error” messages (DE8599): This release resolves this issue. The “Internal Logic Error” message is no longer generated when the NGP Panel with I/O reader is online.

• ILS locks fail to execute reader mode change at end of Timezone Reader Mode if start or end intervals overlap with different day of week selections (DE9308, DE9427): This release resolves this issue. ILS locks execute reader mode as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 4

• Areas assigned to an NGP LCD keypad do not update properly after a database download (DE9316, DE9390, EE6022): This release resolves this issue. Area assignments work as expected after a database download.

• OTIS embedded reader does not recognize card format offset (DE9739): This release resolves this issue. The OTIS embedded reader recognizes supported card formats and offsets as expected.

• Socket leaks with Galaxy and NGP panels affect overall system stability and prevent communication to/from devices (DE10797): This release resolves this issue. Galaxy and NGP panels work as expected.

• Unnecessary query to BADGE_NGP table is performed when downloading cardholders to non-NGP panel types causing the Communication Server to stop working (OG-29460, EE5714): This release resolves this issue. Panel downloads and the Communication Server work as expected.

2.5. DataConduIT • DataConduIT and Replicator experience memory issues during massive badge updates

(DE8561, EE5742): This release resolves this issue. DataConduIT and Replicator work as expected under extreme resource demands.

2.6. DataExchange • Unable to change the database connection for a new DataExchange import script

(DE8127, EE5522): This release resolves this issue. The ODBC dialog opens as expected after clicking Change Connection.

• “Unable to Connect to Source” error message: General error: invalid window handle (DE8703, EE5895): This release resolves this issue. DataExchange executes scripts as expected.

2.7. Digital Video • Alarm Monitoring takes longer than expected to show status for Lenel NVRs and

cameras on Enterprise systems with a large number of Lenel NVRs sharing the same Communication Server (DE5701): This release resolves this issue. Alarm Monitoring shows status for Lenel NVRs and cameras on Enterprise systems in an acceptable amount of time.

2.8. Enterprise • Access level modifications on separate badges may cause “Failed – Requires User

Decision” errors during replication (DE5992, EE5244): This release resolves this issue. Modifications made to access levels on separate badges works as expected.

• Replication to one region is much slower than other regions (DE7639, EE5696): This release resolves this issue. Replication to all regions works as expected.

• Communication Server can take up to 5 minutes to reconnect to database when updating a badge on master and region servers, preventing badge updates from reaching panel (DE7642, EE5522): This release resolves this issue. The Communication Server works as expected during badge updates on the master and region servers.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 5

• Replication does not transfer date/time values in UTC causing discrepancies to appear between the Master and Region if in different time zones (DE7660, EE5451): This release resolves this issue. Date and time values transfer in UTC as expected.

• Site Publication Server experiences connection issues over SSL (DE7663, EE5419): This release resolves this issue. Transactions replicate from Master to Region, and Region to Master as expected.

• “Failed – Requires User Decision” errors occur in Replication when making access level changes on separate badges assigned to the same cardholder (DE7664, EE5244): This release resolves this issue. Replication works as expected.

• Site Publication Server experiences memory issues due to slow hardware command processing (DE8143, EE5662): This release resolves this issue. The Site Publication Server works as expected.

2.9. Linkage Server • Linkage Server on a Master Server generates Failed RPC records from “Use or Lose”

and “Deactivate” Status threads (DE9530): This release resolves this issue. The Linkage Server on a Master Server works as expected.

2.10. Login Driver • “Database error encountered” message appears when changing password from Login

Driver (DE7786, EE5522): This release resolves this issue. Changing the login password from the Login Driver.

2.11. Replicator • Site Publication Server does not download segment groups as additional segments

(OG-30355, EE5183): This release resolves this issue. The Site Publication Server downloads segment groups as additional segments as expected.

2.12. Reports • “Cardholder Report Generation Error” occurs when trying to search using multiple

criteria, including with/without photo or signature (EE5542): This release resolves this issue. Cardholder reports can be generated and searched using multiple criteria as expected.

• Error occurs when generating a cardholder report sorted by last name and filtered by “No Directory” for account (EE5578): This release resolves this issue. Cardholders can be sorted and filtered in order to generate a report as expected.

2.13. Segmentation • Cardholders and badges cannot be modified in an environment with Cardholder

Segmentation enabled after upgrading from OnGuard 6.5.624 to OnGuard 7.0.1067 (DE6150, EE5402): This release resolves this issue. Cardholders and badges can be modified as expected after upgrading OnGuard.

2.14. System Administration • Use of identical DNS names with different port numbers for access panels not possible

(DE5993): This release resolves this issue. Access panels with the same hostname but different port numbers can be added in System Administration as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 6

• Invalid zone number in Alarm Monitoring for alarms from Galaxy 18/128/500 panels (OG-30199): This release resolves this issue. Zone numbers are displayed correctly in Alarm Monitoring for Galaxy panels.

3. OnGuard 7.0 SP1 Resolved Issues This section contains a list of issues that have been resolved in OnGuard 7.0 SP1.

3.1. Access Control • Despite several database downloads, controller status still displays as “Secondary”

even though controller communicates via primary connection (OG-28653): Updating to controller firmware 1.194 resolves this issue.

• A slave reader for a dual reader interface added using the Wizard does not work (OG-29730): This release resolves this issue. The slave reader works as expected when added using the Wizard.

• Global I/O does not unmask input groups (OG-30099): This release resolves this issue. Input groups are unmasked in Global I/O as expected.

• Only the first of multiple AD 300 locks comes online (OG-30124): This release resolves this issue. All AD 300 locks come online as expected.

• Lenel Access Control Series controllers lose badges and other data unexpectedly; a controller download resolves issue (OG-30160): Firmware revision 1.194 resolves an issue in which controllers unexpectedly lose card formats, badges and other data.

3.2. Actions • Scheduler/actions may not load if installing OnGuard on a new system with SQL Server

2012 or higher (OG-30066): This release resolves this issue with SQL Native Client 10.

3.3. Alarm Monitoring • Alarm Monitoring operation slows after the “Display Controller Capacity” option is

enabled (OG-30059): This release resolves this issue. Alarm Monitoring works as expected.

• Alarm Monitoring stops working while performing certain operations when the Occupancy Report dialog is open (OG-30060): This release resolves this issue. Alarm Monitoring works as expected.

3.4. Archives • Enabling archive database feature on SQL Express does not launch Setup Assistant

(OG-30203): This release resolves this issue. Setup Assistant launches as expected when the archive database feature in SQL Express is enabled.

3.5. Cardholder View • “Does not have at least one of the selected levels” option on the Cardholder Access

Levels sub-tab does not work (OG-30166): This release resolves this issue. The “Does not have at least one of the selected levels” option works as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 7

3.6. Communication Server • Input/Output Local Linkage no longer works for Lenel Access Series controllers after

performing a full download (OG-30082): This release resolves this issue. Input/Output Local Linkage works as expected for all Lenel Access Series controllers.

3.7. DataConduIT • The PrimarySegmentId parameter cannot be used as a filter when using Lnl_Cardholder

class (OG-30156): This release resolves this issue. The PrimarySegmentId parameter works as expected.

3.8. DataExchange • “Scroll cursor can’t select blob columns” error message occurs in DataExchange

(OG-29723): This release resolves this issue. DataExchange scripts work as expected.

3.9. Digital Video • Alarm Monitoring stops working when the Video window is maximized and the Alarm

Monitoring window is minimized then maximized (OG-29945): This release resolves this issue. Alarm Monitoring works as expected when minimized or maximized with the Video window maximized.

3.10. Global Input/Output (I/O) • Global I/O does not unmask input groups (OG-30099): This release resolves this issue.

The Global I/O masks and unmasks as expected.

3.11. Licensing • Wi-Q readers added to OnGuard against Local Readers license count OG-30074): This

release resolves this issue. Wi-Q readers are no longer counted against the Local Readers license in OnGuard.

3.12. Linkage Server • The Linkage Server stops working while processing temporary access levels; an “Out of

memory/failed writing update” error message appears (OG-29921): This release resolves this issue. The Linkage Server works as expected.

3.13. NGP • Two events appear in Alarm Monitoring with one badge swipe (OG-29951): This release

resolves this issue. Only one event is generated as expected in Alarm Monitoring when a badge is swiped.

• NGP/NGP with OCF does not perform an automatic database download when upgrading firmware from an older version (OG-30116): This release resolves this issue. The database automatically downloads as expected after a firmware update.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 8

3.14. Replicator • Site Publication Server stops publishing transactions if a particular transaction fails to

pre-load transaction data (OG-30085): This release resolves this issue. The Site Publication Server works as expected.

• Hardware transaction error occurs when Replicator is used after several hardware additions and deletions (Enterprise) (OG-30030): This release resolves this issue. The Replicator works as expected.

• Vinca key registry setting required for Microsoft Cluster or NEC ExpressCluster 64-bit configurations (OG-30110): This release resolves this issue. The Vinca key setting is now included in the registry file on the Supplemental Materials disc.

• Enterprise transactions may fail if the date/time formats differ between the source and target site (OG-30123): This release resolves this issue. No errors occur when date format is changed to dd-MMM-yy in Region and then Replication is done after modification on Master.

• Publication Site Server stops working when handling large numbers of skipped transactions due to segmentation rules (OG-30133): This release resolves this issue. The Publication Site Server now works as expected.

• “Too many parameters” error message appears in log file when modifying cardholders (OG-30140): This release resolves this issue. Replication completes as expected without any errors in the log file.

• Site Publication Server – Transactions appear stuck in “Awaiting Processing at Destination” status if source transaction is deleted from BDG2TRN record (OG-30149): This release resolves this issue. Transactions are processed as expected.

3.15. Segmentation • Adding badges for badge types with additional segments causes System

Administration to stop working when logged into the primary segment of the badge type (OG-30136): This release resolves this issue. Adding a cardholder with a badge type assigned to multiple segments works as expected.

3.16. System Administration • Auxiliary outputs on 2RP CASI readers are not functional (OG-30120): This release

resolves this issue. The auxiliary outputs on 2RP CASI readers work as expected.

• Access panel "promote" process does not work if an LNL-1320 is configured with both readers (OG-30131): This release resolves this issue. Access panels with dual readers defined can be promoted as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 9

4. OnGuard 7.0 Resolved Issues This section contains a list of issues that have been resolved in OnGuard 7.0.

4.1. Access Control • Turnstile Mode Issues: Access Granted/Door Used when first person is in turnstile and

second person presents badge (OG-12944): Turnstile Mode now pulses strike even when status input is asserted. Upgrading to panel firmware version 1.173 or later is required.

• Event Flooding of LNL-500, -1000, and -2000 Panels (OG-20357): This release resolved an issue in which LNL-500, -1000, and -2000 panels are flooded with events (tens of thousands) if multiple badges are presented shortly after the panel loses a network connection.

• LNL-2220 Panel shows incorrect connection type after reboot (OG-22798): This release resolves an issue in which the LNL-2220 panel displayed an incorrect connection type on its configuration web page after the panel is rebooted. Upgrading to panel firmware version 1.173 or later is required.

• LNL-1320-U with firmware v.10.11 goes offline when downstream from an LNL-8000 (OG-23059): This release resolves this issue. An LNL-1320-U with firmware v.10.11 installed stays online when connected to an LNL-8000.

• A fire alarm point restored at keypad and NGP keypad displays as “Burglary Restored” in Alarm Monitoring (OG-23078): This release resolves an issue in which a fire alarm point that is restored at the keypad and NGP keypad displays as “Burglary Restored” in Alarm Monitoring. A restored fire alarm point now displays as “Fire Restored” in Alarm Monitoring.

• Automatic changes does not work properly when ILS time zones assigned to ILS locks are not in order (data sent from PDA) (OG-24483): This issue is resolved in the ILS PDA Application version 2.0.4.5.

• NGP LCD keypad multi-badge delay not properly configured in panel (OG-24690): This release resolves this issue. The multi-badge delay is now properly configured in the panel.

• V-Station 2G/3G Keypad does not operate in Cipher Mode when connected to an LNL-1300 Series 2 Single Reader Interface Module (OG-24516): This release resolves this issue. Cipher Mode works as expected for both V-Station 2G/3G Keypads. All other user commands entered at the V-Station 2G/3G Keypads also work as expected.

• Guardall panel clock can be up to 59 seconds off from the actual time (OG-24823): This release resolves this issue.

• Cardholder Time & Attendance report displays double entries for NGP 3320i with NGP-1300-U Single Door Controller connected (OG-25636): This release resolves this issue. The Cardholder Time and Attendance report displays entries as expected.

• Incorrect battery level indication is displayed for ILS wireless locks (OG-25729): This release resolves this issue. The battery level indication for ILS wireless locks is displayed as expected.

• No way to release the Mercury Local I/O time zone once it is activated (OG-25786): This release resolves this issue. The Pulse command can be used to release the time zone to normal operation from a prior permanent activation or deactivation.

• Cards encoded with specific badge numbers are not read by the iCAM 4000 or iCAM 7000 Iris cameras (OG-26057): This issue is resolved with iCAM 4000 firmware version 3.05.02 and iCAM 7000 firmware version 7.08.02.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 10

• iCAM 4000 and iCAM 7000 Iris Cameras are not reading cards in Option 1 when using an external reader (OG-26058): This release resolves this issue. Iris cameras read cards as expected.

• NGP area groups are not enabled (OG-26454): This release resolves this issue. Area groups can be enabled from the NGP keypad and remain enabled when OnGuard downloads to the controller.

• Global I/O actions stop functioning after SQL Server is restarted (OG-26608): This release resolves this issue. Global I/O actions continue to function as expected after SQL Server is restarted.

• Tailgate option (Readers Form>Settings Tab) is not correctly validated for Mercury readers (OG-26860): This release resolves this issue. The Tailgate option validates for Mercury readers as expected.

• Users without internal accounts cannot add event text to Global I/O Generic Event type (OG-26865): This release resolves this issue. Users are not required to have an internal account in order to add event text in the Event Text field when creating a Generic Event global I/O.

• Verification errors occur when using the 4GFXS Readers with the LNL-1320 Dual Reader Interface Module (OG-27036): This issue is resolved using the following updates:

• LNL-1320 firmware version 1.55 or later • Bioscrypt 4G firmware version 4.1.12.0.2.0.0 or later

• NGP LCD Keypad removed from local I/O function and access level definitions (OG-27220): The NGP LCD Keypad is not a reader and cannot lock or reinstate a lock. Therefore, it has been removed from the definitions for local I/O functions and access levels.

• Entering more than 255 characters in the Notes field for a Reader results in a “Data truncated” error message and generates false events (OG-27800): This release resolves this issue. The “Data truncated” error message no longer appears when more than 255 characters are entered into the Reader Notes field. Up to 1999 characters can now be added. OnGuard also no longer generates false events.

4.2. Alarm Monitoring • “Biometric Mismatch, No Biometric Template Data” alarms reported in Alarm

Monitoring (OG-18857): This release resolves an issue in which “Biometric Mismatch, No Biometric Template Data” alarms are reported in Alarm Monitoring when an RSI Handkey biometric score in a cardholder’s biometric template surpasses the individual/system rejection threshold.

• Multiple events are generated in Alarm Monitoring for all readers when modifying a single reader (OG-22788): This release resolves an issue in which multiple events are generated for all readers when modifying a single reader.

• Performance issues when loading Alarm Monitoring with several video devices configured (OG-24679): This release resolves this issue. Alarm Monitoring loads as expected.

• Alarm Monitoring does not display “Burglary Restore” after the system is reset (OG-24723): This release resolves an issue in which Alarm Monitoring continues to show “Burglary Alarm” after a Guardall system is reset. Alarm Monitoring now shows “Burglary Restore” when the system is reset.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 11

• “SMux Provider: Physical connection is not usable” errors when acknowledging alarms (OG-24883): This release resolves an issue that caused “SMux Provider: Physical connection is not usable” errors when acknowledging alarms.

• Alarm Monitoring does not exit properly when Windows session ends (OG-24543): This release resolves an issue that caused Alarm Monitoring to not exit properly when the Windows session ends.

• “Intercom Exchange Failure” message in Alarm Monitoring (OG-24692): This release resolves an issue with how intercom failure and restoral messages are displayed in Alarm Monitoring. When an intercom is disconnected, Alarm Monitoring now shows “Intercom Exchange Failure.” When the intercom is reconnected, Alarm Monitoring now shows “Intercom Exchange Failure OK.”

• Custom format not supported for Omnikey proximity card (OG-24775): This release supports custom Omnikey proximity card ATR decode formats.

• Door Held Open status display issue after unmasking on Alarm Monitor (OG-24909): This release resolves this issue. The door no longer remains in a Door Held Open status in Alarm Monitoring after it is unmasked.

• Failure to activate/deactivate/pulse “Both Reader Auxiliary Outputs” in Alarm Monitoring (OG-24922): This release resolves an issue when attempting to activate, deactivate, or pulse the auxiliary outputs on a reader from Alarm Monitoring.

• In Alarm Monitoring - Edit menu items are duplicated for custom added menu items (OG-25090): This release resolves an issue in which Edit menu items are duplicated for custom added menu items.

• Separating readers connected to the same Reader Interface Module can create a “Reader Interface Offline” status in Alarm Monitoring (OG-25217): In order to separate readers connected to the same Reader Interface Module RIM) with monitoring zones, the second reader must contain the first reader. Otherwise, a “Reader Interface Offline” status (yellow “X”) appears next to the RIM in Alarm Monitoring.

• In Alarm Monitoring, the area is not identified when an NGP Duress alarm is reported (OG-25219): This release resolves an issue in which the area is not identified in Alarm Monitoring when a “Duress” alarm is reported.

• Guardall Px/Qx/Rx Area status does not display properly in Alarm Monitoring when the panel first comes online (OG-25267): This release resolves an issue in which Guardall Px/Qx/Rx Area Status does not display properly in Alarm Monitoring when the panel first comes online.

• “Device Type Mismatch” alarm does not clear from Alarm Monitoring when an NGP panel is mismatched (OG-25517): This release resolves this issue. The "Device Type Mismatch" alarm is no longer generated for the incorrect panel model type. The status in Alarm Monitoring does display the"Controller/configuration type mismatch" message.

• Central Station report delay is not reported in Alarm Monitoring (OG-25881): NGP firmware version 1.02.032 and later resolves an issue where the “HSC Trouble” event was reported only when central station communication was established and then lost. Now, the event is also reported even when the central station has not been contacted since the last NGP panel startup.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 12

• Duplicate Key Errors when adding in the hex address of Spider Alert device (OG-26204): Configuration of hexadecimal addresses with combinations of a letter and a number is configured and saved where it previously failed. The devices are present online and report alarms correctly in Alarm Monitoring.

• In Alarm Monitoring, if a software communication error occurs with an NGP, the NGP panel icon is marked with the wrong indication (OG-26620): This release resolves an issue in which the NGP panel icon in Alarm Monitoring displays as black (offline) instead of red when experiencing a software communication error. The icon now displays as intended.

• When sending Generic Input events, the alarm name is displayed in OnGuard instead of the text that associated with the event (OG-26778): In Alarm Monitoring, when Generic Input events are sent, its associated text now appears for the alarm description instead of only the alarm name. Generic Input events are:

• Input Alarmed - L_GENERIC_INPUT_ALARMED • Input Normal - L_GENERIC_INPUT_NORMAL • Input Low Low - L_GENERIC_INPUT_LOW_LOW • Input Low - L_GENERIC_INPUT_LOW • Input High - L_GENERIC_INPUT_HIGH • Input High High - L_GENERIC_INPUT_HIGH_HIGH

• The “Next to Master/Perimeter Arm” checkmark does not display in the Alarm Monitoring hardware tree (OG-26864): This release resolves this issue. The checkmark appears next to the appropriate selection based on the current area arming state.

• Device/Camera links in Alarm Monitoring do not work (OG-27116): This release resolves this issue. Camera/device links work as expected in Alarm Monitoring.

• Access panels fail to come online in Alarm Monitoring (OG-27118): This release resolves this issue. Access panels (Mercury and NGP) come online in Alarm Monitoring as expected.

• Custom “Out of Zone Device Camera linkage” shows blank (white) video window for out-of-zone video recorders (OG-27125): This release resolves this issue. Video windows in Alarm Monitoring work as expected.

• With LNL-1320, Cabinet Tamper alarm appears and does not clear for both readers (OG-27972): This release resolves this issue. The Cabinet Tamper status is only displayed on Reader 1 when both readers are configured, and the status clears as expected when the tamper condition is restored.

• When alarms are forwarded to another workstation and acknowledged in a different order, the alarms are not acknowledged on the workstations (OG-29010): This release resolves this issue. Alarms that are forwarded to other workstations and acknowledged in a different order than they were forwarded in are acknowledged on the workstations as expected.

• Two opening door events after activating “Execute Command on Single Click” and “Disable Command Verification” (OG-29514): This release resolves this issue. A single click on the reader icon no longer triggers two pulses of the output (double opening command) when the “Execute Command on Single Click” and “Disable Command Verification” options are activated.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 13

• Readers assigned to the Lenel M Series access panels display as offline unless the first reader is included in the monitoring zone (OG-29171): This release resolves this issue. Readers assigned to the Lenel M Series access panels display as online as expected.

4.3. Area Access Manager • A user’s assigned Area Access Manager levels can be accidentally removed when

segments are in use (OG-25276): This release resolves this issue. Area access manager levels assigned to a user are retained when segments are enabled.

4.4. Badge Printing • Zebra ZXP Series 3 USB Card Printer requires addition to ACS.INI default file to enable

encoding (OG-25042): This release resolves the encoding issue with the Zebra ZXP Series 3 USB Card Printer. The ACS.ini default file includes the syntax to enable encoding for this printer.

• Cannot Modify Badge ID in System Administration after printing badge (OG-25861): Users are now able to Modify Badge ID after printing if the badge type, badge ID allocation is set to “From ‘Cardholder ID’”.

4.5. Cardholders • Simultaneously adding badges from two clients can exceed the maximum number of

active badges (OG-24822): This release resolves an issue that incorrectly enabled 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.

• A cardholder’s PIN appears as plain text when changed at the NGP Keypad (OG-25066): This release resolves an issue in which a cardholder’s PIN appears as plain text in Alarm Monitoring when the cardholder changes his/her PIN at the LCD keypad.

• “Save on Exit” feature does not save the “Show Last Attempted Access” preference from Cardholder Form (OG-27086): This release resolves this issue. The cardholder preference settings are saved after logout and login when selecting "Save Settings on Exit" feature in "View" menu.

• The “Status,” “Default door,” and “Two Man Type” fields do not refresh correctly for Add/Modify selections (OG-28268): This release resolves this issue. The “Status,” “Default door,” and “Two Man Type” fields on the Cardholders > Badge form refresh as expected.

4.6. Central Station • NGP: Central Station reporting issues (OG-25064): This release resolves several issues

with Central Station reporting from an NGP panel, including improper reporting of special alarms (AC failure, battery trouble), improper reporting of account codes, and account codes reported via SIA protocol being clipped to four digits.

• NGP connection to a Bosch IP receiver using non-SOCKS protocol does not work properly (OG-25776): This release resolves this issue.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 14

4.7. Client Update • Automatic client update not working on localized installations (OG-26392): This release

resolves this issue. The automatic client update works as expected.

• Unable to start LS Client Update Server configured under a virtual computer name (OG-27837): This release resolves this issue. The LS Client Update Server starts as expected when configured under a virtual computer name.

4.8. Communication Server • Software Connection Error: Panel offline unless the Communication Server is run as an

authenticated user (OG-22419): This release resolves this issue. The panel comes online when the Communication Server is started as a service.

• Communication server must be restarted to receive updated presets from the RC-C recorder (OG-23671): This release resolves this issue. The Communication server does not need to be restarted in order to receive updated presets from the RC-C recorder.

• Galaxy GD520 alarms for Keypad, RIO, and Central Unit are not reported correctly (OG-24071): This release resolves this issue. Galaxy GD520 alarms for the Keypad, RIO, and Central unit are reported as expected.

• CRC calculation is incorrect when sending NACK message while using SIA receiver output format (OG-25208): This release resolves this issue. The CRC calculation is now correct for a NACK message sent using SIA format.

• Input/output local linkage – heap corruption while reading output data (OG-25499): This release resolves this issue. The heap corruption while reading outputs on an NGP panel no longer occurs.

• Firmware download to Mercury panels may take longer than expected (OG-25503): This release resolves an issue in which a default poll delay resulted in firmware download times that were much longer than expected. In this release, the poll delay is automatically adjusted based on the online panel count.

• Database download breaks the Auxiliary Output 2 Function for the strike follower (OG-25631): This release resolves this issue. The Auxiliary Output 2 function for the strike follower works as expected after a database download.

• Access events are not logged in the database if the STATUSTZ, DENYTZ, and/or the GRANTTZ fields in the READER table are set to NULL (OG-25672): This release resolves this issue. Access events are logged as expected.

• Communication server startup performance can be greatly improved (OG-25707): Load time for records in the database has been improved by retrieving information when the Communication Server is first started.

• Alarm Monitoring does not display the correct state for an area (OG-26921): This release resolves an issue in which Alarm Monitoring did not show the correct state for an area when the area was in the "not ready for arming," "bypassed points," and/or the "forced points" states. Alarm Monitoring now shows the correct area state.

• After upgrading OnGuard, Enterprise installations may see Communication Server errors or issues with the Last Location replication (OG-26940): This release resolves an issue in which, after an upgrade, “Event Polling Stopped” errors would appear in Alarm Monitoring or errors with the Last Location replication would occur.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 15

• Galaxy panels have repeated continuous COMM loss (OG-28546): This release resolves this issue. Galaxy panels maintain stable communication when brought online in Alarm Monitoring.

• Guardall PX/QX/RX panels lose configuration settings such as IP address and wireless settings (OG-29107): This release resolves this issue. Guardall PX/QX/RX panels retain all configuration settings as expected.

4.9. Database • UTC conversion utility must be run before last location records can be changed

(OG-24370): With this release, the Last Location records can be changed without first running the UTC conversion utility.

• Subsequent run of database setup fails for upgraded database (OG-26279): This release resolves this issue. Database Setup runs as expected when upgrading the OnGuard database.

• Incremental database downloads are not functioning correctly for NGP (OG-26824): This release resolves this issue. Database downloads to an NGP panel no longer fail if communication between OnGuard and the NGP panel is interrupted.

• “Specified cast is not valid” error message occurs when upgrading Oracle Enterprise Master with custom reports (OG-29215): This release resolves this issue. The OnGuard upgrade works as expected when upgrading from database versions 6.3 or older.

• DataConduIT does not receive cardholder software events when there are a large number of user-defined fields (OG-29524): This release resolves this issue. DataConduIT receives cardholder software events as expected (for 64-bit systems only).

4.10. DataConduIT • When passing in time properties to an incoming DataConduIT message queue, the UTC

offset is ignored and set to -240 minutes (OG-21836): Before this release, when passing a message through an incoming message queue to the DataConduIT message queue service, it would accept time of the format 2010-12-20T14:30:00. However, it would ignore any UTC offset passed in, and set the offset to -240 minutes. After this fix, it now accepts time in the following 3 formats:

• 2010-12-20T14:30:00 (The UTC offset is set to the UTC offset on the machine in which DataConduITQueueServer.exe is running on.)

• 2010-12-22T21:00:00-05:00 (The offset is specified: -5 hours in this case. Positive/negative offsets and non-zero minutes are supported as well.)

• 2010-12-22T21:00:00Z (The trailing Z indicates that the time is specified in UTC.) • Wrong deactivate date for visitor badge when visit is signed in using DataConduIT

(OG-24680): This release resolves an issue that caused the wrong deactivate date for the visitor badge when the visit is signed in using DataConduIT.

• Unable to filter Lnl_LoggedEvent by AccessResult in DataConduIT (OG-24714): This release resolves this issue. The query for Lnl_LoggedEvent filter by AccessResult works as expected.

• DataConduIT - Cannot create a badge when the badge type's ID allocation = "import from card" (OG-25075): This release resolves an issue in which a badge cannot be created when the Badge Type's ID Allocation = "import from card".

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 16

• DataConduIT - Cannot create badge when "Automatic" is selected on Cardholder Options > Badge ID Allocation (OG-25397): This release resolves this issue. Badges can be created as expected.

• Defining custom alarms can put multiple items on the message queue and create delivery database errors (OG-25464): This release resolves an issue. Custom alarms can be defined in DataConduIT as expected.

• DataConduIT allows a visit to be added without setting a scheduled time in and time out (OG-25693): This release fixes this issue. DataConduIT now requires a scheduled time in or time out when added a visit.

• DataConduIT crashes when empty alarm is pulled from alarm list (OG-25856): This has been fixed so that DataConduIT continues to function properly.

• DataConduIT's Lnl_Account software events are not populating all fields (OG-26349): In versions of OnGuard before version 7.0, Client applications that subscribed to DataConduIT's _InstanceOperationEvent for the Lnl_Account would not receive data for the following account properties:

• DirectoryID • ID • PersonID

This issue is corrected in OnGuard 7.0.

4.11. DataExchange • DataExchange does not support synonyms during writeback (6x-9733): This release

resolves this issue. DataExchange can now write back to a third-party table in Oracle that uses synonyms.

• DataExchange fails to copy access levels (OG-26184): This release resolves this issue. DataExchange copies access levels as expected.

• DataExchange actions intermittently report failure even though the script runs properly (OG-26854): This release resolves this issue. DataExchange reports the correct status when executing an action via the Scheduler.

• Error occurs while exporting pictures when the “lastname” field contains special characters (OG-29219): This release resolves this issue. Special filename characters are now removed for the default "unique name" for images.

• DataExchange scripts stop working when importing from and/or writing to a table with a binary column (OG-29265): This release resolves this issue. DataExchange scripts work as expected.

4.12. Default Data • December 2011 Microsoft time zone updates (OG-24776): This release includes the

December 2011 Microsoft time zone updates.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 17

4.13. Digital Video • Video from Failover Recorder cannot be exported (OG-15744): This release resolves this

issue. Video from a camera set to failover can be exported from the primary Lenel NVR before, during, and after the failover.

• Exporting a video clip with bitmap that is larger than the video frame causes the export to stop responding (OG-21808): This release resolves this issue. The video exports without errors.

• Many Lenel NVR applications and utilities are not displaying correct version information (OG-23217): The following applications now follow the same version numbers as the rest of OnGuard applications: Lenel Hybrid Card VMD Configuration, Lenel NVR Live Video Setup, and Lenel Video Player.

• Communication Server needs to restart to get the updated presets from RC-C Recorder (OG-23671): This release resolves this issue. When importing PTZ camera presets to an RC-C recorder, you do not need to restart the Communication Server in order for the PTZ camera presets to display correctly in Alarm Monitoring.

• PTZ Zoom in NetEVS is reversed (OG-23778): This release resolves an issue that caused PTZ zoom in NetEVS to be reversed (Zoom in zoomed out and vice-versa).

• Multiple PTZ cameras called to their presets from single input only responds to first camera listing (OG-24044): This release resolves this issue. All PTZ cameras return to their configured presets when the input is triggered.

• Camera Tour in Alarm Monitoring does not stay maximized (OG-24064): This release resolves this issue. Camera Tour stays maximized in Alarm Monitoring.

• NetDVMS: Restoring the network connection does not give "Video Source Signal Lost" alarm (OG-24376): This release resolves this issue. When using a NetDVMS or RC-C recorder with an Axis Encoder, the camera status is reported as expected in Alarm Monitoring..

• When using Lenel NVR 7 with an older version of OnGuard (6.4 and earlier), Time-Lapse with H264 or MPEG4 will not work correctly (OG-24784): This release resolves this issue. Time lapses with H264 and MPEG4 work as expected when using Lenel NVR 7 with OnGuard 7.0.

• Speed control text does not update in a timely manner on video window (OG-25049): This release resolves an issue in which speed control text does not update in a timely manner on Video Window.

• Prism Migration Tool does not return any results for Lenel NVR’s on a Prism Server (OG-25106): This release resolves this issue. The Prism Migration Tool works as expected.

• Recorder/channel statistics not available in Prism (OG-25205): This release resolves an issue that prevents recorder and channel statistics from being retrieved in Prism.

• PTZ preset import has duplicates and also deletes and re-adds presets (OG-25220): This release resolves an issue in which PTZ Preset Import has duplicates and re-adds existing presets.

• Simultaneous PTZ preset actions executed through Global I/O’s increase handle count and memory usage in Linkage Server (OG-25298): This release resolves an issue in which linkage server bandwidth was heavily taxed by PTZ preset actions executed via global I/O’s. The linkage server is able to handle the PTZ preset action load.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 18

• Video Viewer takes longer than expected to display status tree (OG-25477): This release resolves an issue in which the status tree in Video Viewer took longer than expected to open upon log-in.

• Prism Migration Tool import errors (OG-26269): This release resolves this issue. Upon import, the Prism Migration Tool identifies cameras on a recorder, and migrates the channels as expected.

• asf video export does not work (OG-27459): This release resolves an issue in which, after an upgrade of OnGuard, only a short segment of .asf video export would work, and segments 15 minutes or longer in length would not export at all. .asf video exports work as expected in this release.

• Default GOV length settings does not display in Video Tab when upgrading Lenel NVR and OnGuard (OG-28350): This release resolves this issue. The default GOV length settings are displayed as expected.

• TruVision TVR 40 Recorder is not discovered in DeviceDiscoveryConsole on a WMware workstation (OG-28997): This release resolves this issue. The DeviceDiscoveryConsole discovers the TruVision TVR 40 Recorder on a WMware workstation as well as a desktop workstation.

• When using a matrix switcher, PTZ commands may go to the wrong camera (OG-29852): This release resolves an issue in which the wrong camera sometimes received the PTZ command when a matrix switcher was used. The last camera activated received the PTZ command as a result of the “Set Camera” command not being sent for the next camera. With this release, the “Set Camera” command is sent when commands for new cameras are sent to the matrix switcher.

4.14. Discovery Console • LNL-3300-M5 ISC displays as “Lenel LNL-“ and “Camera” in Device Discovery Console

(OG-28815): This release resolves this issue. The LNL-3300-M5 ISC correctly displays as “LNL-3300-M5” and as “Access Controller” for device type in the Device Discovery Console.

4.15. Elevators • Otis Compass integration does not include NGP readers in the Elevator Terminal >

Access Control Configuration > Reader combo box (OG-25896): NGP readers are now included on this configuration form for Elevator Dispatching (Elevator Terminal > Access Control Configuration).

• Elevator terminals: after period of inactivity or several reconfigurations, terminal can lose communication with assigned reader (OG-26090): This release resolves this issue. After reconfiguring elevator terminals or after a period of inactivity, the terminal responds as expected.

• Elevator Dispatching: after ITS hardware (DES, DER) lost and restored network communication, hardware is not properly updated (OG-26106): This release resolves this issue. After a period of inactivity or a disconnection, upon reconnection, the terminal goes to the correct destination floor as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 19

4.16. Enterprise • Anomalies detected during database setup upgrade for indexes that should not be

present on an Enterprise master (OG-15792): This release resolves this issue. Indexes for new systems that are converted to Enterprise masters are properly converted.

• Cannot add or change a user via DataConduIT in an Enterprise installation or a segmented system (OG-16060): This release resolves this issue. Users can be added or changed using DataConduIT as expected.

• DataConduIT does not allow badge modifications if the badge’s ID belongs to a non-local (Enterprise) range (OG-25680): This release resolves this issue with Enterprise systems that use ID ranges for the IDs of a given badge type.

• Triggers added to the Enterprise master database on upgrade cause invalid hardware transactions to be logged (OG-26933): This release resolves this issue. The triggers added to the Enterprise master database during an upgrade are now properly tagged.

• OnGuard Enterprise fails to load .NET prerequisites on a Windows 8/Windows 8.1 machine (OG-27117): This release resolves this issue. On a Windows 8/Windows 8.1 machine, OnGuard Enterprise installs the Microsoft .NET prerequisites as expected.

4.17. FormsDesigner • Default door field not recreated with default value when making a form change;

DataConduIT breaks (OG-25275): This release resolves an issue in Forms Designer that affects the performance of DataConduIT.

• Improper naming of drop-down list fields in FormsDesigner no longer crashes DataConduIT (OG-24102): Prior to OnGuard 7.0, drop-down list fields created in FormsDesigner might cause DataConduIT to crash if a field's Object Name did not follow specific naming rules. This issue is resolved in OnGuard 7.0. The naming rules are that Object Names:

• must start with a letter • cannot begin or end with an underscore ("_") • all remaining characters must be letters, digits, or underscores

All characters that do not follow these rules are stripped from the Object Name. Furthermore, "Lnl_" is added to the beginning of all Object Names. For example, an Object Name of "_Doc Department_" becomes "Lnl_DocDepartment".

• Selections made from a drop-down menu added in FormsDesigner are not saved (OG-24125): This release resolves this issue. Selections are saved as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 20

4.18. Guardall • Guardall Px/Qx/Rx status issue with arming/disarming (OG-24538): This release

resolves a Guardall Px/Qx/Rx status issue with Arming/Disarming.

• Guardall Px/Qx/Rx Panels do not report events to OnGuard while panel is offline with the Communication server (OG-24689): This release resolves an issue in which Guardall Px/Qx/Rx panels did not report events to OnGuard while offline.

• Guardall Px/Qx/Rx debug logging is inconsistent with the standard OnGuard logging mechanism (OG-25268): This release resolves an issue in which Guardall Px/Qx/Rx debug logging is inconsistent with standard OnGuard logging mechanism.

• Guardall - Data truncated message on configuration (OG-25990): When configuring a Guardall EMEA panel, a “Data truncated” message no longer occurs when making modifications on the Guardall PX Config tab.

4.19. Identity Management • Cannot Modify Badge ID in System Administration after printing badge (OG-25861):

This release resolves this issue. Users can modify badge IDs in System Administration as expected.

• “An error has occurred while consuming this service” error message occurs when sending e-mail from the IDVM Front Desk (OG-29233): This release resolves this issue. IDVM Front Desk works as expected.

• IDVM Front Desk event sign-in locations do not display upon sign-in (OG-29332): This release resolves this issue. The Sign-in Locations menu is now populated when logging into the Front Desk for the first time.

4.20. Installation • FIPS Mode Configuration utility generates an “Invalid Certification” error message

(OG-25321): This release resolves an issue in which the FIPS Mode Configuration Utility displayed a certification error message when launched.

• OnGuard returns an error when attempting to create an unattended client installation (OG-24632, OG-26679): This release resolves this issue. The “setup /a” parameter has been removed. Remote installation of OnGuard has been enhanced with the Manual Unattended Client Deployment. For more information, refer to the Advanced Installation Topics Guide.

• Server Roles and User Mapping permissions are not needed for SQL Server Installation (OG-26874): The Installation Guide incorrectly provided steps for setting Server roles (“dbcreator” and “serveradmin”) and User Mapping permissions (“master” and “tempdb”) during the installation of SQL Server. These roles and permissions are not needed. The DBO permissions created for the Lenel login are sufficient.

• Unable to log in after upgrading an Enterprise system (OG-26796): This release resolves this issue. Users can log into an Enterprise system after upgrading from OnGuard 2010 Hot Fix 3.0.

• OnGuard fails to install if Microsoft SQL Server 2012 is installed first (OG-27137): This release resolves this issue. OnGuard installs as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 21

4.21. Intrusion Detection • The Strike Output drop-down list displays incorrectly when configuring the

“M5/M3000 16DO 1” item under the “M5/M3000 16DO 2” item in the Slots tab (OG-26666): This release resolves this issue. The strike output drop-down list displays the correct item in the Slots tab when configuring the M5/M3000 16DO 1 or M5/M3000 16DO 2.

• Quick arm/disarm function for LNL-3300 does not work (OG-27142): This release resolves this issue. The Quick arm/disarm function works as expected.

4.22. Licensing • FLEXnet license deactivation over phone may not provide a return code to deactivate

the license (OG-25292): This release resolves this issue. The return code to deactivate the license is now provided.

• Cannot change the username and password in License Administration (OG-26844): This release resolves this issue. The username and password can be changed in License Administration.

4.23. Linkage Server • Use or Lose Badge feature generates a syntax error after upgrading OnGuard

(OG-26480): This release resolves this issue. The Use or Lose Badge type works as expected.

4.24. NGP • ACS.INI setting that controls the NGP 'Access service menu' and 'Perform service test'

permission profile configuration should be removed (OG 24446): This release resolves this issue. The ‘Access service menu’ and ‘Perform service test’ checkboxes are only enabled for the NGP intrusion mode.

• NGP Panel denies access to cardholders and generates an Invalid Badge Alarm report when unable to locate the badge records (OG-24467): This release resolves an issue in which an NGP panel denied access to cardholders with valid, active badges and properly configured access levels in the OnGuard software. The NGP panel was unable to locate the badge records and denied access to the cardholders, thus resulting in an Invalid Badge Alarm report in the OnGuard software. With this release, the NGP panel successfully locates the badge record and grants access to the cardholder.

• NGP Door Mode configuration labels for door unlock modes are misleading (OG-24518): In System Administration > Access Control > Readers and Doors > Door Form, the following changes were made to the During schedule and Outside schedule Mode options to reduce confusion:

• Area is Disarmed: Now called Unlocked if Disarmed. When selected, the door is unlocked only if the area on either side of the door is Disarmed.

• Area is Stay/Disarmed: Now called Unlocked if Stay or Disarmed. When selected, the door is unlocked only if the area on either side of the door is Stay or Disarmed.

• NGP LCD Keypad configuration allows “Use for access control” to be selected without requiring an associated door (OG-24693): This release resolves this issue. A door assignment is now required when selecting the Use for access control option.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 22

• Schedules configured on an NGP Panel do not function properly during Daylight Saving Time (DST) transitions (OG-24712): This release resolves this issue. Schedules now function as expected during DST transitions.

• NGP schedules do not work when there are multiple overlapping time intervals (OG-24879): This release resolves this issue. Schedules work as expected with multiple overlapping time intervals.

• Anti-passback auto-reset does not function as expected (OG-25003): NGP firmware version 1.02.032 resolves an issue where anti-passback auto-reset did not function as intended. Now “one free pass” is set for the user after anti-passback is auto-reset.

• Errors can occur when up to 500,000 cardholders are downloaded to NGP (OG-25034): Prior to this release, some cardholders were skipped when downloading up to 500,000 cardholders to an NGP panel. With this release, all cardholders are downloaded as expected.

• “Invalid Access Level” is displayed on Sundays when the “Always” time zone is used (OG-25047): NGP Firmware version 1.02.032 resolves an issue. The “Always” time zone now works as expected.

• Permission profiles are not correctly downloaded to an NGP panel in an Enterprise system (OG-25073): This release resolves this issue. Permission profiles are downloaded as expected.

• Entering an apostrophe in the NGP door or input name causes the door or input to be excluded from the Central Station Setup report (OG-25337): This release resolves this issue. NGP doors and/or inputs with apostrophes in their names are included in the Central Station Setup report.

• Alarm input does not follow Siren Time and Point Reset Time settings (OG-25344): NGP firmware version 1.02.032 or later resolves this issue with timing for point restorations.

• Holiday settings in time zone may not work as expected (OG-25492): NGP firmware versions 1.02.032 or 1.02.026 resolve this issue with holiday settings and time zones.

• Multiple issues with NGP web configuration page (OG-25637): NGP firmware version 1.02.032 fixes the following issues with the NGP web configuration page:

• The web page now reports errors when the user selected an improper (non-license) file for upload.

• The proper web page with the relevant error message now displays when a user attempts to upload a large file as a license.

• Toggle lock during a schedule does not deactivate door contact strike at end of schedule (OG-25790): NGP firmware 1.02.032 resolves this issue. Toggling a lock during a schedule now reinstates the door at the end of scheduled period.

• Adding the full set of 130 doors to an NGP Panel causes doors to go offline and database downloads to fail (OG-25966): This release resolves an issue when trying to configure an NGP system with a full set of 130 doors.

• Holiday settings do not work as expected with all 8 holiday types selected (OG-25984): NGP firmware version 1.02.032 resolves this issue in which a holiday with all eight types selected did not function as intended.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 23

• Cannot establish an SSH connection after changing the system service password (OG-26104): NGP firmware version 1.02.032 resolves this issue in which the password for SSH connections was always at the default value (2482), even if the system service password was changed.

• NGP cannot re-establish communication to OnGuard when the Ethernet connection is removed and then reconnected (OG-26646): NGP firmware version 1.02.032 resolves an issue where in some conditions the NGP panel may permanently block a disconnected network socket, which leads to the permanent loss of the OnGuard connection. The NGP can now re-establish communication to OnGuard when the Ethernet link is reconnected.

• Incremental database downloads are not functioning correctly for NGP (OG-26824): This release resolves this issue in which incremental database downloads failed for NGP.

• “Invalid PIN” alarm occurs for a valid badge when a PIN is entered at normal speed (OG-27883): NGP-UIO firmware version 11.13.02 resolves this issue. With this firmware update, the NGP-1300-U and NGP-1320-U grant access to valid PIN entries as expected.

• “Door Contact Tamper Active” alarm is generated in Alarm Monitoring when the 2RP or 2SRP board is removed from its slot (OG-28676): This release resolves this issue. No events are generated in Alarm Monitoring when the 2RP or 2SRP board is removed.

4.25. Remote Monitoring • Cannot drag an alarm into the Remote Monitor (OG-25152): This release resolves this

issue. Remote Monitoring installs with no errors. Alarm Monitoring opens and is able to trigger an alarm on a camera. The recorded video for the triggered alarm can be dragged to the remote monitor and played without error.

4.26. Replicator • Pending hardware transactions not reported (OG-16040): This release resolves this

issue. Replicator now reports pending hardware transactions when performing an incremental download.

• During a Cardholder segment change, dependent objects fail to replicate in the same replication cycle (OG-24314): This release resolves this issue. Changes made to Enterprise remove the need for replication cycles. Objects are processed as quickly as possible.

• Control for the Two-man Rule Cardholder form cannot be hidden on Enterprise systems (OG-24316): This release resolves this issue. After the Two-man Rule control is deleted from the Master and a user-defined field form download is performed on the Region, the control is removed from the Cardholder form.

• Unnecessary Enterprise transactions are logged on Enterprise systems for Visit events (OG-23753): This release resolves this issue. Unnecessary Enterprise transactions are still logged, but no longer published, which reduces network traffic.

• When running as a service, Replicator crashes when there are no more IDs available in the Mobil_ID_Control table (OG-25192): This release resolves this issue.

• Replicator stops processing records after it reaches 100 transactions per type, per execution (OG-25242): This release resolves this issue. Replicator now requests the next set of records and continues processing transactions .

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 24

• New Region license check incorrectly includes the Master Server in the existing system count (OG-25325): This release resolves this issue. The Master Server is no longer counted in the New Region license check.

• Delete transactions are not properly processed if the Replicator and database times are not synchronized (OG-25750): This release resolves this issue. Delete transactions are successfully processed.

• After running the Replicator, the number of successful transactions is larger than the total number of transactions (OG-25883): This release resolves this issue. Replicator no longer reports a discrepancy between the number of successful transactions and the total number of transactions.

• Video-related Enterprise hardware transactions fail due to referential integrity errors (OG-26089): This release resolves this issue. Transactions occur as expected.

• Software events for an access level assignment are not upgraded when the access level update is performed using Replicator (OG-26174): This release resolves this issue. Software events are upgraded as expected when using Replicator.

• “Failed -- Account Not On Source” transaction occurs when linking and unlinking a directory account for a Cardholder (OG-26704): This release resolves this issue. This error no longer occurs when using Replicator.

• Over-generation of redundant hardware transactions slows system performance (OG-27549): This release resolves this issue. The hardware transaction processor now looks for any pending redundant transactions and does not run them through the processor. As a result, overall performance is improved.

4.27. Replication Administration • An unexpected application error occurs when viewing the Region hardware

transactions for the first time after setting up the Enterprise environment (OG-25910): This release resolves this issue. OnGuard works as expected when viewing Region hardware transactions.

• GOS Enterprise alerts do not work when configured against the Enterprise Master (OG-29199): This release resolves this issue. Alerts from the master and region are received based on the GOS settings made in the ACS.ini file.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 25

4.28. Reports • “Cardholder Exit/Entry” reader report and “Cardholder Time and Attendance”

date/time report show nothing for NGP Readers (OG-22452): This release resolves an issue that caused the “Cardholder Exit/Entry” reader report and the “Cardholder Time and Attendance” date/time report to show nothing for NGP readers.

• Reports: Alarm panel inputs ‘Contact Normally Open’ field is not showing a value (OG-24715): This release 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.

• Cannot filter on Date/Time in the Visit reports from the Report screen (OG-25481): This release resolves this issue. Date/Time can be filtered from the Report screen.

• Reader report incorrectly displays pulse times for auxiliary outputs (OG-26485): Prior to this release, in the Reader report, Auxiliary Output #1 showed the pulse time for Auxiliary Output #2 and vice-versa. This release resolves this issue. The Reader report correctly displays data.

• “All Events Over Time” report does not include cardholder information for Verify User alarm (NGP) (OG-27067): This release resolves an issue in which cardholder information for the Verify User alarm is not included in the All Events Over Time report.

• “Elevator Dispatching Access Denied and Granted Events” report does not include requested floor (OG-27151): This release resolves this issue. The “Elevator Dispatching Access Denied and Granted Events” report now contains information for the requested floor.

• The Cardholder Time and Attendance Report for NGP incorrectly lists badge activity (OG-28135): This release resolves this issue. The Time and Attendance report now shows badge activity with In Reader 1 and Out Reader 1 instead of In Reader 1 and Out Reader 2.

4.29. Segmentation • Onity/Integra CT30 access level definitions do not work after segmentation is enabled

(OG-24882): This release resolves an issue in which Onity/Integra CT30 access level definitions do not work after Segmentation is enabled.

• Copying data during segmentation can cause gaps in IDs and prevent the ability to lower the max counts for some objects (OG-25373): This release resolves an issue with copying data during segmentation.

• Segment Wizard incorrectly allows you to move panels from a Regional segment to a segment created on the Master (OG-26153): This release resolves this issue. The Segment Wizard only shows local segments for the user to copy settings.

• “Internal logic error: Segmentation Utility cache not read” message entered several times a day in the LenelError.log (OG-26176): This release resolves this issue. The caching of segment-related data has been improved, and repeated entries of error messages in the LenelErro.log file have been significantly reduced.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 26

4.30. Setup Assistant • Unable to view and activate license without errors (OG-25515): This release resolves

this issue. Setup Assistant no longer presents multiple errors that prevent the ability to view and activate licenses When using a FLEXNet license on a fresh installation, or an upgrade, of OnGuard.

• Setup Assistant does not create the service for the Application Server on a system running Microsoft Windows 8/Windows 8.1 (OG-26205): This release resolves this issue. Setup Assistant now creates a service for the Application Server on a machine running Microsoft Windows 8/Windows 8.1 operating system.

4.31. Supplemental Materials Disc • SigniShell driver and SDK files are no longer on the Supplemental Materials Disc

(OG-29217): With this release, the SigniShell driver and SDK files have been removed from the Supplemental Materials Disc (Credential Center Device Drivers > Card Scanning Solutions).

4.32. System Administration • Entire cardholder name is mapped to the first name field on the Cardholder form

(OG-23009): This release resolves this issue. Imported cardholder data now maps to the appropriate fields as expected.

• Terminals for elevator dispatches added on a Master (OG-23085): This release resolves an issue in which terminals could be added for elevator dispatches on the Master. Terminals can only be added on a Region.

• Camera name field on Camera form in System Administration only accepts up to 32 characters (OG-25070): This release resolves an issue in which the Camera Name field only allowed up to 32 characters. The field can support up to 96 characters.

• System Administration stops responding if a user with no Field/Page Permission Group accesses Badge Types (OG-25105): This release resolves an issue in which System Administration stops responding if a user with no Field/Page Permission Group accesses Badge Types.

• Slow performance on the Users screen in System Administration (OG-25287): This release resolves an issue related to the Last Successful Login control. System Administration works as expected.

• Need to implement searching of global I/O groups within System Administration (OG-25742): This release includes the implementation of searching of global I/O group within System Administration.

• The on-screen help for the “Timezone Activate/Deactivate” option on the Local I/O Function list is incorrect (OG-25789): This release resolves this issue. The corrected on-screen help reads as follows:

• TRUE: Temporarily activates the timezone until the next time interval occurs • FALSE: Temporarily deactivates the timezone until the next time interval occurs

• The added ID range is not displayed in the Allocated Ranges list (OG-25848): This release resolves this issue. In System Administration > Administration > Badge Types > ID Ranges, the added ID range is displayed as expected in the Allocated Ranges list.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 27

• Selecting a panel on the Selective Cardholder Download Form may cause System Administration to crash (OG-27078): This release resolves an issue that caused System Administration to crash when selecting a panel on the Selective Cardholder Download Form.

• Baud rate cannot be set when configuring an Intercom panel (OG-29901): This release resolves this issue. The baud rate can be set when configuring a Commend GE300/GE800 Intercom device or a Generic Intercom device.

4.33. Visitor Management • Changes made to Visitor Management user interface layout not saved on exit

(OG-26869): This release resolves an issue in which changes made to the Visitor Management user interface, such as column sizes and column order, were not saved when Visitor Management was exited. All custom changes to the user interface are now saved.

4.34. Web Application Server • “HTTP (405) Method Not Allowed” message appears when attempting to launch web

applications (OG-28796): This release resolves this issue. The an HTTP (405) Method Not Allowed message no longer appears when launching web applications such as FrontDesk, Kiosk, or AdminAPP.

4.35. Web Area Access Manager • In Web Area Access Manager , typing a colon (:) in either of the time fields of the Access

Level Assignment Wizard results in sign-on screen being returned to the User (OG-24377): Previously, typing a time using a colon (:) for the activation or deactivation time would cause the Area Access Manager (Browser-based Client) to automatically log out, returning to the sign-on screen. This issue has been fixed.

• Web Area Access Manager cannot assign access levels if the access level or badge type is in a segment group (OG-26035): A warning message appears when an access level in one segment group is assigned to a cardholder whose badge type is in a different segment group.

• The Web Area Access Manager page locks up after clicking the Filter button (OG-26898): This release resolves an issue in which the Web Area Access Manager page locks up after clicking the Filter button. The page and Filter button now work as expected.

• “HTTP Error 503” message appears when attempting to access Web Area Access Manager (OG-27150): This release resolves this issue. When attempting to access the Web Area Access Manager, the following error message may appear: “HTTP Error 503. The service is unavailable.”

4.36. Web Service • Visitors created in Visitor Management Host and Front Desk applications fail to save

UDFs when created after the IIS application pool's process model idle time-out expires (OG-28665): This release resolves this issue. Creating visitors in either Visitor Management application works as expected.

DOC-1013-EN-US (September 2016) © 2016 United Technologies Corporation revision 1.022 — 28

4.37. Web VideoViewer • VideoViewer (browser-Based client) stops responding when offline camera is selected

(OG-25035): This release resolves an issue that caused VideoViewer (Browser-based Client) to stop responding when an offline camera is selected.

• Non-system administrator accounts are not able to access Matrix PTZ controls in Web Video Viewer (OG-25118): This release resolves this issue. Matrix PTZ controls can be accessed by non-system administrator users in the Web Video Viewer.

• Enhancement: Option to enable/disable loading of device groups in VideoViewer (browser-based client) (OG-25519): An option was added to enable/disable loading of device groups.

In the Internet Information Services (IIS) Manager: 1. Right-click and explore Lnl.OG.WebService. 2. Modify Preferences.js. Comment or make the value “false” for the following line to

disable loading of groups in WVV: var g_lnl_load_device_groups = true;

• Special characters in a user's password disables the PTZ controls in Web VideoViewer (OG-26010): This release resolves this issue. A user with special characters in the password can still control PTZ in the Web VideoViewer.

• Setting a username and password for an Lenel NVR disables the PTZ controls in Web VideoViewer (OG-26388): This release resolves this issue. PTZ controls in the Web VideoViewer operate as expected after setting the username and password for an Lenel NVR.

• VideoViewer crashes when switching from a live feed to recorded video using the Set Start/End Date option (OG-27020): This release resolves this issue. VideoViewer works as expected when switching from a live feed to recorded video.

• VideoViewer crashes when requesting video recorded with event recording (OG-27068): This release resolves this issue. VideoViewer works as expected when requesting video.


Recommended