Unattended Silent Installation
- Last UpdatedFeb 05, 2024
- 2 minute read
The installation of Plant SCADA can be executed via a command line with the required components specified via a configurable response file.
Note: A silent installation will only work on a clean computer. If you have any existing dependent components on a computer from an earlier installation (such as Operations Control Logger or Platform Common Services), a silent install will not be successful. If this occurs, you can complete your installation by manually running the Plant SCADA Installer.
Response File
A response file specifies the set of components that will be installed during a silent installation. It represents the forms normally seen when interacting with the user interface of the Plant SCADA installer. The available options for each form are configured via a set of properties.
Four preconfigured response files are available for use:
-
All.txt – installs all components
-
DevelopmentWorkstation.txt – installs components for a development workstation
-
RuntimeClient.txt – installs components for a runtime client
-
Server.txt – installs components for a runtime server.
These can be used to install a typical set of components, or they can be used as reference for your own customized response file (see Customize a Response File).
The four files are available from the following directory within the Plant SCADA installation media:
InstallFiles\ResponseFiles
The following example shows the content of the Server.txt response file.
<responsefile>
<install>
ComputerRoleSelectionForm.SelectedComputerRoleName=Server
ServerRoleSelectionForm.ServerRolesList=RuntimeServer,DeploymentServer,
IndustrialGraphicsServer,OPCUAServer,EnterpriseLicenseServer
FeaturesForm.SFeatureList=AVEVA Plant SCADA.Configuration,AVEVA Plant SCADA.Runtime,
AVEVA Plant SCADA.InTouchWebClient,AVEVA Plant SCADA.OpcUaServer,
AVEVA Plant SCADA.DeploymentServer
SecurityGroupForm.AddUserToGroups=true
FirewallForm.ModifyFireWall=true
CustomDestinationSelectionForm.InstallDirPath=C:\Program Files (x86)\AVEVA Plant SCADA
CustomDestinationSelectionForm.ProgramDataPath=C:\Program Data\AVEVA Plant SCADA 2023 R2
</install>
</responsefile>
You can also specify Configurator settings within a response file. See Add Configurator Settings to a Response File.
Silent Install/Uninstall Commands
The following commands can be executed from a command prompt:
-
Command for installation:
Setup.exe /silent "<Response File Path>"
The specified response file needs to be text-based. A full absolute path needs to be provided. For example:
Setup.exe /silent "D:\PlantSCADA\MyResponseFiles\All.txt"
You can also use the "silentnoreboot" option to suppress a machine reboot after installation completes, for example:
Setup.exe /silentnoreboot "<Response File Path>"
-
Command for uninstallation:
Setup.exe /silentuninstall <ID of Plant SCADA>
For example:
Setup.exe /silentuninstall {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
The ID for Plant SCADA can be retrieved from the Setup.xml file, located in the InstallFiles directory within the installation media.
Search for the ID value within the <mainproduct> tags.
Note: Do not manually uninstall any non-core components (such as AVEVA Enterprise Licensing, the Sentinel Driver, PCS, Operation Control Logger or AVEVA Help) prior to running a silent uninstall of Plant SCADA as the silent uninstall may not be successful.
When you run a silent uninstallation, you need to follow the procedure below when also uninstalling any non-core components.
-
Uninstall AVEVA Plant SCADA's core components (using the silent uninstall command).
-
Uninstall AVEVA Enterprise Licensing components:
-
AVEVA Enterprise License Server
-
AVEVA Enterprise License Manager
-
AVEVA Enterprise Licensing Platform.
-
-
Uninstall Schneider Electric Software Update.
-
Uninstall Sentinel System Driver Installer.
-
Uninstall AVEVA Platform Common Services.
-
Uninstall Operations Control Logger.
-
Uninstall AVEVA Help.
Note: You can also use a command to silently install a Plant SCADA update. See Silently Install a Plant SCADA Update.