Prerequisites for Service Bus for Windows Server 1.1 with TLS 1.2 Support
To get more information about Service Bus for Windows Server 1.1 and how to install it, see the Getting Started with Service Bus for Windows Server 1.1 documentation.
Software requirements
- Service Bus for Windows Server 1.1 CU1 must be installed on the computer.
- PowerShell 3.0 must be installed on the computer. PowerShell 3.0 is included in the Windows Management Framework 3.0 installation. To install this update, go to Windows Management Framework 3.0.
- KB 2858668 is required by Service Fabric for Windows Server 2012.
- Service Bus for Windows Server 1.1 with TLS 1.2 support must be installed on the computer to support the new TLS1.1 and TLS1.2 feature.
- 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.
SQL version
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;
GO
USE [Master];
GO
ALTER DATABASE [WFInstanceManagementDB] SET COMPATIBILITY_LEVEL = 120;
GO
ALTER DATABASE [WFManagementDB] SET COMPATIBILITY_LEVEL = 120;
GO
ALTER DATABASE [WFResourceManagementDB] SET COMPATIBILITY_LEVEL = 120;
GO
ALTER DATABASE [SbGatewayDatabase] SET COMPATIBILITY_LEVEL = 120;
GO
ALTER DATABASE [SbManagementDB] SET COMPATIBILITY_LEVEL = 120;
GO
ALTER DATABASE [SBMessageContainer01] SET COMPATIBILITY_LEVEL = 120;
GO
SELECT name, compatibility_level FROM sys.databases;
GO
Please see here for more information on database compatibility:
Supported operating systems
- Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 Standard or Datacenter and Windows Server 2019 Standard or Datacenter.
Service Account requirements
To be able to setup the services to start-up properly, the Service Account that is used to run Service Bus needs to have local administrator privileges at least the first time the services are started.
Dependent services requirements
When the services are being configured or started, they need access to the Windows Firewall service and the Performance Logs & Alerts service. You must ensure that you have these services enabled on the server. You can add exclusions instead if you don't require firewall rules.
Credential requirements
Before you run the executable, you must have administrative credentials on the computer on which you are installing the software. For more information, see the Service Bus Server documentation.
Deployment
This installer must be installed on each computer that uses a Service Bus for Windows Server host in a computer farm.
New farm setup
- Install .NET Framework 4.6.2.
- Install the Visual C++ runtime distribution (by using Web Platform Installer (WebPI)).
- Install the Service Fabric 5.1 (by using WebPI).
- Install the Service Bus for Windows Server 1.1 with TLS 1.2 support (by using WebPI).
- Configure Service Bus farm as it was configured before the upgrade.
Upgrade from existing farm
- Back up the database. Then take the system offline.
- Remove all servers from the farm.
- Uninstall Service Bus for Windows 1.1 CU1.
- Uninstall Windows Fabric 1.0.
- Upgrade SQL Server 2012 to support TLS 1.2.
- Install .NET Framework 4.6.2.
- Install the Visual C++ runtime distribution (by using WebPI).
- Install the Service Fabric 5.1 (by using WebPI).
- Install Service Bus for Windows Server 1.1 with TLS 1.2 support. (by using WebPI)
- Run the Invoke-SBFarmUpgrade cmdlet.
- Rejoin all servers to the farm.
Database changes
Some minimal database changes occur when this update is installed. If you decide to uninstall this update, these database changes are backward-compatible and will not be rolled back.
Restart requirement
You may have to restart the computer after you apply this update.