Frequently Asked Questions

Save PDF

Last UpdatedNov 26, 2025
12 minute read

What are the preferred, supported, and not supported browsers for this platform?

Preferred: Google Chrome
Supported: Microsoft Edge, Mozilla Firefox
Not supported: Apple Safari, Microsoft Internet Explorer

What is the minimum supported screen resolution?

The minimum supported resolution is 1280x720.

Why isn't my System Platform (2023 R2) VM licensed?

Click here for details.

If I create an empty project template, can I add nodes to it later?

Yes. Project Templates can be edited after they have been created. From there, you can add/delete nodes.

If I create a node with no role, can I add software to it later?

Yes. Once nodes have been created, software can be installed manually. For convenience, if a node is created without a role, the installation software is located on drive C: for manual installation of the software.

How do I see installed updates of the node?

Azure Update Manager installs updates on the virtual machines. To view the patch history, in Control Panel, select Programs and Features, and then select Installed Updates.

Can I change the IP address of my machines?

No. The maintenance of the IP addresses of each machine is managed by platform. Each machine is configured to use DHCP. Static IP addresses are not supported.

If I change the name of my node, will the change be reflected in the Manage section of my project template?

Not at this time. A node may be added to an existing project template by editing it and giving it the new name.

Can a project template name be changed?

Not at this time. A new project template will have to be created with the new name.

Is there a domain controller on my project template?

Not at this time.

What operating systems and versions of SQL Server are installed on each type of node?

Release Product	Operating System	Microsoft SQL Server	Microsoft .NET	UAC
PlantSCADA2023R2	Windows Server 2019 Datacenter (64-bit)	N/A	Microsoft .NET 4.8	ON
SP2023R2SP1	Windows Server 2019 Datacenter (64-bit)	Microsoft SQL Server 2022 Express (64-bit)	Microsoft .NET 4.8	ON
SP2023R2	Windows Server 2019 Datacenter (64-bit)	Microsoft SQL Server 2019 Express (64-bit)	Microsoft .NET 4.8	ON
SP2023Enterprise	Windows Server 2019 Datacenter (64-bit)	Microsoft SQL Server 2019 Express (64-bit)	Microsoft .NET 4.8	ON
SP2023	Windows Server 2019 Datacenter (64-bit)	Microsoft SQL Server 2019 Express (64-bit)	Microsoft .NET 4.8	ON
WSP2020R2	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2019 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP2020R2SP1	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2019 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP 2020	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2019 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP 2017 Update 3 SP1	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2016 SP1 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP 2017 Update 3	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2016 SP1 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP 2017 Update 2	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2016 SP1 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP 2017 Update 1	Microsoft Windows 2016 Datacenter (64-bit)	Microsoft SQL Server 2016 SP1 Express (64-bit)	Microsoft .NET 4.7.2	ON
WSP 2014 R2 SP1	Microsoft Windows 2012 R2 Standard (64-bit)	Microsoft SQL Server 2014 Standard (64-bit)	Microsoft .NET 4.5.1	ON
WSP 2014 R2 P01	Microsoft Windows 2012 R2 Standard (64-bit)	Microsoft SQL Server 2014 Standard (64-bit)	Microsoft .NET 4.5.1	ON
WSP 2014 P01	Microsoft Windows 2012 Standard (64-bit)	Microsoft SQL Server 2012 SP1 Standard (64-bit)	Microsoft .NET 4.5	ON
ASP 2012 R2 P1, P2, P3	Microsoft Windows 2008 R2 SP1 Standard (64-bit)	Microsoft SQL Server 2012 Standard (64-bit)	Microsoft .NET 4	OFF
ASP 2012 P01	Microsoft Windows 2008 R2 Standard (64-bit)	Microsoft SQL Server 2008 SP1 (32-bit)	Microsoft .NET 3.5 SP1	OFF
IAS 3.1 SP2 P1	Microsoft Windows 2008 SP2 Standard (32-bit)	Microsoft SQL Server 2008 SP1 (32-bit)	Microsoft .NET 3.5 SP1	OFF

What software is installed with each role?

SP 2023 R2 SP1

