LenelS2

1212 Pittsford-Victor Road

Pittsford, New York 14534
Tel 866.788.5095 Fax 585.248.9185
www.LenelS2.com

OnGuard 8.2 Update 1 Limitations

8.2 Update 1 Purpose

This section contains a list of OnGuard and third-party known limitations for OnGuard 8.2 Update 1, and is intended as a supplement to the
OnGuard 8.2 Limitations.

8.2 Update 1 Area Access Manager (Browser-based Client) Limitations

• In Area Access Manager (Browser-based Client), searching for a cardholder who was assigned an Access Level and is also part
of an Access Level group brings empty results (DE133285, SF-00435): This is a limitation of the API, which currently does not
support this type of search criteria.

8.2 Update 1 System Administration Limitations

• Event routing does not follow the setting in the monitoring zone (DE129337, EE-8702): Monitoring zones will replicate bi-
directionally throughout the entire Enterprise system, but when using Event Routing Groups, these must be created on the region
where they are expected to be used. Event Routing Groups do not replicate.

Limitations for OnGuard 8.2

8.2 Purpose
This section contains a list of OnGuard and third-party known limitations for OnGuard 8.1, and is intended as a supplement to the OnGuard
8.1 Release Notes.

8.2 General Limitations

• SmartID Pro DESFire encoder cannot be added on Windows 11, unless OnGuard is run as Windows Administrator (OG-20141):
In order to use the SmartID Pro DESFire encoder to encode DESFire (TWIC) and GSC (DESFire), OnGuard must be run as Windows
Administrator.
• 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.
• System Settings Do Not Apply to OnGuard Applications Until Restarted: System setting changes, such as font sizes, theme colors,
and new printers are not reflected in running OnGuard applications until they are restarted.
• "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 might show as a long string of numbers. The “long string of numbers” is
called the SID. 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.
• User Is Able to Save a Permission Group Without a Name (DE17123): An empty field for a permission group name will save. After
creating any new System, Cardholder or Monitor permission group, always enter a group name in the field before saving.
• OnGuard NDE wireless Critical Battery not annunciated (DE15924): Alert displays low battery warning but does not identify End
User if the alert is Critical or Low. Users should adjust battery at first signs of battery warning to avoid this issue.

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 1

 OnGuard 8.2 Update 1 Limitations

8.2 Installation and Upgrade Limitations

• OnGuard database cannot be configured on a Turkish Windows server (DE131772): When installing OnGuard on a Turkish
Windows server, the Database Setup step in Setup Assistant fails. The workaround is to install OnGuard on an English Windows
server, or to configure the regional settings on the Turkish server to English.

8.2 Access Control Limitations

