<?xml version="1.0" encoding="utf-8"?>

<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">

	<channel>
		<title>Collaboration Today - Infrastructure - Sametime</title>
		<description>News about IBM Collaboration Solutions</description>
		<link>http://collaborationtoday.info</link>
		<atom:link rel="self" type="application/rss+xml" href="http://collaborationtoday.info?format=rss&amp;count=50" />
		<lastBuildDate>Tue, 9 Jun 2026 11:23:59 -0500</lastBuildDate>
		<image>
			<url>http://collaborationtoday.info/favicon.png</url>
			<title>Collaboration Today - Infrastructure - Sametime</title>
			<link>http://collaborationtoday.info</link>
			<width>32</width>
			<height>32</height>
			<description>News about IBM Collaboration Solutions</description>
		</image>
		<item>
			<title>Migrating using an empty Sametime ST_COMMUNITY_ID</title>
			<link>https://www.angioni.nl/2026/06/07/migrating-using-an-empty-sametime-st_community_id/</link>
			<guid>https://www.angioni.nl/2026/06/07/migrating-using-an-empty-sametime-st_community_id/</guid>
			<pubDate>Tue, 9 Jun 2026 11:23:09 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[Why is this so important to mention and create a blog about it?The ST_COMMUNITY_ID parameter, in sametime.ini, is used for connecting your Contactlist to one or more Sametime Community servers. 


https://www.angioni.nl/wp-content/plugins/w3-total-cache/pub/js/lazyload.min.js width=device-width, initial-scale=1 http://gmpg.org/xfn/11 Migrating using an empty Sametime ST_COMMUNITY_ID | Angioni's Blog Why is this so important to mention and create a blog about it?The ST_COMMUNITY_ID parameter, in sametime.ini, is used for connecting your Contactlist to one or more Sametime Community servers. Until Sametime V9 you could create a Sametime cluster and connect several servers to each other. The procedure tells me to set the ST_COMMUNITY_ID parameter max-image-preview:large angioni zPaeQYhhiPjaQcXtkn9BhbN8zYadx57jY-yzpZrdRbk community,cont]]>
			</content:encoded>
		</item>

		<item>
			<title>Standards are Standards until they are not</title>
			<link>https://wissel.net/blog/2026/04/standards-are-standards-until-they-are-not.html</link>
			<guid>https://wissel.net/blog/2026/04/standards-are-standards-until-they-are-not.html</guid>
			<pubDate>Mon, 13 Apr 2026 08:10:48 -0500</pubDate>
			<dc:creator>Stephan Wissel</dc:creator>
			<content:encoded>
				<![CDATA[Standards are Standards until they are not - In my junior developer days, literally last century, a senior developer enlightened me: 'An open standard is only complete once its wording allows all participants to faithfully implement it to be absolutely incompatible to each other'.
Ambiguity is king. Our modern software is build on a few standard, each of them have rock solid parts (nobody questions a <h1>) and parts of, let's call them disagreements. I'll pick on JWT as an example
]]>
			</content:encoded>
		</item>

		<item>
			<title>New HCL whitepaper on Sametime chat server on Windows</title>
			<link>https://www.robertoboccadoro.com/2026/03/10/new-hcl-whitepaper-on-sametime-chat-server-on-windows/</link>
			<guid>https://www.robertoboccadoro.com/2026/03/10/new-hcl-whitepaper-on-sametime-chat-server-on-windows/</guid>
			<pubDate>Tue, 10 Mar 2026 05:21:53 -0500</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[HCL has just published a whitepaper that explains how to install Sametime 12.0.3 on Windows step-by-step, run it on the same computer as an existing Domino server, and customize the user interface.]]>
			</content:encoded>
		</item>

		<item>
			<title>Howto deploy default Public Groups to (new) Sametime V12 users’ contactlist?</title>
			<link>https://www.angioni.nl/2026/03/02/howto-deploy-default-public-groups-to-new-sametime-v12-users-contactlist/</link>
			<guid>https://www.angioni.nl/2026/03/02/howto-deploy-default-public-groups-to-new-sametime-v12-users-contactlist/</guid>
			<pubDate>Thu, 5 Mar 2026 05:59:03 -0600</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[We need to have a procedure to give new users in the company a default set of Sametime groups to start chatting with their colleagues. Because the contactlist is still in the OLD binay:data:base64 format, you cannot simply add users' groups/contacts in a mongo-collection-way. You have to build the contactlist and decode it in BASE64 format. But there is also another way to do it. 
]]>
			</content:encoded>
		</item>

		<item>
			<title>Create LTPA keys in Windows</title>
			<link>https://www.robertoboccadoro.com/2025/11/18/create-ltpa-keys-in-windows/</link>
			<guid>https://www.robertoboccadoro.com/2025/11/18/create-ltpa-keys-in-windows/</guid>
			<pubDate>Wed, 19 Nov 2025 05:01:38 -0600</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[Sametime 12.0.3 chat server is available on Windows. You may want to have SSO, for example with Domino to have awareness status in email.

You then need a LTPA key, which is very easy to create if you use Docker as referenced in the documentation here https://help.hcl-software.com/sametime/v1203/admin/ltpa_generate_key.html

But what if you don’t use Docker? You need a way to generate a LTPA key in Windows. I found out that is not hard as it may seem and in this post I will explain how to do this.]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime 12.0.x non-containerized on Windows – Step by Step Installation Guide</title>
			<link>https://alichtenberg.cz/hcl-sametime-12-0-x-non-containerized-on-windows-step-by-step-installation-guide/</link>
			<guid>https://alichtenberg.cz/hcl-sametime-12-0-x-non-containerized-on-windows-step-by-step-installation-guide/</guid>
			<pubDate>Fri, 14 Nov 2025 03:00:00 -0600</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[I have created the first version of a detailed installation guide for HCL Sametime 12.0.x for Windows without using containers. This is a guide to basic installation and configuration so that you can easily and quickly start testing Sametime.]]>
			</content:encoded>
		</item>

		<item>
			<title>Notes client LTPA authentication issue after Sametime 12.0.2FP1 upgrade</title>
			<link>https://www.vlaad.lv/lotus.nsf/dx/notes-client-ltpa-authentication-issue-after-sametime-12.0.2fp1-upgrade</link>
			<guid>https://www.vlaad.lv/lotus.nsf/dx/notes-client-ltpa-authentication-issue-after-sametime-12.0.2fp1-upgrade</guid>
			<pubDate>Tue, 27 Aug 2024 10:00:57 -0500</pubDate>
			<dc:creator>Vladislav Tatarincev</dc:creator>
			<content:encoded>
				<![CDATA[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. ]]>
			</content:encoded>
		</item>

		<item>
			<title>After upgrading Sametime to V12.0.2 you cannot send messages to offline users</title>
			<link>https://www.angioni.nl/2024/05/04/after-upgrading-sametime-to-v12-0-2-you-cannot-send-messages-to-offline-users/</link>
			<guid>https://www.angioni.nl/2024/05/04/after-upgrading-sametime-to-v12-0-2-you-cannot-send-messages-to-offline-users/</guid>
			<pubDate>Thu, 9 May 2024 03:20:09 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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. ]]>
			</content:encoded>
		</item>

		<item>
			<title>How to remove a Groupchat in Sametime V12?</title>
			<link>https://www.angioni.nl/2024/04/16/how-to-remove-a-groupchat-in-sametime-v12/</link>
			<guid>https://www.angioni.nl/2024/04/16/how-to-remove-a-groupchat-in-sametime-v12/</guid>
			<pubDate>Wed, 17 Apr 2024 04:01:02 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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:]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime 12.0.2 statistics &amp; settings are gone after restart server</title>
			<link>https://www.angioni.nl/2024/04/05/sametime-12-0-2-statistics-settings-are-gone-after-restart-server/</link>
			<guid>https://www.angioni.nl/2024/04/05/sametime-12-0-2-statistics-settings-are-gone-after-restart-server/</guid>
			<pubDate>Mon, 8 Apr 2024 00:42:19 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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. ]]>
			</content:encoded>
		</item>

		<item>
			<title>How to add admins to HCL Sametime 12.0.2 </title>
			<link>https://alichtenberg.cz/how-to-add-admins-to-hcl-sametime-12-0-2/</link>
			<guid>https://alichtenberg.cz/how-to-add-admins-to-hcl-sametime-12-0-2/</guid>
			<pubDate>Wed, 6 Mar 2024 16:56:28 -0600</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime upgrade – A thing to be aware of</title>
			<link>https://www.robertoboccadoro.com/2024/01/02/sametime-upgrade-a-thing-to-be-aware-of/</link>
			<guid>https://www.robertoboccadoro.com/2024/01/02/sametime-upgrade-a-thing-to-be-aware-of/</guid>
			<pubDate>Tue, 2 Jan 2024 10:18:18 -0600</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[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!!!]]>
			</content:encoded>
		</item>

		<item>
			<title>Losing the persistent chat history of a renamed HCL Sametime 12 user - how to fix it </title>
			<link>https://alichtenberg.cz/losing-the-persistent-chat-history-of-a-renamed-hcl-sametime-12-user-how-to-fix-it/</link>
			<guid>https://alichtenberg.cz/losing-the-persistent-chat-history-of-a-renamed-hcl-sametime-12-user-how-to-fix-it/</guid>
			<pubDate>Mon, 6 Nov 2023 03:36:06 -0600</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime monitoring dashboard on Docker</title>
			<link>https://www.robertoboccadoro.com/2023/04/03/sametime-monitoring-dashboard-on-docker/</link>
			<guid>https://www.robertoboccadoro.com/2023/04/03/sametime-monitoring-dashboard-on-docker/</guid>
			<pubDate>Mon, 3 Apr 2023 06:25:27 -0500</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Richard Pajerski: Securing access to MongoDB with Sametime 12 Premium</title>
			<link>https://www.rhpconsult.com/blog/richard/entry/securing-access-to-mongodb-with</link>
			<guid>https://www.rhpconsult.com/blog/richard/entry/securing-access-to-mongodb-with</guid>
			<pubDate>Wed, 15 Feb 2023 01:46:25 -0600</pubDate>
			<dc:creator>Richard Pajerski</dc:creator>
			<content:encoded>
				<![CDATA[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*...  :-(]]>
			</content:encoded>
		</item>

		<item>
			<title>Problem with Prometheus in Sametime monitoring dashboard</title>
			<link>https://www.robertoboccadoro.com/2023/02/08/problem-with-prometheus-in-sametime-monitoring-dashboard/</link>
			<guid>https://www.robertoboccadoro.com/2023/02/08/problem-with-prometheus-in-sametime-monitoring-dashboard/</guid>
			<pubDate>Wed, 8 Feb 2023 11:26:30 -0600</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime V12 MongoDB LDAP issue when using webusers</title>
			<link>https://www.angioni.nl/2023/01/29/sametime-v12-mongodb-ldap-converter-issue-when-using-webusers/</link>
			<guid>https://www.angioni.nl/2023/01/29/sametime-v12-mongodb-ldap-converter-issue-when-using-webusers/</guid>
			<pubDate>Mon, 30 Jan 2023 01:57:15 -0600</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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? ]]>
			</content:encoded>
		</item>

		<item>
			<title>Certificate Information tool </title>
			<link>https://www.xpagedeveloper.com/2023/certificate-information-tool</link>
			<guid>https://www.xpagedeveloper.com/2023/certificate-information-tool</guid>
			<pubDate>Tue, 17 Jan 2023 02:40:04 -0600</pubDate>
			<dc:creator>Fredrik Norling</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime 12.0.1 - How to upgrade</title>
			<link>https://alichtenberg.cz/hcl-sametime-12-0-1-how-to-upgrade/</link>
			<guid>https://alichtenberg.cz/hcl-sametime-12-0-1-how-to-upgrade/</guid>
			<pubDate>Mon, 21 Nov 2022 16:09:14 -0600</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime V12.0.1/12.0.2 cannot connect to LDAPS:636 using TLSv1.2</title>
			<link>https://www.angioni.nl/2022/10/30/sametime-v12-0-1-12-0-2-cannot-connect-to-ldaps636-using-tlsv1-2/</link>
			<guid>https://www.angioni.nl/2022/10/30/sametime-v12-0-1-12-0-2-cannot-connect-to-ldaps636-using-tlsv1-2/</guid>
			<pubDate>Mon, 31 Oct 2022 04:49:42 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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]]]]>
			</content:encoded>
		</item>

		<item>
			<title>How to migrate older Sametime to HCL Sametime 12 Guide - Ales Lichtenberg</title>
			<link>https://alichtenberg.cz/how-to-migrate-older-sametime-to-hcl-sametime-12-guide/</link>
			<guid>https://alichtenberg.cz/how-to-migrate-older-sametime-to-hcl-sametime-12-guide/</guid>
			<pubDate>Tue, 27 Sep 2022 10:04:03 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Updating Sametime 12 to FP1. Not all customizations are kept</title>
			<link>https://www.robertoboccadoro.com/2022/07/21/updating-sametime-12-to-fp1-not-all-customizations-are-kept/</link>
			<guid>https://www.robertoboccadoro.com/2022/07/21/updating-sametime-12-to-fp1-not-all-customizations-are-kept/</guid>
			<pubDate>Fri, 22 Jul 2022 05:30:21 -0500</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>How to start Sametime automatically when the OS starts </title>
			<link>https://alichtenberg.cz/how-to-start-sametime-automatically-when-the-os-starts/</link>
			<guid>https://alichtenberg.cz/how-to-start-sametime-automatically-when-the-os-starts/</guid>
			<pubDate>Tue, 19 Jul 2022 03:23:35 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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?]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime Premium and HCL Sametime 12.0 FP1 is out</title>
			<link>https://alichtenberg.cz/hcl-sametime-premium-and-hcl-sametime-12-0-fp1-is-out/</link>
			<guid>https://alichtenberg.cz/hcl-sametime-premium-and-hcl-sametime-12-0-fp1-is-out/</guid>
			<pubDate>Fri, 15 Jul 2022 05:51:40 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>Extra “Sametime V12 MongoDB roles” in a highly secured Mongo environment</title>
			<link>https://www.angioni.nl/2022/07/09/extra-sametime-v12-mongodb-roles-in-a-highly-secured-mongo-environment/</link>
			<guid>https://www.angioni.nl/2022/07/09/extra-sametime-v12-mongodb-roles-in-a-highly-secured-mongo-environment/</guid>
			<pubDate>Mon, 11 Jul 2022 04:26:53 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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.
]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime Connect client 11.6 IF3 and Sametime 12.0 Standard Client Updated</title>
			<link>https://alichtenberg.cz/hcl-sametime-connect-client-11-6-if3-and-sametime-12-0-standard-client-updated/</link>
			<guid>https://alichtenberg.cz/hcl-sametime-connect-client-11-6-if3-and-sametime-12-0-standard-client-updated/</guid>
			<pubDate>Fri, 3 Jun 2022 01:55:43 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>My install guide “HCL Sametime 12.0 – Step by Step” is out</title>
			<link>https://alichtenberg.cz/my-install-guide-hcl-sametime-v12-0-step-by-step-is-out/</link>
			<guid>https://alichtenberg.cz/my-install-guide-hcl-sametime-v12-0-step-by-step-is-out/</guid>
			<pubDate>Fri, 20 May 2022 03:15:32 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime Premium and HCL Sametime 12.0 released </title>
			<link>https://alichtenberg.cz/hcl-sametime-premium-and-hcl-sametime-12-0-released/</link>
			<guid>https://alichtenberg.cz/hcl-sametime-premium-and-hcl-sametime-12-0-released/</guid>
			<pubDate>Thu, 28 Apr 2022 16:56:47 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[Sametime V12 Premium has just been released. Here is an overview with links to the necessary documents.

]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime 11.6 IF2 installation results in a non-working proxy when you don’t have a meeting server. </title>
			<link>https://www.angioni.nl/2022/03/24/sametime-11-6-if2-installation-results-in-a-non-working-proxy-when-you-dont-have-a-meeting-server/</link>
			<guid>https://www.angioni.nl/2022/03/24/sametime-11-6-if2-installation-results-in-a-non-working-proxy-when-you-dont-have-a-meeting-server/</guid>
			<pubDate>Fri, 25 Mar 2022 16:27:58 -0500</pubDate>
			<dc:creator>Remco Angioni</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime Proxy Server issue after upgrading to 11.6 IF2</title>
			<link>https://brandlrainer.info/2022/03/24/sametime-proxy-server-issue-after-upgrading-to-11-6-if2/</link>
			<guid>https://brandlrainer.info/2022/03/24/sametime-proxy-server-issue-after-upgrading-to-11-6-if2/</guid>
			<pubDate>Fri, 25 Mar 2022 02:26:29 -0500</pubDate>
			<dc:creator>Rainer Brandl</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime – RunFaster=1</title>
			<link>https://milanmatejic.wordpress.com/2022/03/03/hcl-sametime-runfaster1/</link>
			<guid>https://milanmatejic.wordpress.com/2022/03/03/hcl-sametime-runfaster1/</guid>
			<pubDate>Thu, 3 Mar 2022 02:50:09 -0600</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[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.
]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime – Setting the Community ID</title>
			<link>https://milanmatejic.wordpress.com/2021/12/06/hcl-sametime-setting-the-community-id/</link>
			<guid>https://milanmatejic.wordpress.com/2021/12/06/hcl-sametime-setting-the-community-id/</guid>
			<pubDate>Tue, 7 Dec 2021 02:40:38 -0600</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[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
]]>
			</content:encoded>
		</item>

		<item>
			<title>Disabling persistent chat in Sametime 11.x</title>
			<link>https://brandlrainer.info/2021/11/17/disabling-persistent-chat-in-sametime-11-x/</link>
			<guid>https://brandlrainer.info/2021/11/17/disabling-persistent-chat-in-sametime-11-x/</guid>
			<pubDate>Wed, 17 Nov 2021 06:55:15 -0600</pubDate>
			<dc:creator>Rainer Brandl</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>How I solved the problem Sametime integration with iNotes / Verse</title>
			<link>https://alichtenberg.cz/how-i-solved-the-problem-sametime-integration-with-inotes-verse/</link>
			<guid>https://alichtenberg.cz/how-i-solved-the-problem-sametime-integration-with-inotes-verse/</guid>
			<pubDate>Mon, 27 Sep 2021 03:42:45 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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.]]>
			</content:encoded>
		</item>

		<item>
			<title>Some interesting video sources of HCL Digital Solutions for Summer</title>
			<link>https://alichtenberg.cz/some-interesting-video-sources-of-hcl-digital-solutions-for-summer/</link>
			<guid>https://alichtenberg.cz/some-interesting-video-sources-of-hcl-digital-solutions-for-summer/</guid>
			<pubDate>Thu, 22 Jul 2021 08:34:50 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[HCL publishes short video tutorials on its YouTube channel, so I chose a few for the holiday time.
Here are a few links.]]>
			</content:encoded>
		</item>

		<item>
			<title>Updated Table of Client types that are connecting to a Sametime server (include Notes 12)</title>
			<link>https://alichtenberg.cz/updated-table-of-types-of-clients-connecting-to-the-sametime-server-include-notes-12/</link>
			<guid>https://alichtenberg.cz/updated-table-of-types-of-clients-connecting-to-the-sametime-server-include-notes-12/</guid>
			<pubDate>Wed, 16 Jun 2021 01:04:13 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[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]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime 11.6 and MongoDB 4.4 - how to enable mongo security correctly</title>
			<link>https://blog.msbiro.net/2021/06/hcl-sametime-116-mongodb-44-enable-security-mongo-key-replica-set.html</link>
			<guid>https://blog.msbiro.net/2021/06/hcl-sametime-116-mongodb-44-enable-security-mongo-key-replica-set.html</guid>
			<pubDate>Mon, 14 Jun 2021 01:53:36 -0500</pubDate>
			<dc:creator>Matteo Bisi</dc:creator>
			<content:encoded>
				<![CDATA[HCL Sametime 11.6 is supporting MongoDB 4.4 and this is the suggested version in case of new install.

One of the suggested steps during a Community setup is enable the Mongo security as described here , but the steps there are not enough, because 4.4 version in case of replica set , require also the creation and the use of a shared key to every Mongo server involved in the replica set, even if the replica set is composed by 1 node.]]>
			</content:encoded>
		</item>

		<item>
			<title>How to install correctly Sametime Community over Domino 11.0.1 FP3 on linux</title>
			<link>https://blog.msbiro.net/2021/06/how-install-sametime-community-116-correctly-over-domino-1101-fp3-on-linux.html</link>
			<guid>https://blog.msbiro.net/2021/06/how-install-sametime-community-116-correctly-over-domino-1101-fp3-on-linux.html</guid>
			<pubDate>Wed, 9 Jun 2021 09:44:28 -0500</pubDate>
			<dc:creator>Matteo Bisi</dc:creator>
			<content:encoded>
				<![CDATA[ During last weeks I'm working mostly on HCL Sametime preparing some meetings environments.

After the release of the 11.6 we have noted the server wasn't able to start if installed after FP3 of Domino 11.0.1.



The issue is similar to the Traveler issue , but we have fixed it in this way:]]>
			</content:encoded>
		</item>

		<item>
			<title>How to upgrade HCL Sametime Community and Proxy server 11.5 to 11.6</title>
			<link>https://alichtenberg.cz/how-to-upgrade-hcl-sametime-community-and-proxy-server-11-5-to-11-6/</link>
			<guid>https://alichtenberg.cz/how-to-upgrade-hcl-sametime-community-and-proxy-server-11-5-to-11-6/</guid>
			<pubDate>Tue, 1 Jun 2021 03:01:59 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[HCL Sametime server 11.6 was released. Official announcements will come soon.
Register for this official launch event on June 7

Although the upgrade from version 11.5 is the same as previous release, I created a simple Step by Step tutorial.]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime Meetings – Meeting Chat Issue</title>
			<link>https://milanmatejic.wordpress.com/2021/05/17/hcl-sametime-meetings-meeting-chat-issue/</link>
			<guid>https://milanmatejic.wordpress.com/2021/05/17/hcl-sametime-meetings-meeting-chat-issue/</guid>
			<pubDate>Mon, 17 May 2021 05:20:04 -0500</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[Recently I ran into the issue with HCL Sametime, the Chat was not working inside the Sametime Meetings. In this environment, the Sametime Meetings components are deployed on a single Docker host server. After a little bit of Troubleshooting and Log Analysis, I found the following error in the Sametime Proxy catalina logs: 
WARNING [https-jsse-nio-443-exec-8] com.ibm.rtc.stproxy.servlet.STProxyServlet.forward CLFRX0050E: User null – /stwebapi/chat/nway – <meeting_server_ip_address> is not authenticated.]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime Meetings Live Stream on YouTube</title>
			<link>https://alichtenberg.cz/sametime-meetings-live-stream-on-youtube/</link>
			<guid>https://alichtenberg.cz/sametime-meetings-live-stream-on-youtube/</guid>
			<pubDate>Tue, 4 May 2021 13:14:12 -0500</pubDate>
			<dc:creator>Ales Lichtenberg</dc:creator>
			<content:encoded>
				<![CDATA[Have you had the opportunity to try Live Stream from your Sametime Meeting meetings? Setup is not complicated.

I have prepared a short step by step manual.]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime Policies – Troubleshooting</title>
			<link>https://milanmatejic.wordpress.com/2021/04/19/hcl-sametime-policies-troubleshooting/</link>
			<guid>https://milanmatejic.wordpress.com/2021/04/19/hcl-sametime-policies-troubleshooting/</guid>
			<pubDate>Mon, 19 Apr 2021 03:08:18 -0500</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[I needed to set a new HCL Sametime policy just for a handful of users, so I have decided to do this via an explicit Sametime policy, assigned to the users via a new user group in LDAP user repository. This process is simple and very well documented, check out the official documentation if you have to do this
https://help.hcltechsw.com/sametime/11.5/admin/creating_new_policy.html
]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime Meetings 11.5 and LTPA version 2</title>
			<link>https://milanmatejic.wordpress.com/2021/04/01/hcl-sametime-meetings-11-5-and-ltpa-version-2/</link>
			<guid>https://milanmatejic.wordpress.com/2021/04/01/hcl-sametime-meetings-11-5-and-ltpa-version-2/</guid>
			<pubDate>Thu, 1 Apr 2021 03:39:00 -0500</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[As the LTPA Token version 2 is more secure than the LTPA Token version 1, it has become a new default for me. Lately I found out that the Sametime Meetings Server does not accept the LTPA Token v2 out of the box, more on that in the following. :-) ]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime Proxy 11.5IF1 issues with iNotes integration</title>
			<link>http://www.robertoboccadoro.com/2021/04/01/sametime-proxy-11-5if1-issues-with-inotes-integration/</link>
			<guid>http://www.robertoboccadoro.com/2021/04/01/sametime-proxy-11-5if1-issues-with-inotes-integration/</guid>
			<pubDate>Thu, 1 Apr 2021 03:37:27 -0500</pubDate>
			<dc:creator>Roberto Boccadoro</dc:creator>
			<content:encoded>
				<![CDATA[I updated the Sametime Proxy server 11.5 to IF1 for a customer, and the integration with iNotes broke.
When a user tried to start a chat with another user he received an error]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Sametime - Access User Directory over LDAPs</title>
			<link>https://milanmatejic.wordpress.com/2021/03/09/hcl-sametime-access-user-directory-over-ldaps/</link>
			<guid>https://milanmatejic.wordpress.com/2021/03/09/hcl-sametime-access-user-directory-over-ldaps/</guid>
			<pubDate>Tue, 9 Mar 2021 02:19:46 -0600</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[Configuring HCL Sametime Community Server to access the user directory over LDAPs is straightforward and usually fairly simple. In order to configure the access to Microsoft Active Directory for example, over LDAPs, you have to do the following...]]>
			</content:encoded>
		</item>

		<item>
			<title>Employee Experiences and the Digital Office</title>
			<link>https://www.prominic.net/2021/01/14/employee-experiences-and-the-digital-office/</link>
			<guid>https://www.prominic.net/2021/01/14/employee-experiences-and-the-digital-office/</guid>
			<pubDate>Thu, 14 Jan 2021 09:53:20 -0600</pubDate>
			<dc:creator>Prominic.NET</dc:creator>
			<content:encoded>
				<![CDATA[The Digital Office and Project Yuzu Offering a Vision of Cohesive Employee Experience
HCL is planning to deliver a complete tool for you to work with when it comes to your daily activities, be it e-mails, chats, meetings, etc. Project Yuzu is aiming to give users just that.
As of now, Project Yuzu is a concept for what will become a Digital Office solution.]]>
			</content:encoded>
		</item>

		<item>
			<title>HCL Traveler Database Migration – From DB2 to MS SQL – Made Easy</title>
			<link>https://milanmatejic.wordpress.com/2021/01/06/hcl-traveler-database-migration-from-db2-to-ms-sql-made-easy/</link>
			<guid>https://milanmatejic.wordpress.com/2021/01/06/hcl-traveler-database-migration-from-db2-to-ms-sql-made-easy/</guid>
			<pubDate>Thu, 7 Jan 2021 02:55:43 -0600</pubDate>
			<dc:creator>Milan Matejic</dc:creator>
			<content:encoded>
				<![CDATA[One of my customers wanted to migrate the HCL Traveler Database from IBM DB2 to Microsoft SQL. The customer is using Microsoft SQL for all other applications, which is set up with redundancy and high availability in mind, so this was a sensible choice, opposed to running a single instance of DB2. ]]>
			</content:encoded>
		</item>

		<item>
			<title>Sametime Meetings Premium internally without Google STUN servers</title>
			<link>http://blog.nashcom.de/nashcomblog.nsf/dx/sametime-meetings-premium-internally-without-google-stun-servers.htm</link>
			<guid>http://blog.nashcom.de/nashcomblog.nsf/dx/sametime-meetings-premium-internally-without-google-stun-servers.htm</guid>
			<pubDate>Mon, 28 Dec 2020 02:38:41 -0600</pubDate>
			<dc:creator>Daniel Nashed</dc:creator>
			<content:encoded>
				<![CDATA[We ran into this today. A customer is using ST Meetings Premium in their intranet and have no connection outside.
This isn't only a challenge for software installation and updates, but also causes issues with ST meetings if the Google STUN servers cannot be reached.

Side note: The update from Pre-Release to Premium by the way just took 1 hour for the meeting server, community server and proxy server all togehter!

A STUN server is actually a TURN server, taking care that server and client can talk to each other if a NAT environment is involved.
This can hit you even in an intranet depending on the network segmentation with IPv4 addressing.

In case NAT is involved you would need an internal TURN server. If no NAT is involved you still have to disable the Google STUN servers.]]>
			</content:encoded>
		</item>

		<item>
			<title>Troubleshooting steps when migrating from Sametime 11.5 Pre-Release to Premium</title>
			<link>https://debisschopk.wordpress.com/2020/12/15/troubleshooting-steps-when-migrating-from-sametime-11-5-pre-release-to-premium/</link>
			<guid>https://debisschopk.wordpress.com/2020/12/15/troubleshooting-steps-when-migrating-from-sametime-11-5-pre-release-to-premium/</guid>
			<pubDate>Tue, 15 Dec 2020 08:39:44 -0600</pubDate>
			<dc:creator>Kris de Bisschop</dc:creator>
			<content:encoded>
				<![CDATA[Hello all, Right after the release of Sametime 11.5 Premium, I was eager to upgrade our Sametime environment from the Pre-Release environment to the Premium Release. At first sight it went very well to do the upgrades but after some testing I realized there were some issues. For instance, when we loaded the Sametime Web client, the client kept on loading without showing any information.
]]>
			</content:encoded>
		</item>

		<item>
			<title>Get a A+ security rating on your Sametime Meeting Server </title>
			<link>https://dominopeople.ie/get-a-a-security-rating-on-your-sametime-meeting-server/</link>
			<guid>https://dominopeople.ie/get-a-a-security-rating-on-your-sametime-meeting-server/</guid>
			<pubDate>Sat, 5 Dec 2020 08:02:02 -0600</pubDate>
			<dc:creator>Cormac McCarthy</dc:creator>
			<content:encoded>
				<![CDATA[This blog shows how to achieve an A+ security rating for your Sametime 11.5 Premium Meetings server on the excellent Qualsys SSL Labs test

Firstly, please if you want an end user demo of Sametime Meetings then look here for more information.

Again Ales Lichtenberg’s site is where you want to go for a guide on setting up Meetings.]]>
			</content:encoded>
		</item>

	</channel>
</rss>