Hi Team,

In one of my cases, the customer has informed us that, due to Microsoft deprecating NTLM and their requirement to migrate to Kerberos, they need to update the F5 router name from xxxTitle to xxxK2Title.

To ensure that in-flight processes remain accessible after the F5 router name change, the customer would like to know which K2 system database tables may need to be updated to reflect the new router name (i.e., updating references from xxx_____ to xxxK2___). Specifically, they are looking to update URLs from the old format https://_______/___.TravelExpense.wap/ to the new format https://___k2___/___.TravelExpense.wap/.

The new URL https://___k2____/___.TravelExpense.wap/ points to the .NET web application that interfaces with the K2 server K2P01. The customer has noted that some of the K2 system database tables contain references to the old F5 router name used in front of the Web App.

So far, the customer has identified the following two tables that contain such URL references:

• [ServerLog].[ActInstDestData]

• [ServerLog].[ProcInstData]

While the customer has already updated their DNS settings to point to the new URL, some applications are still being redirected to the old URL.

That said, I am unsure whether manually modifying these database tables is advisable, as we generally do not recommend making direct changes to the K2 database due to potential impacts on system stability and supportability.

Any suggestions, guidance, or best practices for addressing this situation would be highly appreciated.