OnGuard 2009 6.3 Release Notes

OnGuard 2009
Version 6.3
Release Notes
1. OnGuard 2009, 6.3...................................................................................................................................8
1.1. Upgrades........................................................................................................................................8
1.1.1. Full Download Required for Enterprise Systems after Upgrade..............................................8
1.1.2. Universal Time Conversion Utility Must be Run on All Systems After Upgrade....................8
1.1.3. Upgrade Requirement for Enterprise Customers Using Visitor Management.........................8
1.1.4. Oracle Regions with Many Events May Experience Long Database Setup Run Time (OG-
15176) ..................................................................................................................................................8
1.1.5. Full Download for LNVR Recorders with H.264 Cameras Configured..................................9
1.1.6. Badge Design Programming with List Builder Lists Will Not Function in BadgeDesigner
After Upgrade to OnGuard 2009 (OG-15935).........................................................................................9
2. Versioning Information.............................................................................................................................9
2.1. Current Access Control Firmware and Special Application Versions...........................................9
2.2. Current Digital Video Firmware....................................................................................................9
2.3. Minimum Server System Requirements.......................................................................................9
2.4. Supported Operating Systems.....................................................................................................10
2.4.1. Windows XP Professional with Service Pack 2 or Service Pack 3 is REQUIRED...............10
2.4.2. Windows Server 2003 Standard and Enterprise, Service Pack 2 or R2 Service Pack 2 is
REQUIRED............................................................................................................................................10
2.4.3. Windows Vista with Service Pack 1.......................................................................................10
2.4.4. Windows Server 2008 with Service Pack 1............................................................................10
2.4.5. Service Packs and Critical Patches.........................................................................................11
2.5. Security Utility............................................................................................................................11
2.6. Supported Database Systems.......................................................................................................11
2.6.1. Microsoft SQL Server 2005 Express Edition SP2, 32-bit and 64-bit.....................................11
2.6.2. Microsoft SQL Server 2005 Standard Edition SP2, 32-bit and 64-bit...................................11
2.6.3. Microsoft SQL Server 2005 Enterprise Edition SP2, 32-bit and 64-bit.................................11
2.6.4. Microsoft SQL Server 2008 Express Edition, 32-bit and 64-bit............................................11
2.6.5. Microsoft SQL Server 2008 Standard Edition, 32-bit and 64-bit...........................................11
2.6.6. Microsoft SQL Server 2008 Enterprise Edition, 32-bit and 64-bit.........................................11
2.6.7. Oracle 9i R2 32-bit (9.2.0.8) Server and Client.....................................................................12
2.6.8. Oracle 10g R1 32-bit (10.1.0.7) Server and Client.................................................................12
2.6.9. Oracle 10g R2 32-bit (10.2.0.4) Server..................................................................................12
2.6.10. Oracle 10g R2 32-bit (10.2.0.3) Client with ODBC Driver Patch
(p5699495_10203_WINNT)..................................................................................................................12
2.6.11. Oracle 10g XE only with the LNV Suite................................................................................12
2.6.12. Oracle 11g 32-bit (11.1.0.6) Server and Client.......................................................................12
2.6.13. Oracle 11g 64-bit (11.1.0.7) Server with 32-bit Client installed if OnGuard is running on the
same server as the database....................................................................................................................12
2.7. Supported System Components..................................................................................................12
2.8. VMware Platforms......................................................................................................................12
2.9. Supported Third-party Components............................................................................................12
2.10. Antivirus Software Applications.................................................................................................13
2.11. Supported Web Browser..............................................................................................................13
2.12. Supported Terminal Services.......................................................................................................13
2.13. OPC Versions..............................................................................................................................13
2.14. SNMP Versions...........................................................................................................................13
2.15. Support Pending..........................................................................................................................13
2.15.1. High Availability Systems Pending Certification...................................................................13
2.15.2. MobileVerify...........................................................................................................................14
2.16. End of Life Products...................................................................................................................14
2.16.1. VeriSoft Server and Client......................................................................................................14
2.16.2. Emergin Wireless....................................................................................................................14
2.16.3. Ultra Scan...............................................................................................................................14
3. New Features..........................................................................................................................................15
3.1. Access Control............................................................................................................................15
3.1.1. Onity Integra Support.............................................................................................................15
3.1.2. Duress Card Formats..............................................................................................................15
3.1.3. Reversed Bit Order Card Formats..........................................................................................15
3.1.4. Bioscrypt Duress Finger Support...........................................................................................15
3.1.5. New Behavior for Alarm Shunt with Pre-Alarm or Tailgate Configuration Resolves
Compatibility Issue (OG-16091)............................................................................................................16
3.1.6. HID Edge Access Level Configuration Enhancement...........................................................16
3.1.7. Support for Lenel-branded HID Edge Readers......................................................................16
3.1.8. Additional Hardware Settings for Encryption........................................................................16
3.1.9. Downstream Encryption Status in Alarm Monitoring............................................................16
3.1.10. Scheduled Unlocked Mode and Input Supervision Supported for HID Readers...................16
3.1.11. New Schlage Configuration/Demo Tool (CDT).....................................................................16
3.2. Visitor Management....................................................................................................................17
3.2.1. Host.........................................................................................................................................17
3.2.2. Advanced Search....................................................................................................................17
3.2.3. Delegates................................................................................................................................17
3.2.4. Administration........................................................................................................................17
3.2.5. Front Desk..............................................................................................................................17
3.2.6. Kiosk.......................................................................................................................................17
3.2.7. Bulk User Import Tool for New Visitor Management Applications.......................................17
3.3. Digital Video...............................................................................................................................17
3.3.1. Support for Additional IP Cameras, Video Servers, and Encoders........................................17
3.3.2. Support for RTP Protocol.......................................................................................................18
3.3.3. LNVR Redundant Failover.....................................................................................................18
3.3.4. Video Quality Enhancement Algorithms................................................................................18
3.3.5. Double Video on Alarm Enhancements..................................................................................18
3.3.6. Network Video over HTTP via Proxy....................................................................................18
3.3.7. Optimization of IntelligentVideo Events................................................................................19
3.3.8. IntelligentVideo Embedded Analytics....................................................................................19
3.3.9. Integrated Support for goVision Video Recorders.................................................................19
3.4. High Availability Systems...........................................................................................................20
3.4.1. NEC Fault Tolerant Server Monitoring Service.....................................................................20
3.4.2. NEC ExpressCluster Monitoring Service...............................................................................20
3.4.3. NEC ExpressCluster Utility...................................................................................................20
4. Known Issues/Updates...........................................................................................................................22
4.1. General........................................................................................................................................22
4.1.1. Modifying or Removing OnGuard.........................................................................................22
4.1.2. Temporary Files Remain After Installation Has Completed..................................................22
4.1.3. SQL Server 2005 Installation Instructions Moved to Advanced Installation Topics Guide...22
4.1.4. Oracle Systems Need to be Set Up to Use Windows Authentication by Default...................22
4.1.5. World Time Zone Default Data Updated................................................................................22
4.1.6. Flash Player Removed from Supplemental Materials Disc....................................................22
4.1.7. Web Application Server Not Recommended with Windows XP or Windows Vista..............22
4.1.8. Browser-based Application Security......................................................................................23
4.1.9. Column Heading Tooltips Disabled for Windows XP (OG-12746).......................................23
4.1.10. Windows Vista: Security Utility Must be Run Manually for Public Profile..........................23
4.1.11. Windows Vista: ACS.INI File Cannot be Edited by Administrator Group Member..............23
4.1.12. Error 1905. Module C:\Program Files\OnGuard\msvbvm50.dll Failed to Unregister...........23
4.1.13. FormsDesigner Field Style Border and Inside Edge not Functioning Properly.....................23
4.1.14. User with View/Add Readers Permission Can Modify Destination Assurance (OG-17969) 23
4.2. Access Control............................................................................................................................23
4.2.1. Onity Integra Locks: Door Does Not Come Out of AFC Office Mode with AFC Office on
Enter and Second Swipe of Badge (DE1671)........................................................................................23
4.2.2. Deleting Badges from Onity Integra Locks............................................................................23
4.2.3. Open Supervised Device Protocol Reader Tamper Switch Monitoring.................................23
4.2.4. Reader Alarm Shunt Not Supported with LNL-2220 in Paired Mode...................................24
4.2.5. HID Edge Software for Device Communication Not Supported with Windows Vista or
Windows Server 2008 (OG-17749)........................................................................................................24
4.2.6. HID Edge Panels Drop Offline After a Period of Time (OG-16588).....................................24
4.2.7. HID Edge Devices Replaced with Another Device May Not Grant Access (OG-18068).....24
4.2.8. Strike Field States Cutoff on Close (OG-18019)....................................................................24
4.2.9. Low Battery and Tamper Reporting for Schlage Wireless Locks (OG-18069).....................24
4.2.10. OSDP Reader May Have Incorrect LED Display (OG-17529).............................................24
4.2.11. Intrusion Mask Group Correctly Suppresses Alarm Events (OG-17542)..............................24
4.2.12. Updated Wiring Diagram for Handkey Readers (OG-17875)................................................24
4.2.13. Downstream Encryption Key Download Will Fail if any I/O Modules Are Offline..............24
4.2.14. Area Access Manager Browser-based Client Reports Not Supported with Windows
Authentication on Windows Server 2008 or Windows Vista (OG-18066)............................................25
4.3. Identity Management...................................................................................................................25
4.3.1. Change in 10 Print Slap Record Format (OG-13658)............................................................25
4.3.2. Shared Card Printer May Be Unknown in Default Printer for Badge Type Drop-down Client
Workstations...........................................................................................................................................25
4.3.3. Magicard Prima 3 Must Use Driver Version 5.7....................................................................25
4.4. Visitor Management....................................................................................................................25
4.4.1. Visitor Management Browser-based Client Applications Not Supported with Windows
Server ................................................................................................................................................25
4.4.2. URL for Visitor Management Host and Administration (DE379)..........................................25
4.4.3. After Logging into Visitor Administration, an Error Occurs Stating, “The current user is not
authorized to perform this operation.” (DE1596)...................................................................................25
4.4.4. After Adding List Builder Items, IIS Must be Restarted (DE318).........................................25
4.4.5. Sign-in Locations Must be Modified (S2902)........................................................................25
4.4.6. Supported Date Format (DE385)............................................................................................26
4.4.7. Searching is Based on the Visitor Last Name.........................................................................26
4.4.8. After Using Basic Search to Find a Visitor, it is Not Possible to Perform the Same Search
Again ................................................................................................................................................26
4.4.9. Advanced Search Results are Based on the Last Entry When Two or More of the Same
Search Criteria are Selected (DE1586)...................................................................................................26
4.4.10. Limited Support for Group Visits...........................................................................................26
4.4.11. Group Visit Limitation of 75 Visitors (S3592).......................................................................26
4.4.12. When Deleting a Large Group Event, the System May Experience a Slight Wait Time
(DE1480)....................................................................................................................................................
26
4.4.13. Visitors Can Sometimes be Saved Without Filling in All Required Fields (DE393).............26
4.4.14. A Visitor Management Host User Should Not be Linked with Directory Accounts Associated
with Different Cardholders (DE1094)....................................................................................................26
4.4.15. Login with the Correct User Name and Password Fails if Access to the System is Disabled
(DE1471)....................................................................................................................................................
26
4.4.16. A Change in User Permissions Requires Recycling the Application Pool (DE1275)............26
4.4.17. Cardholder Permission to Delete Visits is Required to Remove Visitors from an Event
(DE411) ................................................................................................................................................27
4.4.18. To Schedule Events, Both the Visit Add and Modify Permissions are Required (DE1118). .27
4.4.19. To Sign a Visitor In or Out with Front Desk or Kiosk, the Visit Modify and Sign-in/out
Permissions are Needed (DE1486).........................................................................................................27
4.4.20. The Badge Use Limit View Permission is Required for Printing Badges in Front Desk or
Kiosk (DE1307)......................................................................................................................................27
4.4.21. To Send E-mail Notification of an Event, the Global I/O Permission is Needed (DE1516)..27
4.4.22. E-mails Do Not Have the Scheduled Time or Visit Key if the Event Was Created in System
Administration, ID CredentialCenter, or Visitor Management (DE1580).............................................27
4.4.23. UDFs Appear to be Missing when Changes to Events are Cancelled (DE1723)...................27
4.4.24. To See Events in Front Desk in a Segmented System, the Segments Permission is Needed
(DE1459)....................................................................................................................................................
27
4.4.25. A Host and Their Delegate Should be Assigned the Same Segment (DE1192).....................27
4.4.26. In BadgeDesigner, the Visit Times Indicate that They are UTC When They Are Not
(DE1284)....................................................................................................................................................
28
4.4.27. Front Desk or Kiosk Has the Error, “The HTTP Request is Unauthorized with Client
Authentication Scheme 'Negotiate'. The Authentication Header Received from the Server Was
'Negotiate,NTLM'.” (DE1296)...............................................................................................................28
4.4.28. Access Control Badges Retain Previous Access Levels When Reassigned (OG-15158)......28
4.4.29. Error Messages that Result From Not Having JavaScript Are Not Localized (DE395)........28
4.4.30. The Service Trace Viewer Tool is Needed to View the Visitor Management Tracing File
(DE1472)....................................................................................................................................................
28
4.4.31. Minimum Module Width and PDF417 Correction Are Not Supported (S3794)....................28
4.4.32. Only TrueType Fonts Are Supported for Badge Printing.......................................................28
4.4.33. Kiosk Has the Error, “You need permission to print badges to use the Kiosk.” (DE1531).. .28
4.5. Digital Video...............................................................................................................................28
4.5.1. Warning – Security!................................................................................................................28
4.5.2. Frame Rates Higher than 50fps May Not be Accurate (OG-16061).....................................29
4.5.3. Reduced Rate Recording Not Supported with H.264 Cameras..............................................29
4.5.4. Axis Cameras with H.264 Compression Do Not Support Square Pixel Compensation (OG-
17659) ................................................................................................................................................29
4.5.5. IntelligentVideo Database Upgrade Utility............................................................................29
4.5.6. IntelligentVideo Events Allow Region of Interest that Extends Past the Image Boundaries. 29
4.5.7. Audio Limitations...................................................................................................................29
4.5.8. Single Sign-on Not Supported with VideoViewer (Browser-based Client) and Video over
HTTP (OG-18129).................................................................................................................................29
4.5.9. Gaps in Recorded Video when Saving Embedded Event Configuration to Camera (OG-
17880) ................................................................................................................................................30
4.5.10. NAS Compatibility.................................................................................................................30
4.5.11. Device Discovery Console Cannot Find Lenel Camera if Adapter has IPv6 Address (OG-
15951) ................................................................................................................................................30
4.5.12. Device Discovery Console Cannot Find Lenel Cameras on Windows Vista (OG-15991)....30
4.5.13. Panasonic Camera Model Numbers in the Device Discovery Console (OG-17442).............30
4.5.14. Panasonic NW474 Does Not Support Compression Changes (OG-17927)...........................30
4.5.15. False Motion Detection Alarms from Lenel ICT230 Located in a Dark Room (OG-17771) 30
4.5.16. Limited Support for IQEye Cameras with Device Discovery Console..................................30
4.5.17. Double Video on Alarm May Not Be Displayed in Pairs.......................................................30
4.5.18. Double Video on Alarm with LDVR......................................................................................31
4.5.19. Double Video with Time-lapse Limitation.............................................................................31
4.5.20. Serial and USB Joysticks Limited to First Application Used.................................................31
4.5.21. Buffering Streaming Video is Disabled by Default................................................................31
4.5.22. Buffering Streaming Video with Audio Causes Lag in Timestamp.......................................31
4.5.23. Streaming Video Server Not Supported with H.264 Video Source........................................31
4.5.24. Reset to Defaults Needed for Upgraded RTP Cameras (OG-18167).....................................31
4.5.25. Video Artifacts with RTP over UDP with Some Bitrate/Resolution Combinations (OG-
18053) ................................................................................................................................................31
4.5.26. Joystick Control Difficult Due to Delays in Video (OG-15077)............................................32
4.5.27. Background PTZ Tour Interruption May Not Succeed..........................................................32
4.5.28. PTZ Tour Server Does Not Run on Channel in Failover (OG-17970)...................................32
4.5.29. LNVR with Oracle Express: Security Utility Must be Run Manually After Configuration is
Complete 32
4.5.30. Video May Freeze When Failover Occurs (OG-15743).........................................................32
4.5.31. Error When Switching to Live Video after Viewing Recorded from Archive Server (OG-
17598) ................................................................................................................................................32
4.5.32. Windows Vista Server: LDVR Recorders Cannot be Automatically Discovered..................32
4.5.33. Windows Vista Client: LNVR Failover Issue........................................................................32
4.5.34. Windows Server 2008: Enabling Video Export (OG-17701).................................................33
4.5.35. PAL Cameras may not have Frame Rates Color-coded to Indicate Supported Frame Rates. 33
4.5.36. LNVR Motion Detection Not Supported with IQinVision Cameras (OG-16501).................33
4.6. Enterprise....................................................................................................................................33
4.6.1. Update to Full Downloads Without Images...........................................................................33
4.6.2. Changing Badge IDs on Mobile Badging and Enterprise Systems (OG-15107)...................33
4.6.3. Badge Template Transaction Failed with Violation of Primary Key Error (OG-17915).......33
4.6.4. Anomalies Warning During Database Setup for Indexes that Should Not be Present on
Enterprise and Distributed ID Masters...................................................................................................34
4.6.5. Global I/O Restrictions...........................................................................................................34
4.6.6. Duplicate Dynamic Segment Names After Upgrade..............................................................34
4.6.7. Pre-existing User-specific Layouts Not Replicated to Enterprise Master..............................34
4.6.8. Directory Accounts Link to Cardholder or User Not Replicated to Enterprise Master (OG-
18199) ................................................................................................................................................34
4.6.9. Referential Integrity Error when Saving Camera Layouts.....................................................34
4.6.10. IntelligentVideo Applications Not Available on Enterprise Master when Configured on a
Child Region...........................................................................................................................................34
4.6.11. IntelligentVideo Applications Not Supported with IntelligentVideo Application Server
Located on a Different Region...............................................................................................................34
5. Limitations..............................................................................................................................................35
5.1. General........................................................................................................................................35
5.1.1. Installation May Appear Not to Start on Slower Systems......................................................35
5.1.2. Double-click Generates an Error in the Online Help.............................................................35
5.1.3. System Settings Do Not Apply to OnGuard Applications Until Restarted............................35
5.1.4. “Names” and “User Names” for Directory Accounts Linked to Cardholders are not Resolved
................................................................................................................................................35
5.2. Access Control............................................................................................................................35
5.2.1. Inaccurate Search Results Count in Browser-based Area Access Manager...........................35
5.2.2. IIS User Account Must Have Access to Temp Folder for Area Access Manager Browser-
based Client Reports (OG-18175)..........................................................................................................35
5.2.3. Additional Keys During Biometric Verification Will be Ignored...........................................35
5.3. Identity Management...................................................................................................................35
5.3.1. IE SmartTOUCH Sector Allocation Limitation.....................................................................35
5.3.2. Magicard Prima M Does Not Include Parity for Track 1 (OG-18107)..................................35
5.3.3. Field Type Must be Text for Phone Numbers.........................................................................35
5.3.4. HID Edge PIN Limitation (OG-16039)..................................................................................36
5.4. Digital Video...............................................................................................................................36
5.4.1. Recorded Video Cannot be Exported from a Failover Video Recorder.................................36
5.4.2. MPEG4 with Axis Cameras....................................................................................................36
5.4.3. Lumenera Cameras.................................................................................................................36
5.4.4. White Balance Setting Must be Configured from Panasonic Camera Web Page...................36
5.4.5. Connection to Panasonic i-Pro Network Cameras in MPEG4 May Fail After Multiple
Connections are Made (OG-17488).......................................................................................................37
5.4.6. Some Panasonic WV-NP1000/1004 Camera Settings Must Be Applied Manually...............37
5.4.7. Lumenera LI045C Resolution is Limited...............................................................................37
5.4.8. Mobotix Cameras Require a Longer Direct Connect Default Timeout (OG-15569).............37
5.4.9. Frame Rate Drops With AXIS 241Q When the Camera Web Page is Opened......................37
5.4.10. AXIS 240x Video Servers Do Not Report an Error When Offline........................................37
5.4.11. Inputs Not Supported with HIKVision Cameras (OG-18062)...............................................37
5.4.12. Non-numeric Passwords Not Supported by HIKVision Cameras (OG-18028).....................37
5.4.13. Video Appears Washed-out After Adjusting Resolution on HIKVision DS-2CD852F Camera
(OG-18054)............................................................................................................................................38
5.4.14. HIKVision/Lenel PCI Boards May Require Manual Driver Installation (OG-17395)..........38
5.4.15. Toshiba Cameras Do Not Support Maximum Frame Rate With Maximum Resolution........38
5.4.16. Cannot Limit Frame Rate on Bosch Cameras from the Camera Web Page...........................38
5.4.17. Shadow Effect with Bosch Dinion Camera............................................................................38
5.4.18. Bosch 8008 Camera................................................................................................................38
5.4.19. Upgrading H.264 Sony Camera Firmware May Require a Full Download...........................38
5.4.20. Device Camera Link and Capture Video on Event Delay......................................................38
5.4.21. Offline LNVR May Cause a Delay in Alarm Reporting........................................................38
5.4.22. Go To PTZ Preset Feature Not Supported when LNVR is Offline........................................38
5.4.23. Black Video Cells in Remote Monitor...................................................................................38
5.4.24. Selecting a Video Cell in Browser-based VideoViewer Automatically Locks PTZ...............38
5.4.25. In-Camera Storage Feature Considerations............................................................................39
5.4.26. ASF Files Not Supported in Alarm Monitoring.....................................................................39
5.4.27. Exported LDVR Files Not Automatically Associated with VideoViewer..............................39
5.4.28. Video Export from Browser-based VideoViewer in Windows Vista......................................39
5.4.29. Setting the Color Mask with Grayness in Object Detection...................................................39
5.4.30. Intel Decoder Must be Installed for Playback with the Panasonic 474 (6x-8916).................39
5.4.31. Oracle Errors When Adding Cameras (OG-17708)...............................................................39
6. Copyright and Trademark Notice...........................................................................................................40
1. OnGuard 2009, 6.3
This document provides an overview of the features, enhancements and changes available in this release.
Installation instructions are available in portable document format (PDF) on this disc in the ..\Program
Files\OnGuard\doc\ folder. OnGuard 2009 (6.3) from this point forward will be referred to as OnGuard
2009.
OnGuard clients purchased from Lenel no longer ship with the OnGuard software DVD. OnGuard
installation and supplemental DVDs are now available for download directly from the Lenel Customer
Self-Service Center. To download the OnGuard software, visit the Lenel Web site:
https://customer.lenel.com/?q=support/product-dvd-isos. (You will need a Lenel login to gain
access to this site.) Download the OnGuard software and create a master DVD for all of your client
installations.
Lenel Global Education provides instructor-led Web-based Global Distance Learning for more in depth
knowledge on these new features in OnGuard 2009. The training is available for Value Added Resellers
(VARs), Certified OnGuard System Users, and OnGuard System User Administrators. Please visit the
Lenel Web site for more details and schedules: https://customer.lenel.com/?q=lls/distance-
learning.
1.1. Upgrades
Direct upgrades of the OnGuard software are supported for all currently supported versions of OnGuard.
For versions older than that, an incremental upgrade will need to be performed. For 6.3, this means that a
5.11 system would need to be upgraded to 5.12.012 first; systems 5.12 and newer can upgrade directly.
Important: Please review each of the following items carefully to determine whether additional steps are
needed for your particular upgrade.
1.1.1. Full Download Required for Enterprise Systems after Upgrade

