Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

Status No Status
Categories System Management
Created by Guest
Created on Aug 19, 2022

option to manually disable secondary collective member synchronization

I have experienced several synchronization errors with data archives running on virtual machines in separate errors, generally after MS updates. Please provide a way to stop synchronization of configurations between collective members, so I can perform MS updates and reboots without fear of having to re-synchronize my secondary archives afterwards.
  • Attach files
  • Guest
    Reply
    |
    Aug 19, 2022
    Microsoft operating system patching should not have caused collective members to go out of sync. Have you reviewed this KB article? https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=Applying-Microsoft-Operating-System-patches-to-PI-Servers If you continue to run into issues patching, I recommend you contact tech support.