Foxboro™ DCS

Control Software v8.0

Installation Guide

B0750TP, Rev E

March 2025

https://www.se.com
Legal Information
The information provided in this document contains general descriptions, technical
characteristics and/or recommendations related to products/solutions.
This document is not intended as a substitute for a detailed study or operational and
site-specific development or schematic plan. It is not to be used for determining
suitability or reliability of the products/solutions for specific user applications. It is the
duty of any such user to perform or have any professional expert of its choice
(integrator, specifier or the like) perform the appropriate and comprehensive risk
analysis, evaluation and testing of the products/solutions with respect to the relevant
specific application or use thereof.
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this document are the property of Schneider Electric SE or
its subsidiaries. All other brands may be trademarks of their respective owner.
This document and its content are protected under applicable copyright laws and
provided for informative use only. No part of this document may be reproduced or
transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), for any purpose, without the prior written permission of
Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the
document or its content, except for a non-exclusive and personal license to consult it
on an "as is" basis.
Schneider Electric reserves the right to make changes or updates with respect to or in
the content of this document or the format thereof, at any time without notice.
To the extent permitted by applicable law, no responsibility or liability is
assumed by Schneider Electric and its subsidiaries for any errors or omissions
in the informational content of this document, as well as any non-intended use
or misuse of the content thereof.
 Control Software v8.0 Installation Guide

Table of Contents
Preface ...............................................................................................................8
General Cybersecurity Information ....................................................................8
Product-related Cybersecurity Information .........................................................8
Environmental Data..........................................................................................9
Workstation and Server Types...........................................................................9
Revision Information.......................................................................................10
Related Documents........................................................................................10
Foxboro DCS User Documentation ............................................................10
Control Software Installation and Control Core Services
Compatibility ............................................................................................10
AVEVA User Documentation ..................................................................... 11
Global Customer Support ............................................................................... 11
We Welcome Your Comments......................................................................... 11
Chapter 1: Planning Your Installation ..........................................................12
Installation/Upgrade Overview.........................................................................12
New Installation (Day 0 Installation) ...........................................................12
Upgrade Installation..................................................................................12
Control Software v8.0 Installation...............................................................14
Installation Considerations ..............................................................................15
Minimum System Requirements ................................................................15
Installation/Upgrade Scenarios ..................................................................15
Typical Foxboro DCS Control Software User Roles .....................................15
Upgrade Considerations .................................................................................16
Upgrading to Foxboro DCS Control HMI v8.0..............................................16
Control Software v8.0 License.........................................................................16
Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Primary Domain Controllers ..........................................................................17
Installing Control Software ..............................................................................17
Overview of Group Managed Service Accounts (gMSA) ....................................18
Post-installation Procedure for Primary Domain Controllers...............................19
Creating FCSEngineering and FCSOperators User Accounts ......................19
Updating the Control Software Network Account...............................................23
Updating the Control Software Network Account on Domain Clients...................24
Chapter 3: Installing Foxboro DCS Control Software ...............................25
Pre-installation ...............................................................................................25
Pre-installation Notes................................................................................25
NIC Card Binding Order ............................................................................26
Configuring GMSA on a Newly Added On-Platform Workstation in the
Active Directory ........................................................................................26
Adding an Off-Platform Workstation in the Active Directory ..........................27
Pre-installation for Enterprise Edition CCS Stations Connecting to Off-
Control Network Galaxy Repository ...........................................................29
Installation Considerations for Enterprise Edition Foxboro DCS
Workstations ............................................................................................31

B0750TP, Rev E 3
Control Software v8.0 Installation Guide

Installation Procedure for All Stations...............................................................31

Installing the Latest Software Updates .............................................................41
Reinstalling Foxboro DCS Control Software .....................................................41
Reinstalling at Each Client Workstation ......................................................42
Reinstalling at the Galaxy Database Server ................................................42
Reinstalling Control Software ....................................................................42
Modifying and Uninstalling Foxboro DCS Control Software................................43
Modifying the Existing Installation ..............................................................43
Uninstalling Foxboro DCS Control Software ...............................................50
Chapter 4: Configuring Foxboro DCS Control Software ...........................54
Configuring the AVEVA Enterprise License Server ............................................55
Configuring the Historian Server......................................................................58
Selecting Historian Data Path Drive ...........................................................58
Configuring the Pre-Configuration Plugin .........................................................59
Configuring Control HMI Resolution.................................................................60
Configuring Startup Options for FoxView and Control HMI.................................61
Enabling Control Core Services Configuration ..................................................62
Configuring CSDatabase Preparation ..............................................................63
Configuring Alarm DB Logger Preparation........................................................64
Configuring Galaxy Preparation.......................................................................65
Configuring SQL Maintenance Scripts .............................................................65
Configuring Spreadsheet Features ..................................................................66
Chapter 5: Galaxy Preparation .....................................................................69
Opening Galaxy Preparation ...........................................................................69
Galaxy Preparation on the Galaxy Repository Server........................................69
Galaxy Preparation on Each Galaxy Repository Client ......................................71
Finalizing Galaxy Preparation..........................................................................73
Adding New FDT Roles to the Galaxy Database ...............................................74
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0 (Day
0 Installation) ...................................................................................................76
Introduction ...................................................................................................76
Planning the Upgrade.....................................................................................76
Overview of the Upgrade Process ...................................................................77
Backup Process .............................................................................................79
Backing Up the Galaxy Repository Database..............................................79
Backing Up the InFusionDeployedDB Database .........................................83
Backing Up the AVEVA Historian Database ................................................85
Backing Up the Foxboro DCS Control HMI User Files..................................88
Backup Foxboro DCS Control HMI Files.....................................................89
Backing Up PLB and Sequence Block Source Files.....................................90
Backing Up Condition Advisor Database for Day0 Upgrade .........................90
Installing Foxboro DCS Control Software .........................................................90
Restoration Process .......................................................................................91
Restoring the InFusionDeployedDB Database ............................................91
Restoring the AVEVA Historian Database ...................................................93
Restoring the Foxboro DCS Control HMI User Files ....................................98
Restore Foxboro DCS Control HMI Files ....................................................99

4 B0750TP, Rev E
 Control Software v8.0 Installation Guide

Restoration of the Galaxy Repository Database.............................................. 100

Galaxy Migration and Preparation ................................................................. 100
Before You Begin.................................................................................... 100
Out-of-Support Microsoft Redistributable Packages .................................. 100
Migrating and Preparing the Galaxy ......................................................... 101
Synchronizing the Historian Server Name or Historian Blocks Data Path with
the Backup and Restored Historian Databases............................................... 104
Restoration of HMI Application v6.3 or v7.x Files ............................................ 104
Restoration of Foxboro DCS Control HMI Application v6.3 Files....................... 105
Restoring Custom Style Settings ................................................................... 105
Restoring PLB and Sequence Block Source Files ........................................... 105
Restoring the Condition Advisor Database During a Day 0 Upgrade................. 105
Change Tracking Records from FoxCTS Server ............................................. 106
Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version ........................................................................................................... 107
Migration Overview ...................................................................................... 107
Upgrade Considerations ............................................................................... 108
Overview of the Migration Process........................................................... 108
Control HMI Migration................................................................................... 109
Modifying the Bad Quality Setting ............................................................ 109
Backing Up the Standalone InTouch Applications...................................... 110
Converting Control HMI to the Latest Version of InTouch ........................... 111
Running the Control HMI Migration Tool ................................................... 111
Exporting the Managed Application Window ............................................. 116
Importing Scripts and Windows Using WindowMaker Application ............... 116
Migrating InTouch and Alarm Hot Backup Files ......................................... 120
Updating User Startup Application ........................................................... 121
Exporting and Importing Windows Between Managed Foxboro DCS Control
HMI Applications .......................................................................................... 121
Exporting Industrial Graphics................................................................... 122
Exporting InTouch Windows .................................................................... 122
Importing Industrial Graphics................................................................... 122
Importing InTouch Windows .................................................................... 123
Recustomizing AlarmPanel Windows............................................................. 124
Restarting WindowViewer Application............................................................ 124
Upgrading Client Workstations ...................................................................... 124
Updating Application Startup......................................................................... 125
Setting Application Startup (Preferred Method) ......................................... 125
Setting Application Startup (Alternative Method) ....................................... 125
Chapter 8: Configuring Alarm Priority Mapping Icons on Galaxy
Repository Stations Migrated to Control Software v8.0 .......................... 126
Chapter 9: Installation Troubleshooting .................................................... 128
Galaxy Migration .......................................................................................... 128
Network Account.......................................................................................... 128
IASeriesAlarmProvider ................................................................................. 129
Galaxy Preparation ...................................................................................... 130
Foxboro DCS Control Software Installation .................................................... 130

B0750TP, Rev E 5
Control Software v8.0 Installation Guide

Workstation Recovery .................................................................................. 131

Galaxy Host Station ................................................................................ 131
Client Station ......................................................................................... 133
Modifying Domain Policy for Enterprise Edition CCS v9.8................................ 134
Modifying Local Policies for Local Edition CCS v9.8 ........................................ 136
Configuring Control Software or SQL Services Originally Running with
FoxboroGMSA Accounts .............................................................................. 139
Appendix A: Security Considerations and Procedures ........................... 141
Security Guidelines ...................................................................................... 141
Physical Access ........................................................................................... 141
Enabling and Disabling Virus Scanning Software ............................................ 141
Stations with ePolicy Orchestrator™ (ePO) Software Installed .................... 141
Enabling and Disabling Trellix Endpoint Security (ENS) Software ............... 141
Enabling Virus Scanning ......................................................................... 143
Appendix B: QuickPick Software Components ........................................ 145
Appendix C: Installing AVEVA Licenses.................................................... 150
Activating Licenses ...................................................................................... 150
Activating Licenses Online ...................................................................... 151
Activating Licenses Offline ...................................................................... 152
Deactivating Licenses................................................................................... 155
Deactivating Licenses Online .................................................................. 156
Deactivating Licenses Offline .................................................................. 157
Enterprise License Server Configuration ........................................................ 160
Reserving Licenses ...................................................................................... 161
Exporting and Importing Reservations for Devices .......................................... 163
Exporting the Device Reservation Details ................................................ 163
Editing .CSV File .................................................................................... 164
Importing the Device Reservation Details ................................................. 164
Appendix D: Verifying and Activating Microsoft Visio .............................. 166
Verifying Visio 2021 Activation Status ............................................................ 166
Activating Visio 2021 with Internet............................................................ 168
Activating Visio 2021 by Telephone .......................................................... 168
Activating Excel 2021 with Internet........................................................... 169
Activating Excel 2021 by Telephone ......................................................... 169
Appendix E: Installing Microsoft SQL Server 2019 ................................. 170
Manual Installation of Microsoft SQL Server 2019........................................... 170
Setting up the Foxboro GMSA on Enterprise Edition ....................................... 170
Microsoft SQL Server 2019 Standard Edition.................................................. 171
Microsoft SQL Server 2019 Express Edition ................................................... 172
Glossary ......................................................................................................... 174

6 B0750TP, Rev E
Important Safety Instructions Control Software v8.0 Installation Guide

Important Safety Instructions

Read these instructions carefully and look at the equipment to become familiar with it
before trying to install, operate, service, or maintain it. The following safety messages
might appear throughout this manual or on the equipment to warn of potential hazards
or to call attention to information that clarifies or simplifies a procedure.

The addition of this symbol to a “Danger” or “Warning” safety message

indicates that an electrical hazard exists that results in personal injury if
the instructions are not followed.
This safety alert symbol that lets you know about potential personal
injury hazards. Obey all safety messages with this symbol to avoid
possible injury or death.

DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death
or serious injury.
Failure to follow these instructions will result in death or serious injury.

WARNING
WARNING indicates a hazardous situation that, if not avoided, could result in
death or serious injury.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

CAUTION
CAUTION indicates a hazardous situation that, if not avoided, could result in
minor or moderate injury.
Failure to follow these instructions can result in injury or equipment damage.

NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions can result in equipment damage.

Please Note
Electrical equipment should only be installed, operated, serviced, and maintained by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction,
installation, and operation of electrical equipment and has received safety training to
recognize and avoid the hazards involved.

B0750TP, Rev E 7
Control Software v8.0 Installation Guide Preface

Preface
This document provides instructions for installing EcoStruxure™ Foxboro™ DCS
Control Software v8.0 on the EcoStruxure Foxboro DCS.
This version of the document applies to Foxboro DCS Control Software 8.0. For
earlier versions of Control Software, see earlier revisions of this document.
The terms controller, control processor, and CP are used interchangeably throughout
this document.

General Cybersecurity Information

In recent years, the growing number of networked machines and production plants
has seen a corresponding increase in the potential for cyber threats, such as
unauthorized access, data breaches, and operational disruptions. You must,
therefore, consider all possible cybersecurity measures to help protect assets and
systems against such threats.
To help keep your Schneider Electric products secure and protected, it is in your best
interest to implement the cybersecurity best practices as described in the
Recommended Cybersecurity Best Practices document.
Schneider Electric provides additional information and assistance:
• Subscribe to the Schneider Electric security newsletter.
• Visit the Cybersecurity Support Portal web page to:
◦ Find Security Notifications
◦ Report vulnerabilities and incidents
• Visit the Schneider Electric Cybersecurity and Data Protection Posture web page
to:
◦ Access the cybersecurity posture
◦ Learn more about cybersecurity in the Cybersecurity Academy
◦ Explore the cybersecurity services from Schneider Electric

Product-related Cybersecurity Information

Use this product inside a secure industrial automation and control system. Total
protection of components (equipment/devices), systems, organizations, and networks
from cyber attack threats required multi-layered cyber risk mitigation measures, early
detection of incidents, and appropriate response and recovery plans when incidents
occur. For more information, see Appendix A: Security Considerations and
Procedures, page 141 and EcoStruxure™ Foxboro™ DCS Cybersecurity Reference
Guide (B0700HZ).

8 B0750TP, Rev E
Preface Control Software v8.0 Installation Guide

