• 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 10 Enterprise 2019 LTSC 64-bit (v1809)
  • Windows 10 Enterprise 2021 LTSC 64-bit (21H2)
  • Windows 10 Professional 64-bit (preferred)
  • Windows 11 Enterprise (64-bit)
  • Windows 11 Professional (64-bit) (preferred)

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

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

• 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

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

• FactoryTalk View SE v15.00.00

• FactoryTalk Services Platform v6.50.00 (CPR9 SR 15) or later
• FactoryTalk Linx v6.50.00 (CPR9 SR 15) or later
• FactoryTalk Activation Manager v5.01.01

• 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.

• Support for FactoryTalk Link OPC UA Connector
  FactoryTalk Batch v17.00.00 introduces enhanced connectivity with OPC UA data servers via the FactoryTalk Linx OPC UA Connector. The updated workflow for browsing data server paths now includes FactoryTalk Linx OPC UA Connectors defined within the FactoryTalk Directory. Additionally, the FactoryTalk Batch Server can read and write tags on an OPC UA data server, providing seamless data integration and improved operational eiciency.

• Scripted Area Model import
  FactoryTalk Batch v17.00.00 includes a new feature that allows users to script the import of an Area Model XML (AXML) file into an Equipment Model configuration (CFG) file. This enhancement empowers engineers to develop area models using their preferred tools and seamlessly integrate those area models within FactoryTalk Batch. The new application supports importing either a complete area model into a new Equipment Model or a partial area model into an existing Equipment Model configuration (CFG) file, offering greater flexibility and eiciency in managing equipment models. Additionally, this feature can be utilized from a command line or within a script, providing even more versatility for automation and integration.

• Scripted Recipe import
  FactoryTalk Batch v17.00.00 adds a new feature that allows users to import recipes using scripting. The new application enables engineers to automate the import process, improving workflows and reducing manual effort. Whether working from a command line or within a script, users can now eiciently manage and update recipes.
  Enhanced features

• Material Server technology update
  In FactoryTalk Batch v17.00.00, the Material Server has been migrated to a modern technology stack, helping to ensure performance, security, and future enhancements for our FactoryTalk Batch software suite.

• Archive database improvements
  FactoryTalk Batch v17.00.00 includes significant improvements in database performance and report generation speed. It also introduces our new database migration utility, making it easier than ever to transition older database schemas to our improved, optimized schema.

• Installation and Migration improvements
  The FactoryTalk Batch v17.00.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.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.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.00.
  NOTE: The FactoryTalk Batch Database Management Tool is being deprecated. The tool will only support database schemas for older versions.

1. FactoryTalk Batch View is installed before FactoryTalk View SE

   The FactoryTalk View SE installation process does not check for port conflicts when installing with the option Secure communication with TLS and does not provide the option to select a different port. If FactoryTalk Batch View is installed first and assigns port 443 to its secure communication, and then FactoryTalk View SE is installed and the option Secure communication with TLS is selected, the installation will fail with communications errors due to the port being unavailable.

   The FactoryTalk Batch View installation process does detect the port conflict and provides the option to select a different secure communications port.

   To work around this issue, install FactoryTalk Batch View after FactoryTalk View SE.

   Anomaly first identified in FactoryTalk Batch View version 2.01.00.

2. Installing new FactoryTalk-enabled software that uses HTTPS communication after installing FactoryTalk Batch View

   Because the other FactoryTalk software does not check communication during install, a port conflict (port 443) will be created. As a result, FactoryTalk Batch View client and HMI user controls cannot communicate with the FactoryTalk Batch View server.

   Anomaly first identified in FactoryTalk Services Platform version 6.30.00.

   Use one of these workarounds to resolve this issue:

• If you installed FactoryTalk Reverse Proxy:

1. On the computer hosting a FactoryTalk-enabled software server, open FactoryTalk Administration Console.
2. In the Explorer pane, go to localhost > System > Policies > System Policies > Security Policy.
3. Change Reverse Proxy Port to other available ports instead of 443.
4. If Reverse Proxy Port is changed, the system will make changes to Site Bindings in Internet Information Services (IIS) Default Web Site.
5. You may need to remove port 443 in IIS to make sure that the software works appropriately.
6. You may also need to configure Product Policies for the FactoryTalk-enabled software to make sure that its HTTPS port in use is the same as Reverse Proxy Port.
7. Select Apply, and then select OK.



