FactoryTalk View Site Edition Version 5.0, 5.

1, SR1, SR2, (CPR9)

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)
For a distributed system using redundant HMI servers these are steps
to minimize downtime when applying software patch roll-ups
Depending on the design, content, and complexity of your control system, you might have to perform additional tasks to
support the patch roll-up installation, especially if you are patching several other non-FTView FactoryTalk enabled
products in a production environment. If that is the case, the goal of the information provided in this chapter is to help you
safeguard the live application, while helping to ensure that the patching process is efficient and successful.
To illustrate a path that includes such supporting tasks, this information describes how to patch a deployed network
application that consists of the following computers:
Example: FactoryTalk View SE network application with redundant servers

In this example, Server #1 is the name of the primary server computer, Server #2 is the name of the secondary server
computer, and Workstation #1 is the name of the engineering workstation.
As there are many possible variations for the architecture of any type of application, parts of this documented process
might not apply directly to the application you are patching.
If you have questions about architectural elements not covered in this chapter, for example, because your application is
more or less complex than the example provided, please contact your local Rockwell Automation Sales office for
assistance.

Page 1 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Overview: Patching an FTViewSE networked application that uses redundant HMI servers
Use the following multi-step checklist as a guideline for patching your redundant HMI server networked application.
Details about each step are described in more detail further on in this document.
Page

Part 1: Preparation for applying patch roll-up.................................................................................3

Step 1 Preparing to patch the FTViewSE HMI application.......................................................................3
Step 2 Back up the FTViewSE HMI application........................................................................................5

Part 2: Applying patches to computers in the FTViewSE network...............................................7

Step 3 - Apply patch roll-up on Server #1....................................................................................................7
Step 4 Apply patch roll-up on Workstation #1...........................................................................................8
Step 5 Apply patch roll-up on other selected Client computers................................................................8
Step 6 Test the FactoryTalk View SE application with the new patches...................................................8
Step 7 Apply patch roll-up on Server #2...................................................................................................9
Step 8 Apply patch roll-up on remaining un-patched Client computers..................................................10
Step 9 Test to verify redundancy operation for HMI and Data servers...................................................10
Step 10 Investigation of any potential issues that arise after initial testing.............................................11
Reference to additional Rockwell Automation Knowledgbase documents:...................................................12

Page 2 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Part 1: Preparation for applying patch roll-up

Step 1 Preparing to patch the FTViewSE HMI application
Before getting started with the upgrade:
Schedule down time for the upgrade.
Ensure that the user performing the upgrade has administrative rights.
Record the names and passwords of administrative users.
Ensure that the HMI server project is identical on the Primary and Secondary HMI servers.

Schedule down time for the upgrade

During the patch roll-up process described in this proceedure, the deployed FactoryTalk View SE application needs to be
shut down during Step 6 Test the FactoryTalk View SE application with the new patches. In your upgrade process,
be sure to schedule down time, and notify affected personnel about times when the application needs to be shut down.

Ensure that the user performing the upgrade has administrative rights
To perform certain tasks, the user performing the upgrade must have administrative rights in Windows and at the
FactoryTalk Network Directory.
Windows administrative rights are required to install FactoryTalk View SE and supporting software, because the setup
program creates program folders and modifies registry entries.
FactoryTalk administrative rights are required to log on to the FactoryTalk Network Directory, for example, when you use
the FactoryTalk Directory Server Location Utility.
To open the utility, you must log on as a FactoryTalk administrator on the local computer.
To specify a remote Network Directory location, you must also have administrative rights on the remote computer.
FactoryTalk administrative rights are also required to back up and restore FactoryTalk View SE applications.
Important:

During this process there are several activities that are preformed while disconnected from the network.
Although it is often possible to login to the FactoryTalk Directory using domain credentials (username &
password) when a domain controller is not available, it is recommended that you also have at least one
FactoryTalk User (specifically a NON-windows Linked user) which has administrative rights for the
FactoryTalk Directory.

Record the names and passwords of administrative users

Before backing up the deployed application, ensure that you have recorded the user names and passwords of users that
belong to the FactoryTalk administrators group.
Only members of the FactoryTalk administrators group can add, remove, or modify FactoryTalk user accounts, if this is
necessary after restoring a backed-up application.
Page 3 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Important:
Note:

The may
HMI
Redundant
You
Secondary
Server
also
HMI
status
use
HMI
servers
the
can
server
FactoryTalk
beinindicated
version
computer
Diagnostics
5.0,
bywill
either
5.1,
automatically
SR1,
the
Viewer
HMI
SR2,Server
to(CPR9)
reboot
check
properties
at
provide
and
theconfirm
end
awindow
preferred
of replication
the appropriate
or Server
Switchover
process.
Status
messages
option.
For
window.
more
are
Thesenote
Make
logged
detailed
windows
forinformation
server
of thecan
Switchover
status.
be
you
accessed
canoption
refer
bysetting.
opening
to the ItRockwell
FTView
can be set
Studio
Automation
to either
and right
ofKnowledgebase
theclicking
two options
on thebelow:
Answer
HMI server
ID 38407
name inthe application
Click
RSViewSE
Start >4.0
Alltree
(CPR7+)
Programs
and choosing
& 5.0
> Rockwell
(CPR9)
eitherHMI
Properties
Software
Project>or
Replication
FactoryTalk
Server Status.
Process
Tools
TheSteps.
>FactoryTalk
Diagnostics
Administration
Viewer.
Console

Continue
will only
usingprovide
the secondary
the Server
server
Status
even
window.
when the primary server
becomes available again.
Switch over to the primary server when it becomes available.

Ensure that the HMI server project is identical on the Primary and Secondary HMI servers

1.

Be sure that the application and HMI project files on the primary server are the most recent up to date application
files, before you attempt to replicate them to the secondary server and then back them up.
Make sure the Primary HMI server is the Active server. Using FTView Studio, right click on the HMI server and
choose Properties. The dialog should indicate:
Primary Server:
Secondary Server:

Active
Standby

If the server status is not as indicated above then you need to stop this procedure now and investigate. Make any
adjustments or corrections before proceeding with the patch roll-up installation.

2.

Using FTView Studio, run the AlarmAcceptEdits command to ensure Alarm edits are up to date and synchronized
between the Primary and Secondary servers.

3.

Copy the HMI server project from the Primary to the Secondary computer. Using FTView Studio, right click on the
HMI server and choose properties. Go to the redundancy tab and press the Replicate Primary to Secondary button.
Review the HMI server status information. The dialog will indicate various status messages during the replicate
process.
Wait for the HMI server project replication to fully complete. Using FTView Studio, right click on the HMI server
and choose Properties. Do not proceed further until the dialog once again indicates the following:
Primary Server:
Secondary Server:

Active
Standby

Page 4 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Note:

The HMI Server Backup and Restore utility is installed with FTViewSE version 5.1, so for previous versions
the HMI Server Backup and Restore utility will need to be installed on Server #1 and on Server #2. For
more information you can refer to the Rockwell Automation Knowledgebase Answer ID 30310 Backup
and Restore Utility for HMI Server.

Step 2 Back up the FTViewSE HMI application

Back up the HMI server project
On Server #1, use the HMI Server Backup and Restore utility to back up the primary servers HMI project. Click Start >
All Programs > Rockwell Software > FactoryTalk View > Tools > HMI Server Backup and Restore. For details about
using the utility, click the Help button. It is always good practice to create a back up copy prior to making any edits or
changes to your HMI application / architecture.

Back up the application

On Server #1, use the FactoryTalk Administration Console to back up the deployed FactoryTalk View SE network
application.
The back-up operation creates an application archive that includes area names, server names, server properties, and
application languages. If the back-up operation includes System information, user and computer accounts, as well as other
FactoryTalk system-level settings, are also archived. For more information, see About backing up System information
with an application, next.
Other application files, such as HMI project files, product activation, and logged historical data (trends, alarms, and
diagnostic messages) must be backed up and restored separately.

About backing up System information with an application

The following illustration shows what a FactoryTalk View SE network application looks like, in the Explorer window in
FactoryTalk View Studio.

Page 5 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Important:

Before backing up an application, record the user names and passwords of administrative users set up for
the application, in case this information is required for the restore operation.

The FactoryTalk Network Directory is represented at the top of application hierarchy. One level down, the System folder
stores settings that are used by all the applications that belong to the same Network Directory.
For example, FactoryTalk user and computer accounts set up for each application are stored in the System folder.
When you back up a network application, System information for the application is not archived automatically.
To save the System information, for example, in order to preserve user and computer accounts, you must select the check
box, Backup System in archive.
If you do back up System information with a network application, when you restore the application, you can choose
whether to restore the archived System information. Keep in mind that the restored System information will not merge
with existing FactoryTalk System settings held at the current FactoryTalk Network Directory.
Instead, if the Network Directory on the local computer is active, you will replace user and computer accounts set up for
any other application using the directory.