LenelS2 Series Access Control Limitations
• Series 3 Boards not working after firmware download (DE39542): This is a third party limitation. In Alarm Monitoring, do not start
firmware download to IO and/or Reader Interface boards while their controller is receiving a firmware download. Before attempting
to downloading firmware to IO and/or Reader Interface boards, wait until the controller is back online and operational with all
downstream boards reporting normally.
• LNL-3300-GCM controller added with incorrect type needs a database download to correct the configuration (DE10656): This
is a known limitation. To update the number of inputs, outputs, or readers after the initial controller definition in System
Administration, the controller needs to be reset and the configuration downloaded.
• Hold time functionality doesn't work with ACU readers (DE10636): This is a limitation of the ACU boards.
• LNL-1300e and LNL-2210: OSDP Device Support (DE8563):
• LNL-1300e (IP Interface) reader port 1 supports (1) one OSDP device only
• LNL-2210 reader port 1 supports (1) one OSDP device only
• LNL-1300e reader board stays offline when dual NIC is connected during failover (DE40129): The LNL-1300e reader board only
connects to a controller via the Primary Network Connection. The LNL-1300e will be offline if the controller has a dual NIC
configuration and fails over to the second NIC.
• Integrated Intrusion LCD Display of Event History Adds Spurious Event for Alarms with Door Set for Entry Delay (OG-15920):
When utilizing the new Intrusion Mask Groups, an alarm caused by a Door Status event set for "Trigger" point mode will result in an
extra event being displayed in the LCD keypad event history. The extra event will be labeled "256 TYPE ERROR" and have the same
time as the door event, and can be ignored. This issue will be addressed in a future firmware version.
• OSDP Reader Might Have Incorrect LED Display (OG-17529): If power is lost to an Open Supervised Device Protocol (OSDP) reader,
but power to the LenelS2 reader interface is maintained, the LED display pattern might be incorrect until an access activity takes
place.
• Door Strike Time (OG-19333): For LNL access panels, the Door Strike time is about ½-second shorter than what you configure it for.
• Downstream Encryption Key Download Will Fail if any I/O Modules Are Offline (OG-23268): 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. If a board is known to be offline, delete it from the system to download keys to the other boards.
• Promoting an LNL-500/1000/2000 access panel to the LNL-2210/LNL-X2210: In order to promote an access panel to the LNL-
X2210, the panel’s Primary Connection must be configured as a LAN type. In addition, the panel’s existing devices need to conform
with one of the configurations supported by the LNL-X2210:
• Up to eight downstream RS-485 devices (readers modules and alarm panels)
• Up to 17 readers (using eight dual reader interface modules and one on-board reader)
• LNL-X2210: Changing between a downstream and non-downstream configuration might require a full download to the panel:
Changing the LNL-X2210 configuration between downstream and non-downstream readers might require a database download to
the panel. Specifically, downloads are required when the first downstream device is added to the LNL-2210 or the only downstream
device is deleted from the panel.
• LNL-X2210: Other on-board reader support limitations:
• LNL-X2210 on-board readers do not support Aux Inputs
• LNL-X2210 on-board reader #1 supports Aux Outputs Output1 controls only
• LNL-X2210 on-board reader #2 does not support the independent Door Contact/REX controls; it is expected to be linked to
reader #1, where Door Contact/REX Controls are defined.
• Limited OSDP Reader File Transfer: OnGuard can have an unrestricted number of files that can be stored for OSDP file transfer in
the database. Then up to five of those files can be loaded into any X-Series controller for transfer to readers managed by that
controller.
• LenelS2 Series access panels do not support configuration of holidays longer than 127 days (DE131401, EE-9910): LenelS2
Series access panels do not support configuration of holidays longer than 127 days even though OnGuard System Administration
allows holidays up to 255 days long to be configured. This is not possible in OnGuard due to a limitation in the LenelS2 Series access

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 2

 OnGuard 8.2 Update 1 Limitations

panels. To configure holidays spanning more than 127 days, add multiple holidays as needed with each holiday in the range of 0-127
days.
• Primary-Secondary OSDP biometric readers connected to the LNL-1324Ee (DE127753): Connecting OSDP biometric readers to
an LNL-1324e in a primray-secondary configuration is not supported.
• OSDP File Transfer – no synchronization when removed through the web page (DE40628): An OSDP file downloaded or
transferred using the option in Alarm Monitoring, cannot be deleted from OnGuard through the web page for the controller or reader
interface board. If the file is deleted using the web page, download/transfer it again in Alarm Monitoring (Select yes to the
“overwrite” prompt) and then delete it in Alarm Monitoring.

Third-party Access Control Limitations

• A yellow cross-mark is displayed on SimonsVoss locks when the locks are idle (DE131113): In Alarm Monitoring, SimonsVoss
locks may go offline after being left idle to save power when the lock batteries are low.
• Elevator Dispatching Systems Do Not Support Precision Access Levels (OG-22797): Elevator dispatching systems do not support
precision access levels.
• Guardall Px device translator filters out the Set/Unset alarms from being reported to OnGuard (OG-25249).
• 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.
• Galaxy Ethernet Module Not Supported for Dimension Panels: Galaxy Ethernet module is not supported for Dimension panels.
• Bosch B5512 displays Offboard Relay in Device Column (Alarm Monitoring) when the Onboard Relay is Set/Reset by user
(DE126274): This is a BOSCH protocol Limitation. We recommend avoid using outputs 1-3. Only use relay 4 and higher for event/
relay mapping and manual control.
• Nisca PR5350 badge printer generates "Unable to end page" error (DE130290): In the System Administration > Badge Type
form, if the Back layout drop-down is left blank and the badge is sent to a Nisca PR5350 printer, the printer does not move the card
to the encoding station, and the badge printing error "Unable to end page" is shown. To correct this issue, make a selection in the
Back layout drop-down.

8.2 Advisor Advanced Limitations

