Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Communication Drivers
  • AVEVA Communication Drivers Tech Notes

TN - IO - 26110314 Moving OI Server Configuration From One Machine To Another

Last updated: November 3rd, 2026

Description

  • Author: Josh Andrade
  • Published: November 3rd, 2026

Details:

  • Document Version: 001
  • Applies to Version(s): all

 

 

Description  

There are times when you are replacing existing systems or upgrading it to a new version; and the original system contains connections to PLCs. 

When setting up the new system, you’ll have to configure the connections to be able to communicate with the PLC devices. Sometimes, it can be several connections and repetitive work if already done once on the old system.

 

Solution Steps:

Each driver has a configuration file which you can take to the new machine to carry the entire structure from the OI Server Manager configuration.

 

Open File Explorer -> navigate to:

C:\ProgramData\Wonderware

 

Note: If you do not see “Program Data”, make sure you go to View -> Show Hidden Items:

 

From there, depending on what you have installed, will depend on what folder names you see. If you’re using OI Servers, you’ll want to navigate to:

C:\ProgramData\Wonderware\OI-Server\$Operations Integration Supervisory Servers$\

 

From this folder, select what driver’s configuration you want to backup:

 

In this example, we’ll take the OI MBTCP’s configuration, the file that holds the structure in the OI Server Manager is a .aacfg file:

 

You can now take this file, and place it on a different machine in the same directory to bring in the configuration structure.

 

Note: This example uses an MBTCP driver. For other drivers, the path and file name may be different. Also, if going from a DA Server to an OI Server, you’ll have to rename the file (i.e. DASMBTCP.aacfg to MBTCP.aacfg).

                                     _____________________________________________________________________________________________________

 

communication driver migration configuration aacfg
Give feedback about this article

Recommended articles

[ISS Support Case] OI Server Disconnects

Client reached out as when attempting to start ABCIP server it will fail and deactivate after a few seconds.

Read More

[ISS Support Case] OI Server diagnostics

OI Server - they can see diagnostic but from the GR node and dev station when they look at diagnostic they cant see anything. oiabcip and mbtcp CDP 7.2.200

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Group Logo

© 2026 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand