AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Installation
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

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).
  • Attach files
  • Kenneth Reiss
    Reply
    |     Aug 20, 2022
    Agree with this concept. Instead of C:\ the installer should utilize %TEMP% or %TMP% for the pisetup.ini file and logs, before moving them to %PIHOME%\dat
  • Guest
    Reply
    |     Aug 20, 2022
    Another option (suggested by Martin Bryant) would be able to specify the log path with a command line option or by editing the setup.ini file.
  • Guest
    Reply
    |     Aug 20, 2022
    Are you asking specifically about the PI Server install kit?
  • Guest
    Reply
    |     Aug 20, 2022
    Thanks for the info I'm facing this same issue. (BTW I do not have access to Osisoft Azure DevOps, please keep posting the status of the work item)