To back up a network application

1.

On Server #1, click Start > All Programs > Rockwell Software > FactoryTalk Administration Console.

2.

In the Select FactoryTalk Directory dialog box, select Network, and then click OK.

3.

In the Explorer window, right click the application you want to back up, and then click Backup.

4.

Specify an archive name and location. To specify a location other than the default, type the path or click the Browse
button to find and select a location.

5.

Select the check box, Backup System in archive, and then click OK. The back-up operation saves an application
archive file with a .bak extension to the specified location. The default location is: C:\Documents and Settings\All
Users\Documents (Windows 2000, Windows XP, and Windows Server 2003).

Page 6 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Note:
Important:

Inyou
To
If
this
avoid
are
example
introducing
unableit to
is assumed
physically
mismatched
that
getand
the
access
FactoryTalk
incompatible
to the network
Network
patched
cables
Directory
software
for a is
computer,
components
also located
then
into
on
another
aServer
deployed
option
#1. is to
production
disable
However,
theifsystem
appropriate
the FT be
Directory
sure
network
to is
notlocated
card
startfrom
uponcomputers
within
another
thecomputer
or
Network
reconnect
in
Connections
the
them
network,
to the
forthen
network
the computer.
steps
before
1 and
To
you
3access
are instructed
the
above
Network
should be
Connections
to do
applied
so in to
thethe
window
following
computer
gosteps.
tohosting
the Control
the FT Directory
Panel or next.
click Sart > Run > type control
netconnections and press OK. (Typing ncpa.cpl will also open this window.)

Part 2: Applying patches to computers in the FTViewSE network

Applying the patch roll-up to computers in the networked redundant HMI application will be performed in stages. This
will provide the ability to test your application functionality with the latest patch roll-up on some of the computers before
committing all the computers in the network to the roll-up installation. If issues do appear after initial testing with the new
patch roll-up, you will be able to quickly fall back to running the HMI application on the computers that were not patched.
This can provide minimum downtime while any issues are investigated and corrected. This option is described in Step 10.

Step 3 - Apply patch roll-up on Server #1

Remove Server #1 from service.
Watch and confirm failover, where Server #2 becomes the Active HMI server.
Install patch roll-up on Server #1.

To remove Server #1 from service

While performing the patch installation it is important to remove the server from service, and prevent any clients from
attempting to use the server during the update.
The most effective way to remove the server from service is to physically remove it from the network so that no other
computer on the network can access it.

1.

The computer will need to be disconnected from the network. Physically remove all network cables from either ports
on the computer or their corresponding connections at a switch.

2.

Wait for Server #2 to become the Active HMI server. Using FTView Studio, right click on the HMI server and choose
Properties. Do not proceed further until the dialog indicates the following:
Primary Server:
Secondary Server:

3.

Not Available
Active

Install any required patch roll-ups to Server #1 as outlined in the in Rockwell Automation Knowledgebase Answer ID
47015 - FactoryTalk View SE 5.00.00 (with CPR9 platform) - Patch Roll-up. Reboot Server #1, but do not
reconnect it to the network until instructed to do so later on in this procedure.

Page 7 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Note:
Important:

In this
You
For
this
can
example
part
test of
thethe
itFactoryTalkViewSE
isupgrade,
assumedthe
thatFactoryTalk
theapplication
FactoryTalk
Viewwith
SE
Network
the
application
new
Directory
patches
is shut
isusing
also
down
located
only
temporarily
Server
on Server
#1until
and#1.
Server #1
Workstation
and
However,
Workstation
if the
#1.FTHowever,
#1
Directory
are connected
there
is located
are tomany
onthe
a computer
network
possible and
in
variations
therestarted.
network
for other
the
In your
architecture
thanpatch
Server
roll-up
of
#1,any
then
installation
application
process,
this
patched
beand
sure
FT
you
toDirectory
schedule
have many
computer
down
HMItime,
Client
should
and
computers.
notify
beaffected
connected
You may
personnel
choose
to the
about
tonetwork
patch
times
several
when
and started
other
the application
clients to
needs
before
at
Server
be
thisshut
time.
#1down.
as
Do
per
not
Step
patch
2. all of your Client computers now. Leave some temporarily
un-patched in case you need to fail back to running an un-patched system. Skip Step 5 if you
do not wish to patch additional Client computers at this time.

Step 4 Apply patch roll-up on Workstation #1

Remove Workstation #1 from service.
Install patch roll-up on Workstation #1.
1.