• When using Advisor Advanced intrusion panels, a maximum of 25 intrusion panels per communication server are allowed, with a
maximum of 2000 users or cardholders per panel.
• When the intrusion panel is in either the Armed or Fault state, no panel configuration is possible. There are numerous Fault states,
including "Alarm."
• OnGuard cannot reliably send data to the intrusion panel while an Installer or a user is logged into the panel using a keypad.
OnGuard cannot send user configuration during that time, and OnGuard might lose its connection to the intrusion panel or the
panel’s status might change between online and offline. In that case, reconnect OnGuard to the intrusion panel manually.
• Events are not sent from an intrusion panel during configuration. After configuration data has downloaded, the waiting events are
sent.
• The intrusion panel has several different event logs. Some events are stored in more than one log. The driver reads all panel
logs, resulting in what appears to be duplicate events in Alarm Monitoring.
• If the connection to the intrusion panel is broken during the database download, some data might not make it to the panel, resulting
in a Panel Options Mismatch event. To correct this event, perform another database download to the panel and/or refresh (upload)
the panel to the OnGuard software.
• The intrusion panels log in again after each configuration command, and also after issuing the Refresh Device Tree command in
Alarm Monitoring. After the command is sent, wait until the Remove Program Begin event is shown in Alarm Monitoring before
issuing the next command.
• If a user enters several incorrect PINs in panel options, the intrusion panel will refuse the connection for some time. If the next PIN
attempts are also incorrect, the length of time that the panel refuses connection increases.
• Linkage issue when using Advisor Advanced DGP output. When using a DGP output, the activation status to build a global I/O that
changes the reader mode (for example, to Unlocked) provides good output, but the linkage is not executed. The same action with an
output located on the Advisor Advanced Board functions correctly. This functionality is not supported by either Advisor Advanced or
the OnGuard software.

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 3

 OnGuard 8.2 Update 1 Limitations

8.2 Browser-based Client Application Limitations

• Unable to Launch OnGuard Credentials for a segmented User (DE103178): After changing segmentation in OnGuard, the
OpenAccess service must be restarted.
• OnGuard Credentials user without Modify Cardholder permissions cannot add cardholder photos (DE131695): If an OnGuard
Credentials user has Add permissions but does not have Modify permissions, then the user cannot add cardholder photos. The user
must have the Cardholder Permission Group > Cardholders > Cardholder "Modify" permission to add cardholder badge photos.
• Mobile device orientation and resolution limitations: OnGuard browser-based clients and modules are designed to function on
various device resolutions through responsive interface architecture. While portrait mode is supported on most devices, scrolling
and other interactions may be required to view and interact with all elements in a given interface. For best results, view in landscape
mode for phone- and tablet-sized devices, with a recommended resolution greater than 1024 pixel width. The OnGuard browser-
based clients and modules may not display as expected on smaller tablets and phones with lower resolutions.

8.2 Database Limitations

• Performance issues occur in OnGuard when using Oracle 12c (DE14905): Due to changes in Oracle 12c that are beyond LenelS2’s
control, customers may experience delays in the user interface, based on database response times, that would affect their utilization
of the OnGuard software. LenelS2 submitted a ticket to Oracle about this issue, and Oracle recommended a patch (WINDOWS DB
BUNDLE PATCH 12.1.0.2.160719) for all installations of OnGuard with Oracle 12c. LenelS2 recommends that all OnGuard systems
with Oracle databases keep up-to-date on patches released by Oracle. Oracle has informed LenelS2 that they consider the
performance issue closed. If performance issues persist, contact Oracle support.

8.2 DataConduIT Limitations

• DataConduIT's Lnl_AlarmOutput and Lnl_AlarmInput methods not supported on elevator hardware (OG-25694): In
DataConduIT, all methods for the Lnl_AlarmInput and Lnl_AlarmOutput classes are not supported on LenelS2 alarm panels when
those panels are designated as elevator hardware.
• DataConduIT option installs during a custom installation, but the service fails to start and generates a WMI error
(DE132252): To resolve this issue, select the DataConduIT and OpenAccess options when performing a custom installation.

8.2 Digital Video Limitations

The following pages describe the digital video limitations for OnGuard 8.1.

8.2 General System Limitations

