Review these minimum and recommended system requirements for installing, configuring, and running FactoryTalk Batch v16.00. Unless noted, these requirements assume that no other applications are installed on the computer. Preferred operating systems and software applications are prioritized for support, testing, and post-release patch qualifications.

• Server requirements
  • 8 -GB of RAM memory
  • 100-GB free hard disk space
  • Intel® Core™ i5 standard power processor or greater

• Client requirements
  • 4-GB of RAM memory
  • 30 GB free hard disk space
  • Intel Core i5 standard power processor or greater

• Windows Server®
  • Windows Server 2022 Standard Edition (preferred)
  • Windows Server 2019 Standard Edition (preferred)
  • Windows Server 2022 Datacenter Edition
  • Windows Server 2019 DataCenter Edition

• Windows®
  • Windows 11 Professional (64-bit) (preferred)
  • Windows 10 Professional (64-bit) Build 1909 or later (preferred)
  • Windows 11 Enterprise (64-bit)
  • Windows 10 Enterprise (64-bit) Build 1909 or later

Tip: The installer software inhibits installation of FactoryTalk software on all Windows 7 and 32-bit operating systems, including Windows 10 (32 bit).

(for storing recipes, materials, reports, and journal archives)

• SQL Server®
  • SQL Server 2022 (English version only)
  • SQL Server 2019 (English version only)

(for FactoryTalk Batch View only)

• Google® Chrome™ browser (preferred)
• Microsoft Edge™ based on Chromium version:  80.0.361.50 or higher
• Apple® Safari®
• Firefox®

(for FactoryTalk Batch only)

• Firmware revision 18 or later on ControlLogix 5570 and CompactLogix 5370 family of controllers – for integration of PhaseManager with FactoryTalk Batch
• Firmware revision 32 or later on ControlLogix 5580 and CompactLogix 5380 family of controllers – for integration of PhaseManager with FactoryTalk Batch
• Firmware revision 29 or later on ControlLogix 5570 and CompactLogix 5370 family of controllers - for integration of SequenceManager with FactoryTalk Batch
• Firmware revision 35 or later on ControlLogix 5580P and CompactLogix 5380P family of controllers - for integration of SequenceManager with FactoryTalk Batch

(for FactoryTalk Batch only)

• Studio 5000 Logix Designer v18.00 or later - for synchronization of PhaseManager with FactoryTalk Batch Equipment Editor

(for integration of FactoryTalk Batch View HMI Controls and legacy FactoryTalk Batch ActiveX controls only)

• FactoryTalk View SE v14.00 (preferred)
• FactoryTalk View SE v13.00

• FactoryTalk Services Platform v6.40.00 (CPR9 SR 14) or later
• FactoryTalk Linx v6.40.00 (CPR9 SR 14) or later
• FactoryTalk Activation Manager v5.01.00 or later

Rockwell Automation tests software products under a standard configuration of operating systems and antivirus software. For additional information, see the Knowledgebase Document ID: PN24 - Rockwell Software Products and Antivirus Software.

The warranty does not cover systems that do not meet the minimum requirements for the version of software.

• The FactoryTalk Batch Server computer cannot be configured as a:

• Domain controller
• DHCP server
• WINS server
• RAS server
• DNS server
• Master Browser

• The FactoryTalk Batch Server computer does not support replication.
• Install FactoryTalk Batch software on an NTFS formatted hard disk drive, as Windows security features are available only for drives that are formatted to use NTFS.
• Warranty does not cover systems with modified DCOM configuration settings. Configuring settings using DCOMCNFG may stop the FactoryTalk Batch Server and prevent the FactoryTalk Batch Service Manager from functioning correctly.

FactoryTalk Batch v16.00 has these new, enhanced, and deprecated features:

Deferred Material Parameters

FactoryTalk Batch Server v16.00 adds the ability to defer material parameters to a higher-level recipe, allowing customers to apply modular programming practices and take advantage of formulations when developing material-based recipes.

Support of UTC time stamp in the Event Journal files

The UTC time stamp of batch events is now recorded at the time of the event to prevent displaying ambiguous values from the BatchHistoryEx database after transitioning out of daylight savings.

In FactoryTalk Batch v16.00 a new journal file format has been added.  The new file format is based on JSON Lines format and uses a new file extension (*.evtj).The new format also includes a new data field for storing the GMT time for a record, making integration of data between multiple systems easier and more accurate.  The batch server can be configured to use either the legacy file format (tab-delimited EVT) or the new format.

• The file extension name.evt or .evtj is configured during installation but can be updated in the Equipment Editor Server Options dialog box.
• When the Event Journal file format is JSON, (EVTJ), the UTC time is no longer calculated by the BatchHistoryEx database. The UTC time field in the database is from the Event Journal value.  If the legacy file format is used (tab-delimited EVT), the UTC time in the database is calculated by the BatchHistoryEx database.

Improved Logging

FactoryTalk Batch v16.00 improves logging of server information, warning, and error messages. Messages that were previously sent to the Windows Application log are now sent to the FactoryTalk Diagnostics logs. This feature also includes new messages for Runtime Area Model Updates, Warm and Warm All restarts, and changes in communication status between the Material Server and Batch Server. This feature aligns diagnostics messages for the FactoryTalk Batch system with other FactoryTalk software and makes troubleshooting system issues easier.

Installation and Migration Improvements

The FactoryTalk Batch v16.00 installer includes improved migration of existing Batch Archive databases.

Legacy Event Journal Format

The tab delimited event journal format (EVT) will not be updated or enhanced. It has been replaced by the enhanced JSON Lines based format (EVTJ) and the option to use legacy EVT format will be removed in a future release. We recommend systems using FactoryTalk Batch v16.00 or later move to the new EVTJ format.

Legacy client applications

The FactoryTalk eProcedure Client, legacy FactoryTalk Batch View Client, and the FactoryTalk Batch ActiveX Controls are not included nor supported by FactoryTalk Batch v15.00 and later. If your production system has dependencies on these products, transition to the modern FactoryTalk Batch View and FactoryTalk Batch View HMI Controls before upgrading to FactoryTalk Batch v16.00.

Pop-up notifications are persistent (519919, 519912)

For example: When an invalid login is used, a pop-up notification is displayed, indicating that the login is invalid. The notification is not cleared even after a successful login is completed.

Corrected in FactoryTalk Batch View v2.01.

First identified in FactoryTalk Batch View v2.00.

To work around this issue, the user must close the notification.

Creating a material-based batch fails when no binding units are satisfied (3153921)

Creating a batch from a material-based recipe that uses “By Configuration” binding and Material Class, may fail to be created in the following scenario: The material that is selected during batch creation for the Material Class was created in the material database after the batch server was started.  In this case, the batch server will not have the new material in the Materials enumeration. 

To work around the issue, perform an online area model deploy using the same area model that the server is currently using. This will cause the Batch Server to read in the new material from the Material Database.

First identified in v16.00

