I came across an HCL Domino environment with HCL Sametime where the Sametime embedded clients were logging in via LTPA but with a different authentication server than the Sametime Community server. As you can imagine, this was important to keep in mind during a Sametime migration. The Domino server used for authenticating Sametime clients is also hosting multiple websites and using multiple LTPA tokens, so the question was, which LTPA token is actually used for authenticating the Sametime clients.

If you experience the issue with HCL Sametime 11 Proxy, where the WebClient just loads endlesly after a user logs in, and the following error is present in "catalina.out" log file (of the Sametime Proxy component): CLFRX0049E: Failed to query the user info: <username>, reason 80000005 Check the "UserInfoConfig.xml" file, on the Sametime Community Server,

In the HCL Sametime version 11 there is no System Console, which means that the Name Change tasks have to be created directly in the "stnamechange.nsf" database. This process is not documented. After trying to reinvent the wheel and failing gloriously, I decided to write a blog post about it. :-)