After upgrading to OnGuard 2009, Enterprise systems must perform a full download.
Note: With this release when performing a full download without images, images at the Regional Servers
will remain intact. OnGuard will identify images that have changed and generate the necessary transactions
for processing these photos in the background.
1.1.2. Universal Time Conversion Utility Must be Run on All Systems After
Upgrade
The Universal Time Conversion (UTC) Utility is used to collect World Time Zone information to be used
to convert local dates and times in the system to the new standard UTC time. Standard OnGuard reports
have been converted to use UTC time which allows users in multiple time zones to see the same data but in
their local time. For systems that are being upgraded, any custom reports and/or custom DataExchange
scripts will need to be updated to account for this change and work properly. For more information, refer to
the Upgrade Guide.
1.1.3. Upgrade Requirement for Enterprise Customers Using Visitor Management

Due to the complex architectural changes in Enterprise, customers using Visitor Management in an
Enterprise environment must archive all signed-out visits at each Regional Server prior to performing the
upgrade. In addition, all visits on the Master Server should also be archived. Failure to perform the
archiving may result in incorrect sign out times being replicated to the Regional Servers.
1.1.4. Oracle
Regions with Many Events May Experience Long Database Setup
Run Time (OG-15176)
During an upgrade of an OnGuard 2008 (6.0) or earlier system running Oracle with millions of events,
regions may take an extended amount of time to run Database Setup. The length of time this may take can
be extended on systems that additionally have thousands of custom event parameters. The amount of time
required to upgrade may exceed a day (24 hours).
1.1.5. Full Download for LNVR Recorders with H.264 Cameras Configured
After upgrading to OnGuard 2009, systems with H.264 cameras should perform a full download on all
LNVR recorders. For more information, refer to 4.5.3 Reduced Rate Recording Not Supported with H.264
Cameras.
1.1.6. BadgeDesign Programming with List Builder Lists Will Not Function in
BadgeDesigner After Upgrade to OnGuard 2009 (OG-15935)
Any badge layout programming configured in BadgeDesigner that uses controlling fields with List Builder
lists will not function after an upgrade to OnGuard 2009 from OnGuard 2006 (5.12.110) or earlier. This
may cause the badge design for newly printed badges that use any UDF drop-down fields configured with
List Builder to be incorrect. To resolve this issue, run the Program Badge Repair Utility located at \
Program Files\OnGuard\ProgramBadgeRepairUtility.exe after running Database Setup to upgrade your
database to OnGuard 2009.
2. Versioning Information
2.1. Current Access Control Firmware and Special Application Versions

Note: Before downloading the firmware in this release to Lenel access control boards, please ensure that
DIP switch or jumper 8 is in the OFF position. Failure to take this step will result in an inability to
communicate to these boards until the switch or jumper position is corrected, and may therefore affect
normal operation of your system. If the ISC is online, the status of the DIP switch 8 can be verified in
System Administration on the Access Panels > Diagnostics sub-tab.
 LNL-500/1000/2000 ISC Version v3.118

 LNL-2220/3300 ISC Version v1.068
 LNL-1100/1200 Series 1 Version v1.04
 LNL-1100/1200 Series 2 Version v1.29
 LNL-CK Rev A Version v1.30
 LNL-CK Rev B/C Version v1.50
 LNL-1320 Series 1 Version v1.13
 LNL-1300 Series 1 Download not supported
 Identix with LNL-500B gateway firmware v1.16
 Bioscrypt with LNL-500B gateway firmware v1.26
 RSI biometrics with LNL-500B gateway firmware v1.25
 Recognition Source PIM-485-16-OT with wireless LNL-500W gateway firmware v1.10
2.2. Current Digital Video Firmware

 Lenel Digital Video Recorder (LDVR) – Firmware Version 7.21
 Lenel Network Video Recorder (LNVR) – Firmware Version 6.3.249
 Intelligent Video Server (IVS) – Firmware Version 6.3.249
 Intelligent Video Application Server (IVAS) – Firmware Version 6.3.249
 Remote Monitoring – Firmware Version 6.3.249
 Lenel Streaming Video Server (LSVS) – Firmware Version 6.3.249
