BizTalk 2016: Additional post install changes in multi-server environment

To provide high availability for BizTalk databases, Microsoft recommends BizTalk databases be created in the following way:

S.No	SQL Instance	BizTalk Databases
1	AUTHENTICATION	SSODB
2	RUNTIME	BizTalkMsgBoxDb BizTalkRulesEngineDb BAMPrimaryImport BAMStarSchema BAMAlertsApplication
3	MGMT	BizTalkMgmtDb
4	TRACKING	BizTalkDTADb EsbItineraryDb EsbExceptionDb
5	REPORTING	Custom DBs

In addition to the BizTalk Server 2016 & SQL 2016 installation pre-requisites, the following changes are required on BizTalk 2016 App & DB servers:

1. The Windows Firewall has been turned off on all servers. These changes have been applied to Domain, Public & Private profiles.

2. The COM+ Network access has been enabled in Windows Firewall to allow communication between the App & DB Servers.

3. The registry entry for RemoteAccessEnabled at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3 was modified to ‘1’.

4. The CID values on all four servers were the same, this is a case when the servers are cloned. This was deterring the BizTalk Group to be configured. The MSDTC had to be uninstalled & installed again on BizTalk App servers to have a different set of CID.

After these changes, BizTalk was successfully configured on both App Servers.