PMT Security

Advanced Access Control

Access Control

Nexus220 Web Reports Using Microsoft Edge

Nexus220 Web Reports Using Microsoft Edge

Nexus220 Web Reports can be viewed using Microsoft Edge with Internet Explorer Mode Enabled

When selecting Web, then Web Home Page in Nexus220, Nexus220 will attempt to launch the Web Reports Home page with the default browser that is configure for the PC Nexus220 is installed on. The Nexus220 Web Home Page was designed to use Internet Explorer. With Internet Explorer not being supported by Microsoft, Microsoft has made Microsoft Edge Browser available with an Internet Explorer Compatibility Function, The Nexus220 Web Home Page will need to be opened and viewed in Microsoft Edge with IE compatibility mode enabled.

Below are the steps to accomplish this:

  1. Open Microsoft Edge.
  2. Click the Settings and More (ellipsis) button in the top-right corner.
  3. Select the Settings option.
  4. Click on Default browser.
  5. Under the “Internet Explorer compatibility” section, turn on the “Allow sites to be reloaded in Internet Explorer mode” toggle switch to enable IE Mode on Edge.
  6. Click the Restart button. Enable IE mode on Edge

If the URL for the Nexus220 Web Home Page does not open after enabling the settings, you can follow the steps below to resolve the issue.

Open website with IE Mode on Edge

To open an incompatible website with IE Mode on Edge, use these steps:

  1. Open Microsoft Edge.
  2. Click the Settings and More (ellipsis) button in the top-right corner.
  3. Click the “Reload in Internet Explorer mode” option. Reload in Internet Explorer mode
  4. (Optional) Right-click the tab and select the “Reload tab in Internet Explorer mode” option.

After you complete the steps, the website should reload in compatibility mode. The option won’t be available in the menu if the feature is not enabled.

If you want to exit IE Mode, use the same instructions, but in step 3, select the “Exit Internet Explorer mode” option.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Resolving log4j Vulnerabilities

Resolving log4j Vulnerabilities

This process involves replacing the current log4j with a compatible alternative that addresses the reported vulnerabilities.

This process involves replacing the current log4j with a compatible alternative that addresses the reported vulnerabilities. It is important to proceed with caution and run a test before proceeding with the replacement. The following instructions aim to make the update as seamless as possible.

Summary:

There are two files that need to be removed from the same folder, and then you will place the attached library/file into that same folder.

Steps to stop the OMNIA:

Server App and Running as a Service

OMNIA running as a Service

1. Go to Services

2. Right Click OMNIA Service, Stop the OMNIA Service

Server App:

1. Before starting, ensure that your OMNIA Server is completely turned off. You can check this by clicking the small arrow on the bottom right corner of your taskbar.

2. Once clicked, you will see the OMNIA Server icon if it is running.

3. Right-click on the image and select “Exit.”

4. Click on the “Yes” option in the dialog box that appears.

5. Click on the small arrow again and make sure you no longer see the OMNIA Server logo. It may take a minute for it to shut down completely.

Steps to upgrade your OMNIA system:

1. Remove the highlighted files mentioned below. These files can be found in the default install location of OMNIA, which is also highlighted in the image provided. If you have installed OMNIA in a different location, navigate to that location and go into the version folder (the name of the version folder may vary depending on your update/installation history).

Note: It is recommended to copy these files to another location so that you can revert to the original state if any unforeseen problems occur.

2. Once the highlighted libraries are deleted, please copy and paste the library/file from the downloadable zip found at this link:

https://pmtronics-my.sharepoint.com/:f:/p/jeffrey_coleman/EiqzDxz-ULJJp2n8jhDV5vIB1t-jWWjdHF8drVLM0uw2iw?e=5DFjMv

You have now successfully updated your log4j and can start up the OMNIA Service or the OMNIA Server App again.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Step by Step Install of OMNIA 4.6.5 with 2019 SQL Express and SQL Management Studio

Step by Step Install of OMNIA 4.6.5 with 2019 SQL Express and SQL Management Studio

Installing OMNIA 4.6.5

This is a step by step guide to installing OMNIA 4.6.5 and SQL 2019 Express. Please ensure you are logged in the PC/Server with Local Administrator Rights. This installer will not fail with proper permissions and being run as administrator.

Download the OMNIA.iso from PMTronics

