There are two ways to access IBM Sametime Meetings – with a browser or the rich client. Using the browser client has some limitations, but most of them are not that important.
Have a look at “Meeting features in Connect versus web clients” for more details.
What you should consider is the quality when documents are converted for online presentations. Depending on the client you use, the OS and the software you have installed, documents are either converted locally or by the Sametime conversion server.
There are only a few document types (odp, ppt and pptx) which are converted locally (and only if you use the rich client): “What document types are locally/client converted when adding them into a meeting room?”
When uploading documents via the browser client, document conversion always happens on the server and contrary to the documentation this is not a “High quality conversion & presentation of PDF, ODF and Microsoft Office files” at all.
The quality can be really poor and sometime even useless – and if I say quality, I do not mean typical conversion artefacts, I mean black boxes in PDFs, where you should see images, mirrored text in Powerpoints and so on.
Apparently, the Stellent converter is not as powerful as it should be.
At least for Powerpoints you should always use the rich client to upload them. The qualitiy is almost 1:1 (of course, without animation).
Sametime meeting rooms are usually not used so much and so it might happen that users forget the password of their meeting rooms.
But how to recover a lost meeting room password?
The answer is simple. You can’t!
But before you panic – you can easily set a new password in the appropriate room properties without knowing the old one. The disadvantage is that you have to inform all meeting participant about the password change and give them the new one.
-> How can the owner of a Sametime 8.5 meeting room recover a lost or forgotten password?
-> LO59908: NEED A WAY FOR AN IBM SAMETIME MEETING ROOM OWNER TO RECOVER THE PASSWORD SET ON A ROOM IF THAT PASSWORD WAS LOST.
When using IBM Sametime with all or some of its WebSphere components on Microsoft Windows it makes sense to create Windows services for all the Node Agents, WebSphere Application and Proxy Servers. If you are really good, you even create dependencies between the particular components to make sure that the services are started in a appropriate sequence.
There is a lot of documentation about creating the services and it’s quite simple:
Using these services and dependencies works like a charm, but under certain circumstances they might be the cause of some problems.
Therefore, here are some (maybe helpful) tips and experiences:
Only a few days after discovering a cross-site scripting vulnerability in IBM Sametime, a fix is available in IBM Fix Central.
The security issue may affect stand-alone, embedded and web clients, but not mobile and basic clients and not Sametime version 8.0.1, 8.0.0 or 7.5.1.
More details and the appropriate fix can be found here: Fix available for potential security vulnerability in IBM Sametime.