PI Server
Welcome to the
PI Server feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Remove installation kits' dependency on write permission to root C:\.
Some organizations do not provide admin accounts with write permission to the root C:\ directory. The install kits of most PI products copy the setup.ini to C:\pisetup.ini, and then write the logs to C:\ before moving them to %pipc%\dat, both of which require write permission to C:\. The only workaround for now is to find someone with that permission to run the kit (typically an IT member).
19 votes -
Utility to completely uninstall all OSIsoft PI products from a machine
It would be helping to have a utility do a complete uninstall of all the PI products from a machine including registry keys and hidden files.
12 votes -
Running PI System within Docker
Run the PI Server within Docker (https://www.docker.com/) to get better economies of scale.
Might already be possible, but need advice supporting this architecture.
8 votes -
Provide OSIsoft products in Docker containers to allow rapid deployment
The PI Square blogs on containers are enticing. I am looking forward to rapid deployment of OSIsoft products in containers.
7 votes -
Allow individual MSIs to be extracted from the PI Server 2018 install kit
(from case 939560)
I kindly request you add an enhancement request to allow individual MSIs to be extracted from the install kit. On numerous occasions, I’ve had upgrade/install failures that could be easily overcome by re-running the affected MSI individually, as opposed to from the wrapper.
6 votes -
Use the HTTPS versions of links in "Help link", "Support link", and "Update information" in Control Panel → Programs and Features
In Control Panel → Programs and Features, when you click on the PI programs in general (i.e. not just those that are part of PI Server), you will see that most of them use an HTTP link for their "Help link", "Support link", and "Update information". Please use the HTTPS versions of links. This would help show that OSIsoft cares about the privacy of their customers. It would also be more accurate since the HTTP links redirect to HTTPS.
5 votes -
Add OPCclient to all PI OPC DA server install kit
In verifying the OPC DA server DCOM setting you need to use the OPCclient to check PI tags values. In the OPC DA server 2017 you need the latest version of OPCclient (was not in OCP client tools) to allow to connect correctly to the OPC DA server 2017. If the OPCclient was in the OPC DA server 2017 I would not had needed to go down load OPC Tools kit.
5 votes -
Resizing the Installation Complete and Installation Error Window
For users who are performing installations through the use of PI System installation kits they would like the ability to resize the Installation Complete (Installation Error) Window so that they can get all of the details on all of the modules of the installation kit within one image/view without the need to horizontally scroll, losing the view of the module name while looking at the status and comments. Furthermore for installation kits with many products currently not able to view all of the products at once, must vertically scroll, seeing only partial list. Being able to resize this windows would…
5 votes -
Selectively install 32-bit versus 64-bit versions of PI programs
Currently, install kits such as those of PI DataLink, PI AF Client, PI API, PI SDK, PI OLEDB Provider, and PI OLEDB Enterprise always install both the 32-bit and 64-bit versions. Most of the time, one of these versions is unused and simply wasting disk space, cluttering the list of installed programs, and making the user wonder why they have 2 versions of the same program. Uninstalling the unused versions is only a temporary fix, since any upgrade to the programs will cause both versions to be installed again.
In future install kits, please allow the user to choose the…
4 votes -
4 votes
-
In future releases of PI Server, provide an installer that does not install itself in Windows Programs & Features.
Regulations and rules require pre-installation approval and documentation of all programs installed on a machine. Please provide an installer or a method of installation that prevents the installer from appearing in Programs & Features.
Furthermore, always provide a comprehensive, detailed list of programs that will be/can be installed in each installation kit.
3 votes -
Have a consistent presence of a terminating \ in the PIHOME and PIHOME64 environment variables
By default, PIHOME is "C:\Program Files (x86)\PIPC" and PIHOME64 is "C:\Program Files\PIPC\". For new installations, please consider either having the terminating \ on both or removing the terminating \ from both. The current inconsistency can confuse anyone that tries to write the path to anything within the PIHOME or PIHOME64 folder.
2 votes -
Consistently name the local groups that PI adds
Some examples of names of the local groups that PI adds are:
AFQueryEngines
AFServers
PI Buffering Administrators
PI Connector Administrators
PI Web API AdminsPlease consider making the naming more consistent. For example:
PI Asset Framework Query Engines
PI Asset Framework Servers
PI Buffer Subsystem Administrators
PI Connector Administrators
PI Web API AdministratorsAt the very least, please make sure that the group names start with "PI" so that the PI groups are grouped together when the groups are sorted in alphabetical order, much like what was done for the PI services.
2 votes -
Request that the install kit inform the user of pending installs and unintalls
Today a coworker requested that I install the web api and web crawler on an application server that already was running analysis and notifications. I ran the AF install kit, selected api and crawler because I just wanted to add those and the software performed the install but also uninstalled analysis and notifications without warning. It was probably a bad assumption on my part that it would only install what I asked it to and do nothing else.
Please pass this along to tech support and/or developers. Request that the install kit inform the user of pending installs and unintalls.
…
2 votes -
Allow PI Server components to be removed at installation time
Currently, when you run the PI Server install kit to perform an upgrade, existing PI Server components cannot be unselected, and so they are upgraded. This gives the impression that they cannot be uninstalled, but they can actually be uninstalled by modifying the installation in Programs And Features in the Control Panel. This is unintuitive.
Please allow PI Server components to be uninstalled at the same time as upgrading other PI Server components, otherwise many of the legacy components will continue to live unnecessarily in many customers' PI systems.
1 vote -
Be able to perform silent installs with different silent.ini file path
I have a customer who would like to perform silent installs and be able to specify a different file path for the silent.ini file. Currently the silent installs only work if the unzipped setup kit is all in one folder.
1 vote -
When PI AF Client is updated, update all install kits that contain PI AF Client
A lot of times, install kits such as the one for PI DataLink contain an older version of PI AF Client than the one that is included in the PI AF Client install kit.
To make things easier for customers, whenever PI AF Client is updated, consider updating all install kits that contain PI AF Client.
1 vote
- Don't see your idea?