PremiSys® LT |
|
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. Matrix Systems 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 Version 4.10 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®; 2019 Express - SQL Server install Only supports 64-bit operating system.
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.
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.
Important: When upgrading from a version older than v4.9, Photo Recall Pop-up Transaction Details window is disabled by defualt. Contact Tech Support to enable if needed
Important: With the release of v4.10 will be using a new license server instance. If on a version older than v4.10 and having issues licensing, contact Tech Support for assistance.
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.
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.
Important: When upgrading from a version older than v4.9, Photo Recall Pop-up Transaction Details window is disabled by defualt. Contact Tech Support to enable if needed
Important: With the release of v4.10 will be using a new license server instance. If on a version older than v4.10 and having issues licensing, contact Tech Support for assistance.
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
- 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.10 | December 20, 2023 | |
| New Features |
| |
| Resolved Issues |
| |
| PremiSys 4.9 | June 30, 2023 | |
| New Features |
| |
| Resolved Issues |
| |
| PremiSys 4.8 | July 29, 2022 | |
| New Features |
| |
| Resolved Issues |
| |
| PremiSys 4.7 | August 2, 2021 | |
| New Features |
| |
| Resolved Issues |
| |
| PremiSys 4.6 | October 14, 2020 | |
| New Features |
| |
| Resolved Issues |
| |
| PremiSys 4.5 | April 22, 2020 | |
| New Features |
| |
| Resolved Issues |
| |
Legal Notices
No Liability for Consequential DamagesIn no event shall SGI Matrix, LLC DBA Matrix Systems 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 Matrix Systems 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 PremiSys program purchased, unless specifically instructed to do so by PremiSys 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 PremiSys program partially or wholly unusable.
© 2023 SGI Matrix,LLC All rights reserved.
PremiSys® is registered trademark of SGI Matrix, LLC 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.