Products of SP 2023 R2 SP1	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian
Application Server	x	x	x	x		x	x
Bootstrap	x	x	x	x		x	x
IDE	x	x
Galaxy_Repository	x
InTouch	x	x	x			x	x
InTouch Development	x	x				x
InTouch Runtime	x	x	x			x	x
Historian Client	x	x
Historian Server			x	x				x
InTouch Access Anywhere Secure Gateway					x

Products of SCADA 2023 R2

Products of SCADA 2023 R2	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian
AVEVA Common Components		x	x
Platform Common Services		x	x
AVEVA Plant SCADA		x	x
Configuration		x
Runtime		x	x
Deployment Server		x
OPC UA Server		x
Industrial Graphics Web Server		x
Drivers		x

SP 2023 R2

Products of SP 2023 R2	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian
Application Server	x	x	x	x		x	x
Bootstrap	x	x	x	x		x	x
IDE	x	x
Galaxy_Repository	x
InTouch	x	x	x			x	x
InTouch Development	x	x				x
InTouch Runtime	x	x	x			x	x
Historian Client	x	x
Historian Server			x	x				x
InTouch Access Anywhere Secure Gateway					x

SP 2023 Enterprise

Products of SP 2023 Enterprise	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian	Omi Webserver
Application Server	x	x	x	x					x
Bootstrap	x	x	x	x					x
IDE	x	x
Galaxy_Repository	x
InTouch
InTouch Development
InTouch Runtime
Historian Client	x	x	x	x					x
Historian Server				x				x
InTouch Access Anywhere Secure Gateway					x

SP 2023

Products of SP 2023	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian
Application Server	x	x	x	x		x	x
Bootstrap	x	x	x	x		x	x
IDE	x	x
Galaxy_Repository	x
InTouch	x	x	x			x	x
InTouch Development	x	x				x
InTouch Runtime	x	x	x			x	x
Historian Client	x	x	x					x
Historian Server	x			x
InTouch Access Anywhere Secure Gateway					x

SP 2020 R2

Products of SP 2020 R2	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian
Application Server	x	x	x	x		x	x
Bootstrap	x	x	x	x		x	x
IDE	x	x
Galaxy_Repository	x	x
InTouch	x	x	x			x	x
InTouch Development	x	x				x
InTouch Runtime	x	x	x			x	x
Historian Client	x	x	x
Historian Server				x				x
InTouch Access Anywhere Secure Gateway					x

SP 2020 R2 SP1

Products of SP 2020 R2 SP1	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway	InTouch Development	InTouch Runtime	Historian
Application Server	x	x	x	x		x	x
Bootstrap	x	x	x	x		x	x
IDE	x	x
Galaxy_Repository	x	x
InTouch	x	x	x			x	x
InTouch Development	x	x				x
InTouch Runtime	x	x	x			x	x
Historian Client	x	x	x
Historian Server				x				x
InTouch Access Anywhere Secure Gateway					x

WSP 2020

Products of WSP 2020	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway
Application Server	x	x	x	x
Bootstrap	x	x	x	x
IDE	x	x
Galaxy_Repository	x	x
InTouch	x	x	x
InTouch Development	x	x
InTouch Runtime	x	x	x
Historian Client	x	x	x
Historian				x
InTouch Access Anywhere Secure Gateway					x

WSP 2017 Update 3 SP1

Products of WSP 2017 Update 3 SP1	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway
Application Server	x	x	x	x
Bootstrap	x	x	x	x
IDE	x	x
Galaxy_Repository	x	x
InTouch	x	x	x
InTouch Development	x	x
InTouch Runtime	x	x	x
Historian Client	x	x	x
Historian				x
InTouch Access Anywhere Secure Gateway					x

WSP 2017 Update 3

Products of WSP 2017 Update 3	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway
Application Server	x	x	x	x
Bootstrap	x	x	x	x
IDE	x	x
Galaxy_Repository	x	x
InTouch	x	x	x
InTouch Development	x	x
InTouch Runtime	x	x	x
Historian Client	x	x	x
Historian				x
InTouch Access Anywhere Secure Gateway					x

WSP 2017 Update 2