The computer will need to be disconnected from the network. Physically remove all network cables from either ports
on the computer or their corresponding connections at a switch.

2.

Install any required patch roll-ups to Workstation #1 as outlined in the in Rockwell Automation Knowledgebase
Answer ID 47015 - FactoryTalk View SE 5.00.00 (with CPR9 platform) - Patch Roll-up. Shutdown Workstation #1,
but do not reconnect it to the network until instructed to do so later on in this procedure.

Step 5 Apply patch roll-up on other selected Client computers

Remove HMI Client computer(s) from service.
Install patch roll-up on Client computer(s).
1.

The computer will need to be disconnected from the network. Physically remove all network cables from either ports
on the computer or their corresponding connections at a switch.

2.

Install any required patch roll-ups to Client computers as outlined in the in Rockwell Automation Knowledgebase
Answer ID 47015 - FactoryTalk View SE 5.00.00 (with CPR9 platform) - Patch Roll-up. Shutdown Client, but do
not reconnect it to the network until instructed to do so later on in this procedure.

Step 6 Test the FactoryTalk View SE application with the new patches
Disconnect all non-patched computers from the FTViewSE network.
Reconnect Server #1 to the network (Computer is patched and already running).
Reconnect patched Workstation #1 and start up computer (Also reconnect any other patched Client computers).
Open FTView Studio and Client to confirm everything is performing as expected.

1.

All computers that were not patched will need to be disconnected from the network. Physically remove all network
cables from either ports on the computer or their corresponding connections at a switch.

2.

Reconnect Server #1 to the network. This computer should already be running and ready as per Step 3. (If for some
reason it is not up, then start the computer and wait approximately 5 minutes after the computer has come back up to
allow time for all HMI server processes to complete their start up procedures.)

3.

Using FTView Studio, right click on the HMI server and choose Properties. Do not proceed further until the dialog
indicates the following:
Page 8 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)
Primary Server:
Secondary Server:

Active
Not Available

4.

Reconnect Workstation #1 to the network and start up the computer. Allow the computer to fully complete start up
procedures before continuing.

5.

On Workstation #1, Use FTView Studio to open your FTViewSE network application. Browse the application tree
and confirm all components appear as expected and that there are no errors or issues. Start up a Client and confirm
that it performs correctly and shows all expected data.

6.

Reconnect any other patched HMI Client computer to the network and start up the computer(s). Allow the computer
to fully complete start up procedures before continuing.

7.

Start up an HMI Client and confirm that it performs correctly and shows all expected data.

8.

If everything in the FTViewSE network application is performing as expected then proceed to:
Step 7 Apply patch roll-up on Server #2.
If not then jump ahead to:
Step 10 Investigation of any potential issues that arise after initial testing.

Step 7 Apply patch roll-up on Server #2

Remove Workstation #1 from service.
Install patch roll-up on Workstation #1.
Reconnect Server #2 to network.
Start Server #2, watch and confirm that Server #2 becomes the Standby HMI server.
1.

The computer will need to be disconnected from the network. Physically remove all network cables from either ports
on the computer or their corresponding connections at a switch.

2.

Install any required patch roll-ups to Server #2 computers as outlined in the in Rockwell Automation Knowledgebase
Answer ID 47015 - FactoryTalk View SE 5.00.00 (with CPR9 platform) - Patch Roll-up. Shutdown Server #2.

3.

Reconnect the patched Server #2 computer to the network and start up the computer. Wait approximately 5 minutes
after the computer has come back up to allow time for all HMI server processes to complete their start up procedures.

4.

Using FTView Studio, right click on the HMI server and choose Properties. Do not proceed further until the dialog
indicates the following:
Primary Server:
Secondary Server:

Active
Standby

Step 8 Apply patch roll-up on remaining un-patched Client computers

Reconnect patched Client computers and start up computer.
Open HMI Client to confirm everything is performing as expected.
1.

The computer(s) will need to be disconnected from the network. Physically remove all network cables from either
ports on the computer or their corresponding connections at a switch.

Page 9 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)
2.

Install any required patch roll-ups to Client computers as outlined in the in Rockwell Automation Knowledgebase
Answer ID 47015 - FactoryTalk View SE 5.00.00 (with CPR9 platform) - Patch Roll-up. Shutdown Client
computer.

3.

Reconnect the patched HMI Client computer to the network and start up the computer. Allow the computer to fully
complete start procedures before continuing.

4.

Start up an HMI Client and confirm that it performs correctly and shows all expected data

