Logged into Sametime on multiple devices

I have a desktop and a couple of laptops running 12.0.2 in different rooms andI regularly switch between them. We recently upgraded our Sametime server to Sametime 11.6. Prior to the upgrade, if I logged into Sametime on one device it would automatically log me out of any other device that I had been logged onto.

Since the upgrade, I am still showing as logged into Sametime on all of the devices. Is there a setting that handles the automatic log out on one device when I log in on another?

Thx in advance.

It's not a bug, but a feature. ;-)

Why would you want to be logged out of the other Sametime clients, when all messages appear everywhere?

It's all about perspective... one person can see it as a bug and another as a feature. If all IMs appeared on all machines, I would see the value in that.

My issue is that messages sent from one device don't appear on all devices. I have a desktop beside a laptop... logged into Sametime on both. If I send an IM from my desktop to another User, it is not displayed to my laptop and vice versa. It is like I'm maintaining separate IM threads from each machine.

Maybe it will just take getting used to, but for now....

Hi Paul,

For Sametime 11.x, presuming persistence is working properly, "messages sent from one device would appear on all devices" that are of course logged on. What you explain is not the behavior that we would anticipate. It may be best to open a support case so that we may help look around.

A quick video to help check and make sure persistence is working:

HCL Sametime - Persistence Chat Check - Bing video

Keith

Hi Paul,

Thanks again, we do not offer an upgrade path to Sametime 11 from older Sametime versions (Sametime 11 also requires a 64 bit Domino server). Persistence is how Sametime 11 is designed to work, with Mongo, so as you imply persistence is not in use, there is a possibility that we are not configured as intended. We can sort this out with a support case best.

Best Regards, Keith Kopanski

Senior Product Support Engineer, HCL Sametime

Thx for yours, Keith.

I should point out that we have only just upgraded our Sametime Server to 11.6.

I watched the video regarding persistence, but that is not exactly the issue I am referring to.

We have never used persistence, as it is defined in the video. We can of course save a transcript of a Chat, but each time we open a chat with the same person, we are starting a new chat.

What we are now finding with our Notes 12.0.2 Clients and Sametime 11.6 Server is:

  1. Previously, I was only able to log into Sametime on one device at a time. Logging in on a 2nd device would result in me being logged out of the 1st device. I would be challenged on the 1st device to log back into Sametime.
  2. Now I'm logged into Sametime on all of my devices... my desktop and laptop as Paul.
  3. Paul sends an IM to Mario from my desktop
  4. Paul sends an IM to Mario from my laptop
  5. Mario replies to Paul's IM and it only appears on the last device Paul sent from... his laptop... his reply does not appear on Paul's desktop
  6. Mario sees all of the IMs sent from both my desktop and Laptop

The bottom line is Paul's devices have separate IM threads... only Mario sees all of the IMs from both my devices, and Mario's replies are only sent to the last device that the IM was sent from.

It's entirely possible that this is the intended funtionality. Plse let me know if that makes sense to create a support case.

Paul

Check the Sametime.ini file.

In the Config section, set the following flag to activate single client login mode:

VP_ONLY_SINGLE_LOGIN_ALLOWED=1

If the flag is set to 1 the server works in the single login allowed mode. When a new client login request is received, all the previous logins are disconnected. Only one client type connection per computer is allowed at one time (related to client types, not users).

In you case please check if its value is 0. That may be cause of this behaviour.

Another parameter to look for

VPS_EXCLUDED_LOGIN_TYPES=clienttype1, clienttype2

specifies which client types are not considered logins when the server checks whether to accept or disconnect clients.

URL for ref:

https://help.hcltechsw.com/sametime/12/admin/st_adm_comm_singlelogintype_t.html?hl=multiple

Thx for yours, Rahul.

Are you referring to a Sametime.ini nfile on the Server, which I assume would apply to all Users, or an individual User's PC?

Thx in advance

Its for server and applicable to all Users

Making that Change in the Sametime INI file on the server fixed the problem.

Thx to all for your input.