2.3. Minimum Server System Requirements

 Pentium IV Processor
 1 GB RAM
 DVD-ROM
 USB Port
 1024x768 color display
 6 GB of available space
2.4. Supported Operating Systems

The following OnGuard versions have been approved with the listed system service pack. All new systems shipped
from Lenel will include at least these service pack versions. Installations attempted on other operating systems will
not run.
Note: OnGuard is a 32-bit application that can be run on some 64-bit systems. 64-bit systems are only
supported as noted below.
For an up-to-date list of tested operating systems and service packs, refer to the compatibility charts on the
Lenel Web site: https://customer.lenel.com/?q=support/compatibility-charts.
2.4.1. Windows
XP Professional with Service Pack 2 or Service Pack 3 is
REQUIRED.
Windows XP is not recommended for use as the Web Application Server (LS Application Server service)
because the number of client connections to IIS is limited in this operating system.
Windows XP SP2 or SP3 will be called Windows XP, from this point forward, in the OnGuard 2009
Release Notes.
2.4.2. Windows Server 2003 Standard and Enterprise, Service Pack 2 or R2

Service Pack 2 is REQUIRED.
Windows Server 2003 Standard and Enterprise are approved for all OnGuard server and client operations.
Windows Server 2003 64-bit is NOT supported.
Windows Server 2003 Standard and Enterprise are approved for use as any Lenel Digital Video product
host operating system, NOT including the OnGuard GO! product.
Windows Server 2003 Standard and Enterprise can be utilized as the separate OnGuard server with Lenel
Digital Video products.
Windows Server 2003 Standard and Enterprise, SP2 or R2 SP2 will be called Windows Server 2003, from
this point forward, in the OnGuard 2009 Release Notes.
Windows Server 2003 is not supported for communication with HID Edge Devices.
2.4.3. Windows Vista with Service Pack 1

Windows Vista Business and Enterprise editions are supported with OnGuard.
Windows Vista is not recommended for use as the Web Application Server (LS Application Server service)
because the number of client connections to IIS is limited in this operating system.
Windows Vista is not supported for the LDVR or OnGuard GO! systems.
Windows Vista Business and Enterprise SP1 will be called Windows Vista, from this point forward, in the
OnGuard 2009 Release Notes.
Windows Vista is not supported for communication with HID Edge Devices.
LNVR is now supported on Windows Vista Business Edition with the following limitations:
Note: Windows Vista Enterprise Edition is not supported with LNVR.
 Darim boards (all part numbers starting with UVS) are not supported with Windows Vista.
 LNVR Start/Stop Services shortcuts must be run with Administrator rights. This can be
accomplished by using the Administrator account to login to the LNVR or using the Run as
Administrator right-click option for these shortcuts.
2.4.4. Windows Server 2008 with Service Pack 1

Windows Server 2008 Standard and Enterprise are approved for all OnGuard server and client operations.
Windows Server 2008 32-bit and 64-bit are supported.
Windows Server 2008 Standard and Enterprise are NOT approved for use as any Lenel Digital Video
product host operating system.
Windows Server 2008 Standard and Enterprise can be utilized as the separate OnGuard server with Lenel
Digital Video products.
Windows Server 2008 is not supported for communication with HID Edge Devices.
Windows Server 2008 Standard and Enterprise, SP1 will be called Windows Server 2008, from this point
forward, in the OnGuard 2009 Release Notes.
2.4.5. Service Packs and Critical Patches

Please visit the Lenel Customer Self-Service Center Web site for a complete and up to date list of approved
Microsoft Service Packs (Compatibility Charts section) and Critical Patches (Microsoft Security Bulletins
section): https://customer.lenel.com/. The Lenel Security Patch Policy located on the Web site details
the specific conditions and frequency of certification for Microsoft Windows Critical Updates.
Read through this information carefully since it addresses BOTH OPERATING SYSTEMS AND
DATABASES.
For all instances, Lenel STRONGLY RECOMMENDS enabling the uninstall option when installing the
service pack. There have been rare instances where communications and database activity have been affected by the
installation of a service pack. When these situations have occurred, uninstalling the service pack resolved the issues.
Lenel also STRONGLY RECOMMENDS backing up your database before performing any service pack
installation.
2.5. Security Utility

Windows Firewall is supported by use of the Security Utility; other third-party firewalls are not supported.
Note: “Windows Security Utility” was renamed “Security Utility”. The Start menu shortcut, user interface,
and documentation have been updated to reflect this change.
The Security Utility allows OnGuard 2009 users to take advantage of the capabilities of Windows. The
utility must be run to ensure that the OnGuard software will continue to function properly. The utility
automatically adjusts all settings that affect the OnGuard software. It also displays the current system
settings, as well as a list of actions required for normal operation of Lenel software installed on the local
computer.
Note: The Security Utility does not open database communication ports.
The Security Utility runs automatically during OnGuard, LNVR, IVS, IVAS, and Remote Monitor
installations. It must be run manually after LDVR installations. It must also be run manually as a
maintenance procedure after any of the following changes have been made:
 LNVR security setting changes
 IntelligentVideo Server security setting changes
 Windows updates
 Windows service pack changes
 Windows security setting changes
2.6. Supported Database Systems

For an up-to-date list of tested database systems, refer to the compatibility charts on the Lenel Web site:
https://customer.lenel.com/?q=support/compatibility-charts.
Note: When creating or modifying an ODBC connection on a 64-bit operating system, the location where
the ODBC Data Sources are configured is different than on 32-bit operating systems:
 For 32-bit operating systems: Click Start, then navigate to Settings > Control Panel >
Administrative Tools > Data Sources.
 For 64-bit systems: Navigate to C:\windows\SysWOW64 and run the odbccad32.exe file.
2.6.1. Microsoft SQL Server 2005 Express Edition SP2, 32-bit and 64-bit
2.6.2. Microsoft SQL Server 2005 Standard Edition SP2, 32-bit and 64-bit
2.6.3. Microsoft SQL Server 2005 Enterprise Edition SP2, 32-bit and 64-bit
2.6.4. Microsoft SQL Server 2008 Express Edition, 32-bit and 64-bit
2.6.5. Microsoft SQL Server 2008 Standard Edition, 32-bit and 64-bit
2.6.6. Microsoft SQL Server 2008 Enterprise Edition, 32-bit and 64-bit
Important: Microsoft SQL Server 2008 (All Editions) is NOT SUPPORTED with the LNV Suite.
2.6.7. Oracle 9i R2 32-bit (9.2.0.8) Server and Client

Note: There are known issues with Oracle 9i R2 Client 9.2.0.8 with ODBC Driver patch
(p5728282_92080_WINNT). This configuration is not recommended or supported.
2.6.8. Oracle 10g R1 32-bit (10.1.0.7) Server and Client
2.6.9. Oracle 10g R2 32-bit (10.2.0.4) Server
2.6.10. Oracle 10g R2 32-bit (10.2.0.3) Client with ODBC Driver Patch
(p5699495_10203_WINNT)
2.6.11. Oracle 10g XE only with the LNV Suite
2.6.12. Oracle 11g 32-bit (11.1.0.6) Server and Client
2.6.13. Oracle 11g 64-bit (11.1.0.7) Server with 32-bit Client installed if OnGuard
is running on the same server as the database.
Note: SQL Server 2005 requires .NET 2.0 as a prerequisite.
2.7. Supported System Components

 MDAC (REQUIRED)
- Windows XP: MDAC 2.81
- Windows Server 2003: MDAC 2.82
- Windows Vista and Windows Server 2008: MDAC 6.0c
 DirectX (REQUIRED)
- Windows XP and Windows Server 2003: DirectX 9c
- Windows Vista and Windows Server 2008: DirectX 10
 MSXML 6 (REQUIRED) - MSXML 6 is installed automatically with OnGuard.
 Internet Information Services (IIS) (REQUIRED for the Web Application Server)
- Windows XP and Windows Server 2003: IIS 5 and 6 (Windows XP is not recommended
for the Web Application Server)
- Windows Vista and Windows Server 2008: IIS 7 (Windows Vista is not recommended for
the Web Application Server)
 Adobe Flash Player 9 or later (REQUIRED for Visitor Management Host)
 Microsoft .Net 2.0
 Microsoft .Net 3.5 SP1 (REQUIRED) - Microsoft .Net 3.5 SP1 is installed automatically with
OnGuard when installing using the setup.exe file. To shorten the OnGuard installation time,
install Microsoft .Net 3.5 (available on the Supplemental Materials disc) prior to installing
OnGuard.
 Microsoft Silverlight 2.0 (REQUIRED for Visitor Administration)
Note: If the Microsoft .Net 3.5 SP1 installation fails during the OnGuard installation on Windows Vista or
Windows Server 2008, you must run the System Update Readiness Tool available from Microsoft:
http://support.microsoft.com/kb/947821. To prevent this issue, verify that the Windows Update
service is turned on.
2.8. VMware Platforms

 VMware ESX Server and ESXi Server 3.5.x for all OnGuard services and database server
with software-based license only
 VMware Server 1.0.x
 VMware Workstations 6.0.x and 6.5.x
Note: VMware platforms are not supported with Lenel video products
Note: VMware is supported for OnGuard standard and Enterprise systems.
2.9. Supported Third-party Components

 Crystal Reports XI (11.5) Release 2
 Adobe Reader 9
2.10. Antivirus Software Applications

Lenel does not certify any antivirus software to be used with OnGuard.
Note: Digital Video systems MUST EXCLUDE ALL DATA DRIVES from the antivirus scanning
operations.
 McAfee Virus Scan

McAfee Virus Scan, can be recommended, but is not tested or certified at Lenel and is installed at
the user’s risk.
 Symantec – Norton Antivirus Corporate Edition

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

Trend Micro OfficeScan is used internally at Lenel and can be recommended, but is not certified.
2.11. Supported Web Browser

 Internet Explorer 7.0 (REQUIRED for License Administration and browser-based
applications)
2.12. Supported Terminal Services

OnGuard 2009 will support Terminal Services. This support is a licensed feature. Please refer to the Lenel
Web site to review the current testing status before setting up the following configurations. The Third Party
Applications Compatibility Chart can be accessed at the Customer Self-Service Center at:
 Windows 2003 Terminal Services Client communicates with Windows Server 2003
 Citrix Presentation Server 4.5 for Windows Server 2003
 Citrix is not supported within Windows XP or Windows Vista
2.13. OPC Versions

 OPC Data Access 2.0
 OPC Alarms and Events 1.0
2.14. SNMP Versions

 SNMPv1 Trap Messages are supported.
 SNMPv2 and SNMPv3 Trap messages are not supported.
2.15. Support Pending

The following items are not supported at the time of the OnGuard 2009 release. Support is pending the
completion of testing by Lenel’s Quality Assurance group. Refer to the Compatibility Charts at the
Customer Self-Service Center for the current testing status at: https://customer.lenel.com/?
q=support/compatibility-charts.
2.15.1. High Availability Systems Pending Certification

Important: Support for high availability systems is pending testing by Lenel's Quality Assurance group.
Until testing has been completed, upgrades are at your own risk, and should only be done after performing
your own testing.
OnGuard 2009 will support several high availability configurations. Please refer to the Lenel Web site to
review the current testing status before setting up the following configurations. The Third Party
Applications Compatibility Chart can be accessed at the Customer Self-Service Center at:
 Microsoft Clustering with Windows Server 2003 Enterprise Edition (SP2,R2)
 NEC ExpressCluster X R1 WAN 1.0.5.1 \ LAN 1.0.5.0 with Windows Server 2003 Standard
Edition R2 SP2 and Oracle 10g R2 (10.2.0.3) (32-bit editions ONLY)
 NEC ExpressCluster X R1 WAN 1.0.5.1 \ LAN 1.0.5.0 with Windows Server 2003 Standard
Edition R2 SP2 and SQL Server 2005 Standard R2 SP2 (32-bit editions ONLY)
2.15.2. MobileVerify
MobileVerify support is pending testing for OnGuard 6.3.
2.16. End of Life Products

The following products have discontinued support:
2.16.1. VeriSoft Server and Client
2.16.2. Emergin Wireless
2.16.3. Ultra Scan
3. New Features
3.1. Access Control

3.1.1. Onity Integra Support
OnGuard allows you to set up and manage Onity systems using Onity Integra locks (commonly referred to
in OnGuard as doors) and Onity controllers such as the Integra XPP portable programmer that is treated as
an access panel by OnGuard. In the Onity Integra offline lock configurations, OnGuard acts as a front end
to the Onity data transferred between OnGuard and the Onity locks via the portable programmers.
 Onity Template Support

Onity template support is additional functionality that is required in order to fully capitalize on the
integration of Onity CT locks. This functionality is required in order to limit the number of times a lock
needs to be programmed via the XPP portable programmer. This is accomplished by creating a pre-defined
set of credentials and access rights that typically remain unchanged. These credentials are then downloaded
to the lock and are reused as people are cycled in and out of a facility. This functionality is mostly used in
education markets to handle the large number of incoming and outgoing students throughout the year.
 Configure Onity Alternative Fire Code Settings on a System-wide Basis in System Options
The Alternative Fire Code (AFC) features (Fire Code re-locking timers and Deadbolt) are used in
jurisdictions where the local fire code specifies stand-alone locks cannot automatically relock behind a user
exiting a room. If Manage Alternative Fire Code (AFC) is enabled in System Administration on the
System Options > Onity tab, you can configure the AFC features on a door-by-door basis.
 Blocking Cards are Supported for Onity Integra Locks

Blocking cards are used by authorized personnel to time access through doors; a single blocking card can
be used to block access to any number of locks. Blocking cards can be set up and printed in System
Administration.
 Multiple Operators are Supported for Onity Integra Controllers

The new Operator form allows you to add and configure passwords and permissions for up to 16 XPP
operators to the Onity Integra access panel (controller).
 Printers/encoders Supported for Printing or Encoding Onity Badges

- Fargo HDP5000 printer equipped with an ISO magnetic encoder, using driver version
2.0.0.5 or later.
- Use the Unitech MSR206 magnetic stripe encoder to encode Onity card data.
3.1.2. Duress Card Formats

