Release Notes

FactoryTalk Updater
Version 4.00.00 (released 11/2022)

Catalog Number FactoryTalk Updater 

These release notes describe version information for FactoryTalk Updater, version 4.00.00 (released 11/2022).

Requirements

This release has the following requirements.

System requirements for FactoryTalk Updater version 4.00.00

FactoryTalk Updater works within the system requirements of all Rockwell Automation® software products. For the latest compatibility information, refer to the Product Compatibility and Download Center.

Hardware requirements

FactoryTalk Updater does not have any specific hardware requirements. It runs on any hardware platform that supports the required software, either locally or on a virtual machine.

Rockwell Automation recommends at least 80 MB of available drive space for FactoryTalk Updater.

Software requirements
FactoryTalk Updater runs on these Windows® operating systems:
The installer software inhibits installation of FactoryTalk Updater on all Windows 7 and 32-bit operating systems, including Windows 10 (32 bit).
When you install FactoryTalk Updater, if it is not already present, the following software is installed:

Features

This release includes the following system features.

System features for FactoryTalk Updater version 4.00.00

FactoryTalk Updater version 4.00.00 has these new and enhanced features:

New features

Known Anomalies in This Release

This release has the following known anomalies.

Anomalies for FactoryTalk Updater version 4.00.00

These lists identify the anomalies corrected in FactoryTalk Updater version 4.00.00 and the known anomalies found during testing or reported by customers for this release. Use the identification information provided in the brackets [] to track an anomaly in future releases or to request assistance from Customer Support with a related issue.

Corrected anomalies

Known anomalies

Functional Changes

This release has the following functional changes from the previous release.

Functional changes for FactoryTalk Updater version 4.00.00

None in this release.


Application Notes

This release has the following application notes.

Application notes for FactoryTalk Updater version 4.00.00

These application notes apply to FactoryTalk Updater version 4.00.00.

Graphics driver sometimes blocks port sharing

OneApp.IGCC.WinService.exe, part of the Intel® graphics driver, sometimes occupies the default NetTcp port and blocks port sharing. The block prevents some Windows Communication Foundation (WCF) applications, including FactoryTalk Updater, from using the NetTcp port.

To work around this issue, follow the instructions in this TechConnect article:

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1128478

Install FactoryTalk Agent and FactoryTalk Server machines in the same domain

FactoryTalk Updater version 4.00.00 uses Windows authentication to enhance product security. This requires FactoryTalk Agent and FactoryTalk Server machines to be in the same domain.

Create a self-signed SSL/TLS certificate for using FactoryTalk Updater in a browser

To open the FactoryTalk Updater application in a browser you must use Transport Layer Security (TLS) 1.2 or later. Rockwell Automation recommends that you disable TLS 1.0 and TLS 1.1 in the system. Rockwell Automation also recommends using a certificate signed from your organization's internal certification authority (CA) or a commercial certification authority. Alternately, you can create a self-signed certificate on the FactoryTalk Updater server computer.

Follow these steps to create a self-signed certificate:

  1. On the FactoryTalk Updater server computer, run the following PowerShell command to create a self-signed certificate:
    New-SelfSignedCertificate -FriendlyName EXAMPLE_CERT_NAME -DnsName EXAMPLE_FULL_COMPUTER_NAME -KeyUsage DigitalSignature
    Replace EXAMPLE_CERT_NAME with the name that should appear in the Server Certificates list in Internet Information Services (IIS). For example, use the name "FTUpdater".
    Replace EXAMPLE_FULL_COMPUTER_NAME with the fully qualified domain name of the server. For example, use the name 4sk2h63.example.com.
  2. Open the Internet Information Services (IIS) Manager application.
  3. Select Server Certificates.
  4. In the Server Certificates window, verify the self-signed certificate is visible in the list.
  5. (optional) If you have a CA certificate, right-click in Server Certificates, then:
    • If you have a PFX file containing the certificate (public keys) and the correspondig private keys, select Import.
    • If you have a file from a CA containing the CA's response (such as a CER file), select Complete Certificate Request.
  6. In the Connections list, right click the UpdaterWebServer certificate and select Edit Bindings.
  7. In the Site Bindings dialog, select the https binding and select Edit.
  8. In the Edit Site Binding dialog, in the SSL certificate menu, select the certificate and select OK.
  9. In the Connections list, right click the certificate and select Manage Website > Restart.

