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!!!

Domino upgrade to V14, a consideration  

By Roberto Boccadoro | 12/22/23 9:36 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

I was asked by a friend, who is mostly a developer and not a Domino Admin about upgrading his dev server from V12 to V14. He told me that he uninstalled V12 and installed V14 but then the Domino server would start in setup mode. The reason in simple, but if you were not part of the V14 beta program you may have missed it.

Upgrading Notes client to V12 on Terminal Server  

By Roberto Boccadoro | 9/13/23 12:07 PM | Infrastructure - Notes / Domino | Added by Oliver Busse

I worked with my friend and lady geek, Marianna Tomasatti, at a customer to perform an upgrade of the Notes client to V12.0.2 FP1 on Terminal Server Windows 2019 Datacenter (multi-user installation) because the Notes clients had some issues.

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.

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

Do you have any suggestions for OpenNTF ?   

By Roberto Boccadoro | 10/28/22 12:23 PM | Business - Events / People | Added by Oliver Busse

AS probably you know OpenNTF has a Discord server, that everyone can join, where there are several “channels” (I know that the term is not correct) in which people can talk about specific topics. We have just added one, “#suggestion-box” where everyone is encouraged to go if they have any idea on what OpenNTF should do.

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.

The OpenNTF Discord Server  

By Roberto Boccadoro | 6/16/22 8:16 AM | Business - Events / People | Added by Matteo Bisi

A few months ago, OpenNTF started testing the waters of moving our Slack community over to Discord. The immediate impetus for this was the message-history limitation of our Slack account: on the free tier, we were losing old messages, but upgrading a community of our size to a paid tier would be cost-prohibitive. Once we started looking into using Discord, we found that it offered much more for us than just avoiding history loss. Discord quickly proved itself a much-better match for our community, with better community controls, better voice/video chat with screen sharing, and just generally a more community-focused approach. Joining Since it’s gone so smoothly in a “soft launch”, we think it’s ready to invite everyone more openly. To join our Discord community, visit: https://discord.gg/jmRHpDRnH4

Have questions ? We have answers!  

By Roberto Boccadoro | 10/27/21 2:05 PM | Business - Events / People | Added by Oliver Busse

Got a question about Domino, Notes, Sametime or Connections? Come ask the gurus! We have gathered the brightest minds to take your questions about development and administration. You can ask ahead of time at https://openntf.org/Internal/guru.nsf or ask live in our webinar.

“Official answers”   

By Roberto Boccadoro | 7/8/21 9:52 AM | Business - Events / People | Added by Oliver Busse

I often get a request from a customer if I can give them an “official answer” say, to a request if a feature is available or not. For example recently I had such a request whether something that was doable in iNotes was doable also in Verse.

HCL Domino on Docker Whitepaper  

By Roberto Boccadoro | 7/6/21 10:12 AM | Infrastructure - Notes / Domino | Added by Oliver Busse

Together with Shrikant Jamkhandi and Aniket Salve, both from HCL, I co-authored a whitepaper that covers the installation of the HCL Domino Docker image.

Domino Online Meeting Integration   

By Roberto Boccadoro | 5/4/21 1:16 PM | Infrastructure - Notes / Domino | Added by Oliver Busse

Now that this has been announced publicly at NCUG, btw congrats Hogne for setting up a very useful event, I can talk about DOMI. Me and other Ambassadors have tested it in the last weeks but we were under NDA so we couldn’t share our thoughts.

Follow up to the OpenNTF webinar on Domino administration best practices  

By Roberto Boccadoro | 5/4/21 1:15 PM | Infrastructure - Notes / Domino | Added by Oliver Busse

During the webinar me and Heather ran out of time so we did not have time to talk about all the points that are highlighted in the slides. Here are some details on those point that we did not cover