Configure Magnetic and Wiegand card formats as duress formats. When the controller detects a duress
format, it reports events as duress rather than normal. This setting is different from the Deny On Duress
PIN setting for readers that accept PIN input. The system ignores the duress format setting during badge
encoding.
3.1.3. Reversed Bit Order Card Formats

If your reader reports duress by reversing the bit order, a Wiegand card format can be configured with a
reserved bit order format if your reader is capable of reversing bit order. When the controller detects this
format, it reverses the bit order of the incoming data before processing it. The system ignores this setting
during badge encoding.
3.1.4. Bioscrypt Duress Finger Support

The addition of Duress and Reverse Bit Order Card Format capabilities enable OnGuard to support
Bioscrypt Duress Finger function.
3.1.5. New Behavior for Alarm Shunt with Pre-Alarm or Tailgate Configuration
Resolves Compatibility Issue (OG-16091)
A Tailgate cannot be configured with an alarm shunt because both use auxiliary output 1. Consequently, if
Tailgate is enabled, Alarm Shunt will be deselected and vice versa. If you plan to configure an alarm shunt
and a pre-alarm, they cannot both use auxiliary output 1.
For the LNL-2220 and LNL-1300 readers, if Alarm Shunt is enabled, no pulse aux output option will be
available in the Pre-Alarm mode drop-down list. For the LNL-1320 reader, if Alarm Shunt is enabled,
select Pre-Alarm mode “Pulse aux output 2.”
3.1.6. HID Edge Access Level Configuration Enhancement

HID Edge supports eight (8) access levels per badge per device. OnGuard now warns you when you
attempt to add more than eight (8) access levels with a common HID Edge controller to a cardholder badge,
to bulk badges, or to selected groups.
Note: This functionality is not available in the Area Access Manager browser-based client.
3.1.7. Support for Lenel-branded HID Edge Readers

If you are installing non-Lenel, HID access panels you must purchase a separate license. Lenel-branded
HID access panels come with a built-in license. You can add any combination of HID access panels and
other types of access panels up to the maximum capacity of your OnGuard system.
3.1.8. Additional Hardware Settings for Encryption

The following downstream encryption settings for the LNL-1300 and LNL-1320 were not described in the
Hardware Installation Guide.
The LNL-1100, LNL-1200, LNL-1300, and LNL-1320 Series 2 modules can support encrypted
communications under the following conditions:
 The panel type is an LNL-1100, LNL-1200, LNL-1300, or LNL-1320 Series 2.
 The reader interface is connected to an LNL-2220 or LNL-3300 access panel.
 Both the reader interface and the access panel are downloaded with the latest firmware.
 Host and downstream encryption are both enabled for the specific access panel.
 No more than twelve (12) modules are connected to any port of the LNL-2220 or LNL-3300.
Because the encrypted data is larger, fewer modules can be connected to each port of the
access panel.
In this case, the encryption mode of each reader can be set to one of the following values:
 None - encryption is not required to send communication.
 Not Required - encryption is attempted but if it fails the communication is sent unencrypted.
 Required - encryption is attempted but if it fails the communication is not sent.
 Custom - the custom key is used and if communication cannot be established then an
encryption error status is generated.
Downstream Encryption Status in Alarm Monitoring

After enabling downstream encryption, log out and back in to alarm monitoring to have encryption status
displayed for each downstream device.
Scheduled Unlocked Mode and Input Supervision Supported for HID Readers
Reader functions supported for HID panels allow you to grant access on “Card Only” or “Card and Pin”
and configure strike time, held time, and extended strike for specified users. In addition, suppression of
strike output on REX is supported.
3.1.9. New Schlage Configuration/Demo Tool (CDT)

New Schlage CDT version 3.04 is available on the Supplemental Materials disc in the OEM Access
Control\Schlage Wireless folder. The Schlage CDT utilizes Sun Java instead of Microsoft Java. Microsoft
Java is no longer available.
3.2. Visitor Management
With the release of OnGuard 2009, Visitor Management can be used with the Host, Administration, Front
Desk, and Kiosk applications.
3.2.1. Host
The browser-based Visitor Management Host is used to schedule visits. It requires Internet Explorer 7,
Flash Player 9 or later. The calendar now displays a daily view instead of a weekly view. Flash Player can
be obtained from: http://www.adobe.com/support/flashplayer/downloads.html#fp10.
3.2.2. Advanced Search

Previously, searching criteria was only based on visitor name. Advanced search is now available in the
Visitor Management Host.
3.2.3. Delegates
Hosts can designate delegates to help manage their visit schedule. Delegates require their own user
accounts and permissions to be configured just as hosts would.
3.2.4. Administration
The browser-based Visitor Administration is used to configure properties of the Visitor Management
system. It requires Internet Explorer 7 and Silverlight 2.0. Silverlight can be obtained from
http://www.microsoft.com/silverlight/.
3.2.5. Front Desk

The Front Desk may be used to search for and add visitors, sign in or out, assign an access control badge,
print a temporary adhesive badge, or capture photographs. It supports business card scanning. It requires
the following device drivers: Dymo 400 Turbo/LabelWriter, SnapShell business card scanner (if used). A
camera with a Windows XP/Vista driver may be used. The Front Desk can be deployed through ClickOnce
deployment.
3.2.6. Kiosk
The Kiosk can be used to sign in or out with 3 of 9 3:1 bar codes, print temporary adhesive badges, and
capture photographs. (Extended 3 of 9 bar codes are not supported.) It is installed on a machine with the
following:
 Microsoft Windows XP Professional with SP3 and associated security patches
 Microsoft .NET 3.5 SP1
 Touch-It Virtual Keyboard software
 Device drivers: Parabit printer, Logitech QuickCam Orbit AF camera.
Note: The bar code scanner does not require a driver.
3.2.7. Bulk User Import Tool for New Visitor Management Applications
The user logging into Visitor Management Host, Administration, Front Desk, or Kiosk must be a
cardholder. This cardholder must be paired with a user. This is typically done in System Administration by
creating a directory, linking the cardholder with the directory account, then linking the user to that same
directory account. The Bulk User Import Tool is for quickly adding and linking users to their cardholder
directory accounts. The Bulk User Import Tool will be available for download through the Customer Self-
Service Center under the Installation Tools section:
https://customer.lenel.com/?q=support/installation-tools (You will need a Lenel login to gain
access to this site).
3.3. Digital Video

3.3.1. Support for Additional IP Cameras, Video Servers, and Encoders
Below is a list of the latest IP cameras and encoders that Lenel has added to our current product offering for
the Lenel Network Video Solution, with OnGuard 2009. IP devices are licensed on a per channel license
which is currently already implemented. No new license requirement is needed for the new devices listed
below.
 Axis: P3301, P3301 H264, Q1755, Q1755 H264, Q7401, Q7401 H264, Q7406, Q7406
H264
 HikVision: DS-2CD812PF MPEG4, DS-2CD852F MPEG4, DS-6101HF MPEG4
 Lenel: LC320-FDX MPEG4, LCi-100-DX, LVS310-A MPEG4
 Panasonic: WV-NF284, WV-NF284 MPEG4, WV-NF302, WV-NF302 MPEG4, WV-
NP244, WV-NP244 MPEG4, WV-NP304, WV-NP304 MPEG4, WV-NS954 PTZ, WV-NS954
PTZ MPEG4, WV-NW484S, WV-NW484S MPEG4, WV-NW964 PTZ MPEG4
 Sony: SNC-CM120, SNC-CM120 MPEG4, SNC-CS20, SNC-CS20 MPEG4, SNC-
DM110, SNC-DM110 MPEG4, SNC-DM160, SNC-DM160 MPEG4, SNC-DS10, SNC-
DS10 MPEG4, SNC-DS60, SNC-DS60 MPEG4, SNC-RX530, SNC-RX530 MPEG4, SNC-
RX530 H264, SNC-RX570, SNC-RX570 MPEG4, SNC-RX570 H264
Note: The Lenel LCi-100DX is only supported with a resolution of 720x480.
3.3.2. Support for RTP Protocol

Real-time Transport Protocol (RTP) is a standardized packet format for delivering video and audio over the
Internet. OnGuard now supports RTP working in conjunction with RTSP. The Digital Video > Camera >
RTP Settings sub-tab in System Administration is used to configure the system to receive video from RTP-
enabled cameras. The optimal selecting will be set by default. The following methods are supported by
OnGuard: RPT via Multicast, RTP via RTSP, RTP via RTSP via HTTP, and RTP via UDP/IP. Not all
cameras or standards support RTP/RTSP protocols. Refer to the documentation provided with the camera to
determine the connection type available.
3.3.3. LNVR Redundant Failover

The Redundancy feature is a full-time failover solution. In a failover configuration, video channels are
recorded to the primary recorder unless it goes offline, at which time recording occurs on the secondary
recorder. In a redundant configuration, video channels are recorded to both the primary and secondary
recorders regardless of the status of the primary recorder.
Redundant channel events are not sent to Alarm Monitoring in normal mode. For example, if a motion
detection event occurs on a camera with redundancy configured, the alarm will only be sent to Alarm
Monitoring from the primary recorder. Once the primary fails, the redundant server will start sending
channel events.
Redundancy is configured on the Video Recorder > Failover sub-tab.
3.3.4. Video Quality Enhancement Algorithms

The Video Quality Enhancement (VQE) algorithms are used to enhance video viewing quality. VQE
algorithms can be configured in Alarm Monitoring or Remote Monitor. Algorithms include De-interlacing,
Sharpener, and Fog Removal. VQE algorithms are only available for LNVR camera channels.
3.3.5. Double Video on Alarm Enhancements

Enhancements have been made for the Double Video on Alarm feature. This feature is now configurable
from the Digital Video > Alarm-Video Configuration tab in System Administration.
3.3.6. Network Video over HTTP via Proxy

For systems with the Web Application Servers running Internet Information Services (IIS) 7 on Windows
Vista or Windows Server 2008, VideoViewer browser-based clients located outside of the internal network
now display video over HTTP via proxy. This configuration allows the Web applications to communicate
using HTTP port 80 or HTTPS port 443. For more information about the networking requirements for this
configuration, refer to the Network Video over HTTP via Proxy appendix in the Installation Guide.
For Web Application Servers running on Windows XP and Windows Server 2003, users must be logged
into the Windows client as a Domain user with access to the video recorders to view video with the
VideoViewer browser-based client.
3.3.7. Optimization of IntelligentVideo Events
Optimizations have been made to several IntelligentVideo events to improve their performance.
Object Detection, Loitering and Object Left behind have been optimized to enhance processing speed for
increased throughput. The optimization should enable more channels to be run on the IntelligentVideo
Server.
3.3.8. IntelligentVideo Embedded Analytics

IntelligentVideo embedded analytics is a digital video analysis system with the ability to recognize,
analyze, and classify information. Embedded analytics process the video directly on the camera rather than
on the LNVR or IntelligentVideo Server. Embedded analytics is currently supported for the following
events: Invalid Camera, Loitering, Object Detection, and Smart Video Motion Detection. IntelligentVideo
Embedded Analytics are introduced with the Lenel LCi-100DX camera.
3.3.9. Integrated Support for goVision Video Recorders

Integrated support has been added for goVision R1 and R1.5 video recorders. Basic configuration of the
goVision recorder can be performed in System Administration; Advanced configuration can be applied
from the recorder Web page.
Note: After upgrading a system with goVision previously installed via the add-on, click [Update
Capabilities] on the Digital Video > Video Recorder tab, then right-click the goVision recorder and select
Import From Recorder to update the default information for the camera on the Camera tab. (OG-18154)
 Integration with the goVision DS8000 recorder

 Support for H.264
 goVision channels are now supported in Remote Monitoring
 goVision channels can fully operate in VideoViewer browser-based client
 IntelligentVideo Servers can be configured for goVision recorders
 Import from the goVision recorder is supported so that the configuration of the recorder can
be imported and persisted in the OnGuard database
 Inputs/Outputs can be configured and operated from OnGuard
 Change password is now supported
Limitations:
 The maximum number of client connections is 4. (OG-16260)
 The goVision Remote Station software CANNOT be installed on the same computer as an
OnGuard client.
 The username and password of the goVision recorder must be set to the defaults to view video
in Remote Monitoring and the VideoViewer browser-based client.
 Date and time display should be disabled or masked when using IntelligentVideo events to
prevent false alarms.
 IV Overlay is not supported for goVision recorders. (OG-18040)
 Video Quality Enhancement (VQE) algorithms are not supported with goVision.
 Channels are not displayed properly on the second monitor of a dual monitor system. (OG-
18035)
 Volume sliders and mute functions are not supported (OG-18137)
 Duplicate names are not supported. Before making a change on a goVision channel that has
the same name as another channel in OnGuard, you should change the name to avoid
duplication. (OG-18095)
 Streaming at a live frame rate greater than 6 fps will limit the capabilities of the goVision
recorder in terms of recording audio and detecting motion. Although the System
Administration user-interface allows greater values, the live frame rate should not be set
higher than 6 fps. Some IntelligentVideo algorithms require greater than 6 fps; this will still
impact the capabilities of the recorder but can not be avoided for the IntelligentVideo
algorithms to function properly.
 To set up Global I/O Linkage with goVision recorders, set the input event to use the Device
(DVR) with Generic Event; Under event text for the Generic Event enter “Switch X input
alarm” (where X is the input number).
 The user-defined timezones for “Recording Timezone” and “Motion Detection Timezone”
will not be passed to or from the goVision recorder.
 When changing a setting in System Administration, a full channel download is sent to the
goVision recorder. This means that if a channel has QCIF resolution for Live streaming
(Network) and the user changes the value from the Remote Station application (so that the
System Administration value is QCIF and the Remote Station value is CIF). If you then
change the Brightness to another level in System Administration. OnGuard will transmit
everything including resolution, so the resolution will change back to QCIF.
3.4. High Availability Systems

