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.

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?

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

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.