• (TVN71 only) Compared to the recorder’s web page, additional Bit Rate values are present in OnGuard (DE17104): This is a
limitation of the SDK which provides additional values to OnGuard that are not on the recorder web page.
• Error message pops when launching .asf format video exported from OnGuard with high resolution in Windows Media Player
(DE129503): When playing a Windows Media Format (.asf) file exported from OnGuard, the following error message might be
displayed if the source camera was configured for very high resolution: "Windows Media Player cannot play the file. The Player might
not support the file type or might not support the codec that was used to compress the file." This is a third-party camera limitation of
Windows Media Player.
• Offline LenelS2 NVR Might Cause a Delay in Alarm Reporting: When a LenelS2 NVR is offline, there might be a delay before alarms
are received by the Communication Server.
• There is no warning message to indicate that a camera is offline when attempting updating storage statistics in System
Administration (DE14082): Reconcile with the status in Alarm Monitoring before attempting to update statistics.
• Sub-stream is not online after checking “Add a live sub-stream” (DE15601): After adding a camera and selecting the “Add a live
sub-stream” option in System Administration, the sub-stream has a yellow X and video cannot be viewed for that sub-stream in
Alarm Monitoring. Re-enter the password for the sub-stream in System Administration.
• De-warped views of 360-degree cameras (DE7368): This feature is currently not supported in Web VideoViewer.
• Event Locking (DE14333): Video event locking settings and controls are enabled but ignored for recorders that do not support the
feature including some OAAP recorders. This is a known issue that will be addressed in a future release.

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 4

 OnGuard 8.2 Update 1 Limitations

8.2 Networking and Storage Limitations

• NAS Compatibility (OG-23272): Network Attached Storage (NAS) devices are supported by LenelS2 NVR. 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.

8.2 PTZ Control Limitations

• Selecting a Video Cell in Browser-based VideoViewer Automatically Locks PTZ
(6x-8905): 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.
• Go To PTZ Preset Feature Not Supported when LenelS2 NVR is Offline (OG-12958): The Go To Preset action cannot be executed
when there is a direct connection to the camera. The LenelS2 NVR must be online for this action to be successful.
• Joystick Control Difficult Due to Delays in Video (OG-15077): PTZ might 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.
Note: Modifying the registry could cause irreversible damage to your Windows operating system. Back up the registry
before making any changes. Follow the instructions located at: http://support.microsoft.com/kb/322756.
• 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.
• Schedule PTZ preset failed for the presets created in Alarm Monitoring (OG‑24355): The Schedule PTZ Action failed message is
displayed.

8.2 Remote Monitor Limitations

• Black Video Cells in Remote Monitor (6x-8823): If a video cell appears black in Remote Monitor, click [Stop] and then click [Play]. If
this does not resolve the issue, right-click the Remote Monitor and select Download Database.
• Remote Monitor and Alarm Monitoring Might Become De-synchronized (OG19830): Remote Monitor and Alarm Monitoring might
become de-synchronized after Alarm Monitoring is restarted. For example, Video Quality Enhancement (VQE) settings made for the
Remote Monitor channel are no longer selected in the user interface after restarting Alarm Monitoring.
• Remote Monitor Client and Server do not support Unicode (OG-20866): The Remote Monitor Client and Server do not support
Unicode. This might cause a username or password in a non-ASCII character set to not work in some cases.
• Remote Monitor does not handle an IP change when using a hostname (OG-22986): In order to resolve this, the Communication
Server must be restarted.

8.2 Video and Audio Playback Limitations

• ASF Files Not Supported in Alarm Monitoring (6x-8906): Advanced Systems Format (ASF) files are not compatible with Alarm
Monitoring. If an ASF file is loaded, the date will show incorrectly. ASF files should be opened with Windows Media Player.
• Double Video with Time-lapse Limitation (OG-15507): When using the Double Video on Alarm feature, the time lapse setting must
have the same value as the AlarmDurationMax value, otherwise there might be black video.
• Streaming Video Server Not Supported with H.264 Video Source (OG-16019): The H.264 camera codec is not supported with the
BARCO/Streaming Video Server integration.
• Audio Limitations:
• There is a two second or greater delay in recording audio in MPEG4 (OG-16666)
• Cannot export video from MPEG4 cameras with audio to ASF format (OG-16919)
• 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.
• Video Artifacts with RTP over UDP with Some Bitrate/Resolution Combinations (OG-18053): When using cameras with RTP over
UDP, artifacts might 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

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 5

 OnGuard 8.2 Update 1 Limitations