Step 9 Test to verify redundancy operation for HMI and Data servers
Confirm current HMI server status.
Confirm preferred HMI server Switch Over option.
Shutdown Primary HMI Server.
Confirm fail over to Secondary HMI Server and confirm HMI Client operation.
1.

Using FTView Studio, right click on the HMI server and choose Properties. Go to the redundancy tab and set and
confirm that the Switch Over option is set to your preferred option.

2.

Using FTView Studio, right click on the HMI server and choose Properties. If the dialog is as indicated below then
continue. If not, then something has occurred on your system that should be investigated and the status should be
corrected before continuing.
Primary Server:
Secondary Server:

Active
Standby

3.

Verify redundancy operation by gracefully shutting down the Server #1.

4.

Check that all HMI clients failover to Server #2.

5.

If youre preferred Switchover option is set to:

Continue using the secondary server even when the primary server becomes available again.
Then restart the Server #1 HMI server and confirm it reaches Standby status in the Server Status window. :
Primary Server:
Secondary Server:

Standby
Active

On the HMI server Properties window press the Switchover button to force the Server #1 to become the Active HMI
server. Check that the Server Status becomes:
Primary Server:
Secondary Server:

Active
Standby

Check that youre HMI clients are performing correctly.

Page 10 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Note:

6.

When a Secondary HMI server computer has been the Active HMI server and is then demoted back to
being the Standby HMI server, it is best to reboot the Secondary HMI computer. A reboot of the
Secondary HMI server computer will ensure that when it starts up it will force a fresh initialization of all
processes that need to synchronize between the Primary and Secondary HMI servers.

If youre preferred Switchover option is set to:

Switch over to the primary server when it becomes available.
Restart Server #1 and confirm that it becomes the Active server. Check that your HMI clients are performing
correctly.
Primary Server:
Secondary Server:

Active
Standby

Step 10 Investigation of any potential issues that arise after initial testing
If issues do appear during the initial testing with the newly installed patch roll-up, now is a good time to investigate.
Check and confirm computers, switches and other related hardware are turned on.
Check and confirm all physical network connections on each computer and related hardware are correct.
On each computer, in the operating system check in network connections to confirm network cards are enabled.
Review the patch roll-up installation log files for indications that any of the patch files may have failed to install.
Answer ID 47015 - FactoryTalk View SE 5.00.00 (with CPR9 platform) - Patch Roll-up.
Check the FactoryTalk Diagnostic messages for information that may relate to the cause of the issue experienced.
Click Start > All Programs > Rockwell Software > FactoryTalk Tools > Diagnostics Viewer.
Check the computer operating system Application, Security and System event log messages.
Click Start > Run > Type eventvwr and click OK.
If required, contact Tech Support and/or your local Rockwell Automation Sales office for assistance.

Optional Fall back to running the HMI application on the non- patched computers:
If you have jumped to Step 10 from Step 6 Test the FactoryTalk View SE application with the new patches, then you
will not have patched Server #2 and one or more of the HMI Clients. If you need the FTViewSE networked application up
and running as soon as possible, then do the following for temporary purposes. This will run the HMI application using the
remaining computers that did not have the patch roll-up applied.
Disconnect all computers from the network that had the patch roll-up applied.
Start the un-patched Server #2 (Secondary HMI server) and allow it to completely initialize.
Start the remaining un-patched HMI Client computers.
Check that your HMI clients are performing correctly.
This is for short term running, as you need to determine the problem and correct the patched computers. Do not reconnect
these other (non-functioning) computers back to the production FTViewSE network until any issues are addressed.
Page 11 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357

FactoryTalk View Site Edition Version 5.0, 5.1, SR1, SR2, (CPR9)

Reference to additional Rockwell Automation Knowledgbase documents:

Answer ID 27105 - RSView SE 3.1, 3.2, 4.0 and 5.0 Server Redundancy Guidelines.
Answer ID 38407 - RSViewSE 4.0 (CPR7+) & 5.0 (CPR9) HMI Project Replication Process Steps.
Answer ID 30310 - RSView SE - Backup and Restore Utility for HMI Server.
Answer ID 44624 - FTView SE 5.0 (CPR9) - Determining any Server's Current Status and State in a Display Client.
Answer ID 35411 - Method to automatically reboot the secondary SE server after a failover and switchback.
Answer ID 37110 - FactoryTalk View (RSViewSE) Tips and Best Practices Table of Contents.

Page 12 of 12
Rockwell Automation
Knowledgebase
Answer ID 64357