Start typing to see products you are looking for.
  • Menu
  • Categories

Shopping cart

Close
  Need Customer Care? (800) 233-0298
Menu
Start typing to see products you are looking for.
PremiSys 4.5 ReadMe
PDC IDenticard

PremiSys™ LT
PremiSys™
PremiSys™ Pro

Version 4.5

ReadMe


Refer to this ReadMe for important information concerning installation and use of your software, which may include up-to-the-minute Help instructions and application alerts. Resolved software issues and new known issues are listed here as well. PDC IDenticard strongly recommends that you read these notes in their entirety before using this software.

System Requirements

Please visit the following link for server and client computer requirements:

PremiSys PC Specifications


PremiSys Version 4.5 is compatible with 64-bit versions of supported Windows® operating systems, except 64-bit Windows XP®. The database installed with PremiSys is Microsoft® SQL Server®; 2014 Express - if the operating system is 32-bit the 32-bit version of SQL Server is installed; if the operating system is 64-bit, the 64-bit version of SQL Server is installed.


Notes

Important: If you are using PremiSys™ Mobile, the mobile application for PremiSys and PremiSys Pro, you must open the Security Administration task and assign the new roles for "Manage Mobile Devices", "Mobile" and "Allow Mobile Client Access" to the user groups that can benefit from this new feature. The System Administration group (or the group created in your system to replace the System Administration group) must ALWAYS be given these new roles. For more information, see "Editing User Group Roles" and "Configuring Alarm Acknowledgements" in the Online Help file.

Important: If you are upgrading from a version before 2.16 and have the Salient® or Milestone® video-plugin installed, you will need to re-install the corresponding video-plugin included in the new installation

Important: If PremiSys-ENGAGE site is not created at time of initial licensing of NDE Lock(s), operator can use the NDE Site Generation option found in Tools menu

Important: NDE Locks and Schlage Controls do not support Areas and thus cannot be used with the Muster Report feature. An "access granted" transaction from an NDE Lock or Schlage Control WILL NOT reflect a change of location for a cardholder on the Muster Report.

Important: A maximum of 100 ENGAGE Gateways should be added to a single PremiSys-ENGAGE Site in order to maintain performance of the client application.

Important: When restoring an IDBAK which contains ENGAGE Gateway devices, the IDenticard Windows Service should be manually restarted in order to re-establish proper communication with all Gateway devices.

Important: Deactivation dates are required for cards being used with Resident Manager. Commands cannot be written to card (using an MT20W) unless a deactivation date has been assigned to the card.

Important: When updating ENGAGE device firmware for Online locks, make sure to update gateway firmware to the latest version before updating locks. Gateways and locks must have ENGAGE 5 or higher firmware in order to push new firmware from PremiSys. When updating ENGAGE lock firmware for offline locks, current firmware must be ENGAGE 5 or higher. If you have ENGAGE devices which do not meet these requirements, you must use the ENGAGE Mobile Application to update firmware.

Important: Due to changes in password hashing in PremiSys 4.2, hashed passwords will no longer be accepted in PremiSys APIs. Prior to PremiSys 4.2, the Query API ValidateUser method required a hashed password. API consumers will need to update to send a non-hashed password.

Important: When upgrading to 4.4 from a previous version you will not be able to use auto client update without first temporarily disabling TLS on the file cache service.


Known Issues

  • Help file is not updated to include new or updated features.
  • When upgrading clients, the auto-client update feature cannot install versions of .NET Framework. If an upgrade requires a newer version of .NET Framework then that Framework version will need to be installed before using auto-client update OR the upgrade must be run manually using PremiSys installation files.
  • When logging in after certain plugins are installed on the server a DirectX installation may appear. If the logged in user does not have permissions to install software the DirectX install will fail.
  • An Acknowledging Alarm window that is clicked to close while PremiSys is downloading the video clip does not respond by closing. (reference: 655)
  • When Exacq PTZ-camera video is exported, the resulting file is empty. (reference: 363)
  • Transaction filtering options do not allow the user to filter Rack objects (reference: 63886)
  • Hardware permissions do not apply to Transaction History reports when running a report using an archive file (reference: 67804)
  • Use of the latest Exacq plugin with an exacqVision™ 5.x server may display incorrect camera status in PremiSys
  • The “Unused Active Cards” dashboard widget is limited to display a maximum of 1000 cards in the table-view.
  • A User Logoff transaction will not be generated for a client which is logged off due to a network connection or client-PC issue until the client logs back in.
  • Though IE8 is not a supported browser for use with PremiSys, if you must use it you may notice significant performance issues when using the Dashboard feature set.
  • When using the Dashboard feature from a web-browser, using the browser’s refresh feature requires the user to log in again.
  • Dashboard feature may not work correctly when using Compatibility Mode in versions of Internet Explorer.
  • Mobile users will need to exit and restart their application after a new lookup field is made available to mobile users or when new lookup values are added to a lookup field which has already been made available to mobile users.
  • Use of certain special characters when entering data on a mobile device may result in a Cardholder not displaying correctly in Navigator. (reference: D-01472)
  • User log-on and log-off transactions are not visible in Monitor/Control unless/until at least one Controller has been configured. (reference: D-01618)
  • Scanning of Interleaved 2 of 5 barcodes using the mobile application is only supported on iOS devices and only with iOS version 8 or higher
  • One-time-use cards can be used again after an NDE Lock "phones home" and receives a configuration change or card update. (reference: D-01889)
  • If using NDE Locks with Windows Server 2008 32-bit, you must apply a hotfix from Microsoft for IIS. See https://support.microsoft.com/en-us/kb/980368 for details. (reference: D-01902)
  • Specific properties for LE locks are not present on the ENGAGE Door Report (reference: S-03385)
  • When upgrading PremiSys, the default port number for TCP port for HTTPS bindings is reset to 443 in IIS. (reference: D-02333)
  • New install may fail when installing SQL 2014 Express (reference: D-02496)
  • Hardware changes made using a Resident Manager mobile application are not journaled in the hardware journal(s)
  • Dashboard feature is not accessible using LDAP user logins
  • Mobile application is not compatible with LDAP user logins
  • Changing a password for a user that is currently logged in will break their session, requiring them to log out and then back in again