Follow these steps to export the self-signed certificate as a PFX file:

  1. On the FactoryTalk Updater server computer, open the Internet Information Services (IIS) Manager application.
  2. Select Server Certificates.
  3. In the Server Certificates window, identify the self-signed certificate, then write down or copy its Certificate Hash value. This value will be used in the following steps.
  4. Open PowerShell, then run the following command to create a password for the PFX file:
    $mypwd = ConvertTo-SecureString -String 'EXAMPLE_PASSWORD' -Force -AsPlainText
    Replace EXAMPLE_PASSWORD with the password that will secure the self-signed certificate.
  5. In the same PowerShell window, run the following command to export the self-signed certificate as a PFX file:
    $cert = Get-ChildItem -Path Cert:\LocalMachine\My\EXAMPLE_CERTIFICATE_HASH | Export-PfxCertificate -FilePath C:\mypfx.pfx -Password $mypwd
    Replace EXAMPLE_CERTIFICATE_HASH with the Certificate Hash value identified in previous steps. For example, the value might be ca7e070c4448bc7ae47db59b65e39e8199edae08.
    Replace C:\mypfx.pfx with the file path for the new self-signed PFX file.

Follow these steps to import the self-signed PFX file on FactoryTalk Updater client computers:

  1. Copy the PFX file created in the previous steps to the FactoryTalk Updater client computer.
  2. Double-click on the PFX file. The Certificate Import Wizard appears.
  3. For Store Location, select Local Machine and select Next.
  4. Verify that the certificate file name appears in the File name box and select Next.
  5. Enter the password that you set for the certificate and select Next.
  6. Select Place all certificates in the following store and select Browse to open the Select Certificate Store dialog.
  7. Select the Trusted Root Certification Authorities folder and select OK.
  8. Select Next.
  9. Select Finish.
Change the default HTTPS port for using FactoryTalk Updater in a browser

When you create a self-signed certificate for using FactoryTalk Updater in a browser, the default HTTPS port number is 60129. To assign a different HTTPS port number, you need to complete these tasks:

  • Configure a Windows firewall rule for the self-defined port.
  • Change the port for the default website to the self-defined port in the Internet Information Services (IIS) Manager application.

To configure a Windows firewall rule for the self-defined port:

  1. On the FactoryTalk Updater server computer, on the Start menu, search for Windows Firewall With Advanced Security and open it.
  2. Right click Inbound Rules and select New Rule.
  3. In the New Inbound Rule Wizard dialog, select Port, and then select Next.
  4. In the Steps menu, select TCP Protocol and Ports.
  5. Select Specific local ports and enter a self-defined port number, such as 50000. Select Next.
  6. In the Steps menu, select Name.
  7. In the Name field, enter a name for the new inbound rule, such as FTUpdater Web Client Site New Port, and select Finish.

To change the port for the default website to the self-defined port in the IIS Manager application:

  1. On the FactoryTalk Updater server computer, open the Internet Information Services (IIS) Manager application.
  2. Select Server Certificates.
  3. In the Connections list, under Sites, right-click the UpdaterWebServer certificate then select Edit Bindings.
  4. In the Site Bindings dialog, select the https binding item and select Edit.
  5. In the Edit Site Binding dialog, in the Port box, enter the self-defined port number (for example, 50000) and select OK.
  6. In the Connections list, under Sites, right click the UpdaterWebServer certificate then select Manage Website > Restart.
You can use the self-defined port number to open the FactoryTalk Updater application in a browser. For example:
https://server-computer-name:50000

For server-computer-name, you can insert the IP address or the fully qualified domain name for your FactoryTalk Updater server.

Select language settings for the web client in your browser

To change the display language for the FactoryTalk Updater web client, select a preferred language in your browser settings. The web client supports these languages:

This example shows the language setting in the Chrome browser.

graphic

FactoryTalk Updater displays status message "Disconnected, check system log for details" while using a Proxy Server

FactoryTalk Updater sometimes displays the status message Disconnected, check system log for details while using a proxy server. Refer to this Knowledgebase article for more information:

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1131670

Some fields in the License, Machines, and Activations tabs appear only in English

In this release, some fields in tables in the License, Machines, and Activations tabs are not localized and appear only in English.

FactoryTalk Updater version 4.00.00 installation

Install the required functionality for FactoryTalk Updater:

FactoryTalk Updater Agent

FactoryTalk Updater Agent collects information and activation license data from the Rockwell Automation software installed on the computer. Install the FactoryTalk Updater Agent on each computer that requires data collection. This is the default functionality installed with most Rockwell Automation software.

graphic
Tip: Install FactoryTalk Agent and FactoryTalk Server machines in the same domain.
FactoryTalk Updater Server

FactoryTalk Updater Server:

graphic
Tip: To avoid issues, limit FactoryTalk Updater Server installations to one instance per intranet.
FactoryTalk Updater Client

FactoryTalk Updater Client is the user interface that displays information collected by the FactoryTalk Updater Server. Install FactoryTalk Updater Client to display information from the intranet.

Custom Installation

Use a custom installation to install more than one FactoryTalk Updater functionality.

