Allow interfaces and connectors to run on the Windows IoT operating system (formerly Windows Embedded)

Prior to UniInt v4.6.0.60, UFO sync files created during interface startup would inherit file permissions from their parent folder (assuming child inheritance had been enabled on the folder).

With UniInt v4.6.0.60, this behavior changed and now sync files created by the interface do not respect inheritance.  Instead, they are created with a standard ACL containing only the local "Administrators" and "Users" security groups.

For users with complex file permission schemas, this change introduces additional, unnecessary configuration efforts that scale as interface numbers grow beyond the site-level. 

Add a watchdog counter or something similar into the shared memory header. If the counter fails to update, initiate UFO.

If PIBufSS crashes, data loss can occur.  implement something that allows UniInt to know that the Buffer Subsystem is not responding and initiate failover if available.

This was previously enhancement 119481.

SNMP Interface should support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.

Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".

(Posted on behalf of our customer)

It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.

Currently (as of PI to PI Interface AutoPointSync Connector Version 1.5.0.7), it's not possible to sync changes to "Point type". (See pg 5 of user manual).

Please make this possible in a future release.

Regulatory and/or security requirement to separate data collection from data storage using a one-way data flow. Could apply to Interfaces or Connectors, for example PI Interface for Emerson Ovation.
PI Interface/Connector -> one-way data flow -> PI Server/EDS/OCS

We noticed that changes to the configuration of newer interfaces / connectors like
- PI EMDVBCS interface 4.0
- PI inbatch interface
- PI Connector Wonderware Historian
are no longer recorded in the PI Audit trail. (see also TechSupport Case # 937205)
This is a compliance issue for the regulated industries.

Provide a configuration option in UniInt interfaces, to enable shutdown of the interface if it consistently receives error messages when attempting to write to PI. Recently had an interface successfully connect to PI but not achieve write access to its tags; would've been nice to have this interface gracefully shut down or restart, and allow its UFO failover partner to serve the data flow

I understand that you can remotely view logs using pigetmsg. However this solution does not work for me as the interface is on a controlled network that only allows outbound traffic. I would like a way for the interface node to be able to push out interface logs somewhere such as to my DA, that way I could use SMT to view my interface logs.

1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.

PI Connectors already use the Event Viewer to log messages. It is time for PI Interfaces to do the same.