example, in the case of transmission of larger bitrates and resolutions). RTP over TCP/IP or RTP over RTSP over HTTP might be a
better option with cameras that support them because they are more reliable and do not present this issue.
• Recorded Video Playback Restarts When Returning to Previously Selected Cell in VideoViewer (Browser-based Client)
(OG-19046): Users can request recorded video from the LenelS2 NVR with the VideoViewer (Browser-based Client) that the video
recorder does not have. The video recorder will provide whatever video it can so if the user requests 12:10:00 and the LenelS2 NVR
has video after 12:15:00, the video will play from that available time and onward. The time in the cell will be different from the time
in the requested Begin Time window. When the user selects a different cell and then re-selects the original cell with the time
mismatch, the video will play from the beginning of the available video.
• LenelS2 NVR Issues with Axis Video Servers with No Feeds Connected (OG-19329): Axis analog video servers configured on a
LenelS2 NVR that do not have any video signals plugged into them might cause the LenelS2 NVR to leak memory and eventually stop
responding. This issue can be avoided either by not adding the unconnected channels to OnGuard or by marking them logically
offline.
• Status bar does not show “Offline” if a camera is marked offline (OG-21062): When a camera is manually marked offline, Alarm
Monitoring and Video Viewer will not display a red footer with a “Communication Lost” message at the bottom of the video cell for
the offline camera when the video stream is interrupted.
• Live Video Being Viewed During a VMotion Event of a LenelS2 NVR Might Not Come Back (OG-23740): During a VMotion event, at
near completion, the majority of the channels might go to the "Video signal lost" state in Alarm Monitoring on every client. The
channels might return to the full live frame rate on most clients, but on some they might never come back and stay in the Video
Signal Lost state. Reloading the channels might work in some cases but it might still not solve the issue.
• Alarm Monitoring stops responding when camera resolution is changed during live video (OG-29531): If the resolution for a
camera is changed after the Video Monitoring window is opened, Alarm Monitoring stops responding. To change the resolution,
close the Video Monitoring window, change the camera resolution in System Administration, and then reopen the Video Monitoring
window in Alarm Monitoring.
• Video window returns to default size when Instant Rewind goes to a time prior to the start time (DE128291): In Alarm
Monitoring, video is launched with a specific start time. If after resizing the Video Player window Instant Rewind is used to view a
time that precedes the start time, the Video Player window returns to the original size. This is a known issue that will be addressed in
a future release.
• The Sub-stream camera Port is not the same as the main-stream even though the "Add a live sub-stream" checkbox is
checked when adding a main-stream with a non-default port (DE39307): If a camera is added and configured for a non-default
port value (not 80), and the "Add a live sub-stream" box is checked, the sub stream channel will not automatically be configured to
use the same non-default port. Configure the port manually.
• In Alarm Monitoring or Video Viewer, the first cell in a matrix view is black (DE131972): This problem may occur with any matrix
layout of any number of channels, but it can also occur when a single camera stream is launched.
a. Verify that the Video Card drivers are current and update if needed.
b. Modify the Video Acceleration setting in the Performance dialog (select Options > Performance from the Video Player
window).
c. Move the slider to Full and click OK.
d. Exit the application (Alarm Monitoring or Video Viewer).
e. Log in again and try to load the video. If the result is the same, select another slider position for Video Acceleration and exit
the application.
f. Repeat the previous step as needed.
• De-warped Viewing of 360-degree Cameras (F540): The de-warped viewing of 360 degree cameras has the following limitations:
• No support for Wall mode
• Panamorph lenses (Immervision) are not supported

8.2 VideoViewer Limitations

• VideoViewer (Browser-based Client) CAB fails installation if a supported version of .NET is not installed (OG-20349): .NET is
required on the client. Refer to the Third-party Application Compatibility Chart on Partner Center for the supported versions of .NET.
• In the VideoViewer (Browser-based Client) application, 360 degree camera images are not de-warped as they are in Alarm
Monitoring and VideoViewer (DE7368).
• Connecting to VideoViewer (Browser-based Client) with Internet Explorer 64-bit on a computer with OnGuard does not work
properly (OG-24258): It is recommended to use the 32-bit version of Internet Explorer when using VideoViewer (Browser-based
Client). If the 64-bit version is used, the system might download the CAB file every time the application is started. The user will see an
'x' where the video template should be. There is no way to get video to stream into the 64-bit application.
• In the VideoViewer (Browser-based Client) application, the PTZ speed is the same for all settings (DE13185): This is a third-
party limitation - PTZ speed is speed is not available on the recorder.

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 6

 OnGuard 8.2 Update 1 Limitations

• Cameras show as offline in VideoViewer tree if the camera name is changed in OnGuard Administration (DE14255): Log out and
then log in again to view the camera with the new name.

8.2 Enterprise Limitations

• Global I/O Restrictions (OG-13969): Global I/O linkages will not work between two Enterprise regions. Global I/O configurations
must use the same Linkage Server.
• IntelligentVideo Applications Not Available on Enterprise Global when configured on a Child Region (OG-15971): There is a
known issue with the replication of IntelligentVideo Applications to the Global Server. IntelligentVideo Applications can be
configured and monitored on a per Region basis.
• Referential Integrity Error when Saving Camera Layouts (OG-15973): If a camera layout is saved with cameras added from
another Regional Server via the Camera Lookup feature, a Referential Integrity error might occur. To save a layout that generates the
error, remove the cameras located on other Regional Servers from the layout prior to saving.
• Pre-existing User-specific Layouts Not Replicated to Enterprise Global (OG-16029): Pre-existing user-specific video layouts are
not replicated up to the Global 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.
• Full Download to Region Results in Unexpected Log Size and Application Error (OG-21309): A full download to a Region could
result in a log larger than expected and an application error.
• Event Routing Groups Do Not Replicate (S62584): Event routing groups must be created on the Regional Server where they are
expected to be used. Event routing groups do not replicate.

8.2 Identity Management Limitations

• Field Type Must be Text for Phone Numbers (OG-13728): User-defined phone number fields must have a field type of text, not
numeric. To restrict users to numbers, use a “9” template when defining the field in FormsDesigner. Phone numbers entered as
numeric fields might have their values truncated.
• Fargo DTC4500 does not support encoding: The Fargo DTC4500 Card Printer/Encoder does not support encoding.
• 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.
• Magicard Tango2e Must Use Driver V1.41 (OG-20299): Magicard Tango2e driver V1.42 has a known issue with the installation of
magapi.dll. Driver V1.41 is available on the Supplemental Materials media and should be used instead.
• Cannot Verify Smart Card Formats Using Book 1 on Iris iCAM4000 (OG-27180): Configuring a Smart Card Format using Book 1
settings 16kbits / 2 Application Areas or 16kbits/ 16 Application Areas is not supported by the IrisICUAdmin4000 software.
• A "No Biometric Template” alarm is reported as a "Biometric Mismatch" alarm for OSDP biometric readers connected to
LenelS2 controllers (DE6459): This is a LenelS2 controller limitation. Initially, the "Access Denied: No Biometric Template" alarm is
generated when you present a badge that does not contain any associated biometric data. However, if you present the badge, and
then allow the system to timeout, the "Biometric Mismatch" alarm is generated as expected. According to Mercury, this is the correct
alarm behavior.
• While encoding DESFire cards using an HID SE CP1000 encoder, OnGuard reports an inaccurate count of the remaining credits
when a cardholder has a biometric PIN (DE5660): The credit count may vary depending on the number of files being encoded.
• Performance during batch-issuance of HID mobile credentials: HID requires that OnGuard limit the rate at which mobile
credentials are issued to 10 badges/minute (one badge every 6 seconds). Due to this limitation, you might experience degraded
performance when issuing HID mobile credentials in batches.

8.2 Magic Monitor Limitations

• Widgets connect to unintended OnGuard system (DE130026): If you change your configured OnGuard system in Magic Monitor to
a different OnGuard system, any widgets you created that were associated with the original OnGuard system might need to be
reconfigured. Inconsistent behavior might occur until the widgets are reconfigured.
• Connectivity issues (such as when the OnGuard Communication Server is down or if the network connection to the recorder isn’t
functioning correctly) might prevent a recorder’s status from being shown in Magic Monitor correctly. This could cause unexpected
behavior. For example, Magic Monitor might show a recorder offline because of connectivity issues between OnGuard and the
recorder, but users can still retrieve video from that recorder using Magic Monitor’s direct connection to the recorder. Another

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 7

 OnGuard 8.2 Update 1 Limitations

example is that a recorder’s status from OnGuard is online, but video playback from that recorder fails due to connectivity issues
between Magic Monitor and the recorder.
• Cameras marked offline in OnGuard: For OnGuard versions earlier than 8.0, cameras marked offline in OnGuard are still shown in
the Magic Monitor user interface. With OnGuard 8.0 and later, however, cameras marked offline in OnGuard are hidden in the Magic
Monitor user interface.
• Camera rotation/orientation changes in OnGuard: If changes to a camera's rotation or orientation are made in OnGuard, those
changes are not shown in Magic Monitor automatically. Restart Magic Monitor to see changes that were made to a camera's rotation
or orientation in the OnGuard software.
• Milestone video streams reloaded when OnGuard server is refreshed (DE131358): When the OnGuard server is refreshed, video
streams from a Milestone recorder are removed and then reloaded in the Magic Monitor cells.
• Timeline is not synchronized with the playback in Magic Monitor video cell when event has a gap (DE130487): The timeline in a
Magic Monitor video cell might not be synchronized with the playback if the event has a gap. This only affects the playback in the
event pane's embedded video cell, and does not affect other recorded playback locations such as Forensics Desktop.
• OnGuard events do not show status in the Magic Monitor event panel and widget (DE132098): OnGuard events that are not
cleared but are Acknowledged or marked In Progress do not show these states in the in the event panel or widget event lists. The
Acknowledged and In Progress states are shown in the Activity History for each event.
• Magic Monitor cannot be installed on a virtual machine.

