Hello HCL Product Management & Dev's,
We do have currently at least X customers with in sum more than ***k users who would really appreciate to have NSL (Notes Shared Login) running device/computer-independent to be able to use it on more than one computer with the same .bin & .id file. Yes, those customers need that - better today as tomorrow!
Technically all VDI/Citrix customers with NSL enabled are suffering a lot when they deploy a new Citrix Farm or VDI clients based on a new or updated Windows, because NSL is connected to the old device (in the .bin file) and will not work on the new system.
This happens currently with a lot of customers when they are updating their Windows Server 2016 environments to Windows Server 2019 or even 2022. There are customers who has a mixed environments too, which makes it even more harder to maintain Notes on, because of this IMPORTANT and MISSING feature.
If you would allow us to use NFL machine/computer-independent, that would make MANY customers & SO MANY MORE users happy.
With best regards
Christoph Adler (panagenda)
Vladislav Tatarincev (CYONE)
We agree that this would be a great thing to be able to do, however there are a bunch of reasons that make this unachievable for us.
Thomas Hampel's blog post may help some people get past the first part of this idea. https://blog.thomashampel.com/blog/tomcat2000.nsf/dx/shared-logon-failed-with-this-id-after-setting-enableusingappdataforroaming1.htm
Some of the technology used to create the .bin files, in part, resides in Windows. Thus if you are changing/upgrading to a different version of Windows, so of that technology also changes with the change/upgrade. Therefore the .bin file will most probably not work anymore in the new environment and will need to be recreated. As we have no control over what Microsoft do in Windows, we are unable to guarantee that .bin files will persist from version to version.
Sadly, marking this as "No plans to implement".
Yes, most of my customers (all of those who use "SSO") still use Common Login (the one with the windows service), because this works - most of the time, although it is unsupported for current OSs.
They hesitate to go to Notes 12 where this feature is not available anymore...
Same here! I have several customer situations where they facing this issue.
In fact, some customers think to disable NSL and force all users to use a password until all users moved to the new environment before they activate NSL in the new environment again. Sad but true.
greets
Marc Thomas (panagenda)