3.4.1. NEC Fault Tolerant Server Monitoring Service
The NEC Fault Tolerant Server Monitoring Service is now available on Supplemental Materials disc
revision 8. This feature is included with new NEC systems and available for purchase for existing systems.
The Lenel NEC Fault Tolerant (FT) Server Monitoring Service is a Windows Service designed to monitor
changes in hardware and network status on NEC Fault Tolerant servers. Status changes include hardware
that is removed, malfunctions, fails diagnostics, or becomes otherwise disconnected. This service will
monitor for these conditions and will send an alarm for each failure to Alarm Monitoring as well as send an
e-mail message detailing the status change.
 For OnGuard 6.3 and later: One instance of the OnGuard license feature “NEC FT Server
Monitoring” is required.
 For OnGuard 6.1: Licensing is controlled internally. Licensing for OnGuard 6.1 and earlier
requires a license file through Lenel’s Custom Solutions department. To obtain this license,
send an e-mail to cs@lenel.com with the MAC address of the server where the NEC FT
Server Monitoring service will run, typically the Lenel application server.
Refer to the documentation that accompanies the service for additional requirements.
3.4.2. NEC ExpressCluster Monitoring Service

The NEC ExpressCluster Monitoring Service is now available on Supplemental Materials disc revision 8.
This feature is included with new NEC systems and available for purchase for existing systems. The NEC
ExpressCluster Monitoring Service is a Windows Service designed to monitor changes in hardware and
network status on servers clustered using NEC ExpressCluster software. Status changes include inter-
connect network connection failures, disk mirroring failures, critical ExpressCluster service crashes, and all
other events that ExpressCluster reports to the Windows Event Viewer. This service monitors for these
conditions and sends an alarm for each failure to Alarm Monitoring as well as sending an e-mail
notification detailing the status change.
This service is designed to work with any version of NEC ExpressCluster that Lenel supports as well as
any other versions that report status events and errors to the Windows Event Viewer.
 For OnGuard 6.3 and later: One instance of the license feature “NEC Express Cluster
Monitoring” is required.
 For OnGuard 6.1 and earlier: Licensing is controlled internally. Licensing for OnGuard 6.1
and earlier requires a license file through Lenel’s Custom Solutions department. To obtain this
license, send an e-mail to cs@lenel.com with the MAC addresses from both the primary
and secondary servers.
3.4.3. NEC ExpressCluster Utility

The Lenel ExpressCluster Utility (LenelExpressClusterUtility.exe) replaces the LenelVComFix.exe on
Supplemental Materials disc revision 8. The Lenel ExpressCluster Utility allows you to automatically
configure several Windows settings and then modify the following:
 Various registry settings, which vary depending on whether OnGuard is already installed
 License Server Host entry in the ACS.INI file
 Database Connection, Application Server Uniform Resource Identifier (URI), and License
Client Host settings in the application.config file
 Java Policy
 Internet Favorites (an ExpressCluster Manager Favorite is added)
4. Known Issues/Updates
4.1. General
4.1.1. Modifying or Removing OnGuard
The method for repairing or modifying an OnGuard installation has changed. Prior to OnGuard 2009, the
options to modify or repair an OnGuard installation were available by going to Windows Control Panel,
selecting Add or Remove Programs, selecting OnGuard, and clicking [Change]. In OnGuard 2009, the
Modify and Repair options have been removed from Control Panel. Instead, you must re-run the OnGuard
installation setup in order to use these options.
If you choose to repair OnGuard you will need to reset your DSN name, license server name, and any other
custom setting made to the ACS.INI file and/or application.config file. You should back up the ACS.INI
file and/or application.config file before doing any maintenance.
If you are using the repair option when re-installing OnGuard where either the Application Server or
Database Setup features have been installed then you will receive a warning telling you to back up specific
system files. These files are listed in the warning message and will be different for each installation. Make
sure to back up these files or you will lose critical system information located within the files.
4.1.2. Temporary Files Remain After Installation Has Completed

Some components needed by OnGuard may leave temporary files on the system root drive after the
installation. More information can be found here: http://support.microsoft.com/kb/950683.
4.1.3. SQL Server2005 Installation Instructions Moved to Advanced Installation

Topics Guide
Instructions for installing SQL Server 2005 have been moved from the Installation Guide to the Advanced
Installation Topics Guide. The Installation Guide now features instructions for SQL Server 2008.
4.1.4. OracleSystems Need to be Set Up to Use Windows Authentication by

Default
Oracle systems need to be set up to use Windows Authentication by default. After an upgrade, Windows
authentication to the database is assumed for all database setup and browser-based applications. Therefore,
if the user does not have “Windows Authentication” set up, it will need to be configured. If the user does
not want to use Windows Authentication, the Username/Password can be used instead. This will need to be
changed via the ConnectionString file setting in the application.config file AND the password will now be
in plain text. This also applies to SQL Server systems utilizing the browser-based applications.
4.1.5. World Time Zone Default Data Updated

World time zone default data has been updated according to the changes noted on Microsoft’s Web site:
http://support.microsoft.com/kb/955839
4.1.6. Flash Player Removed from Supplemental Materials Disc

Flash Player is required for some browser-based applications. It is no longer available on the Supplemental
Materials disc and can be downloaded from:
http://www.adobe.com/support/flashplayer/downloads.html#fp10.
4.1.7. Web Application Server Not Recommended with Windows XP or Windows

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

If using the browser-based applications, we highly recommend using Windows authentication to control
access to the LDVR and LNVR video servers. If using browser-based applications, disable parent paths for
the Web server for heightened security.
4.1.9. Column Heading Tooltips Disabled for Windows XP (OG-12746)

Tooltips are not available for column headings in OnGuard running on Windows XP.
4.1.10. Windows Vista: Security Utility Must be Run Manually for Public Profile
If the Public Network profile of the Windows Firewall is used in Windows Vista, the Security Utility must
be run again once the profile is active. The Public profile is not updated during the initial run of the
Security Utility.
4.1.11.Windows Vista: ACS.INI File Cannot be Edited by Administrator Group

Member
By default, the Windows Vista Admin account does not have permission to save the ACS.INI file. To work
around this issue, add the Admin user to the ACS.INI file security settings and allow full control.
4.1.12.Error 1905. Module C:\Program Files\OnGuard\msvbvm50.dll Failed to

Unregister
This error may occur when upgrading to OnGuard 2009 on Windows Vista. This error can be safely ignored
with no side effects to the installation.
4.1.13. FormsDesigner Field Style Border and Inside Edge not Functioning
Properly
In order to support recently introduced changes to the user interface, the ability to turn off a sunken edge
border for a control in FormsDesigner has been disabled.
4.1.14.User with View/Add Readers Permission Can Modify Destination

Assurance (OG-17969)
Destination Assurance configurations can be modified by a user who has permission to only view and add
readers.
4.2. Access Control

4.2.1. Onity Integra Locks: Door Does Not Come Out of AFC Office Mode with
AFC Office on Enter and Second Swipe of Badge (DE1671)
When AFC Office when enter is enabled on a lock and Office when exit is not, the lock will only relock
(following an entry event) when either the Relocking timer expires or the Deadbolt ends AFC office
mode option is enabled and invoked. When both AFC Office when enter and Office when exit are
enabled on a lock, the lock will also relock when a valid card is used again, following the entry of exit
events.
4.2.2. Deleting Badges from Onity Integra Locks

When deleting badges from Onity Integra locks, at least 1 badge must always remain on the lock.
Attempting to delete all badges will not succeed, and the lock will retain the same access privileges it had
before the attempt was made. If all access to the lock is to be prohibited, some other mechanism such as
blocking or changing schedules should be used.
4.2.3. Open Supervised Device Protocol Reader Tamper Switch Monitoring
Open Supervised Device Protocol (OSDP) reader tamper switch monitoring now works reliably after
Update Hardware Status is performed.
4.2.4. Reader Alarm Shunt Not Supported with LNL-2220 in Paired Mode
The Alarm Shunt feature does not operate on paired readers. It will operate properly with single readers and
on primary/alternate readers.
4.2.5. HIDEdge Software for Device Communication Not Supported with

Windows Vista or Windows Server 2008 (OG-17749)
The HID Edge software provided to Lenel by HID for device communications is not compatible with
Windows Vista or Windows Server 2008. Communication Servers expected to communicate to Edge
devices cannot use these operating systems.
4.2.6. HID Edge Panels Drop Offline After a Period of Time (OG-16588)
When multiple HID Edge devices are brought online individually, they may drop offline after several
hours. Restarting the Communications Server service will restore all devices to proper operation. To avoid
this issue, restart the Communication Server after bringing multiple HID Edge devices online individually.
This issue is being investigated with HID.
4.2.7. HIDEdge Devices Replaced with Another Device May Not Grant Access
(OG-18068)
It has been reported that in some cases replacing a working HID Edge reader with a different one and then
editing the MAC address in OnGuard will allow the new reader to come online but not grant access. This
could not be reproduced, but if it occurs, deleting the reader definition in System Administration and then
adding the new reader should resolve the issue. This issue is being investigated with HID.
4.2.8. Strike Field States Cutoff on Close (OG-18019)

For HID Edge devices, the Strike field states Cutoff on close. The actual reader strike output will cutoff on
open in all cases.
4.2.9. Low Battery and Tamper Reporting for Schlage Wireless Locks (OG-18069)
To enable low battery and tamper reporting for Schlage wireless locks, the Keypad Type on the reader tab
must be set to LNL-2020 w/ Tamper. This setting can also be used with the Schlage WRI wireless reader
interface, but this will disable keypad support.
4.2.10. OSDP Reader May Have Incorrect LED Display (OG-17529)

If power is lost to an Open Supervised Device Protocol (OSDP) reader, but power to the Lenel reader
interface is maintained, the LED display pattern may be incorrect until some access activity takes place.
4.2.11. Intrusion Mask Group Correctly Suppresses Alarm Events (OG-17542)

There was an issue that caused Intrusion Mask Groups to continue to report alarms in Alarm Monitoring
even if the system was in an after-alarm disarmed state. This issue has been fixed in OnGuard 2009. Alarm
Monitoring will now correctly suppress alarm events while in the after-alarm disarmed state.
4.2.12. Updated Wiring Diagram for Handkey Readers (OG-17875)

The wiring diagram for Handkey readers has been updated to show the preferred grounding method. All
new and existing installations should utilize this new wiring method to prevent damage to the Handkey
unit.
4.2.13. Downstream Encryption Key Download Will Fail if any I/O Modules Are
Offline
If any Series 2 I/O modules (LNL-1300, LNL-1320, LNL-1100, LNL-1200) are offline when the Download
Encryption Keys command is issued from Alarm Monitoring, the command will fail and some or all of the
boards will not receive the keys. To work around this issue, ensure all boards are online or if a board is
known to be offline delete it from the system to download keys to the other boards.
4.2.14. Area Access Manager Browser-based Client Reports Not Supported with
Windows Authentication on Windows Server 2008 or Windows Vista (OG-
18066)
Reports will not run properly from Area Access Manager (Browser-based Client) with Windows
Authentication on Windows Server 2008 or Windows Vista. For these operating systems, only SQL
authentication is supported with browser-based reports.
4.3. Identity Management

4.3.1. Change in 10 Print Slap Record Format (OG-13658)
The 10 Print Slap capture and license have been renamed OpenCapture. Sagem-Morpho templates are now
captured for use with Lenel bioCLASS readers. 10 Print Slap records are now stored in an optimized
format in the database. The record only allocates the amount of space necessary for the fingerprint; the
record is optimized so that it does not save space for all fingerprints if only one is captured. Any existing
10 Print Slap records must be deleted and re-captured following the upgrade to OnGuard 2009 in
order to maintain use of this feature. If existing 10 Print Slap records are not re-captured, Database Setup
may fail, and a database error will be received when viewing a cardholder record that has not been updated.
4.3.2. SharedCard Printer May Be Unknown in Default Printer for Badge Type
Drop-down Client Workstations
When printing to a shared card printer, the name may appear as an "Unknown printer" in the Default
Printer for badge type drop-down on client computers. To work around this problem, select the
"Alternate Printer" and then select a valid printer.
4.3.3. Magicard Prima 3 Must Use Driver Version 5.7

The Magicard Prima 3 printer should use driver version 5.7, not version 5.7 issue 1. If driver version 5.7
issue 1 is used, the printer will not pick up the card from the hopper; it will just time out and not print at all.
4.4. Visitor Management

4.4.1. Visitor Management Browser-based Client Applications Not Supported with
Windows Server
Due to the default IE enhanced security settings preventing the use of some browser components, Visitor
Management Host and Administration are not supported on Windows Server 2003 or Windows Server
2008.
4.4.2. URL for Visitor Management Host and Administration (DE379)

The URLs for Visitor Management are no longer case-sensitive.
4.4.3. After Logging into Visitor Administration, an Error Occurs Stating, “The
current user is not authorized to perform this operation.” (DE1596)
When this error occurs, it may be due to the lack of the directory accounts permission. This permission is
configured on the Users > Cardholder Permission Groups > Cardholder tab in System Administration
or ID CredentialCenter.
4.4.4. After Adding List Builder Items, IIS Must be Restarted (DE318)
List Builder items sometimes do not appear in user-defined drop-down fields. After making changes in List
Builder, it is necessary to restart IIS.
4.4.5. Sign-in Locations Must be Modified (S2902)

For visits scheduled in System Administration, ID CredentialCenter, or Visitor Management, the sign-in
location does not exist. When these visits are modified in Host or Front Desk, a sign-in location must be
provided.
4.4.6. Supported Date Format (DE385)

“Short date, no time” (seen in FormsDesigner) is the only date format supported for date fields in Visitor
Management Host.
4.4.7. Searching is Based on the Visitor Last Name

Performance has been enhanced by limiting basic searching to the visitor’s last name.
4.4.8. After
Using Basic Search to Find a Visitor, it is Not Possible to Perform the
Same Search Again
After a search has been performed in Visitor Management Host, the search results must be cleared and
criteria must be entered to conduct a second search, even if it is the same exact search.
4.4.9. Advanced Search Results are Based on the Last Entry When Two or More of
the Same Search Criteria are Selected (DE1586)
When the same search criteria are selected in advanced search, only the last entry will apply to the search.
4.4.10. Limited Support for Group Visits