8.2 OpenAccess Limitations

• In OpenAccess Swagger, the type of "access_level_list" is displayed as "string", should be "list" type (DE11793): Swagger
supports a format which does not match the OpenAccess requirement. Therefore, the “string” type is used.
• The Lnl_MultimediaObject type properties are not completely displayed in the OpenAccess Tool (DE11827): This is a known
limitation. The list controls character limit is 256 per column. For a complete list of properties, refer to the OpenAccess User Guide.
• Calling get_instance for Lnl_User in segmented systems (DE40045): In segmented systems, calling get_instance for Lnl_User
returns “null” for the user’s SegmentID property. The alternative way of getting the user’s segments is to call the GET /user/{id}/
segments method.
• Cannot filter using the "AccessResult" property (DE130064): Searching or filtering using the AccessResult property of the
Lnl_LoggedEvent call returns an "Invalid filter specified" message.

8.2 Reporting and Dashboards Limitations

• SQL Server compatibility: OnGuard Reporting and Dashboards is supported by Microsoft SQL Server 2016 and later.
• User-Defined Fields (UDFs) required for Reporting and Dashboards (DE137643): Reporting and Dashboards installation might fail
during Setup Assistant if your System Administration "Visitors" form is missing the default Organization field because you removed
it using FormsDesigner. If the Organization field is missing, you will be unable to use Reporting and Dashboards until you recreate
that field using FormsDesigner (although you can hide it by setting the size to 0).

8.2 Reports Limitations

• Unable to save report as pdf with a large number of cardholders when custom fields used (DE7938, DE7010): This is a limitation
of Crystal Reports.
• When previewing a report, certain cardholder images may cause System Administration to stop working as expected
(6x-5641): The workaround is to retake the photo that is causing the issue.

8.2 System Administration Limitations

• Hebrew: Instruction template with Native Characters are removed while displaying in OnGuard Monitor (DE16001): When
displaying double-byte characters like Hebrew, the text is not always clearly legible.
• Unable to edit badge type and issue code after printing the badge. (DE16069): Once a badge has been printed, the badge type
cannot be changed and a code can no longer be issued.

8.2 Visitor Management Limitations

• An error is displayed in Visitor Management Front Desk when event detail changes are cancelled and re-entered (DE12660): An
error message is displayed when a field is modified, cancelled, modified again, and then saved.

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 8

 OnGuard 8.2 Update 1 Limitations

• An error is listed in the LenelError.log file when logging into Visitor Management (DE12400): This is a logging limitation. There is
no error in application.
• Unable to modify visit records with multiple visitors created from IDVM application (DE12677): When group visits are scheduled
using Visitor Management Front Desk, they cannot be changed in System Administration, ID Credential Center, or Visitor
Management. Group visits are not supported through these user interfaces.
• 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’s Web site as part of the Windows SDK.
• 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.

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 9

 OnGuard 8.2 Update 1 Limitations

Copyright and Related Notices

