Lenel
Basic information

Product name

  • LenelS2 OnGuard

Integrated product versions

  • 7.5, 7.6, 8.0

Range of functions

  • Automatic synchronization of keyTags with the access levels in OnGuard.
  • Automatic synchronization of OnGuard cardholders/users and their access levels with Commander/keyTags.
  • Automatic synchronization of OnGuard badge with cardnumber field in Commander including activation/deactivating.
  • OnGuard can display Commander notifications for the following events:
    • Assignment changed
    • Cabinet closed
    • Cabinet opened
    • Communications lost
    • Communications returned
    • keyTag duration exceeded
    • keyTag returned
    • keyTag taken
    • Main Power Failure
    • User Assignment Change
  • User/Credential data will automatically be passed and updated in the Key/Asset Management System.
Technical information

Required files

  • Commander Connect 4.x
  • installs Apache Tomcat 6 with Axis 2
  • webservice (API)
  • Java JDK 1.6 or Higher
  • .Net 4.6.2 or Higher
  • syncTool 2.5.4

Supported operating systems and databases

  • Windows 7 Enterprise, Pro, Ultimate 64-bit
  • Windows 8 Enterprise, Professional 64-bit
  • Windows 8.1 Enterprise, Professional 64-bit
  • Windows Server 2012 Standard 64-bit
  • Windows Server 2012 R2 Standard 64-bit
  • Windows 10 and IoT 64-bit
  • Windows Server 2016 (64-bit)
  • Mac, Linux

Supported databases

  • SQL Server 2012 R1 64-bit
  • SQL Server 2014 Express 64-bit
  • SQL Server 2014 R2
  • SQL Server 2014 R1 64-bit
  • SQL Server 2016 64-bit
  • SQL Server 2017 64-bit
Limitations

Limitations

  • OnGuard Holidays are not supported. Only the OnGuard time zone is supported.
  • If the User Time Profile drop down list is used to control badge access to the terminals/cabinets by OnGuard Timezone, a dropdown list must be created in OnGuard.
  • Visitor person Type is not supported by the Commander integration with OnGuard.
  • Users created in Commander are NOT synchronized into OnGuard.
  • If a KeyTag/KeyTag group name in Commander is changed, the corresponding access level in OnGuard must be assigned to the cardholders again.
  • If a Cardholder's name or other user data synched from OnGuard is changed in the Commander, it will be automatically changed back to the OnGuard values by the next synchronization process.
  • OnGuard Badge PIN is not supported by the Commander integration because the PIN is not exposed via the OpenAccess API. Another field can be created using OnGuard FormsDesigner and mapped to the Commander PIN field.
  • If a Cardholder has multiple active badges, only the first assigned active badge will be synchronized by the syncTool.
  • If custom fields are used on the OnGuard Cardholder form, the field name and the object name MUST BE exactly the same when created via OnGuard FormsDesigner.
  • If Commander is successfully integrated with a non-segmented OnGuard system, and OnGuard Segmentation is later enabled, all Commander created Access Levels in OnGuard MUST BE deleted and will be automatically re-created during the next full sync cycle.
  • When an Access Level created by Commander is modified or deleted in OnGuard, it will be re-created with the same name/value that displays in Commander during the next COMPLETE sync cycle.
  • OnGuard Cardholder/Badge dropdown fields cannot be mapped to Commander fields for synchronization, with the following exceptions: Department User Time Profile, proxSafe PIN, proxSafe Terminal User. Field is optionally created for use with the Integration.
  • OnGuard Badge Activation/Deactivation date only is synchronized by syncTool. Date and Time is not supported.
  • When KeyTag auto return feature is enabled in the deister DataComm engine, a KeyTag can be returned without scanning an OnGuard badge.
  • Events from Commander are displayed in OnGuard Monitor as "Generic Event" and the Person column displays only the Badge ID. The Cardholder Name and event description is displayed in the Associated Text, which is displayed when clicking the icon in the info column.
  • When integrated with OnGuard systems with more than 50,000 Access Level assignments to Active Badges, syncTool may take longer than expected to synchronize due to a limitation in the Onguard OpenAccess API.