pmtsecurity.com/download-center/

  1. Select the OMNIA.iso
  2. Mount the OMNIA.iso


  3. Right Click OMNIA 
  4. Select Run as Administrator


  5. Select Run Anyway if Windows Prevents Installer from running


  6. Select Language of Choice, Select OK


  7. Select Next


  8. Accept the Agreement
  9. Select Next


  10. OMNIA Installation location, Select Next


  11. Select the Components to Install
  12. Select Next


  13. Information Dialogue Box Appears
  14. Select Yes
  15. Select Next


  16. Edit Settings Page, only edit settings if needed. Select Edit Setting Box to make Changes. OMNIA will search the localhost automatically for a SQL instance name with a database named OMNIA
  17. Select Next


  18. Error Window will appear, this error is normal
  19. Select Yes
  20. Select Next

  21. Information/Question Window will appear
  22. Select yes
  23. Select Next

  24. Select if Desktop Shortcut is needed
  25. Select Next


  26. Select Install


  27. Installation Process Continues, Select Finish When Completed


  28. After the OMNIA installation completes, The OMNIA Plugin Manager Installation will begin if selected at beginning of installation.
  29. Select Next

  30. Select the Components to install
  31. Select Next

  32. If SQL is not running local, change LOCALHOST to IP address of SQL.
  33. Change SQL Database Name to OMNIA
  34. Select Next

  35. Accept the Plugin Manager License Agreement
  36. Select Next

  37. Select Install

  38. Plugin Installation Continues

  39. Plugin Manager Installation Completed
  40. Select Next

  41. SQL Server Management Studio will need to be downloaded and Installed from Microsoft. This is needed for Database tasks such as Backups.
  42. Select the Windows Start Icon, SQL 2019 will be a  new installation 
  43. Select the newly installed folders drop down arrow
  44. Select the SQL Server 2019 Installation Center
  45. A separate SQL Installation Center window will open
  46. Select Installation
  47. Select Install SQL Server Management Tools, this will open a download link in a web browser.

  48. Select the Management Studio Install download link.

  49. Right Click the SSMS Installer
  50. Select Run as Administrator

  51. Management Studio Installer Window Appears
  52. Select Install


  53. Select Restart

  54. Installation is complete, After the reboot, launch OMNIA from the Desktop Shortcut.



Text

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

OMNIA Hardware Offline Validation

OMNIA Hardware Offline Validation

This article refers to the offline validation capabilities of OMNIA hardware

OMNIA Hardware Offline Validation 

This article refers to the offline validation capabilities of the following OMNIA hardware: 

  1. Control Module (CM) with up to 8 directly connected reader modules (WM). 
  2. Door Controller (DC) An OMNIA Control module set via dipswitch to operate in door controller mode with up to 8 reader modules directly connected. 
  3. iTRT Door Controller. 
  1. CM (Control Module) – requires no offline mode – it is the primary decision maker/controller hence it can only be offline from the server; in which case it will not receive any tagholder/site configuration updates while offline and will not be able to upload any transaction data from its cluster to the server. Once back online, all these updates occur. All (up to 8) reader modules connected directly to the CM will work with full offline validation. 

Risks: 

  • The only real risk here is the transaction buffer eventually being overwritten. Transaction buffer = 10 000 transactions. 

   2.  DC (Door Controller) – A Control Module in DC mode, emulates an iTT/iTRT. There are          two offline modes: a). If there are less than 10 000 tagholders on the site, then DC’s make access control                             decisions by referring to a set of tables containing the access rights of all tagholders on site.             There is essentially no difference to the behavior as compared to a CM, except that only              the first two of the connected cluster modules will be supported in this                            manner. 

Risks: 

  • Only the first 2 modules are supported in this manner. 
  • In this mode, only 10 access groups per tagholder are supported as opposed to the 25 that would be if the DC was online. 
  • A high traffic door that is left offline for a long time will start to overwrite the transaction buffer. 

 b).  If there are more than 10 000 tagholders on site, then the number of tagholders exceeds                 the DC’s local tagholder database (set of tables) capacity. It can’t use this method of                           validation. Instead, it refers to its transaction buffer (of 10 000 transactions). If the                           tagholder that is attempting to tag appears in the transaction buffer with an allowed                         transaction, then that tagholder is allowed access in offline mode.  

 Risks: 

  • Again, only the first 2 modules are supported in this manner.  
  • A high traffic door that is left offline for a long time will start to overwrite the transaction buffer.

3.  iTRT – Identical to above (2) DC, Unit only has 2 reader ports, can not be expanded.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Creating Operator Profiles

Operator Profiles in OMNIA

How to create Operator Profiles in OMNIA

Operator Profiles

Setting up operator profiles and operators in OMNIA

There are several pre-defined operator profiles available in OMNIA, if you find that you need to create a custom profile, follow this procedure:

  1. In OMNIA, browse to the SETUP menu and select OPERATOR PROFILES

2.   Select the

at the top left of the page to add anew profile.

3.   Give the new profile a descriptive name and then select a template from the selection list, select a template that most closely matches what you need in the new profile.

4.   Now that the profile is created, you now need to fine-tune it, move through the menu items and add/remove functionality as needed.

  1. MENUS and FEATURES gives you the ability to decide what menu items an operator with this profile will have access to. Checked means they have access, unchecked means the item is hidden from the operator.
  2. DATA allows you to apply data filters to the profile, for instance, if you want the profile to have access to multiple sites, you would add a SITE filter here and check all sites that you want an operator with this profile to have access to.
  3. Add a filter, give it a name and select what type of filter you require.

Select filter parameters, check means available, unchecked is unavailable. d.   COLUMNS Give access on a more granular level right down to single parameters within a tagholder record, usually one would not need to change anything here unless there is a particular parameter that you do not want the profile to have access to for instance you might not want the operator to have the ability to apply the ACCESS OVERIDE flag to any tags in the system.

e.   FILTERS is a list of system filters that you may want to allow the operator to have access to, this does not limit access and is used in filtering date for things like reports. The default here is usually adequate.
5.  Now that the Profile is configured, go to user logins and apply the profile to the desired user login.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems