PI data archive configuration is currently stored in the windows registry and is difficult to access and manipulate unless you know what you are doing.
The AF Server configuration is stored in an AFSDK.Config file. This file is simple, easy to read and much easier to manipulate.
The PI data archive and AF server configurations should be combined into one file or two separate files in the same location.
We are currently in the design phase of moving the Known Servers Table out of the Windows Registry and into a file. The name and location of this file is still being determined at this time. One of the key goals with this work is to alleviate the issue experienced by PI DataLink users after a Microsoft Office update is performed.
Please continue to share your use cases around this idea!
Agreed, additionally, the file-based architecture would be easier for the AVEVA products to read and write from as compared to the registry. This also makes it far easier for PI Administrators to view the KST and troubleshoot connections.