• If you did not install FactoryTalk Reverse Proxy:

1. On the computer hosting a FactoryTalk-enabled software server, open FactoryTalk Administration Console.
2. In the Explorer pane, go to localhost > System > Policies > Product Policies > FactoryTalk-enabled software > HTTPS Protocol.
3. Change the port to other available ports instead of 443.
4. Select Apply, and then select OK.
5. Open Internet Information Services (IIS) Manager.
6. In the Connections pane, select the server and site for the FactoryTalk-enabled software.
7. In the Actions pane, click Bindings.
8. In the Site Bindings dialog, select the HTTPS site binding, and then click Edit.
9. Change the port number to the one you configured in step c.
10. Click OK.

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.

From the SQL Management Studio, delete and re-add the MTUsers group from the material database, as detailed below:

1. Open the SQL Management Studio.
2. Select the database->Security->Users.
3. Delete MTUsers.
4. Select the material database and click Open File on the toolbar.
5. Browse to the \\Batchctl\Scripts folder and open MaterialTrack_db_Security.sql.
6. Execute the MaterialTrack_db_Security.sql script on the material database.
7. Open the Material Editor.

Anomaly first identified in FactoryTalk Batch version 17.00.00.

From the SQL Management Studio, delete and re-add the MTUsers group from the material database, as detailed below:

1. Open the SQL Management Studio.
2. Select Security->Logins.
3. Delete and recreate the group MTUsers.
4. Select the database->Security->Users.
5. Delete MTUsers.
6. Select the material database and click Open File on the toolbar.
7. Browse to the \\Batchctl\Scripts folder and open MaterialTrack_db_Security.sql.
8. Execute the MaterialTrack_db_Security.sql script on the material database.
9. Open the Material Editor.

Anomaly first identified in FactoryTalk Batch version 17.00.00.

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>

1. Data Server type change
   Data Servers with the type FTLinx are now identified as Live Data. This change is displayed in the Equipment Editor Edit Data Server dialog. The change has no impact on functionality.

2. Material Manager
   The Material Manager Server technology has been updated to .Net in v17.00.00.
   • The custom insertion point sample project, RAMSCustom.dll, is now a C# .Net component. Existing custom RAMSCustom.dll may need to be migrated to the new technology. See the Material Manager Getting Results guide.
   • The change to .Net has forced changes in how the Material Object Model exposes enumeration data types. The enumeration name is included in each enumeration item. This is a namespace issue that Microsoft fixed in .NET

   Example in Batch v16.00.00 (VB6)

   typedef   [uuid (2BF6DB2B-F3FB-4EC5-95A8-E0ABC530ED2F),  version (1.0) ]

                   enum  {

                   GetAllMaterials  =  0,

                   GroupName  =  1,

                   ClassificationName  =  2,

                   MaterialName  =  3

          }  MaterialFilterEnum; 

   Example in Batch v17.00.00 (.NET)

   typedef   [uuid (2BF6DB2B-F3FB-4EC5-95A8-E0ABC530ED2F),  version (1.0) ,

   custom  (0F21F359-AB84-41EB-9A78-36D110E6D2F9, 
   "RA.Batch.MaterialServer.MaterialFilterEnum")

   ]

   enum  {

           MaterialFilterEnum_GetAllMaterials  =  0,

           MaterialFilterEnum_GroupName  =  1,

           MaterialFilterEnum_ClassificationName  =  2,

           MaterialFilterEnum_MaterialName  =  3

   }    MaterialFilterEnum;

3. BatchHistoryEx database schema change

   The schema of the Batch History database, BatchHistoryEx, has been changed to improve performance. Existing BatchHistoryEx databases can be migrated to the new schema by using the FactoryTalk Batch Database Migration Utility. The utility is installed on the BatchHistoryEx machine and can be accessed from the Start menu. The FactoryTalk Batch Database Migration Utility can migrate older BatchHistory and BatchHistoryEx databases to the current schema. The migration to the current schema requires stopping all archiving to the database and can take hours depending on the size of the database.

• Upgrade from FactoryTalk Batch v16.00.00 to FactoryTalk Batch v17.00.00 does NOT require an uninstall of FactoryTalk Batch v16.00.00.

• Before upgrading to FactoryTalk Batch v17.00.00 from FactoryTalk Batch v14.00.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 v17.00.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 v17.00.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?