When group visits are scheduled through the Front Desk or Host, they will appear in the System
Administration, ID CredentialCenter, or Visitor Management user interface as single visits. However, these
single visits cannot be changed through this user interface.
4.4.11. Group Visit Limitation of 75 Visitors (S3592)

Group visits are limited to a maximum of 75 invited visitors to ensure reliable performance.
4.4.12.When Deleting a Large Group Event, the System May Experience a Slight
Wait Time (DE1480)
When a large group event is deleted, notification e-mails are sent for the participants. This may require
some extended wait time while the system performs this function.
4.4.13. Visitors Can Sometimes be Saved Without Filling in All Required Fields
(DE393)
If a field is required, all users should have permission to view and edit it. When a user does not have
permission to view a required field (configured through the Field/Page Permission Group), it will not be
visible in Visitor Management Host; however, saving a newly added visitor will be possible even though
the required field is blank.
4.4.14.A Visitor Management Host User Should Not be Linked with Directory
Accounts Associated with Different Cardholders (DE1094)
Directory accounts associated with different cardholders should not be linked to the same user. This will
prevent that user from accessing Visitor Management Host.
4.4.15. Login with the Correct User Name and Password Fails if Access to the
System is Disabled (DE1471)
When the correct user name and password has been typed in and there is a failure to log in, check that the
user account has access to the system. This is configured on the Users > General tab in System
Administration or ID CredentialCenter.
4.4.16. A Change in User Permissions Requires Recycling the Application Pool

(DE1275)
Changes made to permissions are not immediately applied for Visitor Management Host. Recycling the
application pool in IIS will allow the correct permissions to be applied.
4.4.17. Cardholder Permission to Delete Visits is Required to Remove Visitors

from an Event (DE411)
When removing invited visitors from a scheduled event, you must have this delete permission. Even though
the event is being modified, removing a visitor from a scheduled event is equivalent to deleting an event.
4.4.18. To Schedule Events, Both the Visit Add and Modify Permissions are
Required (DE1118)
To add visit events in Visitor Management Host and Front Desk, users need both the Visit Add and Modify
permissions, which are configured on the Users > Cardholder Permission Groups > Visitor Management
tab in System Administration or ID CredentialCenter.
4.4.19. To Sign a Visitor In or Out with Front Desk or Kiosk, the Visit Modify and
Sign-in/out Permissions are Needed (DE1486)
To sign visitors in or out, users need both the Visit Modify and Sign in/out permissions, which are
configured on the Users > Cardholder Permission Groups > Visitor Management tab in System
Administration or ID CredentialCenter.
4.4.20. The Badge Use Limit View Permission is Required for Printing Badges in
Front Desk or Kiosk (DE1307)
When printing badges for visitors using Front Desk or Kiosk, the Badge Use Limit View permission is
needed. This is configured on the Users > Field/Page Permission Groups tab in System Administration or
ID CredentialCenter.
4.4.21.To Send E-mail Notification of an Event, the Global I/O Permission is

Needed (DE1516)
The notification e-mail will not be sent for scheduled or updated events and an error will not be logged if
the user does not have the Global I/O permission. This is configured on the Users > System Permission
Groups > Global I/O tab in System Administration or ID CredentialCenter.
4.4.22. E-mails Do Not Have the Scheduled Time or Visit Key if the Event Was
Created in System Administration, ID CredentialCenter, or Visitor
Management (DE1580)
When an event has been created in System Administration, ID CredentialCenter, or Visitor Management,
the notification e-mail does not have the scheduled time or visit key. Visit events should be scheduled in
Visitor Management Host or Front Desk.
4.4.23. UDFs Appear to be Missing when Changes to Events are Cancelled

(DE1723)
Modifying events containing user-defined fields (UDFs) and then clicking the [Cancel] button may cause
UDFs to seem to disappear from the Visitor Management Host user interface. To refresh the view properly,
click on the [Today] button and select another event. Then go back to viewing the original event.
4.4.24. To See Events in Front Desk in a Segmented System, the Segments

Permission is Needed (DE1459)
Visit events cannot be seen in Front Desk unless the Segments permission is selected, even though they can
be seen in System Administration, ID CredentialCenter, or Visitor Management. This is configured on the
Users > Cardholder Permission Groups tab in System Administration or ID CredentialCenter.
4.4.25. A Host and Their Delegate Should be Assigned the Same Segment
(DE1192)
In a segmented system, the host and the delegate must be in the same segment. If they are on different
segments, events may appear to be missing from one or both calendars.
4.4.26. In BadgeDesigner, the Visit Times Indicate that They are UTC When They
Are Not (DE1284)
The database fields, “Visit Time In UTC” and “Visit Time Out UTC” will be printed in the time zone of the
visit. They will not be printed in UTC time.
4.4.27. Front Desk or Kiosk Has the Error, “The HTTP Request is Unauthorized
with Client Authentication Scheme 'Negotiate'. The Authentication Header
Received from the Server Was 'Negotiate,NTLM'.” (DE1296)
This error typically occurs when attempting to log into the Front Desk on a computer which is on a
different domain. Typically, one security policy is supported (regardless of the IIS setting). The workaround
is to create a second service with a different security policy and second FrontDeskClickOnce and
KioskClickOnce deployment sites with updated policies and endpoints. For more details, refer to the
Installation Guide. The server should also be added to the Internet Options list of trusted intranet sites.
4.4.28. Access Control Badges Retain Previous Access Levels When Reassigned
(OG-15158)
When an access control badge is assigned to a visitor being signed in, it retains the access levels currently
configured for the badge. Signing in/out a previous visitor with the badge does not change the access levels.
4.4.29. Error Messages that Result From Not Having JavaScript Are Not
Localized (DE395)
Visitor Management requires that JavaScript be enabled in the browser. When it is not, the error message
“This application requires JavaScript. Contact your administrator,” will appear not localized.
4.4.30. The Service Trace Viewer Tool is Needed to View the Visitor Management
Tracing File (DE1472)
Windows Communication Foundation Service Trace Viewer Tool (SvcTraceViewer.exe) should be used to
view the Visitor Management tracing file (Idvm.svcLog) on the server. This can be obtained from Microsoft
as part of the Windows SDK: http://www.microsoft.com/downloads/details.aspx?
FamilyID=e6e1c3df-a74f-4207-8586-711ebe331cdc&displaylang=en
4.4.31. Minimum Module Width and PDF417 Correction Are Not Supported
(S3794)
When printing bar codes on badges, the minimum module width and PDF417 correction are not supported.
4.4.32. Only TrueType Fonts Are Supported for Badge Printing

Badges for Visitor Management should be designed using TrueType fonts. Other fonts may cause an error
when previewing or printing the badge.
4.4.33. Kiosk Has the Error, “You need permission to print badges to use the
Kiosk.” (DE1531)
When this error occurs on the Kiosk, and the Print badges permission has already been properly configured,
be sure that the permission is selected for Badge types and layouts as well. This is configured on the Users
> Cardholder Permission Groups > Badge tab in System Administration and ID CredentialCenter.
4.5. Digital Video

4.5.1. Warning – Security!
In order to facilitate equipment installation and be adaptable to existing corporate security policies, LDVR
and LNVR video servers are shipped and/or configured by default with no security policies. Once a system
is going into production, Lenel recommends that security on these servers should be locked down by your
system administrator so that only users with valid Windows domain accounts have access to video. With
the introduction of the browser-based applications, the ability to access video servers is made much easier
and therefore, using Windows domain authentication to deny access to these servers is highly
recommended and necessary for a secure deployment.
4.5.2. Frame Rates Higher than 50fps May Not be Accurate (OG-16061)
Setting the frame rate to above 50fps on cameras that support high frame rates may result in a slightly
different fps value. For example, if the frame rate is set to 50fps, you may experience a frame rate of 52fps.
4.5.3. Reduced Rate Recording Not Supported with H.264 Cameras

Reduced rate recording (including time-lapse) is not supported with H.264 cameras. The LNVR can only
record at the rate of live recording, not less. Due to the nature of the H.264 algorithm, the gains of such a
configuration are not as necessary as they are with non-motion based encoding technologies such as
MJPEG. The frames that would be dropped comprise an insignificant percentage of the total storage due to
the encoding algorithm.
In previous versions of OnGuard, these features were configurable in System Administration. Any existing
configuration of these features will be reset to their default values and disabled. If upgrading to OnGuard
2009 with existing H.264 cameras, perform a full download for all existing LNVR recorders once the
upgrade is complete. The following camera types are affected:
 Axis: Q7406, Q7401, P3301
 Sony: SNC-DF50DN, SNC-DF80DN, SNC-RZ50, SNC-RX550, SNC-CS50
4.5.4. Axis
Cameras with H.264 Compression Do Not Support Square Pixel
Compensation (OG-17659)
Square pixel compensation is not supported by Axis cameras with H.264 compression. When using square
pixel compensation, the camera still transmits, for example 352x240 if the camera is set to 320x240. The
resolution is corrected in the viewer, thus providing no visual, storage, or bandwidth benefits.
4.5.5. IntelligentVideo Database Upgrade Utility

The IntelligentVideo Database Upgrade Utility is used to update IntelligentVideo event configurations to
OnGuard 2009. This utility is found in the Digital Video folder on the Supplemental Materials disc, and
should be run on the OnGuard database server as a final upgrade step.
Note: Prior to running this utility, make a backup of the IVS.XML file located on the IntelligentVideo
Server at /Documents and Settings/All Users/Application Data/Lenel/LNVSuite/IVS.XML.
4.5.6. IntelligentVideo
Events Allow Region of Interest that Extends Past the
Image Boundaries
The user interface allows a region of interest to be configured that extends outside of the image area with
the Object Crosses a Region and People Counting events. This configuration is not supported and may
cause the event not to function properly.
4.5.7. Audio Limitations

 Cannot export video from MPEG4 cameras with audio to ASF format (OG-16919)
 Live video from the AXIS 210A MPEG4 with audio enabled appears to be in time-lapse mode
(OG-16665)
 There is a two second or greater delay in recording audio in MPEG4 (OG-16666)
4.5.8. Single Sign-on Not Supported with VideoViewer (Browser-based Client) and
Video over HTTP (OG-18129)
Single sign-on is not supported with video over HTTP. To work around this issue, hold the <Shift> key and
manually log in to VideoViewer (Browser-based client). This also affects the Area Access Manager
(Browser-based client) if viewing video.
4.5.9. Gaps
in Recorded Video when Saving Embedded Event Configuration to
Camera (OG-17880)
Saving embedded analytics configuration changes to an LCi-100-dx camera may sometimes result in
several seconds of unrecorded video for the channel. In rare instances this may result briefly in a
Communication Lost alarm for the camera channel.
4.5.10. NAS Compatibility

Network Attached Storage (NAS) devices are supported by LNVR. Not all devices work the same. As with
any storage device responsible for recording continuous streams of data, the continuous uninterrupted
read/write rates for the unit must be in line with the expected incoming/outgoing data streams.
4.5.11.Device Discovery Console Cannot Find Lenel Camera if Adapter has IPv6
Address (OG-15951)
Lenel cameras cannot be discovered if both IPV4 and IPV6 addresses are selected for an interface. The
IPv6 address must be removed for the Lenel cameras to be discovered.
4.5.12. Device Discovery Console Cannot Find Lenel Cameras on Windows Vista
(OG-15991)
Lenel cameras with the latest firmware cannot be detected by the Device Discovery Console on systems
running Windows Vista. The Device Discovery Console must be run under the Administrator account in
order to discover the Lenel cameras. To run the application as administrator, right-click the application file
and select Run as administrator.
4.5.13. Panasonic Camera Model Numbers in the Device Discovery Console

(OG-17442)
Some Panasonic cameras are displayed by their series number rather than their model number in the Device
Discovery Console. These cameras will not display their camera model numbers, but instead they display
the series of the camera. For example, the Panasonic NS954 is part of the WV-NS950 series and would be
displayed as a Panasonic NS950. For a list of Panasonic camera display names, refer to the Device
Discovery Console User Guide.
4.5.14. Panasonic NW474 Does Not Support Compression Changes (OG-17927)

The Panasonic NW474 does not support changing the Compression value on the Digital Video > Video
sub-tab in System Administration. This field has been disabled due to communication issues between the
software and the camera.
4.5.15.False Motion Detection Alarms from Lenel ICT230 Located in a Dark

Room (OG-17771)
There is a known issue with the Lenel ICT230 cameras (firmware version 3.0) generating false motion
detection alarms when they are located in a dark room.
4.5.16. Limited Support for IQEye Cameras with Device Discovery Console
The IQEye cameras have limited functionality with the Device Discovery Console:
 Reboot command not supported
 Check default password command not supported
 Get version command not supported, however version number is populated during initial scan
4.5.17. Double Video on Alarm May Not Be Displayed in Pairs

The default behavior with this feature is to launch recorded and live video in matrix mode. Additional
configuration may be necessary if multiple cameras are linked in a video event to display each camera
channel as a pair of video cells (recorded and live). For more information, refer to the Digital Video
Software User Guide.
4.5.18. Double Video on Alarm with LDVR

For customers using LDVR (non-hybrid systems only), the PauseOnDoubleVideoOnAlarm setting in
the ACS.INI file must be set to 0 on all client computers and channel pre-roll values need to be set to 15 or
more seconds in order to avoid black screen issues and video not available error messages when recorded
video is played back as part of double video on alarm feature. The amount of pre-roll required depends on
the video resolution and bit rate that is used. The larger the size and frequency of the frames, the smaller
pre-roll time can be configured.
4.5.19. Double Video with Time-lapse Limitation

When using the Double Video on Alarm feature, the time lapse setting must have the same value as the
AlarmDurationMax value, otherwise there may be black video.
4.5.20. Serial and USB Joysticks Limited to First Application Used