Version History

PremiSys 4.5 April 22, 2020
New Features
  • Added plugin support for Avigilon ACC7 video servers
  • Added support for Schlage NDE and LE revision 2.0
  • Added support for Schlage NDE revision 2.0 IPB
  • Added support for ENGAGE Invalid Card Audits
  • Upgraded .NET redistributable bundled with the installer to .NET 4.7.2
Resolved Issues
  • Advanced Search dialog fails to open. (reference: Defect 398)
  • Resolved Alarm Acknowledgment failing on new install. (reference: Defect 346)
  • Resolved saving ENGAGE card to cardholder. (reference: Defect 464)
  • Resolved Lockdown Trigger and Procedure issues. (reference: Defect 388)
  • Gateway polling improvements. (reference: Defect 443)
  • Support for Mercury LP controllers in API. (reference: Defect 55)
  • Resolved fault error with Status API. (reference: Defect 494)
  • Resolved Access Area issues in API. (reference: Defect 495)
  • Improved time sync with ENGAGE Gateway.
  • Improved ENGAGE Hardware tree performance.

PremiSys 4.4 October 15, 2019
New Features
  • Added the ability to turn ENGAGE IP Gateway polling On/Off
  • Improved security of APIs and services
  • Added support for high DPI screens
  • Added the ability to use Maps outside of the main PremiSys window
  • Added support for Windows Server 2019
  • Added plugin support for Hanwha video servers
  • Added a report to monitor resident activity when using online and offline ENGAGE locks
  • Added support for Schlage Control hardware revision 2.0
Resolved Issues
  • Made various security enhancements
  • Fixed an issue that could prevent a user from adding Global Groups.
  • Improved the performance loading the Card Properties dialog with a large number of ENGAGE doors.
  • Resolved an issue where an ENGAGE hardware site could not be deleted from the site collection.

PremiSys 4.3 June 18, 2019
New Features
  • Added support for card data that is 64 bit or greater
  • Added support for ASSA ABLOY Aperio Hub and wireless locks
  • Added a RESTful API for performing simple cardholder functions
  • Added Select and Unselect All option for the Manage Printers dialog
  • Upgraded .NET redistributable bundled with the installer to .NET 4.5.2
  • Slight performance improvement in ENGAGE Gateway management service
Resolved Issues
  • Monitor Hardware Tree will lock up when viewing statuses on a system that has a large number of ENGAGE online doors
  • Error in hardware tree interface when denying view permissions for certain channel configurations
  • Mainform toolbar position gets displaced when logging in multiple times in the same session

PremiSys 4.2 February 22, 2019
Resolved Issues
  • Updated password hashing method (CVE-2019-3907)
  • Added option to secure backups with a user-specified password (CVE-2019-3908)

PremiSys 4.1 January 23, 2019
Resolved Issues
  • Removed hardcoded credential and replaced it with a unique system-generated password for each session (CVE-2019-3906)

PremiSys 4.0 January 7, 2019
New Features
  • Added support for ENGAGE CTE as WiFi (Offline) or BLE (Online) devices
  • Maps now support ENGAGE BLE (Online) doors including manual actions
  • ENGAGE Lock Summary Report is now scheduleable
  • Battery Level field was added to the ENGAGE Lock Summary Report
  • Added support for LP Controllers
  • Added support for new "S3 - PoE One-Door Reader Board"
  • Added support for OSDP readers
  • ENGAGE Gateway, Schlage PIM, and Schlage AD300 are now supported on all EP and LP based controllers
  • Global Trigger/Procedures can now use ENGAGE Online locks and Gateways in Triggers and Actions
  • Added support for ENGAGE LE when using ENGAGE Gateways in RSI mode
  • Improved performance when downloading a controller that had a large card database
  • Added option to disable Door Position indicator for ENGAGE NDE and LE locks
  • Added a feature to check for new software version
  • Added RBH50 - 32/16 Card Format for ENGAGE locks
  • Improved usability when linking ENGAGE locks to a Gateway in RSI mode
  • Added MIFARE Plus support for ENGAGE locks
  • Added YOU Get It First subscription license
  • Added support for Schlage AD doors on EP/LP PoE One Door Reader Controllers and EP/LP Two Reader Controllers