• Always prompt for a username and password.
• Not use the Single Sign-on User.
• Not set the Single Sign-on User.

• To install the software with no user interface using the default settings during the installation process. (Silent install)
  Setup.exe /Q /IAcceptAllLicenseTerms

• To install the Chinese language version of the software on the D: drive and display the progress, error, or complete messages during installation and restart the computer if necessary. (Unattended install)
  Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /InstallDrive=D:
  -specific command line parameters

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

  Setup.exe /Q /IAcceptAllLicenseTerms /DomainWorkgroup=Domain /BatchDomain=MyDomain /BatchUserName=User1 /BatchPassword=s3cretp@ssw0rd! / Product=FTBatch /BatchServerName=BatchServer1 /HTTPS_PORT_USER=8443 /CopyCustomerContentSelected=Yes

• 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.

1. (L1) Ensure 'User Account Control: Admin Approval Mode for the Built-in Administrator account' is set to 'Enabled'
2. (L1) Ensure 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' is set to 'Prompt for consent on the secure desktop' or higher Fail
3. (L1) Ensure 'User Account Control: Behavior of the elevation prompt for standard users' is set to 'Automatically deny elevation requests'

• 2.2 User rights assignment
  • 2.2.4 (L1) Ensure 'Act as part of the operating system' is set to 'No One'
  • 2.2.6 (L1) Ensure 'Adjust memory quotas for a process' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE'
  • 2.2.14 (L1) Ensure 'Create a token object' is set to 'No One'
  • 2.2.16 (L1) Ensure 'Create permanent shared objects' is set to 'No One'
  • 2.2.33 (L1) Ensure 'Increase scheduling priority' is set to 'Administrators, Window Manager\Window Manager Group'
  • 2.2.44 (L1) Ensure 'Replace a process level token' is set to 'LOCAL SERVICE, NETWORK SERVICE'.

• 2.2 User rights assignment
  • 2.2.4 (L1) Ensure 'Act as part of the operating system' is set to 'No One'
  • 2.2.6 (L1) Ensure 'Adjust memory quotas for a process' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE'
  • 2.2.14 (L1) Ensure 'Create a token object' is set to 'No One'
  • 2.2.16 (L1) Ensure 'Create permanent shared objects' is set to 'No One'
  • 2.2.33 (L1) Ensure 'Increase scheduling priority' is set to 'Administrators, Window Manager\Window Manager Group'
  • 2.2.44 (L1) Ensure 'Replace a process level token' is set to 'LOCAL SERVICE, NETWORK SERVICE'.
• 2.3.10 Network access
  • 2.3.10.6 (L1) Configure 'Network access: Named Pipes that can be accessed anonymously' (DC only)

• 2.2 User Rights Assignment
  • 2.2.3 (L1) Ensure 'Act as part of the operating system' is set to 'No One'.
  • 2.2.4 (L1) Ensure 'Adjust memory quotas for a process' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE'.
  • 2.2.11 (L1) Ensure 'Create a token object' is set to 'No One'Fail
  • 2.2.13 (L1) Ensure 'Create permanent shared objects' is set to 'No One'.
  • 2.2.25 (L1) Ensure 'Increase scheduling priority' is set to 'Administrators, Window Manager\Window Manager Group'.
  • 2.2.36 (L1) Ensure 'Replace a process level token' is set to 'LOCAL SERVICE, NETWORK SERVICE'.
  • 2.3.10 Network access
  • 2.3.10.8 (L1) Ensure 'Network access: Remotely accessible registry paths and sub-paths' is configured.

• 2.2 User Rights Assignment
  • 2.2.4 (L1) Ensure 'Act as part of the operating system' is set to 'No One'
  • 2.2.6 (L1) Ensure 'Adjust memory quotas for a process' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE'
  • 2.2.14 (L1) Ensure 'Create a token object' is set to 'No One'
  • 2.2.16 (L1) Ensure 'Create permanent shared objects' is set to 'No One'
  • 2.2.33 (L1) Ensure 'Increase scheduling priority' is set to 'Administrators, Window Manager\Window Manager Group'
  • 2.2.44 (L1) Ensure 'Replace a process level token' is set to 'LOCAL SERVICE, NETWORK SERVICE'
• 2.3.10 Network access
  • 2.3.10.9 (L1) Configure 'Network access: Remotely accessible registry paths and sub-paths' is configured