Serial joysticks such as the Panasonic 605 can only be used by one application. Typically the first
application (browser-based VideoViewer or Alarm Monitoring) running will scan the ports and attempt to
connect to a joystick. If the port is occupied (typically by an application that is connected and working with
the port) the port will be skipped from the scan, so the second application will not find the joystick.
USB joysticks (such as the AXIS 295) will work fine with the same user trying to use the joystick from
different applications. The only known limitation for the USB joysticks is that when a different user on the
same computer is trying to use the joystick from a different application it will not work.
4.5.21. Buffering Streaming Video is Disabled by Default

The Buffering Streaming Video feature is now disabled by default and will also be disabled after an
upgrade. For more information about buffering, refer to the Video Monitoring chapter of the Digital Video
Software User Guide.
4.5.22. Buffering Streaming Video with Audio Causes Lag in Timestamp

When the Buffering Streaming Video feature is activated and the video stream contains audio, the
timestamp that is presented by default lags by a few seconds and the lag gradually increases. This has no
effect with the video presented which is in the current live time. A workaround is to click the arrow to get to
the latest minute of the buffering.
4.5.23. Streaming Video Server Not Supported with H.264 Video Source
The H.264 camera codec is not supported with the BARCO/Streaming Video Server integration.
4.5.24. Reset to Defaults Needed for Upgraded RTP Cameras (OG-18167)

LNVR cameras will display incorrect RTP settings after upgrading to OnGuard 2009. After the upgrade is
complete, click the [Reset to Defaults] button on the Camera > RTP sub-tab to reset to the default values.
4.5.25.Video Artifacts with RTP over UDP with Some Bitrate/Resolution

Combinations (OG-18053)
When using cameras with RTP over UDP, artifacts may occur in the final image. This is due to the fact that
UDP is a transmission without acknowledgement protocol and could have loss of packets during
transmission in busy networks. This becomes more obvious when the video is bigger (for example, in the
case of transmission of larger bitrates and resolutions). RTP over TCP/IP or RTP over RTSP over HTTP
may be a better option with cameras that support them because they are more reliable and do not present
this issue.
4.5.26. Joystick Control Difficult Due to Delays in Video (OG-15077)
PTZ may appear slow due to buffering that is included to allow better image quality. For customers that
require better PTZ performance, a workaround exists that includes setting audio to off. The workaround is
to update the registry [HKEY_CURRENT_USER\Software\Lenel\Lnr]"LiveVideoBuffer" -> DWORD.
This value, when set to 0, will speed up the live viewing for both MJPEG and MPEG4 cameras but
introduces audio issues which could not be avoided for this release.
Important: Modifying the registry could cause irreversible damage to your Windows operating
system; be sure to back up the registry before making any changes. Follow the instructions located at:
http://support.microsoft.com/kb/322756.
4.5.27. Background PTZ Tour Interruption May Not Succeed

If a background PTZ tour is interrupted by the user that started it, the tour may fail to stop and control may
not become available to the user.
4.5.28. PTZ Tour Server Does Not Run on Channel in Failover (OG-17970)
The PTZ Tour Server does not work when a channel is in failover mode. The PTZ Tour Server can be
configured while in failover mode, but will not run until the primary video recorder has been restored.
4.5.29.LNVR with Oracle Express: Security Utility Must be Run Manually After
Configuration is Complete
The installation of LNVR with an Oracle Express database requires a reboot once the firmware is installed,
and configuration must be completed after the system reboots. The Security Utility runs prior to the reboot,
however not all of the items necessary are completed at that time. After configuration is complete, the
Security Utility must be run again.
4.5.30. Video May Freeze When Failover Occurs (OG-15743)

When an LNVR enters failover mode, the video playing on any client may stop or go into a small 1 second
loop. Closing the video and reopening it will display live video.
4.5.31. Error When Switching to Live Video after Viewing Recorded from
Archive Server (OG-17598)
When video is opened using the Launch recorded video from > Archive Server right-click menu item in
Alarm Monitoring, the communication path becomes locked to the Archive Server and the player cannot be
switched to live video. If you want to view live video, close the Video Player and launch live video.
4.5.32. Windows Vista Server: LDVR Recorders Cannot be Automatically

Discovered
When configuring video recorders on a Windows Vista server, LDVR recorders can not be automatically
discovered in System Administration.
4.5.33. Windows Vista Client: LNVR Failover Issue

When monitoring video on a Windows Vista client, LNVR cameras may experience issues connecting to a
failover recorder. This issue is caused because ICMP protocol is blocked for the recorder. To workaround
this issue, enable Internet Control Message Protocol (ICMP) in Windows Vista:
1. Open Control Panel > Administrative Tools > Windows Firewall with Advanced Security.
2. Select Inbound Rules in the tree on the left.
3. Click New Rule in the actions window on the right.
4. The Rule Type window is displayed, select Custom and click [Next].
5. The Program window is displayed. Select All programs and click [Next].
6. The Protocol and Ports window is displayed. Set Protocol type to ‘ICMPv4’ and click [Next].
7. The Scope window is displayed, click [Next].
8. The Action window is displayed. Select Allow the connection and click [Next].
9. The Profile window is displayed. Select Domain, Private and Public. Click [Next].
10. The Name window is displayed. Enter a descriptive name and click [Finish].
4.5.34. Windows Server 2008: Enabling Video Export (OG-17701)

To allow Windows Server 2008 to export video, complete the following steps:
1. Right-click My Computer and select Manage.
2. Click on Features in the navigation tree.
3. Click the Add Features link.
4. Select the Desktop Experience check box and click [Install].
Note: This installation requires a reboot. After Desktop Experience has been installed, export to ASF
will work successfully.
4.5.35. PAL Cameras may not have Frame Rates Color-coded to Indicate
Supported Frame Rates
Regions using PAL and incorporating the following list of cameras may not have the frame rate displayed
in green/red to indicate supported frame rates:
 Axis MPEG4 (only): 213 PTZ
 Axis MJPEG (only): 240Q
 Axis MJPEG and MPEG4: 214 PTZ, 215 PTZ, 241Q, 241QA, 241S, 241SA, 243Q , 243SA,
247S
 Lenel: All cameras
 Panasonic MJPEG (only): WV-NS202 PTZ, WV-NW474
 Panasonic MJPEG and MPEG4: WV-NS202a PTZ
 Pixord (MJPEG and MPEG4)
 Sony MJPEG (only): RZ-30, CS3
 Sony MJPEG and MPEG4: DF-40, DF-70, P5, RZ-25, Z20
 Sony MJPEG, MPEG4, H264: CS50, DF-50, DF-80, RX-550, RZ-50
4.5.36. LNVR Motion Detection Not Supported with IQinVision Cameras (OG-
16501)
IQinVision cameras should not be configured with LNVR motion detection. This configuration is not
supported and may cause the system to become unresponsive. To work around this issue, utilize the camera
motion detection functionality and configure the camera to send motion alarms to the OnGuard system.
4.6. Enterprise
4.6.1. Update to Full Downloads Without Images
When performing a full download without images, images at the Regional Servers now remain intact. It is
no longer necessary to manually move the images to the Regional Servers after a full download without
images. OnGuard will also identify images that have changed and generate the necessary transactions for
processing these photos in the background.
4.6.2. Changing Badge IDs on Mobile Badging and Enterprise Systems (OG-
15107)
This release resolves an issue changing badge IDs on Mobile Badging stations and Enterprise systems
when the system is configured for manual badge ID entry. To edit a badge ID:
 The user must have permission to edit badges.
 Badge IDs must be configured for manual entry.
 If the badge has been printed, the user must have permission to edit the badge after printing.
4.6.3. Badge Template Transaction Failed with Violation of Primary Key Error
(OG-17915)
A violation of primary key error occurs if you create a badge template and assign a cardholder to that
template before the template has had a chance to replicate. If the creation of the template is replicated
before the cardholder is assigned, this problem will not be encountered. To work around this error after it
has occurred, purge the transaction that is failing. Once the failed transaction has been purged, other
transactions should be processed successfully and the Badge table will be properly synchronized.
Note: Purging failed transactions will typically result in an unsynchronized system and is not recommended
under other circumstances. This action is specific to a particular processing error and has been tested by
Lenel.
4.6.4. Anomalies Warning During Database Setup for Indexes that Should Not be
Present on Enterprise and Distributed ID Masters
New and upgraded systems that are converted to Enterprise or Distributed ID Masters do not properly have
their indexes cleaned up. Database Setup may report these as anomalies while analyzing your database.
These can be safely cleaned up during the database setup process. In the event that they are not cleaned up
at this point, they will be cleaned up the first time Replicator replicates to the Master Server.
4.6.5. Global I/O Restrictions

Global I/O linkages will not work between two Enterprise regions. Global I/O configurations must use the
same Linkage Server.
4.6.6. Duplicate Dynamic Segment Names After Upgrade

It is possible to have a Regional Server and a Master Server in an Enterprise system with the same node
name if they were previously hosted on the same system. This may result in duplicate segment names being
created during an upgrade. To address this, a 1 will be appended to one of the segment names. These
system segments can be renamed by updating the node name to be unique.
4.6.7. Pre-existing User-specific Layouts Not Replicated to Enterprise Master

Pre-existing user-specific video layouts are not replicated up to the Master Server when user replication is
enabled. This only affects pre-existing layouts. New layouts will be properly replicated. To work around
this limitation, open each existing layout and save it again with the same name.
4.6.8. Directory Accounts Link to Cardholder or User Not Replicated to Enterprise

Master (OG-18199)
If a directory is deleted from the Enterprise Master and those changes are not replicated down to the
Regional Server, any changes linking a directory account from that directory to a cardholder or user will
not replicate up to the Enterprise Master. The transaction will fail with a referential integrity error in the
error log. To address this, unlink the directory account from the cardholder or user and replicate
transactions from the Enterprise Master down to the Regional Server.
4.6.9. Referential Integrity Error when Saving Camera Layouts

If a camera layout is saved with cameras added from another Regional Server via the Camera Lookup
feature, a Referential Integrity error may occur. To save a layout that generates the error, remove the
cameras located on other Regional Servers from the layout prior to saving.
4.6.10. IntelligentVideo Applications Not Available on Enterprise Master when

Configured on a Child Region
There is a known issue with the replication of IntelligentVideo Applications to the Master Server. This issue
will be addressed in a future release.
4.6.11. IntelligentVideo Applications Not Supported with IntelligentVideo

Application Server Located on a Different Region
In Enterprise systems, IntelligentVideo Applications should not be configured for IntelligentVideo
Application Servers that are located on other Regional Servers. This is not a supported configuration, and
the IntelligentVideo Application will not function properly.
5. Limitations
5.1. General
5.1.1. Installation May Appear Not to Start on Slower Systems
After the Preparing to Install window closes, there may be a pause before the installation appears to
continue on slower systems. During this time the mouse pointer may not indicate an hourglass and it may
appear that the installation has stopped. The installation will continue after a few moments.
5.1.2. Double-click Generates an Error in the Online Help

A rapid double-click on a graphic within the online help produces an error. This is a known limitation
within HTML help.
5.1.3. System Settings Do Not Apply to OnGuard Applications Until Restarted

System settings changes, such as font sizes, theme colors, and new printers are not reflected in running
OnGuard applications until they are restarted.
5.1.4. “Names” and “User Names” for Directory Accounts Linked to Cardholders
are not Resolved
After linking a cardholder to a directory, the values in the Name and User Name columns may be displayed
as a long string of numbers. The SID is displayed when the system cannot establish the name of the user
based on the SID. This issue is related to the trust between users, domains, computers, sub-networks.
5.2. Access Control

5.2.1. Inaccurate Search Results Count in Browser-based Area Access Manager
On a system with cardholder and/or badge type segmentation enabled, the results count for searches
displayed in the browser-based Area Access Manager can be incorrect. The workaround is to use the
desktop client Area Access Manager.
5.2.2. IIS
User Account Must Have Access to Temp Folder for Area Access
Manager Browser-based Client Reports (OG-18175)
A “Load report failed from C:\WINDOWS\Temp” error may occur when running reports from the Area
Access Manager Browser-based Client. To successfully run reports, the IIS_WPG (in Windows Server
2003) or IIS_IUSRS (in Windows Server 2008) account must have read/write access to the C:\
WINDOWS\Temp folder.
5.2.3. Additional Keys During Biometric Verification Will be Ignored

During a biometric verification, additional keys pressed at an associated keypad will be ignored and will
not start a new access attempt.
5.3. Identity Management

5.3.1. IE SmartTOUCH Sector Allocation Limitation
The IE SmartTOUCH only works with first 1K (Sector 0 to 15) of a 4K MIFARE card. Any data encoded
in sector 17 or above will not be read by the reader.
5.3.2. Magicard Prima M Does Not Include Parity for Track 1 (OG-18107)
The Magicard Prima M, print driver 3.0.7.0, F/W C02/29/57 printer does not include parity in its bit count
for track 1, and its default setting is 7-bit sign. On most other printer drivers, 7-bit as a default would be
correct. However, to encode standard magnetic track data (IATA) to track 1 on the Prima M, the print
driver must be set to 6-bit sign.
5.3.3. Field Type Must be Text for Phone Numbers

User-defined phone number fields must have a field type of text, not numeric. Phone numbers entered as
numeric fields may have their values truncated.
5.3.4. HID Edge PIN Limitation (OG-16039)

HID VertX/Edge firmware has an 8-digit PIN limitation. OnGuard allows a PIN of up to 9 digits. When
used with Edge readers, the last digit of any 9-digit PIN will be ignored, and the first 8 digits will be
matched.
The workaround for this issue is to configure the system to truncate the PIN to 8 digits. This configuration
will grant or deny access based on the validation of the first 8 digits entered by the user.
5.4. Digital Video

5.4.1. Recorded Video Cannot be Exported from a Failover Video Recorder
Video that is recorded to a failover video recorder cannot be exported.
5.4.2. MPEG4 with Axis Cameras

 Camera time-stamps are not available with Axis MPEG4 cameras.
 Due to the way the Axis cameras communicate, the Inputs and Outputs are not as reliable in