Resolved Issues
  • Scheduled tasks can become corrupted and disappear from the task list (reference: D-02545)
  • Door or Controller Statistics Dialog does not open if item name exceeds 50 characters (reference: D-02546)
  • Certain cardholder filters could prevent a user from being able to run the Access Group with Cardholders Report (reference: D-02549)
  • ENGAGE Locks Summary Report does not save search criteria (reference: D-02558)
  • Could not upgrade firmware on IO Boards from PremiSys clients (reference: D-02556)
  • In some cases when assigning (or removing) an ENGAGE lock on a card, the Card Journal would report an incorrect name of the lock (reference: D-02568)
  • Unable to add or edit an Alarm Point Group (reference: D-02578)
  • Scheduled Transaction History Report would ignore the setting for number of days to include and always report 30 days of transactions (reference: D-02487)
  • After upgrading firmware on controllers, some transactions could appear with an incorrect Transaction Type (reference: D-02527)
  • Frequent display of "Transaction Count Exceeds Preset Limit" transaction when not expected (reference: S-04058)
  • Could not convert an SCP controller to Two Reader Controller if an IO Board with Address 0 was already configured. (reference: D-02552)
  • An elevator set for floor selection mode failed to save in some situations (reference: D-02593)
  • Screen designs with a Migration ID field and CardholderExt field could fail to save CardholderExt data (reference: D-02600)
  • Improved security of service configuration files (reference: S-04402)
  • Improved error handling when parsing JSON from ENGAGE locks (reference: D-02608)

PremiSys 3.2 May 14, 2018
New Features
  • Added a user role to limit which users can manage Badge Types in Card Configuration area of Screen Designs
  • Added select-all/unselect-all to all checked list boxes in options dialog for Transaction List and Alarm Acknowledgement windows
  • Added API support lockout/lockdown features
  • Added Job Title as a searchable and reportable field in the Transaction History Report
  • Added diagnostic information for ENGAGE Offline locks
  • Added fields to existing ENGAGE Lock Report
  • Added ENGAGE Lock Summary Report
  • Added ability to find/filter the list of Action Groups in Trigger/Procedure Wizard
  • Added Double-card feature
  • Enhanced Quick Search feature for Cardholders and added Quick Search for hardware
  • Support ENGAGE RU RM as WiFi (Offline) or BLE (Online) devices
  • Added support for Interior Push Button (IPB) when using Schlage AD series locks
  • Expanded ENGAGE Firmware update feature to support all WiFi lock types, gateways and locks connected via IP Gateways
    • Please see notes section above for important information before using this feature.
  • Improved user interface for discovering ENGAGE offline locks
  • Added support for monitoring status of ENGAGE online locks
  • Added support for SQL 2016
  • Implemented notification to user when non-compliant hardware is detected
Resolved Issues
  • When saving a new cardholder with a card, the Primary and Active flags do not save correctly. (reference: D-02523)
  • Changes made to lookup values are lost after an import is performed (related to D-02512 from 3.0 SP4) (reference: D-02515)
  • Saving a cardholder fails when using a date-time stamp and Migration ID (related to D-02514 from 3.0 SP4) (reference: D-02516)
  • Hardware journal incorrectly identified all doors as being modified when adding one door to a door group (reference: D-02427)
  • ENGAGE Gateway could continue to be polled even after it was deleted from PremiSys (reference: D-02510)
  • Card printing was initiated by clicking dropbox without making a selection (reference: D-02393)
  • Transaction time may report using GMT time while a controller is offline (reference: D-02529)
  • Save Not Successful message appears when saving a cardholder after printing a card and having a Date/Time stamp configured for printing a card (reference: D-02551)

Legal Notices

No Liability for Consequential Damages
In no event shall PDC IDenticard, or its suppliers, be liable for any damages whatsoever (including, without limitations, damages for loss of business profits, interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the software, even if PDC IDenticard has been advised of the possibility of such damages.

Because some states do not allow the exclusion or limitations of consequential or incidental damages, the above limitations may not apply to you.

Unauthorized Modification
Never add, alter or edit any of the system databases or their tables using software applications outside of the PDC IDenticard program purchased, unless specifically instructed to do so by PDC IDenticard Technical Support staff. Adding, deleting or modifying any data, fields, tables and/or databases in any way using Microsoft® SQL or any other third-party software application will adversely affect data integrity and can render the PDC IDenticard program partially or wholly unusable.

© 2009-2020 Brady Worldwide, Inc. All rights reserved.

PDC®, IDenticard®, PremiSys™ and IDentiPASS™ are either registered trademarks or trademarks of Brady Worldwide, Inc. in the United States and/or other countries. Windows® is a registered trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners.
freeshippingicon

Free Shipping over $99

freeshippingicon

Easy Returns

freeshippingicon

Safe and Secure

Scroll To Top

#title#

#price#
×