PremiSys ReadMe
 |
 |
Version 4.8
|
PremiSys LT
PremiSys
PremiSys Pro |
PremiSysID
PremiSysID Pro |
|
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.8 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
If you are upgrading from an unsupported version of PremiSys, click here for important considerations that are required to upgrade to the current version. Check here for a list of supported & unsupported versions.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: Additional Relay configuration requires the relays to be on the SIO as the reader.
Important: Additional Relay configuration requires the use of the next relay associated with the door.
Important: Additional Relay will never activate if the strike is off before the delay expires.
Important: When upgrading from version 4.6 or below, the PremiSys Windows Service must be manually started after the upgrade is completed.
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)
- 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.
- After upgrading to 4.8, Cards and/or Triggers assigned to User Levels that are named "1" or "2" must be resaved.
Version History
| PremiSys 4.8 |
July 29, 2022 |
| New Features |
- Added support for Mercury LP-4502 controllers
- Added support for BEST Wi-Q wireless locks by dormakaba
- Added API integration support for LobbyTECH
- Added card enrollment for ENGAGE locks in Web Client |
| Resolved Issues |
- Resolved Transaction Window would not update correctly. (reference: Defect 88)
- Resolved database performance issue for wireless locks and high number of ACRs. (reference: Defect 1356)
- 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.7 |
August 2, 2021 |
| New Features |
- Added Cardholder Management using web client
- Added support for LDAPS
|
| Resolved Issues |
- Resolved an issue where cards were not being downloaded to LP controllers using the cardholder API (reference: Defect 848)
- Resolved an issue where "Set as Default" was not working for ENGAGE reader configuration (reference: Defect 679)
|
| PremiSys 4.6 |
October 14, 2020 |
| New Features |
- Added the ability to configure Additional Relay to a door
- Added support for Check-In Reader
- Added support to display the Elevator Floor name in Access Group configuration
- Improved operation of the Gateway firmware dialog to only pull information when requested
- Improved operation of the Gateway firmware dialog to only pull information on Gateways that are visible
|
| Resolved Issues |
- Resolved an issue where ENGAGE WiFi locks were using lowercase values as part of the LockIdentifier (reference: Defect 554)
- Resolved an issue where using PC system region other than English (United States) will cause erratic behavior with PremiSys UI (reference: Defect 647)
- Resolved an issue with network discovery dialog preventing further scans and lock of information (reference: Defect 617)
- Resolved an issue with Resident Manager users who are returned to login screen when saving a cardholder record. (reference: Defect 614)
- Resolved an issue with ENGAGE edge devices returning NULL value when requesting status (reference: Defect 688)
- Resolved an issue with poor performance while saving cardholder record. (reference: Defect 689)
- Resolved an issue with Trigger and Procedure operation for ENGAGE CTE and RU/RM edge devices. (reference: Defect 631)
|
| 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.
|
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 Services 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-2022 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.
