Sametime
Notes client LTPA authentication issue after Sametime 12.0.2FP1 upgrade 
By Vladislav Tatarincev | 8/27/24 10:00 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
We use LTPA Token authentication inside company for HCL Sametime 12.0.2. It was working fine.
When Sametime 12.0.2FP1 arrived we upgraded our Sametime and Notes 14 clients were unable to login with LTPA. Only regular password login was working.
Sametime Authentication container logs brought us the following:
error: Error decoding LtpaToken2: "error:1C800064:Provider routines::bad decrypt". Trying as v1: false
[2024/08/23 13:39:41] info: ::ffff:172.22.0.8 - -
We opened case and support mentioned that: in HCL Sametime 12.0.2 FP1 we disabled LTPA V1 token support by default - in favor of LTPA V2 which is more secure.
The Embedded clients, especially the 'older' ones still present only the LTPA V1 tokens.
In Domino SSO document, our configuration was LtpaToken and LTPAToken2.
We changed format of token to "LTPAToken2 only" and did restart of Domino and this has resolved issue.
After upgrading Sametime to V12.0.2 you cannot send messages to offline users 
By Remco Angioni | 5/9/24 3:20 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
After upgrading to Sametime V12.0.2, we cannot send chats to offline users anymore using client or mobile app. After opening a case, HCL told us that there should be a policy for that. But this policy doesn't exists in ../sametime-config/policy/policies.user.xml.
How to remove a Groupchat in Sametime V12?
By Remco Angioni | 4/17/24 4:01 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
When a user creates a groupchat using, let’s say “AllUsers”, this groupchat will consume a lot of resources when AllUsers contain many many users.
Beside asking the users to remove this chat, there is no way to remove this groupchat using a (Admin)gui.
We raised a call to HCL and they solved it by removing it from the backend. Smart one. They even created a KB item about it, using our information. Smart one.
You can terminate the group chat from the MongoDB
Here are the steps:
Sametime 12.0.2 statistics & settings are gone after restart server
By Remco Angioni | 4/8/24 12:42 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
Because of the strange default settings in the Sametime V12.0.2 Docker configuration, all changes in Grafana and Prometheus are gone after you bring the docker containers down and/or when you restart the server. By default, HCL decided that Grafana stores information inside the container.By default, HCL decided that Prometheus data is stored on the host.
When you bring down the Docker containers, Grafana information is gone.
When you restart the entire server, /tmp is cleared and therefor all statistics
Prometheus issue is easy to solve, just change the local path to another location outside /tmp
Grafana also need a local, or Docker storage, outside it’s own container.
How to add admins to HCL Sametime 12.0.2
By Ales Lichtenberg | 3/6/24 4:56 PM | Infrastructure - Sametime | Added by Oliver Busse
Perhaps you, like me, have been looking for a way to add multiple users as HCL Sametime Admins for HCL Sametime 12.0.2. These admins can then view Grafana stats and manage user policies using the UI directly in the Sametime environment.
Sametime upgrade – A thing to be aware of
By Roberto Boccadoro | 1/2/24 10:18 AM | Infrastructure - Sametime | Added by Oliver Busse
Today I noticed that Sametime awareness was not working in Verse. Since it did until a few days ago I started to look what could be wrong. I tried to log in to Sametime and could not.
Alas, time to look at the logs on the server; doing so I noticed a strange error in the community container log. A timeout when connecting to my LDAP server. I checked my Domino server, which is my LDAP and everything was fine. So I started a remote session with my Linux box where I have installed Sametime and all of a sudden weird errors appeared when I tried to change directory from / to /sametime. A look at the filesystem left me horrified. I had the disk full!!!
Losing the persistent chat history of a renamed HCL Sametime 12 user - how to fix it
By Ales Lichtenberg | 11/6/23 3:36 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
If you rename a user and they log into Sametime, they will not see the persistent chat history. This is not a bug and the loss is not permanent. You need to run the database tool to synchronize the data properly. The Sametime 12 documentation describes everything. Here is a simple description of how to perform this process.
Sametime monitoring dashboard on Docker
By Roberto Boccadoro | 4/3/23 6:25 AM | Infrastructure - Sametime | Added by Oliver Busse
Sametime 12.0.1 introduced a new feature, a monitoring dashboard based on Grafana.
But on Docker it was not working, in various panels, for example those related to meetings it showed “no data”. Some of us reported this to HCL and they told that a fix would be provided for FP1.
Richard Pajerski: Securing access to MongoDB with Sametime 12 Premium
By Richard Pajerski | 2/15/23 1:46 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
The thrust of this post is on securing the server itself, and more specifically the MongoDB portion where chat histories, contact lists and other details are stored. HCL supports MongoDB versions 4.2 and higher on a best effort basis and I'm using version 6.0.4 on CentOS 8 for purposes of this post. Here's what worked for me.
After installing, we configure our Sametime database using the MongoDB Shell; upon first connecting, there's no prompt for a password and we're plainly told:
"Access control is not enabled for the database. Read and write access to data and configuration is unrestricted"
Well, that's not good. It was now possible to connect using mongosh and fully control the server *from anywhere, without a password*... :-(
Problem with Prometheus in Sametime monitoring dashboard
By Roberto Boccadoro | 2/8/23 11:26 AM | Infrastructure - Sametime | Added by Oliver Busse
I set up the monitoring dashboard in Sametime, using the provided JSON files; in case you don’t know how to do that, you enable it running this command
docker-compose -f docker-compose.yml -f docker-compose-monitoring.yml up -d
https://help.hcltechsw.com/sametime/1201/admin/Managing_dashboard.html
Today I discovered that my Prometheus container kept crashing, and in the logs I found lines like these
Sametime V12 MongoDB LDAP issue when using webusers
By Remco Angioni | 1/30/23 1:57 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
When you move from a Sametime version running on Domino to the Sametime V12 version, running on Docker......there could be a problem when you have webusers running in your Sametime environment. You always have to run the Sametime Name Change utility to move away from Domino (LDAP) syntax ( CN=Remco/O=ORG to CN=Remco,O=ORG) https://help.hcltechsw.com/sametime/11.6/admin/changing__names_in_contact_and_privacy_lists.html
There is a problem when you have used Sametime 11.6, which already used MongoDB for chatlogging, and used WEBUSERS (and not registered users). Webusers are saved flat in MongoDB and do not contain the CN=…/O=… syntax. When you move to Sametime V12 and converted the users to LDAP and imported vpuserinfo to MongoDB, you see a loss in Contacts and Archive. Your account is no longer connected to your old chats and doesn’t contain any contacts. Why?
Certificate Information tool
By Fredrik Norling | 1/17/23 2:40 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
SSL certificates, SAML certificates, Signing certificates the number is long of different kinds of certificates and you might need to check the name of a certificate, the start or end date or perhaps the thumbprint.
I use the tool mainly to get end dates of certificates sent to me from customers because I hate when they expire and need to be changed without any preparation. And the worst kind that most administrators often miss is the certificates that is auto created i.e. in ADFS servers, Azure Enterprise apps, Okta
HCL Sametime 12.0.1 - How to upgrade
By Ales Lichtenberg | 11/21/22 4:09 PM | Infrastructure - Sametime | Added by Oliver Busse
A few days ago, HCL Sametime and HCL Sametime Premium 12.0.1 were released. The installation is basically the same as for version 12.0, but I modified my guide.
The upgrade is also very simple, so you can check out the guide I prepared.
So you can get started.
Sametime V12.0.1/12.0.2 cannot connect to LDAPS:636 using TLSv1.2
By Remco Angioni | 10/31/22 4:49 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
Setting up Sametime V12.0.1 and V12.0.2 BETA, I discovered that we couldn't connect to LDAPS to a Domino server, or to the AD using TLSv1.2.I discovered it in the Docker environment and noticed in the community log these lines:
community_1 | stuserinfosa 2022-10-04 08:44:04.175 SEVERE 0 — 31 : createConnection : Problem Initalizing context for simple bind
community_1 | javax.naming.CommunicationException: simple bind failed: stldap.domain.internal:636 [Root exception is java.io.IOException: Initial encode failure on StTlsSocket [6]]
How to migrate older Sametime to HCL Sametime 12 Guide - Ales Lichtenberg
By Ales Lichtenberg | 9/27/22 10:04 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
If you are running Sametime V11 or earlier and want to upgrade to Sametime 12, you have two options. They start from scratch with a clean install (sometimes it’s worth it) or migrate existing Sametime to the new Sametime 12.
I have prepared a short guide on how to migrate the contact list (vpuserinfo.nsf) of your users and I have also added the option to convert from native Domino Directory to LDAP, which is a condition for migration to Sametime 12.
Updating Sametime 12 to FP1. Not all customizations are kept
By Roberto Boccadoro | 7/22/22 5:30 AM | Infrastructure - Sametime | Added by Oliver Busse
Upon suggestion from my friend Erik Schwalb of HCL, I upgraded to FP1 a Sametime12 server where I made some branding customization.
Contrary to what I wrote in my previous post not ALL customizations are kept.
How to start Sametime automatically when the OS starts
By Ales Lichtenberg | 7/19/22 3:23 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
In the HCL Knowledge Base, there is an article, https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0099516, on how to configure Sametime 12 to start automatically after the operating system starts.
And what is the procedure?
HCL Sametime Premium and HCL Sametime 12.0 FP1 is out
By Ales Lichtenberg | 7/15/22 5:51 AM | Infrastructure - Sametime | Added by Matteo Bisi
the first FP for Sametime V12.0 is now available and includes the following list of fixes:
Source: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0099322
Extra “Sametime V12 MongoDB roles” in a highly secured Mongo environment
By Remco Angioni | 7/11/22 4:26 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
When following the standard procedure for installing LDAP, MongoDB and Sametime V12. You may discover that the Sametime database user does not have enough rights. The procedure tells us that the following command for creating an user and roles should be enough: db.createUser({user: "sametimeUser", pwd: "sametime", roles:[{role:"readWrite", db:"chatlogging"},{ role:"readWrite", db:"mobileOffline"},{ role:"readWrite", db:"meeting"},{role:"dbAdmin", db:"meeting"},{role:"userAdminAnyDatabase", db:"admin"}]})
Because there was no warning or error at this point we finished the installtion and started Sametime V12, I discovered that we couldn’t login into Sametime. Even when LDAP works correctly and tells us “BIND SUCCESSFULL” in the Sametime Community log.
HCL Sametime Connect client 11.6 IF3 and Sametime 12.0 Standard Client Updated
By Ales Lichtenberg | 6/3/22 1:55 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
When installing HCL Sametime Connect 12.0 client on Windows and Mac platforms, the install does not complete and the following error is reported:
Unexpected results have occurred during the provisioning operation
For additional information, please refer to the logs: C:\user\username\AppData\Roaming\HCL\Sametime\logs
My install guide “HCL Sametime 12.0 – Step by Step” is out
By Ales Lichtenberg | 5/20/22 3:15 AM | Infrastructure - Sametime | Added by Oliver Busse
According to previous announcements, I createted first version a step by step installation guide for HCL Sametime 12.0. It is a guide for basic installation and configuration so that Sametime and Sametime Meetings can be tested easily and quickly.
HCL Sametime Premium and HCL Sametime 12.0 released
By Ales Lichtenberg | 4/28/22 4:56 PM | Infrastructure - Sametime | Added by Oliver Busse
Sametime V12 Premium has just been released. Here is an overview with links to the necessary documents.
Sametime 11.6 IF2 installation results in a non-working proxy when you don’t have a meeting server.
By Remco Angioni | 3/25/22 4:27 PM | Infrastructure - Sametime | Added by Oliver Busse
After installing Sametime 11.6 IF2, i discovered that the entire proxy service will not start at all. In the localhost log you can see the following warning, over and over again. After opening a support ticket, HCL discovered a problem in the code. It seems like Sametime 11.6 IF2 needs a configured meeting server in the config.
Sametime Proxy Server issue after upgrading to 11.6 IF2
By Rainer Brandl | 3/25/22 2:26 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
Yesterday I upgraded a Sametime Proxy Server 11.6 to 11.6 IF2. After the upgrade you could login but then the screen hang and your chats did not display.First I thought about an issue with the database connection and checked the configuration which looked fine. Then Ales sent me a link which helped to get the Proxy Server running again
HCL Sametime – RunFaster=1
By Milan Matejic | 3/3/22 2:50 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
verybody likes when software performs well and feels "snappy", guided by that mantra I've found that with the help of one "sametime.ini" parameter for LDAP tuning, you can improve the "login" performance of the clients and the time it takes to load Sametime Business Cards considerably.
HCL Sametime – Setting the Community ID
By Milan Matejic | 12/7/21 2:40 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
If you are planning to deploy HCL Sametime Community service in a cluster or HA architecture, setting a Community ID is a must. Ideally, this should be an FQDN used for accessing the Community servers, something which is easy to remember, and your users can relate to. So, think ahead and use a name that can be used to access the service externally and internally
Disabling persistent chat in Sametime 11.x
By Rainer Brandl | 11/17/21 6:55 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
In one customer situation I had the request to disable the new ( and great ) functionality of the persistant chat.Well, you have to install the MongoDB during the installation of the Sametime Community Server but can disable the need of the MongoDB afterwards by going through the following steps
How I solved the problem Sametime integration with iNotes / Verse
By Ales Lichtenberg | 9/27/21 3:42 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
I recently worked on one integration of Sametime V 11.6 with iNotes and Verse (2.2.0). I configured everything as usual, but I still couldn’t get Sametime up and running with iNotes and Verse.
Although this has been described in the documentation, discussion forums or on various blogs, I would like to remind you once again that certain parameters need to be used.
Some interesting video sources of HCL Digital Solutions for Summer
By Ales Lichtenberg | 7/22/21 8:34 AM | Infrastructure - Sametime | Added by Oliver Busse
HCL publishes short video tutorials on its YouTube channel, so I chose a few for the holiday time.
Here are a few links.
Updated Table of Client types that are connecting to a Sametime server (include Notes 12)
By Ales Lichtenberg | 6/16/21 1:04 AM | Infrastructure - Sametime | Added by Roberto Boccadoro
The new Notes 12.0 client type (using the embedded Sametime 11.5 product) that uses a connection to the Sametime server has ID 0x12A4