MPEG4 as they are with MJPEG.
 Lenel does not recommend Capture Video only on Event with MPEG4, as it takes several
seconds to connect to the camera and begin recording.
 When using MPEG4 and moving in and out of Time-Lapse recording, there is a one-frame
loss. Therefore, Pre-roll should be set at least one second greater than you need. The higher
the frame rate, the less noticeable this one-frame loss is. Lenel also recommends using a high
frame rate with MPEG4 and Time-Lapse Recording.
 When using an Axis Video Server (241Q, 241S, 241QA, 241SA) you will occasionally
experience a problem where the video will stop recording when you change the frame
resolution. This can be fixed by opening a live video stream and letting it run for several
seconds, or restarting the LNVR services.
 Video Acceleration in the Video Player MUST be set to None in order to insure a clear video
picture.
 Axis cameras may experience a ghosting effect at higher Group of Video Object Planes
(GOV) lengths. This issue is resolved with Axis firmware version 4.40, which is available for
download on the Axis Web site. If the firmware cannot be upgraded, the GOV length should
be set to 30 or less frames.
5.4.3. Lumenera Cameras

 Starting video search may cause computer CPU to enter constant loop due to high resolution
of video. Megapixel video searches that are lengthy may cause the system to stop responding
and require a reboot. Results will vary by computer. Short searches are recommended to avoid
this issue.
 Setting a camera to 1024 x 768 and compression of 10 or less may result in 0 frames being
streamed.
 Lumenera 375 camera image may change from normal to dark if a large dark object blocks or
is placed in close proximity to the lens and covers more than 60% of the field of view for
more than 2 seconds.
Lumenera Technical Support can be reached at +1 613-736-4077 (press 2 from the auto-attendant) between
the hours of 9:00 a.m. to 5:30 p.m. EST or via e-mail at support@lumenera.com.
5.4.4. White Balance Setting Must be Configured from Panasonic Camera Web
Page
The White Balance for Panasonic cameras cannot be updated from the OnGuard user interface and must be
adjusted manually from the camera Web page.
5.4.5. Connectionto Panasonic i-Pro Network Cameras in MPEG4 May Fail After
Multiple Connections are Made (OG-17488)
Note: For more information about Panasonic i-Pro Network Cameras with MPEG4, refer to the Lenel
Knowledge Base.
When multiple connections are made to Panasonic i-Pro network cameras, some of the connections may
fail. This may occur during specific conditions when LNVR services, or network connectivity, are lost and
then restarted, and/or when Lenel LNVR clients simultaneously attempt/make direct connections to
individual cameras. This is fundamentally a camera limitation caused by a limit to the number of
concurrent sessions supported by the cameras. The problem is experienced only in very specific
circumstances. Once a camera is disconnected, the session/UID may not be properly terminated, and is not
automatically released until a timeout has been reached. The default time out for unresponsive
sessions/UIDs with i-Pro network cameras is two (2) minutes. To resolve this issue, close all connections
to the camera and wait two (2) minutes before reconnecting.
5.4.6. Some
Panasonic WV-NP1000/1004 Camera Settings Must Be Applied
Manually
Panasonic WV-NP1000/1004 cameras have settings that cannot be applied by OnGuard. These settings can
be applied to achieve either the best quality or the best frames per second performance. The following
settings modify either of these: "Scan mode" and "Maximum resolution" (depending on the Scan mode
either 1280x960 or 960x720.) When the scan mode is set to Partial Scanning the user can get higher frame
rates but lower quality. At Full Scanning the user gets better quality but lower frames per second. The
maximum resolution needs to be turned off when the user is trying to access lower resolutions from the
LNVR.
5.4.7. Lumenera LI045C Resolution is Limited

The Lumenera LI045C camera has a limitation which only allows a resolution of 720x480 for NTSC and
720x576 for PAL.
5.4.8. Mobotix Cameras Require a Longer Direct Connect Default Timeout (OG-
15569)
Mobotix cameras will not work properly with Direct Connect at default timeout. The default 5 second
timeout will not work since the camera may take longer to start. Set the Direct connect to something longer,
such as 10 seconds.
5.4.9. Frame Rate Drops With AXIS 241Q When the Camera Web Page is Opened
The frame rate drops when viewing video from an AXIS 241Q in OnGuard when the camera Web page is
opened. This is a known third-party limitation with the video server. Camera Web pages should be closed
when viewing video.
5.4.10. AXIS 240x Video Servers Do Not Report an Error When Offline
The AXIS 240x video servers do not support the detection of the video channel interface. These models
will not support the Video Signal Offline feature found in the latest LNVR servers.
5.4.11. Inputs Not Supported with HIKVision Cameras (OG-18062)

Inputs are not supported with HIKVision cameras in this release.
5.4.12. Non-numeric Passwords Not Supported by HIKVision Cameras (OG-

18028)
Non-numeric passwords are not supported for HIKVision cameras. It is possible to successfully change the
password for the camera using the Security tab in System Administration to a non-numeric password. If this
occurs, the user will be locked out of the camera Web page.
5.4.13. Video Appears Washed-out After Adjusting Resolution on HIKVision DS-
2CD852F Camera (OG-18054)
Adjusting the resolution in the HIKVision DS-2CD852F camera causes the video to appear washed-out. To
return the video image to normal after changing the resolution, open the Camera > Video Sensor sub-tab,
click [Reset to Defaults], then click [Apply].
5.4.14. HIKVision/Lenel PCI Boards May Require Manual Driver Installation

(OG-17395)
If HIKVision/Lenel PCI boards are added to an existing LNVR, the drivers for the boards may need to be
installed manually.
5.4.15. Toshiba Cameras Do Not Support Maximum Frame Rate With Maximum
Resolution
Toshiba cameras do not support the ability to obtain the maximum frame rate with the maximum resolution.
This is a third-party camera limitation of Toshiba cameras. The OnGuard system will attempt to obtain the
maximum frames out of the camera but some configurations might not achieve the desired frame rate
because the camera may provide less.
5.4.16. Cannot Limit Frame Rate on Bosch Cameras from the Camera Web Page
The Web page for Bosch cameras offers a Performance Option to limit the frame rate. This option does not
affect the frame rate in OnGuard.
5.4.17. Shadow Effect with Bosch Dinion Camera

A shadow effect on the Bosch Dinion Camera can be removed by enabling the Dynamic Noise Reduction
setting on the Camera Settings > Camera Profile > Enhance section of the camera Web page.
5.4.18. Bosch 8008 Camera

There is a three (3) second delay before video is displayed from a Bosch 8008 camera. This delay is seen
when launching video from the Bosch 8008 and when switching from one 8008 channel to another.
5.4.19. Upgrading H.264 Sony Camera Firmware May Require a Full Download
Changes to Sony firmware affect the H.264 protocol. The LNVR supports both methods, but when
upgrading cameras to the newest firmware you may need to perform a full download for the LNVR to
communicate properly with the camera.
5.4.20. Device Camera Link and Capture Video on Event Delay

When using a Device Camera link, there may be a small lag time of 1 to 2 seconds before the event actually
triggers the event on the camera. This delay should be taken into account when setting pre-roll on a camera.
5.4.21. Offline LNVR May Cause a Delay in Alarm Reporting

When an LNVR is offline, there may be a delay before alarms are received by the Communication Server.
5.4.22. Go To PTZ Preset Feature Not Supported when LNVR is Offline

The Go To Preset action cannot be executed when there is a direct connection to the camera. The LNVR
must be online for this action to be successful.
5.4.23. Black Video Cells in Remote Monitor

If a video cell appears black in Remote Monitor, press stop and then play. If this does not resolve the issue,
right-click the Remote Monitor and select Download Database.
5.4.24. Selecting a Video Cell in Browser-based VideoViewer Automatically

Locks PTZ
When a user selects a cell in browser-based VideoViewer, PTZ control is assumed and PTZ is locked for
other users. To release control of the PTZ, select the lock/unlock button or wait for the timeout.
5.4.25. In-Camera Storage Feature Considerations

 Users should refrain from viewing video during times that the LNVR is downloading video
from the camera. The In-Camera Storage timezone should not be set to Always.
 Cameras configured with In-Camera Storage appear offline in Alarm Monitoring.
Communication Loss/Restored alarms are generated each time video is launched for the
camera. As a workaround, users can configure Camera I/O or Camera Motion Detection.
 Users should not use the filename prefix option on the camera Web page. This setting will
“hide” the files from the LNVR download service. The filename prefix should be left blank.
 If the LNVR is downloading from the camera users may experience delays in stopping LNVR
services.
 Extra memory in the camera can cause it to stop responding. If this occurs, the drive may need
to be formatted.
5.4.26. ASF Files Not Supported in Alarm Monitoring

Advanced Systems Format (ASF) files are not compatible with Alarm Monitoring. If an ASF file is loaded,
the date will appear incorrect. ASF files should be opened with Windows Media Player.
5.4.27. Exported LDVR Files Not Automatically Associated with VideoViewer

VideoViewer must be opened once before exported LDVR files can be opened with a mouse double-click.
5.4.28. Video Export from Browser-based VideoViewer in Windows Vista

When exporting video in Windows Vista, the Windows user must have write access to the location that the
video is saved. The default save location is the Desktop.
5.4.29. Setting the Color Mask with Grayness in Object Detection

The Grayness slider for the color mask in the Object Detection engine is not guaranteed to smoothly change
the color mask. Configure color mask as much as possible using the color palette tool and the Hue slider.
5.4.30. Intel Decoder Must be Installed for Playback with the Panasonic 474 (6x-
8916)
The Intel Decoder is required for playback using the stand-alone video player for the Panasonic 474. Install
the Intel IPP by running Setup.exe from the OnGuard Installation disc in the \Temp\INTEL folder. Copy
the LnrIntlDmo.dll file from the OnGuard disc in the \Common\Lenel\ folder to C:\Program Files\
Common Files\Lenel\ and register the file.
5.4.31. Oracle Errors When Adding Cameras (OG-17708)

Oracle 9i systems should use ODBC Driver 9.2.0.6.5 or later to avoid errors when adding cameras.
Note: There are known issues with Oracle 9i R2 Client 9.2.0.8 with ODBC Driver patch
(p5728282_92080_WINNT). This configuration is not recommended or supported.
6. Copyright and Trademark Notice
Copyright © 2009 Lenel Systems International, Inc. Information in this document is subject to change
without notice. No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Lenel Systems
International, Inc.
The software described in this document is furnished under a license agreement and may only be used in
accordance with the terms of that agreement. Lenel and OnGuard are registered trademarks of Lenel
Systems International, Inc.
Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries. Integral and FlashPoint are
trademarks of Integral Technologies, Inc. Crystal Reports for Windows is a trademark of Crystal Computer
Services, Inc. Oracle is a registered trademark of Oracle Corporation. Other product names mentioned in
this document may be trademarks or registered trademarks of their respective companies and are hereby
acknowledged.

OnGuard 2009 6.3 Release Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OnGuard 2009 6.3 Release Notes

Uploaded by

Copyright:

Available Formats

OnGuard 2009

1.1.1. Full Download Required for Enterprise Systems after Upgrade

1.1.3. Upgrade Requirement for Enterprise Customers Using Visitor Management

2.1. Current Access Control Firmware and Special Application Versions

 LNL-500/1000/2000 ISC Version v3.118

2.2. Current Digital Video Firmware

2.3. Minimum Server System Requirements

2.4. Supported Operating Systems

2.4.2. Windows Server 2003 Standard and Enterprise, Service Pack 2 or R2

2.4.3. Windows Vista with Service Pack 1

2.4.4. Windows Server 2008 with Service Pack 1

2.4.5. Service Packs and Critical Patches

2.5. Security Utility

2.6. Supported Database Systems

2.6.7. Oracle 9i R2 32-bit (9.2.0.8) Server and Client

2.7. Supported System Components

2.8. VMware Platforms

2.9. Supported Third-party Components

2.10. Antivirus Software Applications

 McAfee Virus Scan

 Symantec – Norton Antivirus Corporate Edition

 Trend Micro OfficeScan Corporate Edition version 8.0

2.11. Supported Web Browser

2.12. Supported Terminal Services

2.13. OPC Versions

2.14. SNMP Versions

2.15. Support Pending

2.15.1. High Availability Systems Pending Certification

2.16. End of Life Products

3.1. Access Control

 Onity Template Support

 Blocking Cards are Supported for Onity Integra Locks

 Multiple Operators are Supported for Onity Integra Controllers

 Printers/encoders Supported for Printing or Encoding Onity Badges

3.1.2. Duress Card Formats

3.1.3. Reversed Bit Order Card Formats

3.1.4. Bioscrypt Duress Finger Support

3.1.6. HID Edge Access Level Configuration Enhancement

3.1.7. Support for Lenel-branded HID Edge Readers

3.1.8. Additional Hardware Settings for Encryption

Downstream Encryption Status in Alarm Monitoring

3.1.9. New Schlage Configuration/Demo Tool (CDT)

3.2.2. Advanced Search

3.2.5. Front Desk

3.3. Digital Video

3.3.2. Support for RTP Protocol

3.3.3. LNVR Redundant Failover

3.3.4. Video Quality Enhancement Algorithms

3.3.5. Double Video on Alarm Enhancements

3.3.6. Network Video over HTTP via Proxy

3.3.8. IntelligentVideo Embedded Analytics

3.3.9. Integrated Support for goVision Video Recorders

 Integration with the goVision DS8000 recorder

3.4. High Availability Systems

3.4.2. NEC ExpressCluster Monitoring Service

3.4.3. NEC ExpressCluster Utility

4.1.2. Temporary Files Remain After Installation Has Completed

4.1.3. SQL Server2005 Installation Instructions Moved to Advanced Installation

4.1.4. OracleSystems Need to be Set Up to Use Windows Authentication by

4.1.5. World Time Zone Default Data Updated

4.1.6. Flash Player Removed from Supplemental Materials Disc

4.1.7. Web Application Server Not Recommended with Windows XP or Windows

4.1.8. Browser-based Application Security

4.1.9. Column Heading Tooltips Disabled for Windows XP (OG-12746)