---

Given that you have an Identify instance T1 which uses the Window authentication and its current session mode is SQLServer state whose connection string has the multiSubnetFailover setting, you need to do the following steps to ensure those settings stuffs kept after upgrading to version 5.5.

You should verify the current XmlConfiguration of the Identify instance T1 before  you start upgrading it. The steps are:

1. Access the IdentifyTenant database and run the following script to view all [XmlConfiguration] data (Note: you need to replace #TenantT1 with your own instance name)

If there’s no returned record, you can jump to the next step.
Otherwise, when you look closer at the returned records, you will see something like the sample below:

You need to update the SQLServer as its sessionStateMode as well as its sqlStateServerConnectionString’s content (Note: you need to replace #TenantT1 with your own instance name as well as replace #Base64-encodingconnectionstring with the base64-encoding of your sqlStateServerConnectionString( If your connectionstring supports: “MultiSubnetFailover=True;”, you need to put it to your sqlStateServerConnectionString))

Here is the query sample that I used for my local environment:

2. In order to verify the current Identify instance which ‘s already enabled its MultiSubnetFailover, access the IdentifyTenant database and run the following script to view all [XmlConfiguration] data with its multiSubnetFailover (Note: you need to replace #TenantT1 with your own instance name)
   
   Transact-SQL

   SELECT [TenantId] ,[Name] ,[Version] ,[XmlConfiguration] ,[ConfiguratorId] FROM [dbo].[Tenant] WHERE [XmlConfiguration] NOT LIKE '%multiSubnetFailover="True"%' AND [Name] IN ( N'#TenantT1') GO

   1 2 3 4 5 6 7 8 9

   SELECT [TenantId] ,[Name] ,[Version] ,[XmlConfiguration] ,[ConfiguratorId] FROM [dbo].[Tenant] WHERE [XmlConfiguration] NOT LIKE '%multiSubnetFailover="True"%' AND [Name] IN ( N'#TenantT1') GO

If there’s no returned record, you can jump to the instance upgrade process.
Otherwise, when you look closer at the returned records, you will see something like the sample below:

or

You need to add or update the multiSubnetFailover setting to True  (Note: you need to replace #TenantT1 with your own instance name).

3. Run the Identify configurator and upgrade the Identify instance as usual.

Now your instance uses the SQLServer session state and its connection string has the multi subnet failover setting set correctly. You won’t need to do these manual steps again for future upgrades.

Note: we have prepared a new SQL script for the above steps to apply for all instances at once. There is also a setting to configure a set of instances that you want to skip. You can download it at 66354_XMLConfigurationAutoScript. Please note that you need to set the @sqlStateServerConnectionString and @excludedTenant parameters correctly before you can run it.