WARNING
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Change default passwords at first use to help prevent unauthorized access to
device settings, controls, and information.
• Disable unused ports/services and default accounts, where possible, to
minimize pathways for malicious attacks.
• Place networked devices behind multiple layers of cyber defenses (such as
firewalls, network segmentation, and network intrusion detection and protection.
• Apply the latest updates and hotfixes to your operating system and software.
• Use cybersecurity best practices (for example, least privilege, separate of
duties) to help prevent unauthorized exposure, loss, modification of data and
logs, interruption of services, or unintended operation.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

Environmental Data
For product compliance and environmental information, see the Schneider Electric
Environmental Data Program.

Workstation and Server Types

Control Core A workstation or server that has Control Core Services or legacy
Services I/A Series software installed. This workstation is connected to the
Foxboro DCS Control Network and can contain additional
software packages, including legacy software packages such as
FoxView or AIM* Historian
Control A Foxboro DCS Control Core Services workstation with one or
Software more of these additional software packages installed:
• AVEVA System Platform
• Control Software components such as Control Editors,
Control HMI, and Field Device Expert
• Additional AVEVA components such as AVEVA Historian
Off-Control A workstation or server without Control Core Services or legacy I/
Network A Series software installed. This type of workstation is not
connected to the Foxboro DCS Control Network, but might have
Control Software installed on it. Examples of Off-Control Network
workstations include Off-Platform Galaxy Database Server and
Off-Platform Domain Controller.
Though not on the Foxboro DCS Control Network, these stations
are connected to a secondary network, which is part of the
Foxboro DCS.

B0750TP, Rev E 9
Control Software v8.0 Installation Guide Preface

Revision Information
This revision of the document includes these changes:

Chapter 6 • Added a note to Migrating and Preparing the Galaxy,

page 101.
Appendix D • Updated Appendix D: Verifying and Activating Microsoft
Visio, page 166.

Related Documents
Foxboro DCS User Documentation
• EcoStruxure™ Foxboro™ DCS Access Manager User's Guide (B0750AD)
• EcoStruxure™ Foxboro™ DCS Bulk Data Editor User's Guide (B0750AF)
• EcoStruxure™ Foxboro™ DCS Configuration Utilities User's Guide (B0750AZ)
• EcoStruxure™ Foxboro™ DCS Control Core Services v9.8 Software Installation
Guide (B0700TP)
• EcoStruxure™ Foxboro™ DCS Control Core Services v9.8 Software Release
Notes (B0700TR)
• EcoStruxure™ Foxboro™ DCS Control Database Deployment User’s Guide
(B0750AJ)
• EcoStruxure™ Foxboro™ DCS Control Software Deployment Guide (B0750BA)
• EcoStruxure™ Foxboro™ DCS Control Software v8.0 Release Notes (B0750TQ)
• EcoStruxure™ Foxboro™ DCS Security for Windows 10 21H2 LTSC and Windows
Server 2022 Implementation Guide (B0700WX)
• EcoStruxure™ Foxboro™ DCS Process Automation System Hardware
Configuration User's Guide (B0750BB)
• EcoStruxure™ Foxboro™ DCS Window Construction User's Guide (B0750AS)
• EcoStruxure™ Foxboro™ DCS Trellix ENS 10.7 and ePO 5.10 SP1 for Windows
Server 2022 Installation and User’s Guide (B0700XD)
• EcoStruxure™ Foxboro™ DCS Veritas System Recovery 23 User’s Guide
(B0700WY)
Find the latest version of these documents on the Global Customer Support website.

Control Software Installation and Control Core Services

Compatibility
This document applies to Foxboro DCS Control Software 8.0. For installation
information for earlier versions of Control Software, see the document versions in this
table.

10 B0750TP, Rev E
Preface Control Software v8.0 Installation Guide

Requires
I/A Series
Software/
Control Core
Document Installs InFusion/FCS Services Release
Number B0750RA Title /Control Software Version Notes
B0750RA, Foxboro Evo Control Software Control Software v6.3 v8.8, v9.0, v9.1, B0750SM
rev. W Installation Guide v9.2, or v9.3
B0750RA, Foxboro Evo Control Software Control Software v7.0 v8.8, v9.0, v9.1, B0750SS
rev. Y Installation Guide v9.2, or v9.3
B0750RA, Foxboro Evo Control Software Control Software v7.1 v8.8, v9.0, v9.1, B0750ST
rev. Z Installation Guide v9.2, v9.3, or
v9.4
B0750RA, Foxboro DCS Control Software Control Software v7.2 v9.1, v9.2, v9.3, B0750SW
rev. AC Installation Guide v9.4 or v9.5
B0750RA, Foxboro DCS Control Software Control Software v7.3 v9.6 B0750SX
rev. AD Installation Guide
B0750RA, Foxboro DCS Control Software Control Software v7.4 v9.6 B0750SY
rev. AE Installation Guide
B0750RA, Foxboro DCS Control Software Control Software v7.5 v9.6, v9.7 B0750SZ
rev. AF Installation Guide

AVEVA User Documentation

Control Software is based on the AVEVA™ System Platform architecture and
incorporates several AVEVA products. Relevant AVEVA documentation is installed
with this software and is available in these locations:
• Documentation: Start > AVEVA Documentation
• AVEVA Online Help: Start > AVEVA > AVEVA Help
• Documentation folder at D:\Program Files\ArchestrA\Framework
\Docs...
• Documentation is also located at D:\Program Files\Wonderware\InTouch.

Global Customer Support

For support, visit https://pasupport.se.com (registration required).

We Welcome Your Comments

To help us improve documentation, we want to know about any corrections,
clarifications, or further information you would find useful. Send us an email at
[email protected].
This email address is only for documentation feedback. If you have a technical
problem or question, contact Global Customer Support, page 11.

B0750TP, Rev E 11
Control Software v8.0 Installation Guide Chapter 1: Planning Your Installation

Chapter 1: Planning Your Installation

This chapter provides a general overview of installing Foxboro DCS™ Control
Software (CS) v8.0.

Installation/Upgrade Overview
Control Software v8.0 supports Windows 10 21H2 LTSC and Windows Server 2022
systems on Enterprise or Local Edition configurations.
• A Local Edition/Standard system refers to a Windows workgroup-based setup.
References to Standard Edition also apply to Local Edition.
• An Enterprise Edition/Security Enhanced configuration refers to a Windows
domain-based setup. References to Security Enhanced also apply to Enterprise
Edition.

New Installation (Day 0 Installation)

Control Software v8.0 supports new installations on workstations (with Server 2022 or
Windows 10 21H2 LTSC operating systems) with or without Control Core Services
(CCS) installed.
However, if a workstation has Control Core Services installed, it must be a supported
version. For a list of supported versions, see Control Software Installation and Control
Core Services Compatibility, page 10. Verify that there is at least one workstation with
Control Core Services connected to the Control Network that will act as the Host to
controllers.
For installation of a Galaxy or Historian, we recommend Windows Server 2022.
Although, the Galaxy and Historian can be hosted by a single server, we recommend
that you have dedicated hardware for each machine hosting a major database
(Galaxy, Historian, System Advisor). This is something to consider when hosting
multiple VMs on a V91 or V95 server. For supported architectures, see EcoStruxure™
Foxboro™ DCS Control Software Deployment Guide (B0750BA).
NOTE: If the Compound Summary Access (CSA) server was relocated as part of
the Control Core Services installation, see EcoStruxure™ Foxboro™ DCS Control
Core Services v9.8 Software Installation Guide (B0700TP).

Upgrade Installation
Control Software v8.0 does not support direct upgrades from previous Control
Software versions. To upgrade or migrate previous versions to Control Software v8.0,
you must use a backup of the Control Software galaxy database and migrate it onto a
Control Software v8.0 galaxy repository machine. See Chapter 6: Upgrading to
Foxboro DCS Control Software v8.0 (Day 0 Installation), page 76.
CS 8.0 supports upgrade/migration from CS v6.3, v7.2 and v7.5 versions only.
Workstations with an earlier Control Software version must upgrade to one of the
supported versions before taking a backup for migrating to CS 8.0.
NOTE: For a workstation that needs to have both Control Core Services and
Control Software, Control Core Services has to be installed before Control
Software.

12 B0750TP, Rev E
Chapter 1: Planning Your Installation Control Software v8.0 Installation Guide

NOTE: Control Software operations require the domain controller to be available

at all times. In order to maintain the required high availability of the domain
controller subsystem for Foxboro DCS, configure the system as described in this
section.
Configure the system so there is no single point of failure in the domain controller
subsystem. The domain controller subsystem must always be accessible from
operator workstations, even when a single server or a single network switch is
temporarily unavailable, or a single network cable is disconnected. Specifically:
• Have at least two domain controller servers - a Primary domain controller (PDC)
and a Secondary domain controller (SDC). Depending on the system’s topology,
more than two domain controller servers might be required.
• Have at least two independent networks between the domain controller servers
and every operator workstation in the Foxboro DCS. To do this, do one of these
options:
◦ Deploy a redundant Auxiliary Control Network (ACN) if the ACN is used to
connect domain controller servers with the operator workstations.
◦ Deploy the domain controllers on the redundant Foxboro DCS Control
Network (recommended).

B0750TP, Rev E 13
Control Software v8.0 Installation Guide Chapter 1: Planning Your Installation

Control Software v8.0 Installation

Figure 1 - New Foxboro DCS Control Software v8.0 Installation

A See Chapter 2: Installing Foxboro DCS Control Software v8.0 on Primary Domain Controllers,
page 17

B See Post-installation Procedure for Primary Domain Controllers, page 19

C See Chapter 3: Installing Foxboro DCS Control Software, page 25

D See Chapter 4: Configuring Foxboro DCS Control Software, page 54

E See Chapter 5: Galaxy Preparation, page 69

14 B0750TP, Rev E
Chapter 1: Planning Your Installation Control Software v8.0 Installation Guide

Installation Considerations
Minimum System Requirements
For information about system requirements, see EcoStruxure™ Foxboro™ DCS
Control Editors (PSS 41S-10EDITOR).

Installation/Upgrade Scenarios
Consider these significant points when installing or upgrading to Control Software
v8.0.
Every Control Software DCS system has one computer running Windows Server
2022® operating system to host the Galaxy database. We recommend that the system
has another dedicated server to run the AVEVA Historian software.
The only case where a Galaxy database can be installed through custom installation
on a non-server class machine that is not running Windows Server 2022 operating
system is for the FDE Instrument Edition configuration workstation. In this case, the
Galaxy database can be installed on a workstation running the Windows 10 21H2
LTSC operating system. However, the latter is only used for offline configuration, and
is not connected to a run-time system.
Install Control Software only on:
• Stations with Control Core Services software v9.8 or later.
• Stations with Windows 10 21H2 LTSC or Windows Server 2022 operating
systems that do not have Control Core Services software installed (Off-Platform).
For information about CCS and CS compatibility, see the applicable Release Notes
document shipped with Control Software and Control Software Installation and
Control Core Services Compatibility, page 10.
NOTE: For stations with both Control Core Services and Control Software, Control
Core Services must be installed first using the CCS media.
For more information on configuring users and user groups in Enterprise Edition or
Security Enhanced Environments, see EcoStruxure™ Foxboro™ DCS Security for
Windows 10 21H2 LTSC and Windows Server 2022 Implementation Guide
(B0700WX).

Typical Foxboro DCS Control Software User Roles

As part of security support, user groups are used in Control Core Services v9.1 and
later.
• The FCSEngineering and FCSOperators groups need to be used for all the
operations on stations with Control Core Services v9.1 or later.
NOTE:
You must not operate Control Software v8.0 from any other user profiles other
than the two groups, the FCSEngineering and FCSOperators groups.
In a Control Core Services Enterprise Edition system, users are created on the
PDC. Active Directory Domain Services automatically synchronize the PDC
with the other Domain Controllers. The Network Account configuration is
required only for PDC machines.

B0750TP, Rev E 15
Control Software v8.0 Installation Guide Chapter 1: Planning Your Installation

Creating FCSEngineering/FCSOperators Groups

1. Expand these tree items: Administrative Tools > Active Directory Users and
Computers > Domain Name (Ex: Foxboro.local) > Foxboro > Accounts >
Users > Standard.
2. To add the user to the appropriate group (FCSEngineering and FCSOperators
Groups), right-click the newly-added user name and select Add to group.

Upgrade Considerations
Consider these conditions and develop an upgrade plan if you are performing an
upgrade on a running plant.
• Systems with earlier versions of InFusion/FCS (except FCS v6.3) need to be first
upgraded to Control Software v7.2.MP2 before they can be upgraded to Control
Software v8.0. You need to follow the appropriate upgrade path, depending on
your version of InFusion, FCS, or Control Software. For more information, see the
Control Software v6.3 or v7.2 installation guide referenced in Control Software
Installation and Control Core Services Compatibility, page 10.
• When upgrading or migrating earlier versions of InFusion, FCS, or CS to CS v8.0,
if the earlier Galaxy had one or more optional media such as Field Device Expert,
Field Device Expert Workshop, DeviceNet, or Condition Advisor installed, then
you must install the latest versions of these media on the CS v8.0 machine before
proceeding with the configuration, including Pre-Configuration and Galaxy
Preparation.

Upgrading to Foxboro DCS Control HMI v8.0

Control HMI v8.0 is shipped with the Control HMI v8.0 application template. You must
upgrade Foxboro DCS Control HMI separately from the main set of Control Software
v8.0 packages.

Upgrading to Foxboro DCS Control HMI v8.0 using a Clean Installation

1. Back up all necessary Control HMI files.
For more information, see Chapter 6: Upgrading to Foxboro DCS Control
Software v8.0 (Day 0 Installation), page 76.
2. After installing Control Software v8.0, upgrade the Control HMI Application.
For more information, see Chapter 7: Upgrading to Latest Foxboro DCS Control
HMI Version, page 107.

Control Software v8.0 License

See Appendix C: Installing AVEVA Licenses, page 150 for information about the
Control Software 8.0 licenses.

16 B0750TP, Rev E
Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Primary Domain Controllers Control Software v8.0 Installation Guide

Chapter 2: Installing Foxboro DCS Control Software

v8.0 on Primary Domain Controllers
This chapter is applicable for only Enterprise Edition setups involving Windows
Domain Controllers. For Local Edition and Standalone setups, skip this chapter.
You must install Control Software v8.0 onto Primary Domain Controllers (PDC) on or
off the Foxboro DCS Control Network (Control Network). These are Active Directory
servers needed for Enterprise Edition Control Core Services software. Perform this
procedure for both new installations and upgrades.

Installing Control Software

After installing and configuring Control Core Services (CCS) Active Directory
components, you must install and configure Control Software (CS) Active directory
components by running the Control Software installation media.
See Chapter 9: Installation Troubleshooting, page 128 for a list of known security
concerns and fixes.
NOTE: If the station is being managed by Trellix® ePolicy Orchestrator (ePO) and
Trellix Application Control is deployed with it, perform the steps to import and
install appropriate policies for Foxboro DCS Control Software before continuing
the installation. For information on ePO and allowlisting procedures, see Related
Documents, page 10 for the appropriate EndPoint Protection document.
These steps need to be run on both a new PDC install as well as a PDC being
upgraded from a previous version of CCS/CS.
Perform these steps for new installs and upgrades:

Table 1 - PDC Installation Overview

PDC Procedure
PDC 1. Install CCS v9.8.
New at CCS v9.8/CS 2. Install CS v8.0.
v8.0 3. Run the Foxboro DCS AD Configurator.
PDC 1. Upgrade to CCS 9.8. Refer to EcoStruxure™
Foxboro™ DCS Control Core Services v9.8 Software
Upgrades from the Installation Guide (B0700TP).
previous supported
CCS/CS version to 2. Install CS v8.0.
CCS v9.8/CS 8.0 3. Run the Foxboro DCS AD Configurator.

1. Log in to the Primary Domain Controller using a Domain Administrator account:

• Use the IADomainAdmin (or equivalent) account, if the PDC is on the
Control Network.
• Use the Domain Administrator account if the PDC is on the Off-Control
Network.
2. Insert the Control Software v8.0 DVD into the DVD drive.

B0750TP, Rev E 17
 Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Control Software v8.0 Installation Guide Primary Domain Controllers

3. Navigate to the DVD contents and run Setup.exe.

After all the components are installed, the Foxboro DCS AD Configurator is
launched automatically.

4. Enter a new user name (for example: IAServices or any other name of your
choice) and password that will be used as a Control Software Network Account,
then click Configure.

Overview of Group Managed Service Accounts (gMSA)

Control software creates a gMSA service account named FoxboroGMSA and
configures the Services to run with gMSA login. A group Managed Service Account
(gMSA) is a managed domain account that provides automatic password
management, simplified service principal name (SPN) management, the ability to
delegate the management to other administrators and extends these functionality over
multiple servers.
In most of the infrastructures, service accounts are typical user accounts with the
“Password never expire” option. Since these service accounts are not used regularly,
administrators must keep track of these accounts and their credentials so that
engineers do not face the issue of outdated or misplaced service account credentials.
Otherwise, you must reset the password of the service accounts, and you will need to
update services, databases, and application settings to get the application or services
running again. By using a gMSA service account, Control Software engineers do not
need to reconfigure the CS service login information anymore. Instead, Microsoft
manages the password changes and reconfigures the services automatically.
For more information about gMSA, refer to the Group Managed Service Accounts
Overview information on the Microsoft website.

18 B0750TP, Rev E
Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Primary Domain Controllers Control Software v8.0 Installation Guide

Post-installation Procedure for Primary Domain Controllers

These procedures will complete the Control Software v8.0 installation on Primary
Domain Controllers.
To complete the installation of CS v8.0 on the Domain Controller, user accounts must
be created. This procedure is only performed in the Primary Domain Controller. The
new user accounts will automatically sync with the Secondary Domain Controllers.

Creating FCSEngineering and FCSOperators User Accounts

The user groups FCSEngineering and FCSOperators are the only groups you can
use for Control Software operations.
FCSEngineering and FCSOperators are supported on both Off-Control Network and
On-Control Network PDCs.
On stations with Windows Server 2022 operating systems, the groups that will be
used with Control Software are located in <domain>\Foxboro\Accounts\Groups
\FCSGroups in Active Directory Users and Computers.

Create the user accounts for this Primary Domain Controller (PDC). Do this for each
user:
NOTE: We recommend you create at least one user in the FCSEngineering group
and one user in the FCSoperators group in order to use during FAT/SAT.

B0750TP, Rev E 19
 Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Control Software v8.0 Installation Guide Primary Domain Controllers

1. On the PDC, select Administrative Tools, then open Active Directory Users
and Computers.
2. Navigate to <Domain Name>\Foxboro\Accounts\Users\Standard. Right-
click Standard and select New > User.
The New Object - User dialog box appears.

3. Enter the appropriate values into the First name, Full name, and User logon
name fields.
4. Click Next.
5. Enter the password into the Password and Confirm Password fields. Select the
remaining checkboxes according to your company’s security policy. When done,
click Next.

20 B0750TP, Rev E
Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Primary Domain Controllers Control Software v8.0 Installation Guide

6. Click Finish.
7. In the Active Directory Users and Computers window, double-click the new
username to open the Properties dialog box.

B0750TP, Rev E 21
 Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Control Software v8.0 Installation Guide Primary Domain Controllers

8. Select the Member Of tab and click Add.

22 B0750TP, Rev E
Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Primary Domain Controllers Control Software v8.0 Installation Guide

9. Enter FCS and click Check Names.

10. Select the desired FCS standard user group (for example, FCSEngineering) and
click OK.
11. Click OK again on the Properties dialog box.
12. Repeat these steps for as many users as desired.

Updating the Control Software Network Account

This procedure describes how to update the Control Software network account on the
Primary Domain Controller.
1. On the PDC, click Start > Foxboro DCS > Active Directory Configurator.
The Foxboro DCS AD Configurator dialog appears.

B0750TP, Rev E 23
 Chapter 2: Installing Foxboro DCS Control Software v8.0 on
Control Software v8.0 Installation Guide Primary Domain Controllers

2. Enter the new Control Software Network Account username and password.

3. Click Configure.

Updating the Control Software Network Account on Domain

Clients

NOTICE
POTENTIAL UNDESIRED SYSTEM BEHAVIOR
You must update the Control Software Network Account whenever you modify the
“Foxboro DCS Control Software Network Account” on the Primary Domain
Controller. This helps ensure off node communications between various critical
tasks are maintained and continue to work successfully.
Failure to follow these instructions can result in undesired system behavior.

1. Click the Start menu, and enter Change Network Account.

2. In the Change Network Account dialog box, clear the Create Local Account
checkbox and enter the Domain NetBIOS name in the Domain or Local
Machine Name field.
3. Enter the new CS Network Account username and password and then click OK.

24 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

Chapter 3: Installing Foxboro DCS Control Software

This chapter describes how to install Control Software on stations that have never had
Control Software installed.
If you are installing Control Software as part of a CCS Day 0 install, see Chapter 6:
Upgrading to Foxboro DCS Control Software v8.0 (Day 0 Installation), page 76.
This chapter includes instructions on:
• Pre-installation, page 25
• Installation Procedure for All Stations, page 31
• Installing the Latest Software Updates, page 41
• Reinstalling Foxboro DCS Control Software, page 41
• Modifying and Uninstalling Foxboro DCS Control Software, page 43
However, the instructions in this chapter are not related directly to any of the
predefined configurations. Each possible software component is shown with specific
user actions when necessary.

Pre-installation
Pre-installation Notes
If you are installing a configuration that needs Control Core Services software:
• You must install the Control Core Services software first. The Control Software
installer does not install Control Core Services.
• If you are using FoxView™ instead of Control HMI, you must also install the
FoxView software before proceeding with the Control Software installation.
• If you already have FoxView installed and decide to install the Control HMI as
part of the Control Software installation, you do not need to uninstall the FoxView
software.
You will be prompted to select either one or both the Control HMI/Foxview to be
started in the configurator window when the workstation reboots.
• If you are installing Control Software on an Enterprise system that has been
added to the PDC via the Day1 procedure (for example, an on-control workstation
added via the Day1 procedure), perform the steps in Configuring GMSA on a
Newly Added On-Platform Workstation in the Active Directory, page 26.

NOTICE
POTENTIAL UNSUCCESSFUL INSTALLATION
To install Control Software on an Enterprise system that has been added to the
PDC via the Day1 procedure, perform the steps to configure the GMSA on a
newly added on-platform station in the active directory.
Failure to follow these instructions can result in unsuccessful
installation.

For AVEVA Historian Client:

• If you install the AVEVA Historian Client software and later decide to install
Microsoft Excel software package, then you have to uninstall the AVEVA
Historian Client software first. If the AVEVA Historian Client software installation
detects Excel is already installed, it automatically installs add-ons to this tool.
Additional considerations:

B0750TP, Rev E 25
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

• To install Control Software on an Enterprise system, log on to the station as a

member of the “IA Installer” group such as “ccsinstaller”.
• If you are installing Control Software on an Enterprise System that is an off-
control workstation, perform the steps in Adding an Off-Platform Workstation in
the Active Directory, page 27.

NOTICE
POTENTIAL UNSUCCESSFUL INSTALLATION
To install Control Software on an Enterprise System that is an off-control
workstation perform the steps to add an off-platform station in the active
directory.
Failure to follow these instructions can result in unsuccessful
installation.

• Do not update any third-party software after the Control Software installation
procedure is complete. This includes Microsoft Visio software, Microsoft SQL
Server software, and AVEVA System Platform software. Upgrades to the Control
Software workstations need to be managed through planned updates.
• (For Security Enhanced or Enterprise edition Clients only) In Control Core
Services software v9.1 or later, the FCSOperators and FCSEngineers groups are
used to operate and engineer for workstation logins.
The Plant Operator or Plant Engineers groups do not have privileges to access
any of the Control Software options. The FCS groups inherit the privileges
associated with the traditional I/A Series groups, such as Plant Operator or Plant
Engineers as well as additional privileges to access the Control Software related
operations.
• If the station is being managed by Trellix® ePolicy Orchestrator (ePO) and Trellix
Application Control is deployed with it, perform the steps to import and install
appropriate policies for Foxboro DCS Control Software before continuing the
installation. For information on ePO and allowlisting procedures, see Related
Documents, page 10 for the appropriate EndPoint Protection document.

NIC Card Binding Order

Before installing Control Software, the NIC order might have to be manually set. For
more information, see EcoStruxure™ Foxboro™ DCS Control Software Deployment
Guide (B0750BA).

Configuring GMSA on a Newly Added On-Platform Workstation in

the Active Directory
1. Log on to the PDC using the domain controller account.

26 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

2. For every on-platform workstation added via Day1 on the PDC, do the following:
a. To open the Active Directory Users and Computers console, go to Start
Run, then enter dsa.msc.
b. Navigate to the IA Computers OU under <domain>\Foxboro.
c. Double-click the workstation added via Day1.
d. Click the Member Of tab.
e. Click Add, then add the FoxboroGMSAComputers group.
The workstation is now part of the FoxboroGMSAComputers group.

Adding an Off-Platform Workstation in the Active Directory

If your Galaxy configuration contains an off-platform workstation that is not part of the
CCS Commit, you must add it to the IA Computers group in Active Directory (AD)
and make it a member of FoxboroGMSAComputers. If the machine is not part of
these groups, installation of Control Software prerequisites such as SQL Server will
be unsuccessful.
To add a computer to the required Active Directory groups:
1. Log on to the PDC using domain administrator credentials.
2. In the Primary Domain Controller (PDC), open Active Directory Users and
Computers then go to IA Computers under the Forest/Domain (for example:
offmesh.local).
All computers that are part of the CCS Commit are seen here.

B0750TP, Rev E 27
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

3. Right-click IA Computers and click New > Computer.

4. Provide the Computer name (for example: OFFSRV) and click OK.

5. Right-click the newly added computer (for example: OFFSRV), and click
Properties, then click the Member of tab.

6. Click Add.. in the Select Groups dialog and enter FoxboroGMSAComputers.

28 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

7. Click Check Names and click OK to close the dialog.

8. Verify that FoxboroGMSAComputers is listed in the Member of list and click

OK.
The new Workstation is now part of the IA Computers and
FoxboroGMSAComputers groups.

9. Add this workstation to the domain using a user account that is a member of the
Domain Admins group.

Pre-installation for Enterprise Edition CCS Stations Connecting to

Off-Control Network Galaxy Repository
All workstations with Enterprise Edition Control Core Services software that connect
to Off-Control Network Galaxy Repository (GR) must have the GR entry added to the
hosts file. This helps ensure network connectivity between Off-Control Network GR
station reaches the Foxboro DCS client workstations on the Control Network and vice-
versa.

B0750TP, Rev E 29
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

NOTICE
POTENTIAL SYSTEM FAILURE
Add the Galaxy Repository station to the “hosts” file. If you do not, it will result in
system failure.
Failure to follow these instructions can result in system failure.

To help prevent any detected system issues, perform these pre-installation

procedures.

On the Off-Control Network Galaxy Repository Station

1. Verify that the Off-control network Galaxy Repository station is added to the
IA Computers organizational unit.
It can be found under Administrative Tools > Active Directory Users and
Computers > Domain Name (FOXBORO.local) > Foxboro.
2. On the Galaxy Repository station, open the hosts file, located in the %
systemroot%\system32\drivers\etc directory.
3. Remove any entries pointing to the client station.
For example, if the client station’s ID is AWCL01, remove any entries related to it
available in the “hosts” file.
4. For each client, add an entry for that client with its domain IP address.
For example:
181.182.22.2 AWCL01
181.182.22.3 AWCL02
181.182.22.4 AWCL03
where AWCL01, AWCL02, and AWCL03 are the Galaxy Repository client
stations.
5. Add an entry for the PDC and SDC with its domain IP address.
For example:
181.182.11.1 AWPDC1
181.182.11.2 AWSDC1
6. Save and close the hosts file.
NOTE: This procedure is also applicable for all domain clients which are
connected to Off-control network domain controllers.

On Each On-Control Network Galaxy Repository Client Station

1. On each Galaxy Repository client station, open the hosts file, located in the %
systemroot%\system32\drivers\etc directory.
2. Remove any entries pointing to the Galaxy Repository station.
For example, if Galaxy Repository station is AWGR01, remove any entries
related to it in the hosts file
3. Add an entry for the Galaxy Repository station with its domain IP address. For
example:
181.182.22.1 AWGR01
where AWGR01 is the Galaxy Repository station.
4. Save and close the hosts file.

30 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

Installation Considerations for Enterprise Edition Foxboro DCS

Workstations
Before installing the Control Software on a workstation with Enterprise Edition Control
Core Services software, you must perform these tasks:
1. Disable the virus scan.
NOTE: The virus scan has to be enabled only after the successful completion
of Installation and Configuration process of the Control Software.
For more information, see Enabling and Disabling Virus Scanning Software, page
141.
2. Verify that the CCS software is installed properly on the workstation before
installing Control Software. Perform this step on all Foxboro DCS workstations.
a. On each station where Control Software will be installed, navigate to the
Administrators Properties dialog box.
On the server, select Control Panel > Administrative Tools > Computer
Management > System Tools > Local Users and Groups > Groups >
Administrators.
b. Verify that these Domain members are clearly displayed in legible form:
• Domain Admins
• IA Installer
NOTE: These members can vary depending on the Primary Domain
Controller (PDC) user/groups setup.
c. If the members are not listed or the member names are obfuscated, correct
the Control Core Services software installation before continuing with the
Control Software installation.
For more information, see EcoStruxure™ Foxboro™ DCS Control Core
Services v9.8 Software Release Notes (B0700TR).

Installation Procedure for All Stations

This section discusses how to perform new installations of Control Software onto
stations that do not have Control Software components installed on them.
These instructions apply to all Foxboro DCS Enterprise and Local Edition installs ,
unless otherwise specified in the step.
NOTE: To keep these instructions manageable, these procedures do not show
any dialog boxes that open automatically and do not need any action. These
dialog boxes close automatically when the needed installation actions have taken
place.
NOTE: For Enterprise Edition installations, you must be logged into the station
with a user account that is a member of the IA Installer group, such as
CCSInstaller.
1. Insert the Control Software media into the DVD drive.
If the installation does not start automatically, navigate to the DVD’s top level
directory and run Setup.exe.
2. The Installation starts. Follow the prompts that appear on the Install dialogs.
3. The System Check dialog box appears. If prompted, click Reboot to restart the
workstation.

B0750TP, Rev E 31
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

The workstation reboots and the installation starts automatically. If not, browse to
and click on Setup.exe to restart the installation. Review the system messages
and click Next.

32 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

4. The Control Software Network Account dialog box appears.

a. Clear the Create Local Account checkbox.

b. While installing on a station with Enterprise Edition CCS installed, use the
appropriate user account and password.
For example:
• Domain/Local Machine: <NetBIOS Name>
• Username: <Control Software Network Account>
• Password: <Password>
The correct NetBIOS Name must be used as the Domain/Local Machine
entry. The NetBIOS Name can be found on the PDC. Navigate to Active
Directory Users and Computers on the PDC and right-click on the
Domain Name shown and then select properties from the menu. The
NetBIOS name is found in the “Domain name (pre-Windows 2000)”
under the General tab in the Properties window.
NOTE: The Galaxy Repository workstation, and all other workstations
connected to it, must use the same Domain/Local Machine, Username
and Password during this procedure. Verify that the domain name used
is identical on all machines.
NOTE: While setting up the Control Software Network Account on a
Foxboro DCS system with Enterprise Edition CCS, you might encounter
a message saying The password policy for this account allows the
password to expire and to be changed. This message is displayed
even when the User ID policy is set to Never Expire. You can ignore this
message. Click Yes to proceed with the installation.

B0750TP, Rev E 33
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

c. While installing on a station with Local Edition CCS installed, select the Local
Machine name in the Domain/Local Machine field and click Next.
The Selection dialog box appears.
5. Select the type of installation that you need from the list.
For the software components and features that comprise each option, see
Appendix B: QuickPick Software Components, page 145
• Selection of multiple options is allowed for inclusion of optional components.
• Historical Data Collector, Engineering Client, InTouch Access
Anywhere and Control HMI (Development) are the optional components.
• If you want to make changes in the standard configuration of the selected
options, select Custom.
After you make your selections, click Next.

If you did not select Custom on the Selection dialog box, the Product
Verification dialog box appears. Proceed to Step 6.
If you did select Custom on the Selection dialog box or the Customize
Installation checkbox on the Product Verification dialog box, the Customize
Installation dialog box appears. Proceed to Step 7.
6. The Selection dialog box, displays the components of the selected installation.

34 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

If you want to make any changes in the displayed configuration or the destination
folder, select the Customize Installation checkbox and click Next.

7. On the Customize Installation dialog box, select any combination of installable

features.
Any feature that is not supported in the current configuration will not be available
for selection on this dialog box. It will appear as unavailable.
You can also change the destination folder by clicking Browse on this dialog box.
The destination folder specified here is used while installing all software, with the
exception of SQL Server software and Control HMI software.
After making the selections, click Next. The Directory dialog box appears.

B0750TP, Rev E 35
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

8. The Directory dialog box appears. Select where to install the SQL Server
software.
Optionally, you can select the checkbox to install SQL replication services.
• SQL replication services is used by Condition Advisor. If you are planning to
install Condition Advisor, you can install SQL replication services with the
SQL installation by selecting the checkbox. Otherwise, SQL replication
services will be installed by Condition Advisor software as part of the pre-
requisites.
• If SQL Server Standard or Express Edition is already installed, the SQL
Server installation path will not be available to edit.
After modifying the directories as needed, click Next.

The Prerequisite Installation dialog box appears, which lists the prerequisite
software mandatory for the installation.
9. Click Install Prerequisites to install the mandatory software.
NOTE: The install process prompts you for the Control Software media when
the required software is on that media.

36 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

10. Insert the Control Software Database Management DVD when requested and
click Browse to locate the installer file.
NOTE: If any of the Microsoft SQL Server standard or express edition
installations are unsuccessful, you need to install it manually before
continuing with the Control Software installation. See Appendix E: Installing
Microsoft SQL Server 2019, page 170.

The installation of SQL Server proceeds automatically without any user action.

B0750TP, Rev E 37
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

11. A prompt appears to insert the Control Software Office media. Insert the Control
Software Office DVD into DVD drive and click Browse to locate the installer file
(setup.exe) on the DVD. Click OK after you have selected the file.

12. When the prerequisites are installed and the status of each prerequisite has
changed to met, click Next.
The Dependent Components Installation dialog box appears.
13. Click Install Components.

The Browse for Media dialog box appears.

14. Insert the AVEVA System Platform DVD into the DVD drive and click Browse to
locate the installer file (setup.exe) on the DVD. Click OK after you have selected
the file.

38 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

The AVEVA System Platform installation proceeds.

After the components are installed, the status of each component changes to
met.
15. Click Next.

The Ready to Install Application dialog box appears.

B0750TP, Rev E 39
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

16. Click Install.

17. After all components are installed, the Installation Complete dialog box
appears, click Configure to start the configuration process. To continue, see
Chapter 4: Configuring Foxboro DCS Control Software, page 54.

40 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

Installing the Latest Software Updates

Updates for Control Software the latest service advisories are posted on Global
Customer Support at https://pasupport.se.com (registration required). Visit this site
periodically for the latest updates.
NOTE: We also recommend that you see “Appendix A: Security Updates" in
EcoStruxure™ Foxboro™ DCS Control Software v8.0 Release Notes (B0750TQ)
and install any updates.

Reinstalling Foxboro DCS Control Software

NOTE: This procedure is NOT intended for the recovery of a single workstation,
such as the Galaxy host station. It is not intended to be used for a planned
hardware upgrade to a single station.
If you detect problems and suspect that perhaps the Control Software installation was
not clean, this procedure will allow you to remove and re-install Control Software while
preserving your application data. Perform the steps in the order in which they are
presented in the checklist.
This procedure saves and restores the entire Galaxy database. If you just want to
back up individual objects, see the sections on exporting and importing objects in
EcoStruxure™ Foxboro™ DCS Control Software Deployment Guide (B0750BA).
This procedure is for the specific purpose stated and should not be used if you plan to
perform any other software installation, such as restoring the station to its factory
image and performing a Control Core Services software Day 0 or Day 1 installation,
since doing so could introduce mismatches with what was captured in the Galaxy
database.
1. Back up the entire Galaxy.
a. From the OCMC, expand the Galaxy Database tree node.
b. Select the database you want to back up, right-click the Galaxy, and select
Backup.
c. Supply the filename you want to use for the name of the backup file.
This captures the current deployment states of all the objects.
2. Select all Control Software objects that are deployed by each station
(workstation and server) as undeployed.
For example, Equipment Units, Compounds, Strategies.
a. Open the IDE and connect to the Galaxy.
b. Open the System Platform IDE. For each platform under the Deployment
view, right-click and select Deploy.
c. In the Deploy Status Mismatch field, select the Mark as Deployed
checkbox and click OK.
d. In the Deployment window, right-click at the top of each tree of Foxboro
DCS objects, then select Deploy Utilities > Synchronize Deploy Status.
e. In the Deploy Status Synch Utility window, select Undeployed > Sync.
NOTE: This will leave the control blocks running in their current state on
the physical control processors within the Foxboro DCS system.

B0750TP, Rev E 41
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

3. Undeploy each workstation’s platform object, application engines, DI object(s),

and so on.
Do a cascade undeploy starting at each workstation’s platform object. Platform
objects typically have a name such as “letterbug_Plat”.
4. Undeploy the server’s platform, app engines, DI object(s), and so on.
Do a cascade undeploy starting at the server’s platform object.
5. Delete the Galaxy database.
a. Open the System Platform IDE (Start > AVEVA System Platform > System
Platform IDE).
b. Select the Galaxy name and click Delete.
6. Delete the Galaxy Sync Service database.
a. Select Programs > Microsoft SQL Server Tools 19. Right-click SQL
Server Management Studio and select Run as administrator, then click
Connect.
NOTE: Connect to server AWLBUG and not to AWLBUG
\INFUSIONSECURITY.
b. Expand the Databases entry in the tree.
c. Right-click the InFusionDeployedDb database and select Delete.
d. Select the Close existing connections checkbox, then click OK.

Reinstalling at Each Client Workstation

1. Uninstall Condition Advisor if present on the system.
2. Uninstall Field Device Expert software packs for Foundation Fieldbus. HART, and
Profibus if present. Uninstall DeviceNet if present.
For more information, see the installation guide of the respective software packs
(document references are available in Chapter 5: Galaxy Preparation, page 69).
3. Insert the Control Software DVD and click Uninstall.

Reinstalling at the Galaxy Database Server

1. Uninstall Condition Advisor if present on the system.
2. Uninstall Field Device Expert software packs for Foundation Fieldbus. HART, and
Profibus if present. Uninstall DeviceNet if present.
For more information, see the installation guide of the respective software packs
(document references are available in Chapter 5: Galaxy Preparation, page 69).
3. Insert the Control Software DVD. Click Uninstall.

Reinstalling Control Software

1. Confirm you have completed the steps in these procedures:
• Reinstalling Foxboro DCS Control Software, page 41
• Reinstalling at Each Client Workstation, page 42
• Reinstalling at the Galaxy Database Server, page 42

42 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

2. Starting with the Galaxy database server and then on each client workstation,
insert the Control Software v8.0 DVD. Select the configuration and click Install.
3. Install the Control Software v8.0 as described in Installation Procedure for All
Stations, page 31.
4. Refresh the History and Security database.
a. From the IDE on the Galaxy database server, click Galaxy on the top menu
bar.
b. From the menu, select Refresh History and Security Database.
This operation can take 20 to 60 minutes per CP.

Modifying and Uninstalling Foxboro DCS Control Software

After installing Control Software, you can perform these operations:
• Modify
• Remove Control Software
NOTE: During these procedures, if the Historian component is installed on the
machine, shut down and disable Historian from the Operations Control before
stopping 'aahClientAccessPoint' service.

Modifying the Existing Installation

You can modify an existing installation when you want to add any new components or
additional features to the Control Software. This can include AVEVA Historian
components.
1. Disable the virus scan. For more information, see Enabling and Disabling Virus
Scanning Software, page 141.

B0750TP, Rev E 43
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

2. Run the setup.exe file. Select Modify, then click Next.

The Control Software installation continues and performs a series of system

checks.
3. If the system checks are not met, correct them before continuing. When you are
ready to continue, click Next.

The Feature List appears and displays the list of components that are currently
installed.
4. Select the components you want to install, then click Next.

44 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

The Modify Installation Confirmation dialog box appears displaying the

components that you selected to be modified.

5. Click Modify.
The Directory dialog box appears.
6. Select where you want to install the SQL Server software.
If SQL Server Standard or Express Edition is already installed, the SQL Server
installation path will not be available to edit.
After modifying the directories as needed, click Next.

B0750TP, Rev E 45
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

The Prerequisite Installation dialog box appears listing the software needed for
the features of the selected Quick Pick.
7. Click Install Prerequisites. If all prerequisites are met, click Next.

The List of Dependent Components dialog box appears.

8. Click Install Components.

46 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

The Browse for Media dialog box appears.

9. Click Browse to locate the AVEVA System Platform folder. Select setup.exe,
then click OK.

The AVEVA System Platform installation proceeds.

After the dependent components are installed, the List of Dependent
Components dialog box appears again. The status of each component now
changes to met.

B0750TP, Rev E 47
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

10. Click Next. The Control Software installation proceeds, follow the on-screen
prompts.

NOTICE
POTENTIAL DATA LOSS
After the new components are installed, you must run the Galaxy Preparation
process again. The Galaxy configurator does not indicate that a Galaxy
Preparation is needed for these newly added components and the
GalaxyPreparation item in the Galaxy Configurator window will be displayed as
configured. See Chapter 5: Galaxy Preparation, page 69 for more details.
Failure to follow these instructions can result in data loss.

11. The Close Running Applications form appears, close each application
individually as suggested. After all the listed processes are closed, click Try
Again to proceed.

48 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

NOTE: If the Historian component is installed on the machine, shut down and
disable Historian from Operations Control before stopping
'aahClientAccessPoint' service.

B0750TP, Rev E 49
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

12. After all the components are installed, the Completed Form dialog box appears.
Click Finish to complete the installation.

NOTE: You can install any additional software that you need prior to running
the configurator.

Uninstalling Foxboro DCS Control Software

Use one of these methods to uninstall Control Software:
• Control Software installation DVD
• Control Panel
The Control Software uninstall feature does not remove all installed software
components. For example, it does not uninstall all AVEVA software or Microsoft
packages, such as SQL Server software or Microsoft Office Visio. Also, it does not
delete any user-created files, such as the Galaxy Repository database or user-built
Control HMI windows.

50 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

1. If you want to uninstall the Microsoft packages, you can do so using the Control
Panel > Add/Remove feature only after the Control Software is uninstalled.
NOTE: Workstations can have information (for example, configuration data
and objects) in the Galaxy that might be in a deployed state. Before
uninstalling the software, verify if objects deployed to that station are
undeployed from the corresponding Galaxy.
a. Using the IDE, first undeploy all Foxboro DCS objects (for example,
Equipment Units, Compounds, Strategies, etc.), then undeploy the
associated platform, app engines, areas, DI object(s), etc.
Do a cascade undeploy starting at each workstation’s platform object. If you
are uninstalling the Control Software on a server, as well as on other
workstations, verify that you uninstall the server last.
See EcoStruxure™ Foxboro™ DCS Control Software Deployment Guide
(B0750BA) for procedures for backing up and restoring data if you plan to
reinstall Control Software.
2. Delete the Galaxy Repository database.
a. Open the System Platform IDE (Start > AVEVA System Platform > System
Platform IDE).
b. Select the Galaxy name, and click Delete.
3. Delete the Sync Agent database.
a. Select Programs > Microsoft SQL Server Tools 19, right-click SQL Server
Management Studio and select Run as Administrator.
b. Click Connect.
c. Expand the Databases entry in the tree.
d. Right-click the InFusionDeployedDb database and select Delete.
e. Select the Close existing connections checkbox and click OK.
4. Uninstall FDE packs and Condition Advisor.
a. Uninstall any previously installed optional software packs (Foundation
Fieldbus, PROFIBUS, DeviceNet, HART, or Asset Condition Advisor) before
uninstalling Control Software.
b. See the installation guide of the respective software packs (document
references are available under Chapter 5: Galaxy Preparation, page 69).

Uninstalling Using the Foxboro DCS Control Software Installation DVD

1. Run the setup.exe file.

B0750TP, Rev E 51
Control Software v8.0 Installation Guide Chapter 3: Installing Foxboro DCS Control Software

2. Select Remove and follow the prompts.

52 B0750TP, Rev E
Chapter 3: Installing Foxboro DCS Control Software Control Software v8.0 Installation Guide

Uninstalling Using the Control Panel

1. Navigate to Start > Control Panel > Add or Remove Programs.
2. In the list, select Foxboro DCS Control Editors and Control HMI.
3. Click Remove.
4. In the dialog box that appears, select Remove and follow the prompts.

B0750TP, Rev E 53
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

Chapter 4: Configuring Foxboro DCS Control Software

This chapter describes how to configure Control Software after the installation
process is complete.

NOTICE
POTENTIAL UNSUCCESSFUL CONFIGURATION
Use the correct user login to configure Control Software:

Setup Type User

Enterprise Edition A user that is a member of the IA
Installer group.
Local Edition The same user that is used for
installing Control Software.

Failure to follow these instructions can result in an unsuccessful

configuration.

1. Activate the Control Software licenses using the AVEVA License Manager before
Galaxy Preparation, as described in Appendix C: Installing AVEVA Licenses,
page 150.
This is required for the configuration process on the Galaxy Repository station.
However, client stations that connect to the Galaxy Repository server do not
require licenses before the Galaxy Preparation.

54 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

2. To start the Configurator application, click Start > AVEVA > Configurator.
The options that appear in the Configurator depend on your specific
configuration.
NOTE: If this is a new installation, the Galaxy Preparation entries for
DeviceNet, Profibus, and HART are not displayed. Installation of these
packages is described in Chapter 5: Galaxy Preparation, page 69.

3. You need to configure each item in the tree. To enable configuration of an item:
a. Select the item in the left pane.
The configuration information for the item is displayed in the right pane.
b. Click Configure.

The items for which configuration is not allowed are denoted by the icon.
The blue icon represents a pending plugin configuration and the green check
icon represents a configured plugin.
The Configurator dialog box displays a number of configuration activities
that are needed before the server or workstation is ready to use.
If any feature is not configured, an appropriate legend indicator appears.

Configuring the AVEVA Enterprise License Server

The AVEVA Enterprise License Server plug-in needs to be configured before you
begin configuring any other Configurator plug-in. This plug-in defines the location of
the License Server (with activated AVEVA license(s)) that will host the licenses for the
products installed on the workstation.
To do this, select the AVEVA Enterprise License Server plug-in.

B0750TP, Rev E 55
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

By default, the installation process identifies the local computer as the License Server
(Primary Server Name) name and provides the default server ports.

56 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

1. Change the name of the Primary Server Name to point to the correct License
Server in the network
Click Test Connection.

2. If the connection test is successful, the Configure button is enabled.

3. Click Configure.

B0750TP, Rev E 57
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

4. Click OK if prompted for changing the License Server.

License Server configuration is complete.

Configuring the Historian Server

Historian Server configuration is possible only on workstations with AVEVA Historian
installed. You need to configure the AVEVA Historian Server before you begin Galaxy
Preparation.
For more information, see AVEVA User Documentation, page 11.

Selecting Historian Data Path Drive

The Historian database is created by default in the C drive: C:\Historian\Data. If
you want to create the Historian database on a different drive that has more space,
you can modify the path.
1. In the Configurator tree view, select AVEVA Historian > Server.

58 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

2. In the Data Path field, click ..., then select a new path to create the database in
the desired location.
You do not need to change the database SQL path.
Control Software supports historizing Alarms and Events in AVEVA Historian. If
you plan to use AVEVA Historian to historize Alarms and Events, verify that High-
speed Historian blocks is selected in Alarms and Events Storage.
3. Click Configure to initiate Historian Server Configuration.

Configuring the Pre-Configuration Plugin

The Pre-configuration plugin will perform necessary steps that are required for Control
Software components. This must be configured prior to any other Control Software
configuration plugins are run.

On a Galaxy Repository Server in a Local Edition setup, the Pre-configuration plugin

will display options to select Users that have permissions to run the IDE under non-
elevated mode.
Users that are granted access here will be able to invoke the IDE and run it without
elevated permissions. Select the user accounts that need access in the list box, and
click Grant Access.
In Enterprise Edition setups, GPOs set this automatically.

B0750TP, Rev E 59
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

Click Configure to proceed with the Pre-Configuration process.

Configuring Control HMI Resolution

This plugin will set the screen resolution to the recommended resolution that best
suits the Control HMI Application.

60 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

Configuring Startup Options for FoxView and Control HMI

The HMI Startup Options extension is provided as part of the Configurator. This allows
you to select either Control HMI or FoxView or both as a start-up HMI application. You
can select either Control HMI Alarming or FoxView Alarming as the default alarm
system.

B0750TP, Rev E 61
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

Based on the selection, the corresponding Control HMI will be started after logging in
to the workstation/server.

Enabling Control Core Services Configuration

Select Enable Control Core Services in the left-pane of the Configurator, then
select Configure.

62 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

Configuring CSDatabase Preparation

This plugin creates the Control Software secondary databases that are needed for its
operations and provides the permissions to user groups. If any of the databases do
not exist or the necessary permissions were not provided, this plugin will be marked
as not configured. You should re-run this plugin to fix any issues with these databases
or permissions.
The plugin will also be marked as not configured if you add a new product or feature to
this machine. For example, on a completely setup machine, if you add the AVEVA
Historian product or Condition Advisor, this plugin will be marked as not configured to
allow you to re-run it. It will then setup the required databases and permissions for the
newly added products or features.
NOTE: A reboot prompt appears when you select this plugin. Reboot the system
to re-run the plugin.

B0750TP, Rev E 63
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

Configuring Alarm DB Logger Preparation

This plugin configures necessary permissions for the Alarm DB Logger database to
allow Control HMI to access and retrieve historical alarms and events when required.
When this plugin is loaded, the Server Name combo box is populated with all available
SQL Server instances in the network. Select the SQL Server instance where you
created the Alarm DB Logger database. Upon selection, this plugin populates all
"Alarm DB Logger" databases that exists on that machine. Select the desired
database and click on Configure to provide necessary permissions
Whenever you create a new "Alarm DB Logger" database, you must run this plugin to
provide necessary permissions.
This plugin is not marked as configured to allow multiple executions when required.

64 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

Configuring Galaxy Preparation

This plugin configures the local station to be part of the Galaxy. It also upgrades the
galaxy to the latest version if it was initially imported from another system.
For more information, see Chapter 5: Galaxy Preparation, page 69.

Configuring SQL Maintenance Scripts

This plugin allows you execute SQL performance improvement scripts. When Galaxy
is used for a very long time, SQL data is fragmented and it might degrade the
performance of the application. Run this plugin when you notice performance issues
or periodically to optimize the SQL database performance.

B0750TP, Rev E 65
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

Configuring Spreadsheet Features

This plugin allows you to install the supported Microsoft Excel required for
spreadsheet features like the Grid Editor. Follow this procedure to browse for the
supported media and install the Excel software.
1. Insert the Control Software Office media into the DVD drive.

66 B0750TP, Rev E
Chapter 4: Configuring Foxboro DCS Control Software Control Software v8.0 Installation Guide

2. Navigate to Start > AVEVA > Configurator.

The Configurator dialog box appears.

3. Select Spreadsheet Features.

4. Click Browse, then navigate to the Control Software Office (setup.exe) on the
DVD.

B0750TP, Rev E 67
Control Software v8.0 Installation Guide Chapter 4: Configuring Foxboro DCS Control Software

5. Close any Microsoft Office applications (for example, Visio), and click Configure.
Microsoft Excel is installed.

6. Verify that Visio and Excel are activated.

For more information, see Verifying Visio 2021 Activation Status, page 166.

68 B0750TP, Rev E
Chapter 5: Galaxy Preparation Control Software v8.0 Installation Guide

Chapter 5: Galaxy Preparation

Before you begin the Galaxy Preparation configuration process, plan when you want
to install or upgrade your Control Software for Foundation Fieldbus, PROFIBUS,
DeviceNet, HART, or Condition Advisor that have available upgrades in Control
Software.
NOTE: You must upgrade all previously installed software packages for
Foundation Fieldbus, PROFIBUS, DeviceNet, HART, or Condition Advisor, that
have upgrades available in Control Software before configuring Galaxy
Preparation. The Galaxy Preparation process will not run unless the software
packages have been upgraded.
For installation and upgrade instructions, see:
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for PROFIBUS Networks Installation Guide (B0750CJ)
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for Foundation Fieldbus Installation Guide (B0750CK)
• EcoStruxure™ Foxboro™ DCS DeviceNet Network Installation Guide (B0750CL)
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for HART® Installation Guide (B0750CN)
• EcoStruxure™ Foxboro™ DCS Condition Advisor Installation Guide (B0750CR)

Opening Galaxy Preparation

1. Upgrade any Control Software packs that are needed, or (if planned) install any
software packs not already installed on your station. Refer to the appropriate
documentation listed above.
2. Open the Configurator. From the Start menu, select AVEVA > Configurator.
3. After the Configurator opens, click Galaxy Preparation.

Galaxy Preparation on the Galaxy Repository Server

On the GR node, after installing Control software for the first time, a galaxy must be
created.

B0750TP, Rev E 69
Control Software v8.0 Installation Guide Chapter 5: Galaxy Preparation

1. In the left pane of the Configurator dialog box, select Galaxy Preparation.

2. In the GR Node field, select or enter the letterbug for the Galaxy Repository
server if the letterbug is available. When done, press Enter.
3. In the Galaxy Name field, enter the name of the Galaxy.
4. In the Galaxy Type menu, select AquariusGalaxyBackup.cab (the base Galaxy
database that has to be used), unless you are using another database type (and
are aware of the repercussions of selecting another type). When done, click
Configure.

70 B0750TP, Rev E
Chapter 5: Galaxy Preparation Control Software v8.0 Installation Guide

NOTE: If Galaxy Preparation identifies an existing Galaxy on the station, the

Galaxy Type menu is disabled.

The Galaxy creation process starts. It can take a few minutes to complete.
NOTE: After the Galaxy preparation is successful, the Galaxy Type box
appears empty and is unavailable.

Galaxy Preparation on Each Galaxy Repository Client

These steps can only be completed on the galaxy clients after the GR node is
installed and configured.
1. Confirm you have completed

B0750TP, Rev E 71
Control Software v8.0 Installation Guide Chapter 5: Galaxy Preparation

2. In the GR Node field, select or enter the letterbug for the Galaxy Repository
server if the letterbug is available. When done, press Enter.

If there are any existing Galaxy databases on the Galaxy Repository server, the
Galaxy databases appear in the Galaxy Name menu.
If there are no existing Galaxy databases on the Galaxy Repository server, you
need to create a new Galaxy database on the Galaxy Repository station (see
Galaxy Preparation on the Galaxy Repository Server, page 69) and re-run the
Configurator on the client.
3. Select the appropriate Galaxy to prepare from the menu and click Configure.

72 B0750TP, Rev E
Chapter 5: Galaxy Preparation Control Software v8.0 Installation Guide

Finalizing Galaxy Preparation

1. When the Galaxy Preparation process starts on the Galaxy Repository server or
client, this dialog box appears. Verify the Advanced Communications as
explained in the dialog box, then click OK.

The Galaxy Security login dialog box appears.

2. Enter the Administrator credentials, then click Login.

NOTE: If you are using the AquariusGalaxyBackup.cab for creating the

Galaxy, the default Administrator password is controlsoftware. The Galaxy
database is prepared for Control Software operations. When finished, Galaxy
Preparation starts deploying the Galaxy objects needed for Control Software
based on the type of the station. This dialog box appears during the
deployment:

B0750TP, Rev E 73
Control Software v8.0 Installation Guide Chapter 5: Galaxy Preparation

NOTICE
POTENTIAL DATA LOSS
Sync the station time with the domain controller for stations managed by the
domain controller. If it is not synced, the galaxy preparation process might not
complete properly.
Failure to follow these instructions can result in data loss.

3. After the Galaxy Preparation process is complete, review the Galaxy Preparation
log and Operations Control Management (OCM) log for any system messages
that might have occurred during the Galaxy preparation.

NOTICE
POTENTIAL DATA LOSS
If you are preparing the galaxy for an off-platform GR or client and if the
platform is unable to deploy, modify the platform object Node name to the
corresponding IP address. Then, retry deploying the platform from IDE.
Failure to follow these instructions can result in data loss.

NOTE: For runtime workstations only, the Control HMI application might still
be transferring files. Do not restart the station until the application file transfer
is complete as indicated by the HMI icon shown in the IDE Deployment view.
This file transfer can take several minutes depending on the system and
network performance. The IDE Deployment tree view icon for Control HMI
App Engine changes state to show Deployed when a transfer completes
successfully.
4. If you had planned to install Foundation Fieldbus, PROFIBUS, DeviceNet, HART,
or Condition Advisor in Control Software after the Galaxy Preparation process
has been completed, install these software packs now.
For installation instructions, see the appropriate document listed in Chapter 5:
Galaxy Preparation, page 69.

Adding New FDT Roles to the Galaxy Database

If the Galaxy was migrated from Control Software 4.0 or prior releases and Field
Devices products were never installed, it is possible that required FDT security roles
are missing in the Galaxy database. These roles cannot be added by installation/
configuration. These roles need to be manually added after the Galaxy Preparation
completes the migration process. Perform these steps to finish the database
initialization for the Control Software
Perform these steps to finish the database initialization for the Control Software.
1. Login again as Administrator, if security is enabled.
2. Open Galaxy > Configure > Security > Roles Tab.
3. Add these roles, leaving default (none) permissions for each:
• fdtadministrator
• fdtmaintenance
• fdtobserver
• fdtoemService
• fdtoperator

74 B0750TP, Rev E
Chapter 5: Galaxy Preparation Control Software v8.0 Installation Guide

• fdtplanningEngineer
• InstrumentObserver
• InstrumentOperator
• InstrumentTechnician
• SafetyInstrumentEngineer
• SafetyInstrumentTechnicain

B0750TP, Rev E 75
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

Chapter 6: Upgrading to Foxboro DCS Control

Software v8.0 (Day 0 Installation)
This chapter describes the procedure, considerations, and other information for
upgrading a station with the Control Software v6.3, v7.2, and v7.5 installed to Control
Software v8.0.

Introduction
This procedure allows you to upgrade a station with Control Software v6.3, v7.2, and
v7.5 to a station with Control Software v8.0 installed.
This is not a direct upgrade. This procedure involves:
• Backing up necessary Control Software files (such as the Galaxy database (CAB
file) on a Galaxy Repository node) to an external device.
• Performing a Day 0 installation of Control Core Services software v9.8 and later.
• Installing Control Software v8.0.
• Restoring and migrating the backed-up files (such as the CAB file for the newly
installed Galaxy Repository server).

NOTICE
POTENTIAL DATA LOSS
Plan your upgrade schedules and backups accordingly. Historical data can be
lost during any upgrade.
Failure to follow these instructions can result in data loss.

NOTE: For information on backing up data related to AVEVA applications,

refer to the appropriate AVEVA user guide - see EcoStruxure™ Foxboro™
DCS Control Software Deployment Guide (B0750BA).

Planning the Upgrade

If the upgrade is to be performed on a running plant, these conditions need to be
considered and an upgrade plan needs to be developed:
• You can upgrade Control Software v6.3, v7.2, or v7.5 to Control Software v8.0 on
a platform with Control Core Services software v9.8 and Windows 10 21H2 LTSC
or Windows Server 2022 operating system. This configuration needs to be
created via a new installation on the platform as described in this chapter and in
the EcoStruxure™ Foxboro™ DCS Control Core Services v9.8 Software
Installation Guide (B0700TP).
• Systems with earlier versions of FCS or InFusion first need to upgrade to Control
Software v6.3, v7.2, or v7.5 before upgrading to Control Software v8.0. You must
follow the appropriate upgrade path, depending on your version of InFusion or
FCS software. For more information, see Control Software Installation and
Control Core Services Compatibility, page 10 for the appropriate previous
revision of this document.

76 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

• During the upgrade, each station will reinstall its operating system, Control Core
Services, and Control Software. During this time, the station being upgraded will
not be able to communicate with the other Foxboro DCS workstations. A plan
needs to be prepared in advance that specifies in what order the stations need to
be upgraded.
• During the upgrade of Foxboro DCS control stations using the Control HMI,
displays will be unavailable to show process value updates or for operator sets
and alarm acknowledgment until the upgrade has been completed on the
workstation.
• The plan must specify the order in which Control Software workstations are
upgraded. The planned order needs to verify that other operator stations are
available for operator interaction with control process while the current
workstation is upgraded. The available workstation needs to provide the
capability to allow all the needed operator interactions to keep the process online.
These interactions might include making process setpoint changes, and
performing alarm acknowledgment.

Overview of the Upgrade Process

During the upgrade process, you will have to configure the Galaxy Preparation utility.
Before you begin the Galaxy Preparation configuration process, you must plan when
you want to install the Control Software Packs for Foundation Fieldbus, PROFIBUS,
DeviceNet, HART, or Condition Advisor in Control Software v8.0.
NOTE: If Condition Advisor is installed on the system being upgraded, the galaxy
name after upgrade should be the same as before upgrade.
If you are restoring a migrated Galaxy from Control Software v6.3, v7.2, or v7.5, you
need to have those software packs present on your target system before Galaxy
Preparation. Otherwise, Galaxy Preparation will abort.
For installation instructions, see these documents:
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for PROFIBUS Networks Installation Guide (B0750CJ)
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for Foundation Fieldbus Installation Guide (B0750CK)
• EcoStruxure™ Foxboro™ DCS DeviceNet Network Installation Guide (B0750CL)
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for HART® Installation Guide (B0750CN)
• EcoStruxure™ Foxboro™ DCS Condition Advisor Installation Guide (B0750CR)
These points provide an overview of the upgrade process:
1. Disable VirusScan on the station. For more information, see Enabling and
Disabling Virus Scanning Software, page 141.
NOTE: Only enable the virus scan after successfully completing the
installation, Configuration, and Migration processes for Control Software.
2. If the Galaxy contains old or unused Control HMI templates, delete them before
upgrading the galaxy.

B0750TP, Rev E 77
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

3. Create a backup for:

• Galaxy database backup (.cab) file. See Backing Up the Galaxy Repository
Database, page 79.
Security (InFusionDeployedDB) database. See Backing Up the
InFusionDeployedDB Database, page 83.
AVEVA Historian database. See Backing Up the AVEVA Historian Database,
page 85.
• All Control HMI user files, including v6.x file. See Backing Up the Foxboro
DCS Control HMI User Files, page 88.
• PLB and Sequence block source files. See Backing Up PLB and Sequence
Block Source Files, page 90.
• Condition Advisor database (IAMSMasterDB). See Backing Up Condition
Advisor Database for Day0 Upgrade, page 90.
4. Run the Control software v8.0 installation on only Galaxy Repository
5. If the station is a Galaxy Repository station, the Pre-Upgrade Galaxy Preparation
runs to capture the deploy status of Galaxy objects and backup the Galaxy
database (.cab file).
If this is non-Galaxy Repository station, the upgrade process will not proceed.
6. Install Windows 10 21H2 LTSC or Windows Server 2022 as per your upgrade
plan.
7. If this station will include Control Core Services software v9.8 or later, install this
software as described in EcoStruxure™ Foxboro™ DCS Control Core Services
v9.8 Software Installation Guide (B0700TP). .
8. Install Control Software v8.0 as described in Chapter 3: Installing Foxboro DCS
Control Software, page 25.
9. Restore these:
• Galaxy database backup (.cab) file. See Restoration of the Galaxy
Repository Database, page 100.
• Security (InFusionDeployedDB) database. See Restoring the
InFusionDeployedDB Database, page 91.
• AVEVA Historian database. See Restoring the AVEVA Historian Database,
page 93.
• All Control HMI Application user files. See Restoration of HMI Application
v6.3 or v7.x Files, page 104.
• Control HMI Application v6.x. See Restoration of Foxboro DCS Control HMI
Application v6.3 Files, page 105.
• PLB and Sequence block source files. See Restoring PLB and Sequence
Block Source Files, page 105.
• Condition Advisor database (IAMSMasterDB). See Restoring the Condition
Advisor Database During a Day 0 Upgrade, page 105.
10. Run the Galaxy Preparation utility to restore the deploy status of the Galaxy.
11. Upgrade each Galaxy client station in accordance with the upgrade plan
developed in Planning the Upgrade, page 76.

78 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

12. Use Veritas to back up the station.

Open this application as follows: Start > Veritas System Recovery > Veritas
System Recovery 23.
For Windows Server 2022 or Windows 10 21H2 LTSC, user Veritas. See
EcoStruxure™ Foxboro™ DCS Veritas System Recovery 23 User’s Guide
(B0700WY).
NOTE: The Galaxy database should be backed-up following a successful
upgrade of FCS/Control Software. The operation must be performed from
within the AVEVA OCMC.

Backup Process
Before starting the upgrade process, create a backup of these files:
• Galaxy Repository Database (.cab file)
• Security {InFusionDeployedDB} database
• AVEVA Historian database
• Control HMI user files
• Control HMI
• PLB and Sequence blocks source files
• Condition Monitoring database

Backing Up the Galaxy Repository Database

1. Insert the Control Software DVD into the DVD drive on the station on which you
want to generate the Galaxy database backup (.cab) file (for example, on a
station with Control Software v6.3, v7.2, and v7.5.).Then navigate to the DVD's
top level directory and run setup.exe.

B0750TP, Rev E 79
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

2. The Pre-upgrade Galaxy Preparation dialog box appears. Click Prepare

Galaxy.
NOTE: If this station is not a Galaxy Repository node, a message appears
indicating that it found Control Software vX.x, but did not find a Galaxy
Repository, and thus the upgrade cannot proceed.

80 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

3. The Galaxy Login dialog box appears. If Galaxy security is enabled with the
Galaxy-based, OS User based, or OS Group based Security models in the
Control Software v6.3, v7.2 or v7.5 Galaxy, enter a valid Galaxy user name and
password, and click Login.

B0750TP, Rev E 81
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

4. This dialog box shows the deployment status. Click Backup Galaxy to indicate
the location in which you want to back up the database.

5. The Backup Galaxy Repository dialog box appears. Specify or browse to the
location (on an external drive) to which you want to back up the database. Click
Backup.

82 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

6. After the backup operation completes successfully, a message appears in the

Pre-upgrade Galaxy Preparation dialog box. Click Close.

Backing Up the InFusionDeployedDB Database

The InFusionDeployedDB database is a SQL database located on the Galaxy
Repository. The database maintains changes to security and history configuration of
deployed objects. Whenever the Galaxy database is backed up or restored, the
InFusionDeployedDB database needs to be backed up or restored manually as well.
To back up the InFusionDeployedDB database, proceed as follows:
1. Open the SQL Server Management Studio with elevated permissions using “Run
as Administrator”. Connect to the server whose name is the same as the
workstation’s letterbug.

B0750TP, Rev E 83
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

2. Right-click the InFusionDeployedDB database and select Tasks > Back Up.

84 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

3. In the Back Up Database dialog, either use the default backup filename and
folder to back up the database, or specify your own filename with a .bak
extension and folder if preferred. To provide a new filename and folder, delete the
default filename and folder address from the Back up to table field, and enter the
new filename and folder address.

4. Click OK to backup the database.

5. Save the backed up database on an external drive to retain another backup of
this database.

Backing Up the AVEVA Historian Database

You will need to back up and restore the AVEVA Historian database for any upgrade
to CS v8.0 from CS v6.3, v7.2, or v7.5.
To do this, first back up the Historian database, upgrade the station, and then restore
the Historian database.
1. Stop the Historian. For more information, see AVEVA User Documentation, page
11.
2. Back up the History blocks to an external drive. This can be done either manually
or with the Windows Backup utility (see AVEVA User Documentation, page 11).
To back up history blocks manually, locate the history blocks, and save all the
history blocks’ files to an external drive. Find the history blocks in OCMC under
Historian > Historian Group > Workstation_Letterbug > Management
Console > History Blocks.

B0750TP, Rev E 85
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

Backing Up the Runtime Database to an External Drive

1. Start Microsoft SQL Server Management Studio with elevated permissions
using “Run as Administrator”. You need to log in to the SQL Server using either
the administrator login or your Windows-authenticated account with local
administrative privileges.
2. Expand Databases on the left panel until you see Runtime.

86 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

3. Right-click Runtime, then select Tasks > Back Up. The Back Up Database -
Runtime dialog box appears.

NOTE: In the Destination section the default path of the repository is

displayed. You can modify the destination path.

B0750TP, Rev E 87
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

4. Under Select a Page, click Options. Perform these steps:

• In the Overwrite media section, select Back up to the existing Media set
and Append to the existing backup set.
• In the Reliability section, select the Verify backup when finished
checkbox.

5. Click OK.
6. A confirmation message appears. Click OK.

7. Proceed with station upgrade. Return to whichever upgrade procedure in this

document you are performing. Proceed to the next step when you have finished
the upgrade procedure.

Backing Up the Foxboro DCS Control HMI User Files

Back up the user files for each OS user account (%USERID%) that uses the Control
HMI runtime. Do this on each workstation.
Perform these steps for each OS login user:
1. Open File Explorer.
2. Browse to the AppData\Local folder of each OS user login.
C:\Users\ <OS User ID> \AppData\Local

88 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

3. Right-click the InFusion-View folder and select Send To > Compressed (zipped)
Folder.
4. Store the compressed zip file in a safe location to be restored later.

Backup Foxboro DCS Control HMI Files

The managed version of the Control HMI, Custom Industrial Graphics, and the custom
Style Settings are backed up with the Galaxy.
Day 0 Installs
• Control HMI-related files must be backed up and stored on separate media prior
to doing a Day 1 install. All Control HMI files and user runtime information will be
lost and not backed up. It is always good practice to maintain a separate
individual backup of the Control HMI template and custom Graphics.
• When migrating from a system earlier than Control Software v8.0, if custom
changes have been made to the Galaxy Styles, create a backup of the Galaxy
Style Library. See Backing Up Custom Style Settings, page 89.
• The Control HMI-managed application and custom Industrial Graphics are
backed up with the Galaxy. See subsections in this chapter for steps to create
individual backups.
• If still using the Standalone Control HMI Application, create a backup of the
application folder and files. See Backing Up Standalone Control HMI, page 90.
• Control HMI runtime user settings need to be backed up. User settings include
custom queries or filters that users might create in the runtime. See Backing Up
the Foxboro DCS Control HMI User Files, page 88.
Day 1 Installs
• Control HMI-related files do not need to be backed up to individual files, but It is
always good practice to maintain separate individual backups.

Backing Up the Control HMI $Template

1. Open IDE.
2. Open the template toolbox and navigate to the Control HMI folder.
3. Right-click $ControlHMI_V### template and select Export > Object(s).
4. Store the HMI aaPKG file in an external drive so that it is not lost during the Day0
installation.

Backing Up Custom Graphics

1. Open IDE and switch to the Graphic Toolbox view.
2. Select toolsets that contain custom built Graphics.
3. Right-click the selected toolset(s) and select Export > Object(s).
4. Store the Graphic aaPKG file in an external drive so it is not lost during Day0
installation.

Backing Up Custom Style Settings

1. In the IDE menu, select the Galaxy > Export > All Style libraries.

B0750TP, Rev E 89
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

2. Store the Style.XML file in an external drive so it is not lost during Day0
installation.
NOTE: Before cab file migration, you need to export your styles library if it
has been customized. After the migration you will need to manually import
either the customized styles library or the CS v8.0 styles library into the IDE.

Backing Up Standalone Control HMI

1. Open File Explorer.
2. Browse to the application folder(s), typically: D:\InFusion-View
3. Right-click on the InFusion-View folder and rename the file.
We recommended that you rename InFusion-View to InFusion-View-<date>,
where <date> is the current date.
4. Right-click on the folder and select Send To > Compressed (zipped) Folder.
5. Store this zip file on an external drive so it is not lost during Day0 installation.

Backing Up PLB and Sequence Block Source Files

The source files for the PLB and Sequence blocks are used by, respectively, the PLB
Monitor and SFC Display Manager.
To preserve the blocks’ source files, under the d:\opt\fox\ciocfg directory,
backup all the subdirectories which have the name of a compound. Copy them to an
external drive.

Backing Up Condition Advisor Database for Day0 Upgrade

NOTE: This section is applicable only to systems with Asset Condition Advisor.
IAMSMasterDB is a SQL database available on the Galaxy Repository system. It
contains device condition configuration used by Asset Condition Advisor
application objects.
You must back up the Condition Advisor database from the Galaxy Repository system
to preserve the condition configuration for device monitoring.
1. Navigate to Condition Advisor install media. The install media contains ReadMe.
txt file under the \InstallFiles\SQLREPLPackage\Scripts folder.
2. Follow the instructions provided in the ReadMe.txt file, under the
\InstallFiles\SQLREPLPackage\Scripts folder, to take a backup of
Asset Condition Monitor database using the BackupACMData.ps1 script that is
under the \InstallFiles\SQLREPLPackage\Scripts folder.
3. Save the generated output file (backup file) to an external drive/known location.
4. Manually undeploy Asset management Application engine '<systemName>_
AppAM' on both Galaxy and client systems.

Installing Foxboro DCS Control Software

NOTE: This section assumes that Windows 10 IoT 21H2 LTSC or Windows
Server 2022 and Control Core Services software v9.8 or later, has already been
installed on this station, as per the upgrade plan.

90 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

To install Control Software, see the procedures in Chapter 3: Installing Foxboro DCS
Control Software, page 25.

Restoration Process

NOTICE
POTENTIAL UNSUCCESSFUL CONFIGURATION
Use the correct user login to configure the Control Software:

Setup Type User

Enterprise Edition A user that is a member of the IA
Installer group.
Local Edition The same user that is used for
installing Control Software.

Failure to follow these instructions can result in an unsuccessful

configuration.

After installing Control Software, restore these databases and files:

• Security {InFusionDeployedDB} database
• AVEVA Historian database
• Galaxy Repository Database (.cab file)
• Control HMI user files
• Control HMI
• PLB and Sequence blocks source files
• Transfer the change tracking records for the FoxCTS server
• Condition Monitor Database

Restoring the InFusionDeployedDB Database

The InFusionDeployedDB database is an SQL database located on the Galaxy
Repository. The database maintains changes to security and history configuration of
deployed objects. When the Galaxy database is backed up or restored, the
InFusionDeployedDB database needs to be backed up or restored manually.
1. Under Control Panel > Administrative Tools > Services, stop these services:
• InFusion Security Provider
• InFusionSyncService
• InFusion Deploy Service
2. Open the SQL Server Management Studio with elevated permissions using “Run
as Administrator”. From the Start menu, select All Programs > Microsoft SQL
Server Tools 19 > SQL Server Management Studio 19.
3. Login to the default MSSQLSERVER instance.
4. If InFusionDeployedDb database exists, right-click and then, click Delete. If you
have trouble deleting it check Close existing Connections to force the deletion.

B0750TP, Rev E 91
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

5. Right-click Databases and select Restore Database.

6. In the Restore Database dialog box, select Device and click ... in the window
that appears, select the path to the backup folder where the InFusionDeployedDB
database is saved, and click OK

92 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

7. In the Select the backup sets to restore table, select the checkbox near the
database you want to restore.

8. Click OK.
9. Launch the Configurator: Start > AVEVA > Configurator. Select and configure
the CS Database Preparation plugin to provide the required permissions to
operate the restored database. If you have other databases to restore like
Historian database, you could perform this step after restoring all databases.
10. Under Control Panel > Administrative Tools > Services, restart these services:
• InFusion Security Provider
• InFusionSyncService
• InFusion Deploy Service

Restoring the AVEVA Historian Database

This section outlines how to restore the AVEVA Historian database onto the new
destination server, and assumes that the Historian Server is installed on the new
machine.
1. Open the OCMC and expand Operations Control Management Console >
Historian.
2. Expand Historian Group > <LocalMachine> > Management Console.

B0750TP, Rev E 93
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

3. Right-click Status and click All Tasks > Shutdown (and disable) Historian.

4. Restore the history blocks using the Windows Backup utility (see AVEVA User
Documentation, page 11), or manually restore history blocks by copying backed
up files to their original location.
5. Restore the runtime database from the external drive by performing the steps in
Restoring the Runtime Database to the New Server, page 94.

Restoring the Runtime Database to the New Server

This section describes the steps to restore the Runtime database onto the new
destination server.
1. Open the OCMC, and expand Operations Control Management Console >
Historian.
2. Expand Historian Group > <LocalMachine> > Management Console.

94 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

3. Right-click Status and click All Tasks > Shutdown (and disable) Historian.

4. Start the Microsoft SQL Server Management Studio with elevated permissions
using “Run as Administrator”. From the Start menu, select All Programs
Microsoft SQL Server Tools 19 > SQL Server Management Studio 19.
5. Log in to the default MSSQLSERVER instance.
6. Right-click the Runtime database and click Delete. If you have trouble deleting it,
check Close existing Connections to force the deletion.
7. Copy the Runtime backup file to a folder on the destination server.
8. From the MS SQL Server Management Studio, right-click the Database folder
and click Restore Database. The Restore Database dialog box appears.
9. In the Restore Database dialog box, select Device and click ... to locate the folder
where the Runtime database is copied.

B0750TP, Rev E 95
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

10. The Select Backup Devices dialog box appears. Click Add, browse to the folder,
select the Runtime.bak backup file, then click OK twice to return to the Restore
Database dialog box.

11. Under Destination in the Database filed, verify that Runtime is selected. If not,
then expand the menu and select Runtime.

96 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

12. Under Backup Sets to Restore verify that Restore is selected for the Runtime
database.

13. If you want to modify any further options, click Files and Options on the Restore
Database - Runtime panel. We recommend keeping the default settings
whenever possible.
14. Click OK to begin the restore process.
15. After the restore operation completes successfully, execute this Transact-SQL
script from the MS SQL Server Management Studio to help ensure that all the
Historian Server's pre-configured user accounts and roles are properly
connected:
USE Runtime;
ALTER USER wwAdmin WITH LOGIN = wwAdmin;
ALTER LOGIN wwAdmin WITH DEFAULT_DATABASE = Runtime;
ALTER USER wwUser WITH LOGIN = wwUser;
ALTER LOGIN wwUser WITH DEFAULT_DATABASE = Runtime;
ALTER USER wwPower WITH LOGIN = wwPower;
ALTER LOGIN wwPower WITH DEFAULT_DATABASE = Runtime;
ALTER USER aaAdmin WITH LOGIN = aaAdmin
ALTER LOGIN aaAdmin WITH DEFAULT_DATABASE = Runtime;
ALTER USER aaUser WITH LOGIN = aaUser;
ALTER LOGIN aaUser WITH DEFAULT_DATABASE = Runtime;
ALTER USER aaPower WITH LOGIN = aaPower;
ALTER LOGIN aaPower WITH DEFAULT_DATABASE = Runtime;
ALTER AUTHORIZATION ON DATABASE::Runtime TO aadbo;
16. Execute this SQL script from the MS SQL Server Management Studio after
updating the correct hostname in the commands:
Use Runtime;
DROP USER [<HostName>\aaAdministrators]
DROP USER [<HostName>\aaPowerUsers]
DROP USER [<HostName>\aaUsers]
17. If the Historian Server name (Node Name) in the backup database is different
from the Server name where you are restoring or if the History Blocks storage

B0750TP, Rev E 97
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

path (Data Path) in the backup database is different from the current
configuration 'Data Path' provided, then perform the steps outlined in section
Synchronizing the Historian Server Name or Historian Blocks Data Path with the
Backup and Restored Historian Databases, page 104. If the above conditions do
not apply to you, proceed to Step 18.
18. Open the Configurator. From the Start menu, select AVEVA > Configurator.
19. Configure the Server plugin under the AVEVA Historian section.
NOTE: Verify that the Drop and Create new database checkbox is cleared.

20. Select and configure the CS Database Preparation plugin to provide the
required permissions to operate the restored database. If you have other
databases to restore such as the Historian database, you can perform this step
after restoring all databases.

Restoring the Foxboro DCS Control HMI User Files

When restoring User profile runtime files, User accounts must exist first. After OS user
are created, unzip the back up file to the User’s Appdata\Local folder.
Perform these steps for each OS login user:
1. Open File Explorer.
2. Browse to the compressed zip file location.
3. Double-click the zip file to open it in File Explorer.
4. Right-click the infusion-View folder and select Copy.
5. Browse to the AppData\Local folder of each OS user login.
C:\Users\ <OS User ID> \AppData\Local

98 B0750TP, Rev E
Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

6. Paste the InFusion-View folder into the local folder.

Restore Foxboro DCS Control HMI Files

Whether doing a Day0 migration install or just trying to restore backups, the
procedures are the same. Perform these steps to restore your backup files.

Restoring the Control HMI $Template

The backup Control HMI $Template will not import if there is a template with the same
name.
1. Open System Platform IDE.
2. Open the template toolbox and navigate to the Control HMI folder.
3. Rename the Control HMI $template if it has the same name as what is being
restored.
4. Import the backup by navigating to Galaxy > Import > Objects > From Package.
5. Browse to the Control HMI $Template in your backup location.
6. Click Open to import.

Restoring Custom Graphics

1. From System Platform IDE, navigate to Galaxy > Import > Objects > From
Package.
2. Browse to the Graphic backup file.
3. Select the Graphics aaPKG file and click Open to import.

Restoring Custom Style Settings

1. From System Platform IDE, navigate to Galaxy > Configure > Galaxy > Styles.
2. Click … (right) and select Import.

3. Browse to the backup style XML file.

4. Select the XML file and click Open to import.
5. After the file is imported, select the imported style to set it as default.

Restoring Standalone Control HMI

1. Open File Explorer.
2. Browse to the compressed zip file location.
3. Double-click on the zip file to open it in File Explorer.

B0750TP, Rev E 99
 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

4. Drag the Infusion-View folder to a new location on the D: drive.

Restoration of the Galaxy Repository Database

You need to install the previously installed software packs that have upgrades
available. We recommended that you perform the install before configuring Galaxy
Preparation.
To restore the Galaxy Repository database (.cab file) it needs to be available in the
Configurator. Therefore, the .cab file has to be copied to:
<drive>:\Program Files\ArchestrA\Framework\Bin\BackupGalaxies
If the Configurator dialog box is open, close it before copying the .cab file. Then it will
be able to load the copied .cab file when it re-opens.

Galaxy Migration and Preparation

Before You Begin
Before you begin the Galaxy Preparation configuration process, install the software
packs for Foundation Fieldbus, PROFIBUS, DeviceNet, HART, or Condition Advisor
support in Control Software v8.0.
For installation and upgrade instructions, see:
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for PROFIBUS Networks Installation Guide (B0750CJ)
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for Foundation Fieldbus Installation Guide (B0750CK)
• EcoStruxure™ Foxboro™ DCS DeviceNet Network Installation Guide (B0750CL)
• EcoStruxure™ Foxboro™ DCS Field Device Expert and Field Device Expert
Workshop for HART® Installation Guide (B0750CN)
• EcoStruxure™ Foxboro™ DCS Condition Advisor Installation Guide (B0750CR)

Out-of-Support Microsoft Redistributable Packages

You must install out-of-support Microsoft redistributable packages before migrating
.cab files from previous versions of Control Software. These packages have reached
their end-of-life, are no longer supported by Microsoft, and might pose a security risk if
left installed on the system. If your system requires these packages, you will be
prompted before the migration process starts.
The Microsoft Redistributable packages are included on the System Platform Media in
the Install Files\OutOfSupportRedist folder.

Redistributable Description Folder

Microsoft Visual C++ 2008 VC90SP1/vcredist_x86.exe
Redistributable
Microsoft Visual C++ 2010 VC10SP1/vcredist_x86.exe
Redistributable
VC10SP1/vcredist_x64.exe

100 B0750TP, Rev E

Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

Once migration is complete, we strongly recommend you uninstall the packages if

they are not required by other installed software products. Use Control Panel >
Programs and Features to uninstall.
NOTE: If these packages already existed on the machine, they might be required
by other installed software products

Migrating and Preparing the Galaxy

1. If you are running Galaxy Preparation on a Galaxy Repository station, verify that
AVEVA licenses are installed as described in Appendix C: Installing AVEVA
Licenses, page 150. However, client stations that connect to the Galaxy
Repository server do not need licenses before the Galaxy Preparation.
2. Open the Configurator: Start > AVEVA > Configurator.
3. After the Configurator opens, click Galaxy Preparation.
4. For the Galaxy Repository server:
a. In the GR Node field, select or type in the letterbug for the Galaxy Repository
server if the letterbug is available. When done, press Enter.

b. In the Galaxy Name field, type the name of the Galaxy. We recommend
using the same name as the older Galaxy’s name.
NOTE: For systems with Condition Advisor, the Galaxy name must
match the older version Galaxy's name.
c. In the Galaxy Type menu, select the older galaxy .cab file that you have
backed up.
d. Click Configure.
The Galaxy creation process starts. It can take a few minutes to complete.

B0750TP, Rev E 101

 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

After Galaxy creation (which might take a few minutes) is successful, the
Galaxy migration process is initiated. The migration process might take a few
hours to complete.
Before the migration process starts, you might see a message prompting you
to install VC++ redistributable packages in the OutofSupportRedist
folder on the System Platform media under the InstallFiles folder.
Go to System Platform media > InstallFiles > OutofSupportRedist and
install all the packages.
e. After the migration process is complete, Galaxy Preparation prompts you to
reboot the station. Reboot the station.
After reboot, the Configurator starts automatically.
If it does not restart, open the Configurator from Start > AVEVA >
Configurator.
Once the Configurator opens, click Galaxy Preparation.
NOTE: The Galaxy migration process is not complete until a second
pass of Galaxy Preparation is run and completed.
f. In the GR Node field, type the letterbug for the Galaxy Repository server.
then press Enter.
g. In the Galaxy Name menu, select the appropriate Galaxy. When done, click
Configure.
5. For each Galaxy Repository client:
a. In the GR Node field, select or type in the letterbug for the Galaxy Repository
server if the letterbug is available. When done, press Enter.
b. If there are any existing Galaxy databases on the Galaxy Repository server,
the Galaxy databases appear in the Galaxy Name menu. Select the
appropriate Galaxy to prepare from the menu and click Configure.
6. The Galaxy Preparation process initiates on the Galaxy Repository server or
client, and the Foxboro Install dialog box appears. After verifying the Advanced
Communications as explained in the dialog box, click OK.

102 B0750TP, Rev E

Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

7. When the Galaxy Preparation dialog box appears:

• If you want the objects to be deployed during the Galaxy Preparation, click
Yes.
• If you want the Platform, App Engines, and other objects under them to
remain in an undeployed state, click No.
NOTE: This is only applicable when the Platform is in the undeployed
state.

8. The Galaxy database is prepared for Control Software operations. When finished,
Galaxy Preparation starts deploying the Galaxy objects needed for Control
Software based on the type of the station. This dialog box appears during the
deployment.

9. After the Galaxy Preparation process is complete, review the Galaxy Preparation
log for any system messages that might have occurred during the Galaxy
preparation.
NOTE: For runtime workstations only, the Control HMI application might still
be transferring files. Do not restart the station until the application file transfer
is complete, as indicated by the HMI icon that is shown in the IDE
Deployment View. This file transfer can take several minutes depending on
the system and network performance. The IDE Deployment tree view icon for
Control HMI App Engine changes state to show Deployed when a transfer
completes successfully.
10. After the Galaxy Preparation is complete, review the Operations Control
Management Console (OCMC) log to verify that all objects migrated. If any
objects did not migrate, see the Galaxy Migration section in Chapter 9:
Installation Troubleshooting, page 128.
11. Reboot the system.

B0750TP, Rev E 103

 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

Synchronizing the Historian Server Name or Historian

Blocks Data Path with the Backup and Restored Historian
Databases
If the Historian Server name (Node Name) in the backup database is different from the
server name where you are restoring, then perform these steps:
1. Verify that the Historian Server is still inactive and disabled.
2. Copy and modify these Transact-SQL statements for the Historian server to run
on the new node.
UPDATE StorageNode SET ComputerName = 'NewNodeName' WHERE
ComputerName ='OldNodeName'
UPDATE ServerList SET ComputerName = 'NewNodeName' WHERE
ComputerName = 'OldNodeName'
UPDATE InTouchNode SET MachineName = 'NewNodeName' WHERE
MachineName = 'OldNodeName'
UPDATE IOServer SET ComputerName = 'NewNodeName' WHERE
ComputerName = 'OldNodeName'
UPDATE IODriver SET ComputerName = 'NewNodeName' WHERE
ComputerName = 'OldNodeName'
If the History Blocks storage path (Data Path) in the backup database is different
from the current configuration 'Data Path' you have configured, you can continue
to Step 3.
3. Before modifying the storage location paths, run this SELECT statement and use
Windows Explorer to confirm the paths listed:
SELECT * FROM StorageLocation
4. Use these statements to modify any paths that are different on this node, if
needed.
Replace the drive letter “x” in this code with the drive letter that is appropriate for
your installation.
UPDATE StorageLocation SET path = 'x:\Historian\DATA
\Circular' WHERE StorageType = 1
UPDATE StorageLocation SET path = 'x:\Historian\DATA
\Buffer' WHERE StorageType = 3
UPDATE StorageLocation SET path = 'x:\Historian\DATA
\Permanent' WHERE StorageType = 4

Restoration of HMI Application v6.3 or v7.x Files

For each user you backed up in Backing Up the Foxboro DCS Control HMI User Files,
page 88, log the user into the station so that the appropriate USER files are created by
the operating system for that user. Once the USER files are created, restore the
user’s zip file. On Windows 10 21H2 LTSC and Windows Server 2022, restore the zip
files to this location:
C:\Users\%USERID\AppData\Local\
Where %USERID is the name of the user.
Example: C:\Users\Fox \AppData\Local\InFusion-View.

104 B0750TP, Rev E

Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
(Day 0 Installation) Control Software v8.0 Installation Guide

Restoration of Foxboro DCS Control HMI Application v6.3

Files
Restore the “InFusion-View-<date>” zip file to the D: drive as described in Chapter 7:
Upgrading to Latest Foxboro DCS Control HMI Version, page 107.

Restoring Custom Style Settings

NOTE: After migration, you will need to manually import either the customized
styles library or the CS v8.0 styles library into the IDE.
1. In the IDE menu, click the Galaxy > Import > Style libraries.
2. Import the Style.XML file if you customized and stored it prior to migration. See
Backing Up Custom Style Settings, page 89.
3. If the customized styles library is not available, import the ControlHMIStyles.xml
from Path C:\Program Files (x86)\Invensys\InFusion\View\Support
\ ControlHMIStyles.xml.

Restoring PLB and Sequence Block Source Files

To restore the PLB and Sequence blocks’ source files, copy the subdirectories that
were backed up in Backing Up PLB and Sequence Block Source Files, page 90 into
the d:\opt\fox\ciocfg directory.

Restoring the Condition Advisor Database During a Day 0

Upgrade
This section is applicable to systems with the Condition Advisor.
NOTE: Restore the Condition Advisor database after completing the installation of
the Condition Advisor on the Galaxy server and all client systems.
1. Navigate to Condition Advisor install media.
The install media contains 'ReadMe.txt' file under \InstallFiles
\SQLREPLPackage\Scripts folder.
2. Follow the instructions in the ReadMe.txt file to restore the Condition Advisor
database using the backed up file.
3. Manually undeploy/deploy the Asset Management Application engine '_AppAM'
on the Galaxy and client systems.

B0750TP, Rev E 105

 Chapter 6: Upgrading to Foxboro DCS Control Software v8.0
Control Software v8.0 Installation Guide (Day 0 Installation)

Change Tracking Records from FoxCTS Server

If FoxCTS was enabled before upgrading to Control Software v8.0, perform the
following to continue transferring the change tracking records to the FoxCTS server
after Control Software v6.3 or v7.x > Control Software v8.0:
1. Stop and start the FoxCTS Transfer Service as described in EcoStruxure™
Foxboro™ DCS Control Database Deployment User’s Guide (B0750AJ).
2. Verify that the startup type for the FoxCTS Service is shown in the Services
application as Started, as described in EcoStruxure™ Foxboro™ DCS FoxCTS™
Change Tracking Configuration and Administration Guide (B0193VV).

106 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

Chapter 7: Upgrading to Latest Foxboro DCS Control

HMI Version
This chapter describes upgrading to the latest version of the Control HMI software
(formerly known as InFusion View and FCS InTouch Application software).
• Control Software only supports the Control HMI as a managed InTouch
Application. The Control HMI runs in either 4:3 or 16:9 resolutions. If you upgrade
from a standalone application, all functionalities remain the same with some
changes in the default content and how the application is maintained.:
• Managed 1920 x 1080
◦ Supports Industrial Graphics and Situational Awareness Libraries.
◦ Compiled in 1920x1080 resolution.
◦ Editable from the Control Editor Environment in any resolution.
◦ Opens in WindowMaker only through System Platform IDE.
◦ Workstation and Window Style Defaults are set to WideScreen Aspect.
◦ You need to change Framer style settings to Legacy if the Managed
application is installed on a 1280 x 1024 workstation
◦ Only contains three sets of Detail Display faceplates.
NOTE: The Standalone application is only supported until the Control Software
v6.3 release.
NOTE: There is a minor performance impact when Control HMI runs in a
resolution that it is not compiled; for example, the Control HMI 1280 application
runs in 1920 resolution. However, Control HMI has to recompile windows every
time they are opened in a different resolution.
All workstations and windows need to be assigned a style. Workstations and windows
that are not assigned to a style automatically use the default style settings. The default
style settings depend on which version of the Control HMI application is installed. For
details on creating and assigning styles, see EcoStruxure™ Foxboro™ DCS Framer
and Alarm Management User’s Guide (B0750AR).

Migration Overview
When upgrading Control HMI from a previous version, the user content must be
migrated from the current application into the latest CHMI ViewApp template installed
with the Control Software Galaxy database.
You must migrate the application before upgrading so that it is automatically deployed
to client stations when the client stations are upgraded. Otherwise, the application will
need to be re-deployed to all stations after it is migrated.
This installation procedure is recommended:
1. Migrate the GR Node to the latest version of Control Software.
2. Migrate the Control HMI Development Node to the latest version of Control
Software if it is not on the GR Node. This situation might exist in systems with Off-
Control Network Galaxy Repositories.
• Access to the GR node is needed when editing the managed Control HMI
application. Verify that the Control HMI Development Node is installed on the
Galaxy Repository.

B0750TP, Rev E 107

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

3. Merge the source HMI application into the latest installed Control HMI Template.
Support scenarios include:
• Standalone Control HMI -> Managed Control HMI
• Managed Control HMI -> Managed Control HMI
NOTE: The Control HMI Template is located in the System Platform IDE
Template Toolbox under the Control HMI folder. The Control HMI naming
conventions is “$ControlHMI_V” + Control Software Version. The template
with the highest version number is the latest version.
4. Migrate client workstations to the latest version of Control Software.
5. Deploy the migrated application to client stations.

Upgrade Considerations
While migrating to Control Software v8.0 from a release before Control Software v7.0,
you need to consider the new features in the latest AVEVA System Platform.
• The Galaxy Style Library has new settings for numerical formatting. On migrated
systems, the indicator for Bad Quality status is !. This does not match the default
indicator, *, on new installations or in the default Control HMI InTouch Advanced
Formatting setting. You need to manually modify the Quality Style Value.

Overview of the Migration Process

To migrate to the latest Foxboro DCS Control HMI, the user-built windows and scripts
need to be imported into the latest Control HMI Template. This process is documented
in EcoStruxure™ Foxboro™ DCS Window Construction User's Guide (B0750AS).
NOTE: This process assumes that the standalone Control HMI application
directory is D:\InFusion-View. If the location of the default Control HMI
application was changed during software installation, substitute the new location
for the D:\InFusion-View directory.
NOTE: After installing the latest version of Control software on a workstation, the
original version of the Control HMI is not modified. A new version of the Control
HMI is installed and deployed. This means that immediately after installing the
latest version of Control Software, user-built windows are no longer accessible in
the Control HMI runtime.
1. Back up the existing Control HMI application.
• For Standalone applications, make a copy of the InTouch Application
directories. Verify that both WindowViewer and WindowMaker software are
shut down before making a copy of the directory.
• For Managed applications, there is no need to back up the current
$ControlHMI_v### application template. After installing the latest version of
Control Software, there will be a new $ControlHMI_v### application template
installed in the Template toolbox.
2. Convert the InTouch application if a new version of AVEVA System Platform is
installed.
This is done by opening the original HMI application with the new version of
InTouch WindowMaker.

108 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

3. Migrate the Control HMI files. Run the Control HMI Migration Tool to automatically
perform these merge functions:
a. Dump the tag database from the original Control HMI Application.
b. Load the dumped tag database into the installed Control HMI application.
c. Copy the user-built SmartSymbols from the original Control HMI application
into the installed Control HMI application.
d. Copy configuration files created by Framer from the original Control HMI
application into the installed Control HMI application.
4. Export all custom built windows from the existing HMI application into a
temporary folder, if the existing Control HMI application is managed.
5. Import all the windows and scripts from the existing Control HMI application into
the latest installed Control HMI application.
If third party ActiveX controls are used within the InTouch windows, install the
controls before importing any windows from the legacy application.
NOTE: Starting with Control Software 7.2, the Control HMI no longer supports
the ActiveX Alarm Panels. For instructions on creating a custom Alarm Panel
Graphic, see EcoStruxure™ Foxboro™ DCS Window Construction User's
Guide (B0750AS).
NOTE: When migrating from an older version of InFusion View software to
Control HMI, you might encounter a system message similar to this:
Installer Custom Action Failure: Resetting previous default I/A DM:
Object reference not set to an instance of an object Installer Custom
Action Failure: I/A Applications: Object reference not set to an instance
of an object.
These messages can be ignored. Click OK to continue with the installation.

Control HMI Migration

Installing the latest version of Control HMI software means that, not only has new
software been installed on the workstation, but a new Control HMI is also available.
Previously built windows and scripts need to be imported into the new Control HMI.
The Control HMI Migration tool can be used to automate some of the steps, but script
and window importing needs a manual process.

Modifying the Bad Quality Setting

1. Open the System Platform IDE.
2. From the IDE menu, select Galaxy > Configure > Galaxy > Styles. The Styles
dialog box appears in the right pane.
3. Click Format tab.

B0750TP, Rev E 109

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

4. Modify the Special Characters settings.

5. Click Save to store the settings.

• The Control HMI is no longer released as a Standalone InTouch Application.
Standalone HMI applications need to be migrated to the managed Control
HMI application. For more information, see EcoStruxure™ Foxboro™ DCS
Window Construction User's Guide (B0750AS).

Backing Up the Standalone InTouch Applications

1. Verify that the WindowMaker and WindowViewer applications are not running
during the backup procedure.
2. Copy the original Control HMI application directories to backup directories.
These backup directories are not to be modified during the migration procedure.
As an alternative, you can use Windows Explorer to send the application folder to
a compressed zip file.

110 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

Converting Control HMI to the Latest Version of InTouch

If a new version of InTouch WindowMaker is installed, users will need to convert their
application to latest InTouch version.
NOTE: During conversion, OCMC will report detected warnings that Smart
Symbols are missing. This is expected and can be ignored.

Converting Control HMI to the Latest Version of InTouch for Standalone

Applications
1. Open the InTouch Application Manager. Navigate to Start > AVEVA InTouch HMI
> Application Manager.
2. Find the original application typically located at
d:\Infusion-View-<timestamp> or d:\Infusion-View.
3. Select the original application and open WindowMaker.
4. Select Yes to convert the application.
5. Exit WindowMaker when the conversion is complete.

Converting Control HMI to the Latest Version of InTouch for Managed

Applications
1. Open the System Platform IDE.
2. Open the Template Toolbox and expand the Control HMI folder.
3. Double-click on the current application Template.
4. Select Yes to convert the application.
5. Exit WindowMaker when the conversion is complete.

Running the Control HMI Migration Tool

1. Verify that the WindowMaker and WindowViewer applications are not running
during the migration procedure.
2. Run the Application Migration Tool.
Navigate to Start > Foxboro DCS Control Software > ControlHMIMigration.
3. If WindowMaker or WindowViewer are open, close InTouch and click Retry to
continue.

B0750TP, Rev E 111

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

4. This tool displays all Standalone Control HMI applications present in the
workstation and all the Managed Control HMI applications created in all the
Galaxies present in this Node.

For secure setups or if the Galaxy has security permissions, the Galaxy Login
Window dialog box appears.
NOTE: The Galaxy Login Window dialog box only appears when the Galaxy
has the security model set to Galaxy security.
a. Enter the user name and password to retrieve the managed applications.

112 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

If any Control HMI application is not displayed in the list, manually select the
directory by clicking Browse. Managed applications present in the Galaxy cannot
be added manually.
Click Refresh to reload all the Control HMI applications. This re-logins to the
Galaxy and queries for the managed applications present in the Galaxy. Manually
added Control HMI applications are not displayed after reloading the Control HMI
applications.

B0750TP, Rev E 113

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

5. From the Source Applications list, select the current application . The current
application is the source of all the user built windows and scripts.
6. From the Destination Application list, select the newly installed application
template.
7. Confirm that the InTouch Application directory has been backed up. Selecting
Cancel quits the Selection confirmation process and displays the Information
dialog box.

114 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

8. Confirm that the source Control HMI application has been converted to latest
InTouch version in this dialog box. Selecting No will quit the selection
confirmation process.

9. Click Migrate. It might take a few minutes to complete the migration process. If
the migration completes successfully, close the window and continue with the rest
of the migration process. If the migration is unsuccessful, re-initiate the migration
process after resolving the detected errors.

At this point all tags, user-defined SmartSymbols, and Framer configuration files
have been merged into the destination application. The next step is to import the
user-built scripts and windows from the source application into the destination
application.

B0750TP, Rev E 115

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

Exporting the Managed Application Window

When migrating from a managed application, it is necessary to first export the custom-
built InTouch windows from the source application before importing them into the
latest destination application template.
From System Platform IDE, proceed as follows:
1. Double-click on the original Control HMI application template to open it in
WindowMaker.
2. Verify that all the windows are closed.
3. From the File menu, select Export Window….
4. Select an easy-to-find folder in which all the export files will go. Remember this
folder for importing into the newer application, such as d:\exports.
5. Click OK. The Windows to Export dialog box appears.
6. Select all of the custom-built windows.

7. Click OK.

Importing Scripts and Windows Using WindowMaker Application

Continue the migration procedure by starting WindowMaker software. For Managed
Control HMI applications, WindowMaker can be opened from System Platform IDE by
double-clicking on the Control HMI application. Verify that the tag database from the
original application has been loaded into the new Control HMI application.
1. Verify that the original application tag database has been loaded into the new
Control HMI application. From WindowMaker, select Home > Tag dictionary,
then scroll through the tag list, verifying that tags from the original application are
included in the list, and then close this dialog box.

116 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

2. Start the Operations Control Management Console to monitor detected and

notifications that are logged during the import process. Navigate to Start >
AVEVA > Operations Control Management Console. Within the OCMC, view
the message log for the local workstation.

3. Import all the user-written scripts from the original application. If no user-written
scripts were created, skip this step and proceed to Step 4.
a. From WindowMaker, select File > Import > Visualization > Windows and
scripts. The Import from Directory dialog box appears. Select the InTouch
directory for import.
• For managed applications the path is to the Galaxy file repository, which
is typically: D:\Program Files\ArchestrA\Framework
\FileRepository\<GalaxyName>\ObjectFileStorage\$<base
template name>\CheckedIn
For example: D:\Program Files\ArchestrA\Framework
\FileRepository\Galaxy1\ObjectFileStorage$ControlHMI_v73
\CheckedIn

b. Select the user-written scripts to import. DO NOT import any of the scripts
supplied with the Control HMI application. These scripts include:

B0750TP, Rev E 117

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

• Data Change scripts with a prefix of “Z” plus the $Operator and
$Language scripts
• Key scripts for the Ctrl and Shift keys, Home, Return, plus the F1 and
F12 keys
• Conditions scripts with a prefix of “Z”, plus the $InactivityWarning
• Quick Functions with a prefix of “hmi” or “Z”
• The Application Script
c. Verify that you select the Use Existing Tags checkbox.
d. On the Application Data Import Options dialog box, click Import.

118 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

4. Import all the user-built windows from the Standalone Source application or
exported managed windows. If third-party ActiveX controls are used within
InTouch windows, verify to install the controls prior to importing windows from the
legacy application. For more details, see EcoStruxure™ Foxboro™ DCS Window
Construction User's Guide (B0750AS)
a. From WindowMaker software, select File > Import > Visualization >
Windows and scripts. The Import from Directory dialog box appears.
b. From the Import from Directory dialog box, select the InTouch directory for
import.
Select the InTouch Application that contains the user-built process graphics
windows.
NOTE: For managed applications, select the folder where the original
managed application windows were exported. See Exporting and Importing
Windows Between Managed Foxboro DCS Control HMI Applications, page
121.

5. To import the window:

a. From the Import dialog, select the Windows tab .
b. Click on the window to select the user-built windows in the application (that
is, select all windows that do not start with the prefix “Z”).

B0750TP, Rev E 119

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

c. Select the Use Existing Tags checkbox.

d. From the Application Data Import Options dialog box, select Import.
Depending on how many windows are being imported, it might take many
minutes for the import to complete.

Migrating InTouch and Alarm Hot Backup Files

This step is only needed if the Alarmgrp.ini file is used for large queries or there are
configured Alarm Hot Backup Pairs configured in the original application.
1. Confirm the latest Control HMI Application is open in WindowMaker.
2. Open Windows Explorer and browse to the CheckedOut folder of the original
application. It is typically located in D:\Program Files\ArchestrA
\Framework\FileRepository\<Your Galaxy Name>
\ObjectFileStorage\<Original CHMI Template Name>\CheckedOut
For example: D:\Program Files\ArchestrA\Framework
\FileRepository\AW001_GR\ObjectFileStorage\$ControlHMI_v71
\CheckedOut
3. Copy the alrmgrp.ini and provacc.ini files if they exist.
4. Browse to the CheckedOut folder of the latest Control HMI template. It should be
located under the same ObjectFileStorage folder as described in Step 2.
For example: D:\Program Files\ArchestrA\Framework
\FileRepository\AW001_GR\ObjectFileStorage\$ControlHMI_v72
\CheckedOut
5. Paste the copied files into the CheckedOut folder.
6. Save and close WindowMaker.

120 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

Updating User Startup Application

When switching from the Standalone Control HMI application to the managed Control
HMI application, it might be necessary to update which application starts when each
user logs into the workstations.
To change the application startup, log in as each user and:
1. Close WindowMaker and WindowViewer.
2. Open the InTouch Application Manager. Navigate to Start > AVEVA InTouch HMI
> Application Manager.
3. Select the listed managed Control HMI application. For example:

4. Click ... > WindowViewer to launch the application.

5. Exit WindowViewer when done.
6. Repeat for each user login.
After changes have been made to one user setup, the modified user win.ini file
can be manually copied to other user win.ini files instead of logging in as each
user and repeating the process. User win.ini files are located in: c:\Users
\<userID>\AppData\Local\Wonderware.

Exporting and Importing Windows Between Managed

Foxboro DCS Control HMI Applications
Managed application windows might contain instances of Industrial Graphics. These
windows cannot be imported into standalone applications and need to be exported
before they can be imported into other managed applications.
Moving InTouch windows from one Galaxy to another needs that the associated
Custom Industrial Graphics be exported from the source Galaxy and imported into the
destination Galaxy.

B0750TP, Rev E 121

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

Exporting Industrial Graphics

This step is only needed if the managed applications reside in two different Galaxies.
Users will open the System Platform IDE Graphic tool box and export all custom
graphics that are used in the InTouch windows.
• Open System Platform IDE.
• Open the Graphic Toolbox.
• Browse to and select all custom graphics.
• Right-click and select Export > Selected Object(s).
• Select a folder to store the graphics and click Save.
This needs to be the same folder where the InTouch Windows will be exported.

Exporting InTouch Windows

These steps are needed only when merging two managed applications. Users will
open the source managed application and export the InTouch windows.
1. Open System Platform IDE.
2. Open the Template Toolbox.
3. Browse to and double-click on the Control HMI template that contains the InTouch
windows to be exported. This will open WindowMaker.
4. From WindowMaker, select File > Export .
5. Select a folder to store the InTouch Windows and click OK.
This needs to be the same folder where the custom Industrial Graphics were
exported.
6. Select the windows to export from the dialog box and click OK.

Importing Industrial Graphics

This step is only needed if the managed applications reside in two different Galaxies.
Users will open the System Platform IDE and import the custom graphics package
that was exported from the source Galaxy.
1. Open System Platform IDE.
2. From the Galaxy menu, select Import > Objects > From package.
3. Browse to the folder that contains the export package.

122 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

4. Select the package and click Open to open the Import Preference dialog box.

5. Select the appropriate import options and click OK.

Importing InTouch Windows

This step is needed only when merging two managed applications. Users will open
the source managed application and export the InTouch windows.
1. Open System Platform IDE.
2. Open the Template Toolbox.
3. Browse to and double-click on the Control HMI template where windows are
being imported. WindowMaker appears.
4. From WindowMaker select File > Import.
5. Select a folder that contains the exported InTouch Windows and click OK. The
Import Options dialog appears.
6. Perform the normal import procedure as described in Importing Scripts and
Windows Using WindowMaker Application, page 116.

B0750TP, Rev E 123

 Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Control Software v8.0 Installation Guide Version

Recustomizing AlarmPanel Windows

If the AlarmPanel windows were customized in any way, for example, moved or
removed columns, then these customizations need to be done again.

Restarting WindowViewer Application

Imported windows need to be compiled after the migration process is complete. Click
InTouch WindowMaker > Runtime to launch InTouch WindowViewer.
The newly imported windows will recompile. This might take a while.
NOTE: As part of the compilation process, some detected error messages appear
which need to be acknowledged before the compilation can continue.

These detected error messages are normal and can be ignored. They are caused
by the configuration of the AlarmPanel window through InTouch tags.

Upgrading Client Workstations

Install the Control Software v8.0 on client workstations after the Control HMI
application has been migrated. After the installation, the client workstations can be
upgraded with the upgraded migrated application.
The changes to the managed application need to be re-deployed if the client
workstations were upgrade before migrating the application was migrated.
1. Open the System Platform IDE.
2. Open the Deployment View.
3. Select the deployed instance of the Control HMI application.
It is located on the station's AppV engine: <StationID>_Plat > <stationID>_
AppV > <StationID>_HMI.
4. Right-click on the instance and select deploy to deploy changes.
5. Repeat the process for each client workstation.
NOTE: Wait until deployment is complete before closing IDE. The HMI
deployment and file transfer can take several minutes depending on the
system and network performance. The IDE Deployment tree view icon for
Control HMI App Engine changes state to show Deployed when a transfer
completes successfully.

124 B0750TP, Rev E

Chapter 7: Upgrading to Latest Foxboro DCS Control HMI
Version Control Software v8.0 Installation Guide

Updating Application Startup

When switching from the standalone Control HMI application to the managed Control
HMI application, it might be necessary to update which application starts when each
user logs into the workstations.

Setting Application Startup (Preferred Method)

1. Log in as each user and:
a. Open the InTouch Application Manager: Start > AVEVA InTouch HMI >
Application Manager.
b. Select the listed managed Control HMI application.

2. Click ... > WindowViewer to launch the application.

3. When finished, exit WindowViewer.
4. Repeat for each user login.

Setting Application Startup (Alternative Method)

Alternatively, you can rename the win.ini file located in each of the user folders to set
the startup.
1. Open File Explorer.
2. Browse to C:\Users.
This shows all users that have logged into the workstation.
3. Browse to the AppData\Local\Wonderware folder of each users.
4. If the folder exists, rename the win.ini file.
When a user logs into the station a new win.ini file is created with the proper
settings.

B0750TP, Rev E 125

 Chapter 8: Configuring Alarm Priority Mapping Icons on Galaxy
Control Software v8.0 Installation Guide Repository Stations Migrated to Control Software v8.0

Chapter 8: Configuring Alarm Priority Mapping Icons

on Galaxy Repository Stations Migrated to Control
Software v8.0
On systems that are migrated from Control Software v6.3 or older versions, the Alarm
Priority icons need to be imported in to the GR Node. These icons are used in the
Industrial Graphic Alarm Border animation to display the severity of the most urgent
alarm. For more information on Control HMI graphics and Alarm Borders, see
EcoStruxure™ Foxboro™ DCS Window Construction User's Guide (B0750AS).
The default Alarm Priority icons do not match the Alarm Styles that are installed on
new installations. These icons need to be updated with icons that match the Control
Software Alarm Styles.
To change the Alarm Priority icons:
1. Open System Platform IDE on a Galaxy Repository machine.
2. Select Alarm and Events Configuration window from Galaxy > Configure >
Galaxy > Alarms and events.
The icons will appear.

126 B0750TP, Rev E

Chapter 8: Configuring Alarm Priority Mapping Icons on Galaxy
Repository Stations Migrated to Control Software v8.0 Control Software v8.0 Installation Guide

3. To update the icon for each severity:

a. Click ....
b. Browse to C:\Program Files (x86)\Invensys\InFusion\View
\Support folder.
c. Select the respective icons from each severity.

Severity File to Select

1 alarm24x24_1.png
2 alarm24x24_2.png
3 alarm24x24_3.png
4 alarm24x24_4.png

After the icons are updated, they need to match the icons as shown.

NOTE: Any image file of type *.bmp, *.png, *.jpg, *.gif. *.jpeg, *.tif, *.tiff, *.
ico and *.emf could be used as the icon for each Alarm Severity. If you
modify the Alarm Border Element Styles, you also need to update these
icons accordingly. For more information on Element Styles, see AVEVA
User Documentation, page 11.

B0750TP, Rev E 127

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

Chapter 9: Installation Troubleshooting

This chapter provides resolutions for issues that might occur during the Control
Software installation process.

Galaxy Migration
Detected Problem Resolution
During Galaxy migration and Switch from multi thread to single thread migration mode and restart
preparation, some objects did not migration.
migrate due to multi threaded
1. In the Galaxy Repository workstation, navigate to the following path in the
operations.
Registry Editor:
\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA
\Framework\GR
2. Add new value (for example, DWORD 32 bit) and rename as
EnableMTM attribute and set value to 0.
3. Add new value (for example, DWORD 32 bit) and rename as
ForceMaxMTMThreads attribute and set value to 1.
4. Reboot the Galaxy Repository workstation.
5. Delete the Galaxy.
6. Restart the Galaxy migration process.
After migration, return to multi threaded mode.
1. In the Galaxy Repository workstation, navigate to the following path in the
Registry Editor:
\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA
\Framework\GR
2. Change the EnableMTM attribute value from 0 to 1.
3. Change ForceMaxMTMThreads attribute value from 1 to 0.
4. Reboot the Galaxy Repository workstation.

Network Account
Detected Problems Resolution
OCMC shows system messages/ 1. Open the Start > AVEVA > Change Network Account.
notification messages - User
2. Enter the domain name in the Local Machine/Domain field.
Account does not exist on
(workstation name) 3. Enter the Network Account.

OCMC shows system messages/ 4. Enter a valid password.

notification messages – Failed to 5. Verify that the same user is used on Galaxy Repository and the client
Impersonate user stations.

128 B0750TP, Rev E

Chapter 9: Installation Troubleshooting Control Software v8.0 Installation Guide

IASeriesAlarmProvider
Detected Problem Resolution
During the CS v8.0.1 upgrade process, if you reboot your workstation before the There is no functionality loss.
Galaxy Preparation process is complete, errors and warnings will appear in the
OCMC. You can ignore these errors and
warnings. These messages will not
These messages appear because the IASeriesAlarmProvider object has not be displayed in the OCMC after the
upgraded to the latest version yet. This object upgrades during Galaxy IASeriesAlarmProvider object
Preparation. After that, these errors/warnings will not appear. upgrades during Galaxy
preparation.
•
IASeriesAlarmProviderRuntime3 Invalid pointer
(80004003) caught at line 168 in
PrimitiveRuntimeSupport.h (in C:\Dev\agent\_work\4\s
\Shared Components\Aveva\MagellanPublic\Includes\SDK\).
•
17388 17392 Error BRO AWSE23_Alrm -
CBaseRuntimeObject::Execute - Execute on primitive id
100 failed. hr = 80004003
•
17388 17392 Error BRO AWSE23_Alrm -
CBaseRuntimeObject::Execute - Going off scan due to
error.
•
Error BRO AWSE23_Alrm - CBaseRuntimeObject::
AddError - Going off scan due to error.
•
17388 17392 Warning BRO AWSE23_Alrm
- CBaseRuntimeObject::UserSetAttributeEx_Common - Sets
are not allowed on a quarantined object.
•
Warning ApplicationCategory Failed to
set object offscan - [group:1 - 1 of 1] object: 3,
status - success:False, categ:<7:
MxCategorySoftwareError>, detected:<5:
MxSourceRespondingAutomationObject>, detail:8016

B0750TP, Rev E 129

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

Galaxy Preparation
Detected Problems Resolution
In the Galaxy Preparation window, 1. Verify whether the Network Account user name is the same on both the
Galaxies are not listed Galaxy server and the client. If not, change the client’s network name as
follows:
Navigate to Start > AVEVA > Change Network Account.
All the Control Software workstations connecting to a Galaxy
workstation need to have the same network account settings.
2. Verify the Application Server license is valid. Start the System Platform
IDE, but do not connect. If the Connect dialog box is displayed without
any detected error dialogs or messages in OCMC, the license is correct.
Perform this step on both the Galaxy Repository and client stations. If
the dialog box reports detected errors, provide valid licenses and retry.
In the Galaxy Preparation window, Open System Platform IDE/Control Editors, open the detected failed object’s
if you see these messages: editor. Update the values manually.
Failed to assign attributes Deploy the platform and its child objects manually.
Failed to deploy the platforms

Foxboro DCS Control Software Installation

Detected Problems Resolution
Unable to open multiple IDE Enable more ports on the client station.
sessions on a client station.
1. End unrequired processes or applications that are using the ports.
For example, the Direct Access application uses a port.
2. Update the port range to allow more ports.
To set a new port range in DCOM scripts:
1. Copy the \DCOMScriptsfolder from the ...\SupportFiles folder,
available on the Control Software v8.0 installation DVD, to C:\.
2. Open the C:\DCOMScripts folder.
3. Edit the UninstallDComScripts.bat file.
Replace SET DComScriptsPATH=%1 with
SET DComScriptsPATH=C:\DComScripts.
4. Double-click the UninstallDComScripts.bat file to uninstall DCOM
script.
5. Reboot the station.
6. Open the C:\DCOMScripts folder
7. Edit the port range from 10004-10021 to the desired port range in
DCOMconfig.PS1. For example: To allow 3 additional ports, update the
range as 10004–10024.
8. Save the DCOMconfig.PS1 file.
9. Install the DCOM script.
10. Reboot the station.

130 B0750TP, Rev E

Chapter 9: Installation Troubleshooting Control Software v8.0 Installation Guide

Workstation Recovery
NOTE: In order for the following procedure to be viable, the Galaxy database
needs to be backed-up on a regular basis. Additional backups might be needed if
extensive database changes are made. Any changes made after a backup, but
before performing these steps, will be lost.
This procedure will guide the installation of workstations with run-time Control
Software which were unsuccessful (that is, hard drive failure) or are undergoing a
planned hardware upgrade. Backups and restorations need to be made at the same
software version.

Galaxy Host Station

1. Load the replacement hardware with the appropriate Windows operating system.
2. Load the replacement hardware with Control Core Services software v9.8 or later
(as needed by Control Software) and any trailer CDs, if included in the desired
configuration.
3. Install the desired Galaxy host workstation configuration. DO NOT run the Galaxy
preparation utility.
NOTE: The next step needs to be performed from the Galaxy host
workstation if that workstation is licensed for the System Platform IDE. If this
workstation is not licensed for the System Platform IDE, then the following
steps can be performed from any workstation connected to the network.
4. Start the System Platform IDE (Start > AVEVA System Platform > System
Platform IDE).
a. From within the System Platform IDE logon screen, enter or select the name
of the Galaxy host workstation in the GR Node Name field (on the Galaxy
host workstation, this will be selected by default).
b. Click New Galaxy.
c. Enter the original name for your Galaxy in the Galaxy Name field and click
Create. If the original Galaxy name is not used, the restore will not succeed.
5. At the Galaxy host workstation, start the OCMC (Start > AVEVA > Operations
Control Management Console).
a. Expand the Galaxy Database Manager node.
b. Select the Galaxy you just created.
c. Select Action > Restore.
d. On Galaxy Database Manager dialog box, read the recommendations and
click Yes.

B0750TP, Rev E 131

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

e. Browse to the backup CAB file for your Galaxy host workstation and click
Open.
NOTE: After installing the Galaxy host workstation and installing the
Control Software, but before Step 6 through Step 9, there will be several
detected error messages in the OCMC log which are related to the
InFusion Sync Service. These detected error messages need to stop
appearing after the procedure has been completed.
6. At each client workstation, start the AVEVA OCMC (Start > AVEVA > Operations
Control Management Console.
a. Expand the Platform Manager node (you might have to login to the Galaxy).
b. Select the Galaxy name (created in Step 4).
c. Select Action > Remove Platform.
d. On the Would you like to remove the Platform? dialog box, click Yes.
e. In the right pane, the status of the platform is shown as transitioned to
Shutting Down.
f. After about a minute, the platform will be shut down. In the right pane, there
has to be an asterisk symbol along with the text: There is no platform
deployed to this node. At this point, the platform has been successfully
removed.

132 B0750TP, Rev E

Chapter 9: Installation Troubleshooting Control Software v8.0 Installation Guide

7. At the Galaxy host workstation, start the System Platform IDE (Start > AVEVA >
System Platform IDE).
a. Click Connect to enter the System Platform IDE editor for the restored
Galaxy.
b. For the Galaxy host workstation platform under the Deployment view, right-
click and select Deploy. Click OK to deploy the platform.
c. For each client platform under the Deployment view, right-click, and select
Undeploy. Select the On Failure Mark as Undeployed checkbox. Click OK
to undeploy the platform.
d. For each client platform under the Deployment view, right-click, and select
Deploy. Click OK to deploy the platform.
8. Open the Configurator dialog box by clicking Start > AVEVA > Configurator.
Select Galaxy Preparation in the left-pane of the Configurator dialog box. Select
the Galaxy Repository Node and Galaxy Name in the right-pane, and click
Configure to start configuring the Galaxy database.
The Galaxy Preparation utility will start the necessary services and processes.
Skipping this step will result in unexpected behavior of the application.
9. For each control processor (FCP280, FCP270, ZCP270, FDC280, or SCD6000)
under each equipment unit in the Deployment view:
a. Right-click the control processor.
b. Select Deploy Utilities > Synchronize DBs. This will synchronize the
Galaxy database with what is actually running in the physical control
processor.
c. Fix the inconsistencies manually in the Output View of the IDE.
NOTE: If there are no configuration/deployment changes from the last
known Galaxy backup, you can skip Step 9, because this process can
take days to complete, depending upon the size of your Galaxy.
NOTE: The previous step will not synchronize parameter value changes
made after the Galaxy was last backed-up, but prior to the Galaxy
restore.
10. Follow the procedures on refreshing the history and security database of the
Galaxy Sync Service in EcoStruxure™ Foxboro™ DCS Access Manager User's
Guide (B0750AD).

Client Station
1. Load the replacement hardware with the appropriate Windows operating system
(Windows 10 21H2 LTSC for a client station).
2. Load the replacement hardware with the appropriate version of Control Core
Services software v9.8 or later (as needed by Control Software v9.8) and trailer
CDs, if included in the desired configuration.
3. Install the desired client workstation configuration. DO NOT run the Galaxy
preparation utility.
4. From within the System Platform IDE, select the client workstation platform
object, right-click and select Deploy. Under the Deploy Status Mismatch group
box, select the Mark as Deployed checkbox. Click OK to deploy the platform.

B0750TP, Rev E 133

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

Modifying Domain Policy for Enterprise Edition CCS v9.8

1. Log on to the PDC using your domain administrator credentials (ex:-
CCSDomainAdmin).
2. Open the Group Policy Management console by selecting Start > Run, and
typing gpmc.msc.
3. Edit the GPO “SE Win10 Computer Security Compliance v1.0”:
a. In the left pane of the Group Policy Management console, expand the nodes:
Group Policy Management > Forest:<forest name> > Domains domain
name > Group Policy Objects.
b. Right-click on the GPO Foxboro Win10 21H2 Computer Security
Compliance v1.0 and from the context menu, select Edit. The Group Policy
Management editor opens.
c. Expand the nodes: Computer Configuration > Administrative Templates
> Windows Components > Internet Explorer > Internet Control Panel >
Security Page > Trusted Sites Zone.
d. On the right pane, select and double-click the setting Turn on Protected
mode.
e. Select Enabled.
f. In the Protected Mode combo box, set the value to Disable.

g. Click OK to close this dialog box.

h. In the same right pane, double-click Logon options.
i. Change the value in the Logon options combo box to Automatic logon
with current username and password.

134 B0750TP, Rev E

Chapter 9: Installation Troubleshooting Control Software v8.0 Installation Guide

j. Click OK to close this dialog box.

k. Close the Group Policy Management Editor dialog box.
4. Repeat Step 3 for the GPO “Foxboro Server 2022 Member Server Security
Compliance v1.0”.
5. On each Windows 10 21H2 LTSC/Windows Server 2022 domain client, run
gpupdate:
a. Log on to the Windows 10 21H2 LTSC/Windows Server 2022 domain client
using “iainstaller” credentials.
b. Open a command prompt in Administrator mode - search for cmd.exe, right-
click it, and select Run as Administrator.
c. In the command prompt, type gpupdate /force and press ENTER.
6. Add sites to Trusted Sites:
a. Log into the machine as a local administrator (ex:- IAInstaller).
b. Navigate to Start and search for Internet Options.
c. Open Internet Options.
d. Select the Security tab.

e. Select Trusted Sites.

B0750TP, Rev E 135

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

f. Click Sites.

g. Uncheck Require server verification (https:) for all sites in this zone.

h. Add the following sites to the list by typing each URL and clicking Add.
• http://localhost
• http://127.0.0.1
• https://localhost
• https://127.0.0.1
• http://<machinename>
• https://<machinename>
i. Click Close to close the Trusted Sites dialog box.
j. Click OK to close the Internet Options dialog box.
k. Restart Internet Explorer to apply the changes.

Modifying Local Policies for Local Edition CCS v9.8

1. Log on to the Windows 10 21H2 LTSC/Windows Server 2022 machine using
Account1 credentials.

136 B0750TP, Rev E

Chapter 9: Installation Troubleshooting Control Software v8.0 Installation Guide

2. Open the Local Group Policy Editor console by selecting Start > Run and typing
gpedit.msc.
3. Expand the nodes: Computer Configuration > Administrative Templates >
Windows Components > Internet Explorer > Internet Control Panel >
Security Page > Trusted Sites Zone.
4. On the right pane, select and double-click the setting Turn on Protected mode.
5. Select Enabled.
6. In the “Protected Mode” combo box, set the value to Disabled.

7. Click OK to close this dialog box.

8. In the same right pane, double-click Logon options.
9. Change the value in the “Logon options” combo box to Automatic logon with
current username and password.

B0750TP, Rev E 137

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

10. Click OK to close this dialog box.

11. Close the Local Group Policy Editor dialog box.
12. Add sites to Trusted Sites:
a. Log into the machine as a local administrator (ex:- Account1).
b. Navigate to Start and search for Internet Options.
c. Open Internet Options.
d. Select the Security tab.

e. Select Trusted Sites.

f. Click Sites.

g. Uncheck Require server verification (https:) for all sites in this zone.

h. Add the following sites to the list by typing each URL and clicking Add.
• http://localhost
• http://127.0.0.1

138 B0750TP, Rev E

Chapter 9: Installation Troubleshooting Control Software v8.0 Installation Guide

• https://localhost
• https://127.0.0.1
• http://<machinename>
• https://<machinename>
i. Click Close to close the Trusted Sites dialog box.
j. Click OK to close the Internet Options dialog box.
k. Restart Internet Explorer to apply the changes.

Configuring Control Software or SQL Services Originally

Running with FoxboroGMSA Accounts
To configure any Control Software or SQL services that were originally running with
the FoxboreGMSA account:
1. Log in as the local administrator on the machine. For example, IAInstaller.
2. Open the Command Prompt by right-clicking the program and clicking Run as
administrator.
3. Open the Services console by going to Start > Run > services.msc.
4. Right-click on the service that you need to reconfigure, and click Properties.
5. Make a note of the service name on the General tab.

B0750TP, Rev E 139

Control Software v8.0 Installation Guide Chapter 9: Installation Troubleshooting

6. Replace the Service name with the service name you noted down in this
command:
sc config <servicename> obj= "offmesh\FoxboroGMSA$" password=
""
7. Copy the command after replacing the text and paste it into the Command
Prompt window that is running in administrator mode.
8. Press Enter to execute the command.

The service is now reconfigured to run with the FoxboroGMSA account.

140 B0750TP, Rev E

Appendix A: Security Considerations and Procedures Control Software v8.0 Installation Guide

Appendix A: Security Considerations and Procedures

Security Guidelines
For more information on the security aspects, best practices, and considerations of
the Foxboro Distributed Control System (DCS) and components, see EcoStruxure™
Foxboro™ DCS Cybersecurity Reference Guide (B0700HZ).

Physical Access
Physical security of the plant control area is your responsibility. This can include
guarded gates to the site, security cameras, locks, badges, biometric devices, and so
on. The physical security of Schneider Electric-supplied workstations and servers is
the responsibility of the customer. Schneider Electric does not provide this level of
security.
It is also your responsibility to help ensure that media used in USB ports and the DVD
drive is verified for security conformance and approved content.

Enabling and Disabling Virus Scanning Software

Stations with ePolicy Orchestrator™ (ePO) Software Installed
For stations with ePO installed, disabling/enabling virus scanning can be done on a
per-station basis.
For I/A Series software v8.8, Control Core Services software v9.0, or later, see
Related Documents, page 10 for the appropriate EndPoint Protection document.

Enabling and Disabling Trellix Endpoint Security (ENS) Software

To disable virus scanning software on stations with ENS installed, perform these
steps:
1. Navigate to Start > Trellix > Trellix Endpoint Security.
2. The Status opens, which has two sections: Threat Prevention and Web Control.
Select the respective section to open the Settings menu. You can also do this by
clicking the downward facing arrow on the top-right corner of the application and
then clicking Settings.

B0750TP, Rev E 141

Control Software v8.0 Installation Guide Appendix A: Security Considerations and Procedures

3. Click Threat Prevention to open settings page. Clear the checkboxes: Enable
Access Protection, Enable Exploit Prevention, Enable On-Access Scanner
and Enable On-Access Scan on system startup. Click Apply.

142 B0750TP, Rev E

Appendix A: Security Considerations and Procedures Control Software v8.0 Installation Guide

4. Click Web Control to open settings menu. Clear the Enable Web Control
checkbox. Click Apply.

Enabling Virus Scanning

To enable virus scanning software on stations with ENS installed, perform these
steps:
1. Navigate to Start > Trellix > Trellix Endpoint Security.
2. The Status tab opens, which has two sections: Threat Prevention and Web
Control. Select the respective section to open the Settings menu. You can also
do this by clicking the downward facing arrow at the top-right corner of the
application and clicking Settings.

B0750TP, Rev E 143

Control Software v8.0 Installation Guide Appendix A: Security Considerations and Procedures

3. Click Threat Prevention to open settings page. Select the checkboxes: Enable
Access Protection, Enable Exploit Prevention, Enable On-Access Scanner
and Enable On-Access Scan on system startup. Click Apply.

4. Click Web Control to open settings page. Select the Enable Web Control
checkbox and click Apply.

144 B0750TP, Rev E

Appendix B: QuickPick Software Components Control Software v8.0 Installation Guide

Appendix B: QuickPick Software Components

This table shows what software components and features comprise each QuickPick
shown in the QuickPick Selection dialog box during the Control Software installation.

Feature List and Description of the Software Components

QuickPick Installed
Engineering Server Foxboro Control Database.
(Control HMI) • Foxboro Control Database File
• SyncService
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Control HMI (Runtime)
• Runtime Components.
Control HMI (Development)
• Windowmaker Components
Common Configuration Components.
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows Server 2022 Standard
Engineering Server (FoxView) Foxboro Control Database.
• Foxboro Control Database File
• SyncService
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components.
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows Server 2022 Standard
Engineering Server (Control HMI Dev Foxboro Control Database.
without Control Core Services)
• Foxboro Control Database File
• SyncService
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor

B0750TP, Rev E 145

Control Software v8.0 Installation Guide Appendix B: QuickPick Software Components

Feature List and Description of the Software Components

QuickPick Installed

Control HMI (Development)

• Windowmaker Components
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platforms
• Windows Server 2022 Standard
Engineering Server (FoxDraw without the Foxboro Control Database.
Control Software)
• Foxboro Control Database File
• SyncService
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows Server 2022 Standard
Engineering Server (No HMI) Foxboro Control Database.
• Foxboro Control Database File
• SyncService
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows Server 2022 Standard
Historian Server AVEVA Historian
• Historian
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations

146 B0750TP, Rev E

Appendix B: QuickPick Software Components Control Software v8.0 Installation Guide

Feature List and Description of the Software Components

QuickPick Installed
• Foxboro Control Utilities
Supported Platforms:
• All
Operator Station (Control HMI) Control HMI (Runtime)
• Runtime Components
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows 10 21H2 LTSC
Operator Station (FoxView) Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows 10 21H2 LTSC
Engineering Client Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Control HMI (Dev)
• Windowmaker Components
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• All
Engineering Client (without Control Core Control Editors
Services)
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor

B0750TP, Rev E 147

Control Software v8.0 Installation Guide Appendix B: QuickPick Software Components

Feature List and Description of the Software Components

QuickPick Installed

Control HMI (Dev)

• Windowmaker Components
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows 10 21H2 LTSC
Standalone (without Control Core Foxboro Control Database.
Services)
• Foxboro Control Database File
• SyncService
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platform:
• Windows 10 21H2 LTSC
Historical Data Collector Foxboro Control Historian Data Collector
• Data Collector
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities
Supported Platforms: All
Control HMI (Development) Control HMI (Development)
• WindowMaker Components
Control Editors
• Engineering Environment Utilities
• Documentation
• Unity Pro Configuration
• Grid Editor
Common Configuration Components
• Foxboro Control Customizations
• Foxboro Control Utilities

148 B0750TP, Rev E

Appendix B: QuickPick Software Components Control Software v8.0 Installation Guide

Feature List and Description of the Software Components

QuickPick Installed

Supported Platforms: All

InTouch Access Anywhere InTouch Runtime Features
• InTouch RunTime
• InTouch Alarm DB Logger
InTouch Access Anywhere Server
• InTouch Access Anywhere
Supported Platform:
• Windows Server 2022 Standard
Custom Selecting the Custom QuickPick allows you to customize the features
you want to install.
Return to the installation procedure and proceed to the next step to
continue with the customization.

B0750TP, Rev E 149

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

Appendix C: Installing AVEVA Licenses

This appendix provides information about the AVEVA licenses and describes the
procedures for installing them in different scenarios.
The AVEVA licensing system installed with Control Software is composed of a
browser-based License Manager and a License Server that together allow you to
share and deliver licenses for your installed products. The licensing system allows
centralized license management, removing the need for dongles, and increase license
security through Activated licenses.
The AVEVA Enterprise Licensing system is supported on the following web browsers:
• Internet Explorer version 10 and later
• Microsoft Edge
• Google Chrome version 33 or later
• Mozilla Firefox later version 28 or later
These are the components of the AVEVA Enterprise Licensing system:
License Manager
The License Manager allows you to quickly access and maintain licenses for certain
installed products in your environments using its scalable, flexible design features.
• Browser-based for scalability and ease of use. It can be remotely accessed by
any of the supported web browsers.
• Light-weight, standalone software that you can install on the same node as the
License Server computer, or on any other node depending on your deployment
needs.
• Manage one or multiple License Servers to organize and manage the licenses in
your unique environment.
• Access details about your licenses, such as usage information, from the License
Manager interface.
License Server
The License Server provides all the functionality to acquire, store, maintain, and serve
licenses to your installed software components.
• Licenses are hosted and maintained on the License Server.
• Securely serve any type of software applications being licensed, including
Windows browsers, tablets, and mobile devices.
• Provide current license usage information.
Activation Server
The Activation Server is a cloud-based Internet-accessible server that the License
Manager connects to for license activation. The License Manager connects to the
AVEVA Activation Server in the cloud only temporarily during the activation process.
For information about product licensing and activation, see AVEVA User
Documentation, page 11.

Activating Licenses
You must configure the License Server and activate the Foxboro DCS Control
Software product license(s) before configuring and using the installed product. The
License Activation is the process of enabling a purchased license on a License
Server for use by a product. The Activation Server takes an Activation ID, validates it,
and provides and an activated license in return.

150 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

You can activate licenses using one of these two methods:

• Online Activation
• Offline Activation

Activating Licenses Online

If your License Server installed machine has access to the internet and the AVEVA
Activation Server, you can use online activation to activate your licenses. Online
activation is the default mode.
1. Start the License Manager.
The browser-based manager is located in the AVEVA Folder (Start > AVEVA >
Enterprise License Manager and uses this URL: http://localhost/
AELicenseManager.
NOTE: If the License Manager is running on a remote node, substitute the
name for the localhost.

2. Click on the running server. Under License Summary, click Add License.
3. Click Browse to search for the desired license file (.xml) to import. If you already
imported licenses, select the checkbox that corresponds to the entitlement
containing the licenses you want to activate.

4. Click Activate.

B0750TP, Rev E 151

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

5. The License Activation panel closes and the selected licenses show as
Activated in the License Summary Grid.

Activating Licenses Offline

If your License Server installed machine does not have access to the internet and the
AVEVA License Activation Server, offline activation provides a workflow to activate
your licenses.
1. Start the License Manager.
The browser-based manager is located in the AVEVA Folder (Start > AVEVA >
Enterprise License Manager and uses this URL: http://localhost/
AELicenseManager.
NOTE: If the License Manager is running on a remote node, substitute the
name for the localhost.

2. Click the menu icon and select Activation Settings.

3. Select Offline Activation.

4. Click the menu icon and click Servers.

152 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

5. Under the License Summary, click Add License.

6. Click Browse to search for the desire license file to import. If you already
imported licenses, select the checkbox that corresponds to the entitlement
containing the license you want to activate.

7. Click Activate.
8. The License Activation panel closes, and the selected licenses show Pending
Activation Request in the License Summary Grid, and the Offline Activation
button turns yellow.
9. Click the Offline Activation menu and click Request Activation / Deactivation.

10. Click Yes on the confirmation dialog.

11. Navigate to the downloads folder and save the license return request file to a
portable media.

B0750TP, Rev E 153

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

12. On a computer with internet access, open either Edge or Chrome and navigate to
the AVEVA Customer Support website.

13. Click License Activation.

14. Under License Activation click Wonderware.
15. Click Choose file and browse to the license request return file, then click Upload
File.

16. Download and save the license response file to a portable media.

154 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

17. Return to the Enterprise License Manager. Click the Offline Activation menu
and select Receive Activation / Deactivation.

18. Browse and select the response file. The license status will show as Activated in
the License Summary Grid.

Deactivating Licenses
You need to deactivate or return the activated license back to the Activation Server, in
the following scenarios:
• In case you want to move the license to another License Server.
• Uninstall/Re-install of Control Software due to any problems seen or you suspect
that the earlier installation was not clean.

You can perform the license deactivation using one of these methods:
• Online Deactivation
• Offline Deactivation

B0750TP, Rev E 155

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

Deactivating Licenses Online

If your License Server installed machine has access to the internet and the AVEVA
License Activation Server, online deactivation provides a workflow to deactivate your
licenses. Online deactivation is the default mode
1. Start the Enterprise License Manager.
The browser-based manager is located in the AVEVA Folder (Start > AVEVA >
Enterprise License Manager and uses this URL: http://localhost/
AELicenseManager.
NOTE: If the License Manager is running on a remote node, substitute the
name for the localhost.

2. Click on the running server. Under License Summary, check the license and then
click Deactivate.

3. Click Yes on the confirmation dialog.

156 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

4. The license will be deactivated. The selected license(s) are removed from the
grid. You can activate these license(s) on the same server or a different server at
a later time.

Deactivating Licenses Offline

If your License Server installed machine does not have access to the internet and the
AVEVA License Activation Server, offline deactivation provides a workflow to
deactivate your licenses.
1. Start the License Manager.
The browser-based manager is located in the AVEVA Folder (Start > AVEVA >
Enterprise License Manager and uses this URL: http://localhost/
AELicenseManager.
NOTE: If the License Manager is running on a remote node, substitute the
name for the localhost.

B0750TP, Rev E 157

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

2. Click on the running server. Under License Summary, check the license and
then click Deactivate.

3. Click Yes on the confirmation dialog.

The license is still activated. There is another entry that shows the license status
as Pending Deactivation Request.
4. Click the Offline Activation menu and select Request Activation /
Deactivation.

5. Click Yes on the confirmation dialog.

6. Navigate to the downloads folder and save the license return request file to a
portable media.

158 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

7. On a computer with internet access, open either Edge or Chrome and navigate to
the AVEVA Customer Support website.

8. Click License Activation.

9. Under License Activation click Wonderware.
10. Browse to the license request return file, by clicking Choose file, enter the text
you see in the image, and click Upload file.

11. Download and save the license response file to a portable media.

B0750TP, Rev E 159

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

12. Return to the Enterprise License Manager. Click the Offline Activation menu
and select Receive Activation / Deactivation.

13. Browse and select the response file. The license will be deactivated. The
selected license(s) are removed from the grid. You can activate these license(s)
on the same server or a different server at a later time.

Enterprise License Server Configuration

The AVEVA License Server acquires, stores, and serves a license for Foxboro DCS
Control Software products. The AVEVA License Server and Manager provide
centralized license management.
The basic steps to configure the location of AVEVA Enterprise License Server are:
1. Navigate to Start > AVEVA > Configurator.
2. Select the AVEVA Enterprise License Server plugin.
3. Enter the Primary Server Name. If the License Server is not installed on the local
node, enter the License Server name.
4. Enter the Server Port. The default port is 55555.
5. Enter the Agent Port. The default port is 59200

160 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

6. Click Configure.

Reserving Licenses
You can reserve a specific product license for servers and workstations on the
network. Reserving a specific product license to a device helps ensure that a user
accessing that device can use the reserved license. This allows those features to be
reserved to a specific machine. The machine will no longer need to attempt to acquire
a specific feature when requested by the software. Licenses can be reserved for any
type of device, depending upon the configuration and functionality of the product.
To reserve a license for a server or workstation:
1. In the Servers Details page, click the Device Reservation tab.

2. Click Add Device.

B0750TP, Rev E 161

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

3. In the Device name field, type the name of the server or workstation for which
you want to reserve the license.
4. From the list of features, select the check boxes for the features you want to
reserve.

5. Click Add. The device and the selected features are displayed in the Device
Reservation tab.

6. Select Checkout and click Apply.

NOTICE
POTENTIAL DATA LOSS
You must ‘checkout’ the licenses. If you do not checkout the licenses, any
network failure or license server failure will lead to a situation in which operator
and engineering stations will not be able to recover from failure.
Failure to follow these instructions can result in data loss.

162 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

Exporting and Importing Reservations for Devices

You can export the device reservation details to a .csv file. The exported .csv file can
be edited to update any existing reservations or add new reservations. If any of the
listed licenses, present in the License Server, is not reserved for a device, a new or
existing device name can be added to which you want to reserve the license. The
edited .csv file can then be imported to the License Manager to update the device
reservation details.

Exporting the Device Reservation Details

1. In the Servers details page, click the Device Reservation tab.
2. Click Export. The License Reservations are exported in .csv format and saved in
Downloads folder. The file is saved with the default filename Reservations
<DeviceName> <Date Time>.

B0750TP, Rev E 163

Control Software v8.0 Installation Guide Appendix C: Installing AVEVA Licenses

3. Open the .csv file. The following details are available:

• Device name
• Count
• Feature
• Part number
• Version
• Expiry
• Checkout
• Comment

Editing .CSV File

1. Browse to the location where the .csv file is available.
2. Open the .csv file.
3. Edit the file as required. If any of the listed licenses is not reserved for a device,
you can add the device name to which you want to reserve these licenses.
4. Save the .csv file.

Importing the Device Reservation Details

1. In the Servers details page, click the Device Reservation tab.

164 B0750TP, Rev E

Appendix C: Installing AVEVA Licenses Control Software v8.0 Installation Guide

2. Click Import.

3. Browse and select the .csv file and then click Open.
4. Click Apply.
The updated reservation changes appear in the grid.

B0750TP, Rev E 165

Control Software v8.0 Installation Guide Appendix D: Verifying and Activating Microsoft Visio

Appendix D: Verifying and Activating Microsoft Visio

NOTE:
Diagnostic Log Files for Visio — When a user runs an Office application, such
as Word or Visio, diagnostic information is collected and saved to log files on the
user’s device. These log files contain information about the processes and
components running in the application, which can help detect, diagnose, and fix
issues, as well as contribute to improvements in Office.
Key Points:
• Log Generation: In earlier versions of Visio, there was an option to disable
the generation of these logs. However, this option is not available in Visio
2021, as the product has evolved, and security features have been
enhanced.
• Log Size Limit: The folders containing these logs will not exceed a size of
120MB.
For more information, see the Microsoft Support website and the Microsoft Learn
website. You can find articles that provide an overview of log files for Office.
Additionally, there are articles that provide insights into the features of the
respective Visio versions.

Verifying Visio 2021 Activation Status

1. From the Start menu, open Visio 2021.
The Your privacy matters dialog box appears.

2. Click Close.
• If the product is not activated, the Microsoft Office Activation Wizard
dialog box might appear.
• If Microsoft Office Activation Wizard does not appear after you open Visio
2021, proceed to Step 4.
3. Click Cancel.
4. Activate Visio 2021 using one of these methods (listed in order of preference):

166 B0750TP, Rev E

Appendix D: Verifying and Activating Microsoft Visio Control Software v8.0 Installation Guide

• Internet: see Activating Visio 2021 with Internet, page 168.

Internet connectivity is required only during the activation process
(approximately three minutes). If you cannot connect to the Internet because
of potential security risks, activate Visio using the telephone.
• Telephone: see Activating Visio 2021 by Telephone, page 168.
5. Click Account to validate your activation status.
The Account dialog box appears.

The Product Information section displays the Visio 2021 activation status.
• If your product is activated, you see Product Activated status. No further
action is required.

• If your product is not activated, you will see Activation Required. Proceed
to Step 6.
6. Use one of these methods (listed in order of preference):
• Internet: see Activating Visio 2021 with Internet, page 168.
• Telephone: see Activating Visio 2021 by Telephone, page 168.

B0750TP, Rev E 167

Control Software v8.0 Installation Guide Appendix D: Verifying and Activating Microsoft Visio

Activating Visio 2021 with Internet

1. Verify that the machine you are using to activate Visio 2021 is connected to the
Internet.
Internet connectivity is required only during the activation process.
2. From the Start menu, open Visio 2021.
The Visio dialog box appears.
3. Click Account.
The Account dialog box appears.
4. Under Product Information, click Activate Product.
The Microsoft Office Activation Wizard appears.
5. Select I want to activate the software over the Internet, then click Next.
This might take several minutes.
6. When the activation is complete, click Close. If necessary, disconnect your
machine from the Internet.
7. Verify that Visio 2021 is activated. See Verifying Visio 2021 Activation Status,
page 166.

Activating Visio 2021 by Telephone

1. From the Start menu, open Visio 2021.
The Visio dialog box appears.
2. Click Account.
The Account dialog box appears.
3. Under Product Information click Activate Product.
The Microsoft Office Activation Wizard appears.
4. Select I want to activate the software by telephone, then click Next.
5. In Step 1 of the Activation Wizard, select your country/region from the list.
Telephone numbers appear.
6. Call the telephone number and follow the instructions dictated on the call.
7. When prompted, provide your Installation ID (shown in Step 2), which is a string
of 63 numbers separated into 9 groups of 7 numbers each.
NOTE: The automated caller responds with your Confirmation ID. Take note
of this ID.
8. In Step 3, enter your Confirmation ID, then click Next.
9. When the activation is complete, click Close.
10. Verify that Visio 2021 is activated. See Verifying Visio 2021 Activation Status,
page 166.

168 B0750TP, Rev E

Appendix D: Verifying and Activating Microsoft Visio Control Software v8.0 Installation Guide

Activating Excel 2021 with Internet

1. Verify that the machine you are using to activate Excel 2021 is connected to the
Internet.
Internet connectivity is required only during the activation process.
2. From the Start menu, open Excel 2021.
The Excel dialog box appears.
3. Click Account.
The Account dialog box appears.
4. Under Product Information, click Activate Product.
The Microsoft Office Activation Wizard appears.
5. Select I want to activate the software over the Internet, then click Next.
This might take several minutes.
6. When the activation is complete, click Close. If necessary, disconnect your
machine from the Internet.
7. Verify that Excel 2021 is activated.

Activating Excel 2021 by Telephone

1. From the Start menu, open Excel 2021.
The Excel dialog box appears.
2. Click Account.
The Account dialog box appears.
3. Click Activate Product.
The Microsoft Office Activation Wizard appears.
4. Select I want to activate the software by telephone, then click Next.
5. In Step 1 of the Activation Wizard, select your country/region from the list.
Telephone numbers appear.
6. Call the telephone number and follow the instructions dictated on the call.
7. When prompted, provide your Installation ID (shown in Step 2), which is a string
of 63 numbers separated into 9 groups of 7 numbers each.
The automated caller responds with your Confirmation ID. Take note of this ID.
8. In Step 3, enter your Confirmation ID, then click Next.
9. When the activation is complete, click Close.
10. Verify that Excel 2021 is activated.

B0750TP, Rev E 169

Control Software v8.0 Installation Guide Appendix E: Installing Microsoft SQL Server 2019

Appendix E: Installing Microsoft SQL Server 2019

Manual Installation of Microsoft SQL Server 2019
Microsoft SQL Server is a mandatory prerequisite for installing Control Software. This
prerequisite is installed automatically from the Control Software DVD. Sometimes the
automatic installation can be unsuccessful due to various reasons. In such cases, you
need to install these prerequisites manually. Please note that, you must try using the
Control Software installation to auto install Microsoft SQL Server product. Only when it
is deemed that Control Software Installation is not able to successfully install it, you
should try installing manually.
NOTE: It is mandatory that SQL Server Installation is performed using a login user
as:
• A user that is a member of the ‘IA Installer’ group (Enterprise Edition setup).
• The same user that is used for installing the Control Software (Local Edition
setup).

Setting up the Foxboro GMSA on Enterprise Edition

SQL Server Installation uses a Group Managed Security Account (GMSA) that must
be available for use on the Foxboro DCS workstation. Perform these steps to set up
the system so the GMSA is fetched from the Primary Domain Controller (PDC).
1. Browse to the \InstallFiles\SupportFiles directory on the Control
Software DVD.
2. Copy FoxboroGMSAAcountScripts folder to the desired location, for example
C:\SQLInstall.
3. Open a Command Prompt with administrative privileges and browse to the C:
\SQLInstall\ FoxboroGMSAAcountScripts.
Enter the following command and press Enter.
InstallADServiceAcct_OnDomainComputer.bat

4. After executing the command, the command prompt displays the status of the
operation. If the operation was not successful, the GMSA was not retrieved from
the PDC. In such a case, do not proceed further and contact Customer Service.

170 B0750TP, Rev E

Appendix E: Installing Microsoft SQL Server 2019 Control Software v8.0 Installation Guide

Microsoft SQL Server 2019 Standard Edition

These steps describe how to set up and execute the required files for a successful
initial SQL Server 2019 standard installation on a Foxboro DCS workstation.

NOTICE
POTENTIAL INSTALLATION FAILURE
Perform the steps in this procedure exactly as described. Failure to properly
perform these steps can result in installation failure, incorrectly installed
components, or proper permissions not being provided to the databases.
Failure to follow these instructions can result in potential installation failure.

1. Browse to the \InstallFiles\SupportFiles directory on the Control

Software DVD.
2. For Enterprise Edition installation, copy SQLSTDManual_EnterpriseEdition.ini file
to the desired location, for example C:\SQLInstall.
For Local Edition installation, copy SQLSTDManual_LocalEdition.ini file to the
desired location, for example C:\SQLInstall.
3. For Enterprise Edition installation update these fields in SQLSTDManual_
EnterpriseEdition.ini:

Field Name Example

AGTSVCACCOUNT= AGTSVCACCOUNT=“foxboro.local
"<DomainName>\FoxboroGMSA$" \FoxboroGMSA$”
SQLSVCACCOUNT= SQLSVCACCOUNT=“foxboro.local
"<DomainName>\FoxboroGMSA$" \FoxboroGMSA$”
SQLSYSADMINACCOUNTS= SQLSYSADMINACCOUNTS=MESH01
<MachineName> \CSSQLAdmins
\CSSQLAdmins<DomainName> foxboro.local\CCSInstaller(a)
\<IAInstaller>
Where:
foxboro.local is the domain name
MESH01 is the machine name.
CCSInstaller is member of IA Installer group.
(a)Note: There is a space between the two account names:
MESH01\CSSQLAdmins foxboro.local\CCSInstaller

4. For Local Edition installation update these fields in SQLSTDManual_

EnterpriseEdition.ini:

Field Name Example

SQLSYSADMINACCOUNTS= SQLSYSADMINACCOUNTS=MESH01
<MachineName> \CSSQLAdmins MESH01\Engineer1
\CSSQLAdmins<MachineName>
\<loggedonAccount>
Where:
MESH01 is the machine name.
Engineer1 is the current logged in Administrator User Account.

B0750TP, Rev E 171

Control Software v8.0 Installation Guide Appendix E: Installing Microsoft SQL Server 2019

5. Verify that the Control Software Database Management DVD is present in DVD
drive.
6. Open a command prompt with administrative privileges and browse to the
SQLSTD2019 folder in the DVD drive.
For example, for a DVD drive mounted to E:\: Open command prompt and enter
CD E:\SQLSTD2019 and press Enter.
7. Enter this command and press Enter:
For Enterprise Edition installation
setup.exe /ConfigurationFile=C:\SQLInstall\SQLSTDManual_
EnterpriseEdition.ini.
For Local Edition installation
setup.exe /ConfigurationFile=C:\SQLInstall\SQLSTDManual_
LocalEdition.ini.
The installation process begins. When the installation is complete review the log
file at C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap
\Log for any detected errors or warnings.

Microsoft SQL Server 2019 Express Edition

Perform these steps to complete the initial installation of SQL Server 2019 Express on
a Foxboro DCS workstation.
1. Browse to the \InstallFiles\SupportFiles directory on the Control
Software DVD.
2. For Enterprise Edition installation, copy SQLEXPManual_EnterpriseEdition.ini file
to the desired location, for example C:\SQLInstall.
For Local Edition installation, copy SQLEXPManual_LocalEdition.ini file to the
desired location, for example C:\SQLInstall.
3. For Enterprise Edition installation update these fields in SQLEXPManual_
EnterpriseEdition.ini:

Field Name Example

AGTSVCACCOUNT= AGTSVCACCOUNT=foxboro.local
"<DomainName>\FoxboroGMSA$" \FoxboroGMSA$
SQLSVCACCOUNT= SQLSVCACCOUNT=foxboro.local
"<DomainName>\FoxboroGMSA$" \FoxboroGMSA$
SQLSYSADMINACCOUNTS= SQLSYSADMINACCOUNTS=MESH01
<MachineName> \CSSQLAdmins foxboro.local
\CSSQLAdmins<DomainName> \CCSInstaller
\<IAInstaller>
Where:
foxboro.local is the domain name
MESH01 is the machine name.
CCSInstaller is member of IA Installer group.

172 B0750TP, Rev E

Appendix E: Installing Microsoft SQL Server 2019 Control Software v8.0 Installation Guide

4. For Local Edition installation update these fields in SQLSTDManual_

EnterpriseEdition.ini:

Field Name Example

SQLSYSADMINACCOUNTS= SQLSYSADMINACCOUNTS=MESH01
<MachineName> \CSSQLAdmins MESH01\Engineer1
\CSSQLAdmins<MachineName>
\<loggedonAccount>
Where:
MESH01 is the machine name.
Engineer1 is the current logged in Administrator User Account.

5. Verify that the Control Software Database Management DVD is present in DVD
drive.
6. Open a command prompt with administrative privileges and browse to the
SQLEXP2019 folder in the DVD drive.
For example, for a DVD drive mounted to E:\: Open command prompt, enter CD
E:\SQLEXP2019, and press Enter.
7. Enter this command and press Enter:
For Enterprise Edition installation
setup.exe /ConfigurationFile=C:\SQLInstall\SQLEXPManual_
EnterpriseEdition.ini.
For Local Edition installation
setup.exe /ConfigurationFile=C:\SQLInstall\SQLEXPManual_
LocalEdition.ini.
The installation process begins. When the installation is complete review the log
file at C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap
\Log for any errors or warnings.

B0750TP, Rev E 173

Control Software v8.0 Installation Guide

Glossary
A
ACN: Auxiliary Communications Network

ASP: AVEVA™ System Platform

AVEVA™ Industrial Graphics: Industrial Graphic Editor tool used to create and edit to
visualize data in an HMI/SCADA system.

AVEVA™ System Platform: The open and extensible technology based on a

distributed, object oriented architecture for supervisory control and manufacturing
information systems.

B
BIOS: Basic Input/Output System

C
COA: Certificate of Authenticity

Compound Summary Access (CSA): Data on the compounds and blocks residing
on a control processor. A central CSA server monitors all the compounds in the
Foxboro DCS system.

Control Core Services (CCS): Core software environment, formerly known as “I/A
(Intelligent Automation) Series software”.

Control Editors (CE): Control software engineering and configuration tools built on
the AVEVA™ System Platform Integrated Development Environment in Foxboro DCS.
Formerly known as “FCS Configuration Tools”, “InFusion Engineering Environment”,
and “IEE”.

Control HMI (CHMI): The collection of windows and related configuration files that
make up the HMI as viewed within InTouch software in Foxboro DCS. Formerly
known as the “FCS InTouch Application”.

Control Network: A switch network that facilitates communications among Foxboro

DCS workstations/servers and other stations. Formerly known as “The MESH Control
Network”.

Control Processor (CP): Foxboro DCS stations acquire input data from sensors and
control field devices through fieldbus modules. The CP performs any mix of
integrated first-level automation functions, such as continuous, sequential, or discrete
logic functions. The CP contains compounds and blocks to perform its control
functions.
NOTE: For conciseness, documents refer to “CP”, which means “a Foxboro DCS
station containing objects”. Such stations include, but are not limited to, the
Control Processors, Device Integrators, and APs.
Control Software (CS): Packages built on the AVEVA™ System Platform Integrated
Development Environment that provide expanded functionality to the Foxboro DCS
Control Core Services. Formerly known as “Foxboro Control Software”.

D
DCS: Distributed Control System. Overall term that refers to a control system in which
the safety control components are distributed, with each component controlled by one
or more controllers.

174 B0750TP, Rev E

 Control Software v8.0 Installation Guide

Device Integration Object (DIO): AVEVA™ System Platform object that manages
communication between an external server and the controller. It enables the operator
to communicate with configured controllers, process commands, and receive
tagname data.

DIMM: Dual In-line Memory Module

E
ECC: Error Checking and Correction

Enterprise Edition Control Core Services: Version of the Control Core Services v9.4
or later for systems requiring Microsoft® Active Directory Domain Controllers.

F
FoxView: An interface between the user and DCS process to view real time plant
data.

Framer: Control HMI tool to organize InTouch™ WindowMaker™ windows into a

representation of a plant facility. It is accessed through the InTouch WindowMaker in
System Platform™ IDE.

G
Galaxy: The database used by System Platform™. Also referred to as “Galaxy
Repository.”

GB: Gigabyte

GCIO: Graphics Controller Input/Output.

Gen10: Model H90 Standard Server or Model V91 Virtualization Host Server (HP
DL380 Gen10)

gMSA: Group Managed Service Accounts

I
iLO: Integrated Lights-Out

IML: Integrated Management Log

IO or I/O: Input and Output or Input/Output

N
NIC: Network Interface Card

O
OCMC: Operations Control Management Console or System Platform System
Management Console. The central runtime system administration/management user
interface in which all required runtime administration functions can be accomplished.

OEM: Original Equipment Manufacturer

OSD: On-Screen Display

P
PCIe: Peripheral Component Interconnect Express

B0750TP, Rev E 175

Control Software v8.0 Installation Guide

Platform Object: A representation of the physical hardware that the System

Platform™ software is running on. The Platform Objects hosts the Engine Objects
(see WinPlatform).

POST: Power On Self Test

Process Automation System: An overall term used to refer to a system which might
include either, or both, Foxboro DCS Control Software and Foxboro DCS Control
Core Services.

R
RAID: Redundant Array of Independent Disks

RAM: Random Access Memory, a form of computer data storage.

RGU: Remote Graphics Unit

S
SATA: Serial Advanced Technology Attachment computer bus interface for connecting
host bus adapters to mass storage devices such as hard drives and optical drives.

SFF: Small Form Factor

System Definition (SysDef): A system configurator.

System Manager (SM): Current user interface for equipment status and change
actions.

System Platform™ IDE: The integrated design and development tool from which all
System Platform objects are configured and deployed to PCs. Use the IDE to create,
configure, and maintain the objects and underlying infrastructure required to
communicate with Triconex controllers in a System Platform environment.

T
TCP/IP: Transport Control Protocol/Internet Protocol, the global standard
communication protocol for the Internet. Can also be used for private networks such
as corporate intranets and distributed control systems.

TCP/IP is a routable protocol, which means that all messages contain not only the
address of the destination station, but the address of a destination network. This
allows TCP/IP messages to be sent to multiple networks in an organization or around
the world, hence its use in the internet.

U
UEFI: Unified Extensible Firmware Interface

V
V91: Model V91 Virtualization Host Server. Hardware supported by Schneider Electric
for Control Core Services and the Control Software virtual machines.

V95: Model V95 Virtualization Host Server. Hardware supported by Schneider Electric
for Control Core Services and the Control Software virtual machines.

VGA: Video Graphics Array. Connector used for computer video output.

VLAN: Virtual Local Area Network

176 B0750TP, Rev E

 Control Software v8.0 Installation Guide

W
WindowMaker: An AVEVA application used for Control HMI Development.

WindowViewer: An AVEVA application used for Control HMI Runtime.

WinPlatform: An object that represents a single computer in a Galaxy, consisting of a

systemwide message exchange component, a set of basic services, the operating
system, and the physical hardware. This object hosts all AppEngines, and is a type of
Platform object.

B0750TP, Rev E 177

Schneider Electric Systems USA, Inc.
70 Mechanic Street
Foxboro, Massachusetts 02035–2040
United States of America

Global Customer Support: https://pasupport.se.com

As standards, specifications, and design change from time to time,

please ask for confirmation of the information given in this publication.

© 2023–2025 Schneider Electric. All rights reserved.

B0750TP, Rev E