©2024 Carrier. All Rights Reserved. All trademarks are the property of their respective owners. LenelS2 is a part of Carrier.
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 prior express written permission of Carrier Fire & Security Americas
Corporation (“LenelS2”), which such permission may have been granted in a separate agreement (i.e., end user license agreement or
software license agreement for the particular application).
Non-English versions of LenelS2 documents are offered as a service to our global audiences. We have attempted to provide an accurate
translation of the text, but the official text is the English text, and any differences in the translation are not binding and have no legal effect.
The software described in this document is furnished under a separate license agreement and may only be used in accordance with the
terms of that agreement.
SAP® Crystal Reports® is the registered trademark of SAP SE or its affiliates in Germany and in several other countries.
Integral and FlashPoint are trademarks of Integral Technologies, Inc.
Portions of this product were created using LEADTOOLS ©1991-2011, LEAD Technologies, Inc. ALL RIGHTS RESERVED.
Active Directory, Microsoft, SQL Server, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
NEC, ExpressCluster and ExpressCluster X are registered trademarks or trademarks of NEC Corporation in the United States and other
countries.
Oracle is a registered trademark of Oracle International Corporation.
Amazon Web Services and the "Powered by AWS" logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other
countries.
Other product names mentioned in this document may be trademarks or registered trademarks of their respective owners and are hereby
acknowledged.
Product Disclaimers and Warnings
THESE PRODUCTS ARE INTENDED FOR SALE TO, AND INSTALLATION BY, AN EXPERIENCED SECURITY PROFESSIONAL. LENELS2 CANNOT
PROVIDE ANY ASSURANCE THAT ANY PERSON OR ENTITY BUYING ITS PRODUCTS, INCLUDING ANY "AUTHORIZED DEALER", IS PROPERLY
TRAINED OR EXPERIENCED TO CORRECTLY INSTALL SECURITY RELATED PRODUCTS.
LENELS2 DOES NOT REPRESENT THAT SOFTWARE, HARDWARE OR RELATED SERVICES MAY NOT BE HACKED, COMPROMISED AND/OR
CIRCUMVENTED. LENELS2 DOES NOT WARRANT THAT SOFTWARE, HARDWARE OR RELATED SERVICES WILL WORK PROPERLY IN ALL
ENVIRONMENTS AND APPLICATIONS AND DOES NOT WARRANT ANY SOFTWARE, HARDWARE OR RELATED SERVICES AGAINST HARMFUL
ELECTROMAGNETIC INTERFERENCE INDUCTION OR RADIATION (EMI, RFI, ETC.) EMITTED FROM EXTERNAL SOURCES. THE ABILITY OF
SOFTWARE, HARDWARE AND RELATED SERVICES TO WORK PROPERLY DEPENDS ON A NUMBER OF PRODUCTS AND SERVICES MADE
AVAILABLE BY THIRD PARTIES OVER WHICH LENELS2 HAS NO CONTROL INCLUDING, BUT NOT LIMITED TO, INTERNET, CELLULAR AND
LANDLINE CONNECTIVITY; MOBILE DEVICE AND RELATED OPERATING SYSTEM COMPATIBILITY; OR PROPER INSTALLATION, CONFIGURATION
AND MAINTENANCE OF AUTHORIZED HARDWARE AND OTHER SOFTWARE.
LENELS2 MAY MAKE CERTAIN BIOMETRIC CAPABILITIES (E.G., FINGERPRINT, VOICE PRINT, FACIAL RECOGNITION, ETC.), DATA RECORDING
CAPABILITIES (E.G., VOICE RECORDING), AND/OR DATA/INFORMATION RECOGNITION AND TRANSLATION CAPABILITIES AVAILABLE IN
PRODUCTS LENELS2 MANUFACTURES AND/OR RESELLS. LENELS2 DOES NOT CONTROL THE CONDITIONS AND METHODS OF USE OF
PRODUCTS IT MANUFACTURES AND/OR RESELLS. THE END-USER AND/OR INSTALLER AND/OR RESELLER/DISTRIBUTOR ACT AS
CONTROLLER OF THE DATA RESULTING FROM USE OF THESE PRODUCTS, INCLUDING ANY RESULTING PERSONALLY IDENTIFIABLE
INFORMATION OR PRIVATE DATA, AND ARE SOLELY RESPONSIBLE TO ENSURE THAT ANY PARTICULAR INSTALLATION AND USE OF
PRODUCTS COMPLY WITH ALL APPLICABLE PRIVACY AND OTHER LAWS, INCLUDING ANY REQUIREMENT TO OBTAIN CONSENT. THE
CAPABILITY OR USE OF ANY PRODUCTS MANUFACTURED OR SOLD BY LENELS2 TO RECORD CONSENT SHALL NOT BE SUBSTITUTED FOR THE
CONTROLLER'S OBLIGATION TO INDEPENDENTLY DETERMINE WHETHER CONSENT IS REQUIRED, NOR SHALL SUCH CAPABILITY OR USE
SHIFT ANY OBLIGATION TO OBTAIN ANY REQUIRED CONSENT TO LENELS2.
For more information on warranty disclaimers and product safety information, please check https://firesecurityproducts.com/en/policy/
product-warning or scan the following code:

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 10

 OnGuard 8.2 Update 1 Limitations

DOC-900-EN-US (2024-01-12) ©2024 Carrier. All Rights Reserved. revision 12.15 — 11