Products of WSP 2017 Update 2	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway
Application Server	x	x	x	x
Bootstrap	x	x	x	x
IDE	x	x
Galaxy_Repository	x
InTouch	x	x	x
InTouch Development	x	x
InTouch Runtime	x	x	x
Historian Client	x	x	x
Historian				x
InTouch Access Anywhere Secure Gateway					x

WSP 2017 Update 1

Products of WSP 2017 Update 1	SP Development Server	Development Workstation	Runtime Client	Historian Server	InTouch Access Anywhere Secure Gateway
Application Server	x	x	x	x
Bootstrap	x	x	x	x
IDE	x	x
Galaxy_Repository	x
InTouch	x	x	x
InTouch Development	x	x
InTouch Runtime	x	x	x
Historian Client	x	x	x
Historian				x
InTouch Access Anywhere Secure Gateway					x

WSP 2014 R2 P1

Products of WSP 2014 R2 P1/SP1	All-In-One Node	SP Development Server	Development Workstation	Runtime Client	Historian Server
Application Server	x	x	x	x	x
Bootstrap	x	x	x	x	x
IDE	x	x	x
Galaxy_Repository	x	x	x
InTouch	x	x	x	x
InTouch Development	x	x	x
InTouch Runtime	x	x	x	x
Historian Client	x	x	x	x
Historian	x				x

WSP 2014 R2 SP1

Products of WSP 2014 R2 P1/SP1	All-In-One Node	SP Development Server	Development Workstation	Runtime Client	Historian Server
Application Server	x	x	x	x	x
Bootstrap	x	x	x	x	x
IDE	x	x	x
Galaxy_Repository	x	x	x
InTouch	x	x	x	x
InTouch Development	x	x	x
InTouch Runtime	x	x	x	x
Historian Client	x	x	x	x
Historian	x				x

WSP 2014 P1

Products of WSP 2014 P1	All-In-One Node	SP Development Server	Development Workstation	Runtime Client	Historian Server
Application Server	x	x	x	x	x
Bootstrap	x	x	x	x	x
IDE	x	x	x
Galaxy_Repository	x	x
InTouch	x	x	x	x
InTouch Development	x	x	x
InTouch Runtime	x	x	x	x
Historian Client	x	x	x	x
Historian	x				x

WSP 2012 R2 P3

Products of WSP 2012 R2 P3	All-In-One Node	SP Development Server	Development Workstation	Runtime Client	Historian Server
Application Server	x	x	x	x	x
Bootstrap	x	x	x	x	x
IDE	x	x	x
Galaxy_Repository	x	x
InTouch	x	x	x	x
InTouch Development	x	x	x
InTouch Runtime	x	x	x	x
Historian Client	x	x	x	x
Historian	x				x

WSP 2012 P1

Products of WSP 2012 P1	All-In-One Node	SP Development Server	Development Workstation	Runtime Client	Historian Server
Application Server	x	x	x	x	x
Bootstrap	x	x	x	x	x
IDE	x	x	x
Galaxy_Repository	x	x
InTouch	x	x	x	x
InTouch Development	x	x	x
InTouch Runtime	x	x	x	x
Historian Client	x	x	x	x
Historian	x				x

IAS

Products of IAS	All-In-One Node	SP Development Server	Development Workstation	Runtime Client	Historian Server
Application Server 3.1 SP3 P1	x	x	x	x	x
Bootstrap	x	x	x	x	x
IDE	x	x	x
Galaxy_Repository	x	x
InTouch	x	x	x	x
InTouch Development	x	x	x
InTouch Runtime	x	x	x	x
Historian Client	x	x	x	x
Historian	x				x

Can a remote IDE node in this product communicate to a GR node?

Yes. Once GR and remote IDE nodes have been created and running, manually add a remote IDE node user to the Users group on the GR.

To manually add a remote ID node user to the Users group

Select a desired project template from the Project Templates page.
On the pop-up menu, select Nodes.
Select View Credentials to get the user and password for both the GR and remote IDE node.
Open a remote desktop connection to a GR node using the user and password from the previous step.
After the GR node virtual machine (VM) is up and running, open the Windows Computer Management utility and expand the tree view.
Go to System Tools>Local Users and Group>Users.
Add the remote user name that was provided by the View Credentials function and clear the User must change password at next logon option.
Select Create.

