Before You Install or Upgrade the AVEVA Batch Management Product

This section discusses several things that you must consider before you install or upgrade the AVEVA Batch Management product.

AVEVA Batch Management supports Server and Client installation in parent-child trusted domain environment and vice versa.

What Happens During the Installation Process

The AVEVA Batch Management installation procedure does the following:

• Installs or upgrades the selected features.

• During a product upgrade, the existing Batch configuration files and history database files are backed up and restored.

  Note: Before performing a batch history migration during an upgrade, ensure that the Batch History database does not contain any customizations. If customizations exist, please remove them beforehand to avoid issues during the migration process.

• Opens the TCP/IP ports required by AVEVA Batch Management that are blocked by default in Windows; configures the program exception for the OLE automation server.

• Adds all the AVEVA Batch Management History Server portals to the trusted sites zone.

When completing a AVEVA Batch Management upgrade, any previous product and patch information is removed from the Add/Remove Programs option within the Control Panel.

You can install AVEVA Batch Management Runtime Client and AVEVA Batch Management Development Client on a terminal server.

The AVEVA Batch Management Installer will not allow you to install AVEVA Batch Management on a Domain Controller.

Using User Account Control (UAC) Enabled Operating Systems with AVEVA Batch Management

When UAC is enabled on operating systems, a security prompt is shown when you start the installation.

If necessary, enter the administrative user credentials to allow the installer to proceed.

Service User Account

The Service user account is a user name and password combination that is used for running the AVEVA Batch Management services, such as EnvMngr, SecMngr, and HistQMngr. Ensure that the user account has Administrator privileges.