To install FactoryTalk Updater
  1. Download the current version of FactoryTalk Updater software.
  1. Launch Setup.exe.
  2. In Select product to install, select one of these options: Agent, Server, Client, Custom Installation.
  1. For the Custom Installation, select Customize.
  2. Select the required options and select Install.
  1. Select Install now to start the installation.
  2. Read and consent to the End User License Agreements by selecting Accept all. The installation starts and a bar displays the progress.
  3. When prompted to restart the computer during the installation, select Restart now to restart the computer and continue the installation. Select Restart later to suspend and exit the installation.
  4. After restarting the computer, FactoryTalk Updater is ready to use. Select Close to exit the installation or perform one of these steps:
  1. Launch FactoryTalk Updater. When requested, enter the User Name and Password credentials for the Windows® account of the Server machine.
Firewall ports and URL access

During operation, FactoryTalk Updater opens these firewall ports on the server:

Port Type
Port Number
Description
TCP
808
Allows the Updater agent and client to connect to the Updater server.
TCP
60129
Allows access to the web-based FactoryTalk Updater client.
UDP
137
Used to ping computer names.
Network-Echo Request (ICMPv4-In)
Allows one computer to contact or ping another computer to test network communications.

During operation, FactoryTalk Updater opens these firewall ports on the agent:

Port Type
Port Number
Description
TCP
30064
Allows access to the agent service to change the server address.
UDP
3702
Allows Auto Discovery broadcast message.
UDP
137
Used to ping computer names.
Network-Echo Request (ICMPv4-In)
Allows one computer to contact or ping another computer to test network communications.

To ensure FactoryTalk Updater can access the Product Compatibility and Download Center (PCDC) data and download the latest patches, add these URLs to the firewall exception list:

When using the server installation:



When using the client installation:
Software applications detected by Updater

FactoryTalk Updater detects information for these software applications:


Unattended or silent install

Use command-line parameters to perform an unattended or silent installation of the software.

Installation Command-line parameters

This table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").

Parameter
Description
/?
Displays the usage options for installation parameters.
/Q
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation using an IT tool or script, and don’t expect any error or restart messages. When using this parameter, check the error codes, and respond as needed. For example, if the installation returns error code 1641, then the IT tool or script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
/QS
Unattended Install, install runs in a quiet simple mode and shows progress through the UI, it does not accept any input but still shows error or restart messages.
When using this parameter, the installation will stop and display a prompt if there are error or restart messages. For example, if an immediate restart is required to complete the install, a restart message will be displayed to confirm the restart. Installation resumes automatically from the point of interruption after restart.
This parameter is required if /Q is not specified.
/IAcceptAllLicenseTerms
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
/AutoRestart
Automatically restarts the computer after the installation is complete. Used when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used silent install (/Q) will return either error code 1641 or 3010 if a restart is required, and unattended install (/QS) will result in a confirmation prompt that must be agreed to before the installation is completed.
/Record
Records the installation options chosen to a recording file.
This parameter is optional.
/Playback
Plays back a recording file to specify the installation options.
This parameter is optional.
/SetupLanguage="value"
Specifies which language is displayed during install process.
The value must be the one of these:
  • ENU
  • CHS
  • DEU
  • ESP
  • FRA
  • ITA
  • JPN
  • KOR
  • PTB
This parameter is optional. If this parameter is not used, the default language is the current user or operating system user interface language.
/Product="value"
Specifies which sub-products will be installed.
The product name must be one of these:
  • Agent
  • Client
  • Custom Installation
  • Server
/IgnoreWarning
Specifies that the setup ignores warnings and continues.
This parameter is optional. If it is not specified, the setup exits when a warning occurs.
Examples

These examples show how to use the installation commands.

Setup.exe /Q /IAcceptAllLicenseTerms /Product=Agent
Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /Product=Client
Error codes

This table identifies the error codes that can be returned by an installation.

Error Code
Value
Description
ERROR_SUCCESS
0
The installation completed successfully.
ERROR_INVALID_PARAMETER
87
One of the parameters was invalid.
ERROR_INSTALL_USEREXIT
1602
The installation was cancelled by the user.
ERROR_INSTALL_FAILURE
1603
A fatal error occurred during installation.
ERROR_BAD_CONFIGURATION
1610
The configuration data for this product is corrupt. Contact your support personnel.
ERROR_REBOOT_CONTINUE
1641
A reboot is required to continue to installation.
ERROR_SUCCESS_REBOOT_REQUIRED
3010
A restart is required to complete the installation. After restart the product is successfully installed.
ERROR_REBOOT_PENDING
3012
A restart is pending and is required before the installation can continue.
ERROR_SUCCESS_NOT_APPLICABLE
3013
The installation cannot proceed because the products are already installed.


CIS Benchmarks test results

FactoryTalk Updater has been tested on CIS Microsoft Windows 10 Enterprise (Release 21H2) Benchmark v1.12.0 (L1).

Exceptions settings for FactoryTalk Updater are listed.

Reference: Recommended guidelines for hardening software, computer, device, and network systems and infrastructure (CIS Benchmarks)





  
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.