The remote IDE user is added to the GR node.
Right-click the newly created user and select Set password.
Enter the remote IDE password that was provided by the View Credentials function, then select OK.
Launch the properties page for the IDE remote user and add Administrators to the Member Of tab, then select OK.
Open a remote desktop connection to the IDE remote.
Launch IDE and successfully connect to the GR node.

What are the permission differences between regular users, project owners and administrators?

The shared project permissions are described in the following table.

	Owner	Non-owner (regular user)	Non-owner (Admin user)
Can start project/machines?	Yes	Yes	Yes
Can stop project/machines?	Yes	Yes	Yes
Can delete project/machines?	Yes	Yes	Yes
Can edit project/machines? Yes/No applies to all of the following: Add new nodes Change metadata Delete nodes Change auto-shutdown time	Yes	Yes	Yes
Can change between shared and personal?	Yes	Yes	Yes
Can change owner?	N/A	N/A	N/A

The personal project permissions are described in the following table.

	Owner	Non-owner (regular user; cannot see this project, so all are No)	Non-owner (Admin user)
Can start project/machines?	Yes	No	Yes
Can stop project/machines?	Yes	No	Yes
Can delete project/machines?	Yes	No	Yes
Can edit project/machines? Yes/No applies to all of the following: Add new nodes Change metadata Delete nodes Change auto-shutdown time	Yes	No	Yes
Can change between shared and personal?	Yes	No	Yes
Can change owner?	N/A	N/A	N/A

Do I stop using my personal or shared credits if I shutdown my VM from the VM operating system?

Yes. If a user shuts down the VM from the operating system, the underlying Azure framework will auto-deallocated VM resource and stop charge in 10 minutes

Within the product, to avoid usage of credits towards machines that are not in use, the user should End a session.

After an Historian VM is up and running for the first time, do I need to manually configure the Historian server?

Yes. A user must manually run the Configurator. You can find the Configurator icon on the Historian VM desktop.

To manually configure the Historian server

Open a remote desktop connection to the Historian node using the user and password from the View Credentials function.
Launch Configurator.exe from C:\Program Files (x86)\Common Files\ArchestrA.
Select Historian Server on the Configurator navigation tree.
Leave the default settings and select Configure.

User Name: sa

Note: If you select the SQL login Information SQL Authentication option, enter the user name and password for SQL server as follows:

User Name: sa

Password: Wonderware111

A green check mark appears for Historian Server after completing the configuration.

Select Extensions on the Configurator navigation tree.
Select an option for SQL Reporting Server and select Configure.
Select Configure to process the configuration.

A green check mark appears for Extensions after completing the configuration.
Close the Configurator.

The Historian server is ready for use.

Does the selected region affect the time zone on a VM?

No! All VMs have the same GMT time zone, no matter which region is selected when creating a project template.

Where can I find a license and release products to install on an empty node?

A Wonderware Installation Media icon can be found on the VM desktop. Each VM has a selected version of products at the C:\<Release product Name> folder (for example,C:\Wonderware System Platform 2014 R2 SP1). The license file (for example,ArchestrA.LIC) is also included in the same folder.

Where can I find information about using AVEVA Integration Studio with Prometheus?

For known issues and product compatibility, see this document:

Prometheus Readme.html

For more information about using Prometheus, see these documents (installed at C:\Program Files\Wonderware\Prometheus):

Wonderware Prometheus 2017 Getting Started with Schneider M580.pdf
Wonderware Prometheus 2017 Getting Started with Allen Bradley.pdf

What products are installed on a Prometheus VM?

Wonderware System Platform 2014 R2 SP1
UnityPro XL (V11.0_IR10E_20151207)
OFS Server (V3.60_3109_DEMO_SP1)

How can I browse an OPC Server that's installed on a different AVEVA Integration Studio node?

Make sure the node hosting OPC Server has a user with the same name and password as the node you are browsing from.

To add a matching user to the OPC Server node

Select node running your OPC Client.
Select View Credentials to view the username and password for that node.
Log into the node running OPC Server.
In Computer Management, select Local Users and Groups, select Users, and select New User.
In the New User dialog, use the same username and password from step 2 to define a new user on this node.
Select Create.

AVEVA™ Integration Studio