This article describes Cumulative Update 5 (CU5) for Workflow Manager 1.0.
- Workflow Manager 1.0 is a prerequisite for Workflow Manager 1.0 CU5.
- Workflow Manager Client 1.0 CU4 is a prerequisite for Workflow Manager 1.0 CU5. It can be downloaded from Cumulative Update 4 for Workflow Manager 1.0 (KB4019220).
- Do not extract the MSP file and install directly from the MSP file. This is not supported.
- We recommend that you test this update before you deploy it in a production environment.
This cumulative update includes all the features and fixes that were included in earlier cumulative updates for Workflow Manager 1.0. More information about previous Cumulative Updates can be found in the Microsoft Knowledge Base at the links below:
2799754: Workflow Manager 1.0 Cumulative Update 1
2902007: Workflow Manager 1.0 Cumulative Update 2
3104066: Workflow Manager 1.0 Cumulative Update 3
4019220: Workflow Manager 1.0 Cumulative Update 4
Features that are added in this update
- Adds support for the TLS protocol versions 1.1 and 1.2.
Issues that are fixed in this update
- Workflow Manager 1.0 CU4 cannot be directly installed from versions that are earlier than Workflow Manager 1.0 CU3. This update fixes the issue and makes sure that Workflow Manager 1.0 CU5 can be installed on top of any earlier versions.
A supported cumulative update package is now available from Microsoft. This cumulative update is available for download in the "Download information" section.
Updates that are included in this cumulative update package
- Workflow Manager 1.0 Cumulative Update 5 (Update)
This cumulative update contains several software updates. This is an update MSI that can be installed on
- A computer with Workflow Manager 1.0
- A computer with Workflow Manager 1.0 CU1
- A computer with Workflow Manager 1.0 CU2
- A computer with Workflow Manager 1.0 CU3
- A computer with Workflow Manager 1.0 CU4
For customers who have new deployments, Workflow Manager 1.0 Refresh CU2 (Web Platform Installer) and Workflow Manager 1.0 CU5 can be installed before configuring the farm. It works with Service Bus 1.1 or Service Bus 1.0 Cumulative Update 1.
For customer who are updating, users must install Workflow Manager Client 1.0 Client with Cumulative Update 4 (Full install) to update client before installing this CU5 update that will update the server only and the Workflow Manager databases.lative update package information
The following files are available for download from the Microsoft Download Center:
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites for Workflow Manager 1.0 CU5
• Workflow Manager Client 1.0 CU4 must be installed on the computer.
• Workflow Manager 1.0 RTM, CU1, CU2, CU3 or CU4 must be installed on the computer.
• PowerShell 3.0 must be installed on the computer to be updated. PowerShell 3.0 is included in the Windows Management Framework 3.0 installation. Go to Windows Management Framework 3.0 to install this update.
• SQL Server 2012 Service Pack 4, SQL Server 2014 Service Pack 3, SQL Server 2016 or SQL Server 2017 must be installed if used in combination with SharePoint.
• SQL Server 2012 Service Pack 4 must be installed if used outside of SharePoint.
• For computers that have Workflow Manager 1.0 installed, either of the following additional requirements must be met:
• The Service Bus 1.0 for Windows Server with cumulative update 2799752 must be installed on the whole computer farm before you install the cumulative update for Workflow Manager 1.0 or
• Service Bus 1.1 for Windows Server must be installed on the computer or
• Service Bus 1.1 with TLS 1.2 Support for Windows Server must be installed on the computer to support the new feature TLS protocol versions 1.1 and 1.2.
If you are using later version of SQL server than SQL Server 2014, for example: SQL Server 2016, then you must change the compatibility model of the databases to version 120. This is due to compatibility with datetime2 date type conversion. You can change compatibility level with below commands. In case you have custom database names you need to change to your specific database names.
SELECT name, compatibility_level FROM sys.databases;
ALTER DATABASE [WFInstanceManagementDB] SET COMPATIBILITY_LEVEL = 120;
ALTER DATABASE [WFManagementDB] SET COMPATIBILITY_LEVEL = 120;
ALTER DATABASE [WFResourceManagementDB] SET COMPATIBILITY_LEVEL = 120;
ALTER DATABASE [SbGatewayDatabase] SET COMPATIBILITY_LEVEL = 120;
ALTER DATABASE [SbManagementDB] SET COMPATIBILITY_LEVEL = 120;
ALTER DATABASE [SBMessageContainer01] SET COMPATIBILITY_LEVEL = 120;
SELECT name, compatibility_level FROM sys.databases;
Please see here for more information on database compatibility:
- Breaking Changes to Database Engine Features in SQL Server 2016
- SQL Server and Azure SQL Database improvements in handling some data types and uncommon operations
SQL Always On Availability Group
- Supported Availability Mode is Synchronous-commit mode.
Supported operating systems
- Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 Standard or Datacenter and Windows Server 2019 Standard or Datacenter.
- Workflow Manager Client 1.0 can also be independently installed on the x86 and x64 versions of Windows 7 and above.
Before you run the executable, you must have administrative credentials on the computer where you are installing the software. See the Workflow Manager documentation for more information.
For each computer that uses a Workflow Manager host in a computer farm, this update must be installed on that computer.
There are some minimal database changes that will occur when this cumulative update is installed. If you decide to uninstall this update, these database changes are backward-compatible and will not be rolled back.
You may have to restart the computer after you apply this cumulative update.