The following are the system requirements for KEPServer Enterprise version 13.01.00.

KEPServer Enterprise 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

KEPServer Enterprise requires the following hardware:

• 1 GHz processor
• 1 GB of RAM
• Ethernet card
• 530 MB free hard disk space

Software requirements

KEPServer Enterprise has been tested on the following operating systems:

• Windows® 10 x64 (Pro and Enterprise Edition) (v2004, v20H2, v21H1, and 21H2)
• Windows 10 IoT Enterprise 2016 Long-Term Servicing Branch (LTSB)
• Windows 10 IoT Enterprise 2016 (LTSB) Embedded*Windows 10 IoT Enterprise 2019 Long-Term Servicing Channel (LTSC)
• Windows Server® 2019 x64
• Windows Server 2016 x64
• Windows Server 2012 x64 R2
• Windows Server 2012 x64
• Windows Server 2022
• Windows 11

* This operating system is supported with the Allen-Bradley® 61xx family of industrial computers and CompactLogix™ 5480 family of controllers.

 Note: Windows Server Core deployments are not supported for Windows Server 2019 and Windows Server 2016.

Software compatibility 

• FactoryTalk Activation Manager version 4.06.13

KEPServer Enterprise version 13.01.00 has the following new and enhanced features:

New features

Server

• General
  • Adds user permissions to control the access to the Event Log, relevant to security, error, warning, and informational messages.
• Configuration API
  • Adds an About endpoint to provide version information about the server. This returns the product ID, product name, and version number.
  • Adds the ability to filter results from the event log endpoint by event type.

CODESYS Driver

• Adds a new property that allows the symbols to be loaded to a local directory to avoid the overhead of symbol copy over the network on every attempt to connect.

Mitsubishi Ethernet Driver

• Adds the ability to specify the connection port when using UDP with the FX3U model.

MTConnect Driver

• Adds the ability to issue a CURRENT command without a path and adds a property in device properties to enable this without changing the behavior of existing projects.

OPC UA Client Driver

• Adds support for continuation points when browsing for tags. This allows the driver to browse in smaller chunks and avoid timeouts related to server processing time when the server has a very large number of items.

• Adds a new custom 8-bit CRC: “Custom #17 (8-bit).”

Enhanced features

Server

• General
  • Updates handling of OS shutdown notifications to give more time for Kepware services to end during OS shutdown or reboot subject to Microsoft’s “Pre-shutdown” notification process.
• Configuration API
  • Changes the default ordering of event log results returned via the Configuration API. Previously, it returned the most recent page 100 events by default sorted in the oldest first order within the JSON array. It now returns the most recent page sorted in the newest first order within the JSON array. This is meant to provide a more intuitive experience when transitioning between pages.
  • Removes notifications in the event log showing user signed-in information via the Configuration API. This information is persisted in the Configuration API transaction log.
  • Changes the default mode for the Configuration API transaction log to a single file.

Modbus TCP/IP Ethernet Driver

• Modifies the _error tag to only toggle based on the device communication status.

MTConnect Driver

• Increases the maximum channels from 256 to 1024.

The following list identifies the anomalies corrected in the KEPServer Enterprise version 13.01.00.

Server

• General
  • Fixes an issue where the device level _ActiveTagCount system tag is not updating correctly.
  • Fixes intermittent memory corruption issues by updating Licensing Tools.
  • Fixes an issue that would cause the configuration window to stop responding during project validation.
• OPC DA Interface
  • Fixes an issue where a Max Age Read specifying read from the device could read from the cache.

ODBC Client Driver

• Fixes an issue where stored procedure OUT string parameters are not cleared before the stored procedure is run.

OPC DA Client Driver

• Fixes an issue where items added are rejected after a server restart.

• Fixes issues with calculating the CRC32 and CRC32 reflected algorithms.
• Fixes an issue where a UDP connection is not being made even though that connection type was specified.

• Hilscher Universal Driver
  
Deprecates this driver. Existing OPF project files have loaded, but the channels present an error in the event log. Existing JSON project files are unable to load.

• Multiple failed attempts to authenticate usernames or passwords will now result in a ten-minute lock-out period. First identified in KEPServer Enterprise version 13.00.00.

• KEPServer Enterprise is only able to browse tags using nested structures within four levels deep. First identified in KEPServer Enterprise version 13.00.00.

KEPServer Enterprise version 13.01.00 has no changes in functionality since the last release.

The following are the application notes for KEPServer Enterprise version 13.01.00.

• You can only install one version of KEPServer Enterprise per computer.
• KEPServer Enterprise version 13.01.00 is only available in the PC edition. KEPServer Enterprise version 10.00.00 is the latest version supported by PanelView Plus.

Mitigation for Microsoft DCOM Hardening patch

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

Set DCOM authentication level of KEPServer Enterprise

When using KEPServer Enterprise, change the authentication level through the following:

1. Open Component Services.
2. Double-click Console Root > Component Services > Computers > My Computer > DCOM Config.

   

3. Right-click KEPServerEnterprise x.xx and select Properties.

 

4. On the General tab, select the authentication level in Authentication Level.


5. Click OK and restart KEPServer Enterprise.

In addition to DCOM configuration, you must configure the following setting:

1. From the notification area, right-click KEPServerEnterprise and select Settings.
   

2. In the Settings - KEPServerEnterprise dialog box, select Runtime Options > Use DCOM configuration settings.

   
   

3. Click OK.

Supported Drivers

The PC edition of KEPServer Enterprise version 13.01.00 supports these drivers:

KEPServer Enterprise versions

This table displays the versions of KEPServer Enterprise and the related or equivalent versions for the following software:

Tip: FactoryTalk View SE and ME Station versions 10.00.00 and 11.00.00 require this patch to use KEPServer Enterprise version 10.00.00: https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1083527