Installing FactoryTalk Batch v14.00 updates FactoryTalk Services Platform to v6.20. There is a known anomaly in FactoryTalk Services Platform 6.11 and 6.20 that impacts FactoryTalk Event Archiver components. When FactoryTalk Diagnostics v6.11 or 6.20 and Microsoft SQL Server Reporting Services 2017 or 2019 are installed on the same computer, Microsoft SQL Server Reporting Services fails to work. This anomaly was first identified in FactoryTalk Services Platform v6.11.00. (#00369202)

To avoid this problem, change the default port used by Microsoft SQL Server Reporting Services from 8082 to another port.
For steps to address the issue after installation is complete, see Knowledgebase Document ID: BF25929 - SQL Server Reporting Services stops working after installing FactoryTalk Diagnostics.

Installing FactoryTalk Batch version 14.00 and later updates FactoryTalk Services Platform to version 6.20 [00369202]

There is a known anomaly in FactoryTalk Services Platform 6.11 and 6.20 that impacts FactoryTalk Event Archiver components. When FactoryTalk Diagnostics version 6.11 or 6.20 and Microsoft SQL Server Reporting Services 2017 or 2019 are installed on the same computer, Microsoft SQL Server Reporting Services fails to work. This anomaly was first identified in FactoryTalk Services Platform version 6.11.00.

To avoid this problem, change the default port used by Microsoft SQL Server Reporting Services from 8082 to another port.
For steps to address the issue after installation is complete, see Knowledgebase Document ID: BF25929 - SQL Server Reporting Services stops working after installing FactoryTalk Diagnostics.

FactoryTalk Batch Material Manager

Material Editor cannot access the material database after upgrading FactoryTalk Batch [929120]

The MTUser account is not in the correct database. Anomaly first identified in FactoryTalk Batch 14.00.

To work around this issue use these steps:

1. Open the SQL Server Management Console.
2. Navigate to the database Logins and delete the MachineName\MTUser login.
3. Navigate to the material database and open the list of users: delete the user account MTUser.
4. Run the script MaterialTrack_DBSecurity.sql on the material database. This will recreate the MTUser user account under the database.
   The script is located in the C:\Program Files(x86)\Rockwell Software\Batch\Scripts folder.
   Access to the material database should now be restored.

FactoryTalk eProcedure

Cannot create HMI Server on a computer with FactoryTalk eProcedure and FactoryTalk View SE [00369237]

After adding eProcedure to a FactoryTalk Batch and FactoryTalk View SE install, an HMI Server cannot be created.

To work around this issue, restart the computer after installing eProcedure, then create the HMI Server. 

 FactoryTalk Batch View 2.00

Pop-up notifications are persistent [519919, 519912]

For example: When an invalid login is used, a pop-up notification is displayed, indicating that the login is invalid. The notification is not cleared even after a successful login is completed.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, the user must close the notification.

Unintended actions from Arbitration Summary page [98187]

On the Arbitration Summary page, when the More menu is open and a user selects Enter, the first item in the More menu is executed, resulting in possible unintended actions.

Anomaly first identified in FactoryTalk Batch View 2.00.

To avoid this issue, in FactoryTalk Security, enable confirmation messages, which prompt to confirm before actions are performed in FactoryTalk Batch View.

Spurious "No master recipes are released to production" message [263925]

When adding a batch to the batch list, the client may display a "No master recipes are released to production" message while the system is gathering the control recipe data.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, wait for the recipes to load. The message disappears after the recipes are loaded.

Spurious client reports of control recipe removal [471548]

During the runtime area model update, the control recipe may be inaccessible to the client, causing the client to report that the control recipe has been removed.

Anomaly first identified in FactoryTalk Batch View 2.00.

The control recipe is not actually removed, so you can ignore this message

Filters not functioning on Arbitration Summary page [760902]

On the Arbitration Summary page, when performing a warm restart or applying a run-time area model update, applied filters may not function as expected.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, reapply filters.

Filter values are not cleared automatically [98193]

When a user sets filter values on a phase while on the Equipment page and then restarts the FactoryTalk Batch View Server, the filter values are not cleared automatically.

Anomaly first identified in FactoryTalk Batch View 2.00.

To work around this issue, after restarting the FactoryTalk Batch View Server, manually clear the filter values.

FactoryTalk Batch View HMI Controls 1.00

FactoryTalk View SE Client process lock [360350]

When a Display Client is closed while running a FactoryTalk View SE display that contains the FactoryTalk Batch HMI Controls, the Display Client process keeps running as a background process. This may prevent the ability to launch subsequent instances of the Display Client.

Anomaly first identified in FactoryTalk Batch View HMI Controls 1.00

To work around this issue, reboot the machine on which the FactoryTalk View SE Display Client is executing.

FactoryTalk View Batch server authorization changes only reflected in FactoryTalk View SE user interface only after login [362225]

If a change is made to the FactoryTalk Batch View authorization policies when a FactoryTalk View SE display containing an HMI Control is in runtime, the change is not reflected in the user interface.

The user is required to log out and then login with valid credentials for the new authorization policy changes to be reflected in the user interface.

Removed BaseFilter batch remains on batch list [CLM 4578]

If a BaseFilter batch state is applied (such as State:Running) and the state changes for a currently visible batch on the Batch List, the batch is visibly removed from the list and the message: Control Recipe <name> has been removed appears.

Even though the applied BaseFilter removes visibility to the batch, the batch is actually still on the batch list and can be viewed from other clients or HMI Controls that do not filter based on the batch state.

Videos are not displayed correctly in manual instruction content served from Batch View Server (1503087)

• The relative path for an image would be:  <img src=”image01.jpg”>
• The relative path for a video would be:  <video><source src=”eprocedure/video01.webm” /></video>
• The relative path for a script would be:  <script src=”eprocedure/script01.js”></script>

FactoryTalk Batch v16.00 has no function changes.

The FactoryTalk Batch v16.00 release has the following application notes.

Impact of Microsoft deprecating VBScript

Microsoft announced the phased deprecation of VBScript in 2024. VBScript is now an optional feature beginning in Windows 11 24H2 and Windows Server 2025. Many FactoryTalk software products released before September 1, 2026, use VBScript during installation.

FactoryTalk Batch versions 18.00.00 and earlier require VBScript for installation. Installation will fail if VBScript is not enabled.

To mitigate the problem, enable VBScript manually. For more information, see the Knowledgebase Document ID: IN41397 - Impact of Microsoft deprecating VBScript. FactoryTalk software products released after September 1, 2026, no longer rely on VBScript.

When upgrading the User Controls between releases, the controls are rewritten and must be deleted and reinstalled. After the install, you must reconfigure the properties on the controls.

If the control is 2.x or later, FactoryTalk View SE applies the properties to the new control. You do not have to reconfigure the properties.

The COM ClassID verifies the new control is compatible. If it is not compatible, the control must be deleted and reinstalled.

In response to Microsoft Distributed Component Object Model (DCOM) Hardening patch (MS KB5004442), the minimum DCOM authentication level used by Rockwell Automation products was raised to Packet Integrity.

Microsoft releases the DCOM Hardening patch in response to CVE-2021-26414. This patch elevates the minimum DCOM authentication level that is required to establish a DCOM connection. DCOM is used by many Rockwell Automation products and may be affected by the change that is made by the Microsoft patch. For additional information about the affected Rockwell Automation products, see the Knowledgebase Document ID: PN1581 - Product Notification 2022-01-001 - Rockwell Automation products unable to establish proper DCOM connection after installing Microsoft DCOM Hardening patch (MS KB5004442).

• Upgrade from FactoryTalk Batch v15.00 to FactoryTalk Batch v16.00 does NOT require an uninstall of FactoryTalk Batch v15.00. Before upgrading to FactoryTalk Batch v16.00 from FactoryTalk Batch v14.00, you must uninstall the previous release and then delete the Batch View Server folder located at C:\Program Files (x86)\Rockwell Software\Batch View Server. Failure to do so will result in the inability to start the FactoryTalk Batch View Server.
• Upgrading from RSLinx CIP communication to FactoryTalk Linx CIP communication is a manual operation. Use these steps:

1. Open the FactoryTalk Administration Console and then navigate to FactoryTalk Linx.
2. Create FactoryTalk Linx shortcuts to the controllers that have the Phase Manager phases or Sequence Manager sequences.
3. Open the area model in the Equipment Editor and navigate to the Data Servers. 
4. Edit each Data Server that is the type Logix5000 CIP, changing the FactoryTalk Linx Controller Shortcut to shortcuts created in step 2.

• The FactoryTalk Batch v16.00 installation requires that the Remote Registry service is set to Automatic and Running. Due to changes in the Windows operating systems, this service only runs for 10 minutes before stopping.
  Immediately start the installation of FactoryTalk Batch v16.00 after the Remote Registry service is started.

• Logix5000 CIP Data servers must use the first instance of a FactoryTalk Linx service.
FactoryTalk Linx v6.40 installs two instances of the FactoryTalk Linx data server. Only the first instance named FactoryTalk Linx Instance01 Server supports the necessary communication interfaces to connect to PhaseManager and SequenceManager on a Logix controller.
When configuring a Logix5000 CIP data server for communications with PhaseManager or SequenceManager, be sure to select the data server that is using the first instance of the FactoryTalk Linx service. 
Use these steps to identify which instance of FactoryTalk Linx is assigned to a data server:
1. Start FactoryTalk Administration Console.
2. In the Explorer pane, browse to the data server
3. Right-click the data server name and select Properties.
4. On the General tab, verify that the entry under Server Type is FactoryTalk Linx Instance01 Server.

Tip: For more information, see the FactoryTalk Linx Help topic What's FactoryTalk Linx instance02 service?

• FactoryTalk Batch Service Manager does not use Single Sign-On credentials.
You must log in to FactoryTalk before using the FactoryTalk Batch Service Manager.
This is because performing a deployment to a runtime server is treated as an elevated privileges operation when launched from the FactoryTalk Batch Service Manager. To run with elevated privilege the FactoryTalk Batch Service Manager must:
• Always prompt for a username and password.
• Not use the Single Sign-on User.
• Not set the Single Sign-on User.

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

The following 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").

These parameters are applicable for all Rockwell Automation software that are available in the installation package.

The command-line install of FactoryTalk Batch performs a full install of FactoryTalk Batch. To install FactoryTalk Batch, FactoryTalk <EA>, FactoryTalk Batch Material Manager, or FactoryTalk Batch View HMI Controls separately use the installation wizard instead of the command-line.

These options are specific to installing FactoryTalk Batch software:

The following example shows how to use the installation commands.

• To install the software with no user interface specifying a custom HTTPS port and copying custom content during the installation process.

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

• The installation program requires TLS 1.0 be enabled so that the SQL server scripts can create and update the Material Manager database. TLS 1.0 is not used by the application and can be disabled after installation is complete.
• Material Editor is a COM+ application. If another service starts or logs in using the same identity before the Material Server is started, stopping that service logs off the user account. If the Material Editor is connected before the other service is stopped, it will still have access to the Material Server, but if it disconnects from the Material Server it will not be able to reconnect until the server is rebooted or the previous service is restarted. For more information and potential workarounds, see the information about COM+ applications on the Microsoft web site.

• Install the FactoryTalk Batch Enterprise Integration Server after completing the FactoryTalk Batch installation to add support for developing enterprise integration features using the provided API.