Interesting Notes 6.5.1 dilemma with integrated Sametime
Tags :Sametime
So the customer decides to upgrade to the
integrated client in Notes 6.5.1 with the free licensing entitlement. They
want everyone to have chat, and that is a great way for Lotus to tease
enterprises into Sametime. But, they also want all the Sametime Connect
users to upgrade to the downloaded 6.5.1 client for those they pay for
to get all the new functionality and to remove AOL. Here is the catch.
They set the Sametime 6.5.1 server to reject all the older Sametime
Connect client versions. Works great! Until the integrated
client logs in. How would the Notes 6.5.1 integrated Sametime client
present itself to the server? Well of course as Sametime 3, who would
ever think it would be 6.5.1 ? So basically you cannot block the
older Connect clients from logging in AND use the integrated client.
Let's visit technote #1168810
| Problem |
| You are running a Notes 6.5.1
client and accessing a Lotus Instant Messaging (Sametime) server to take
advantage of the Notes client instant messaging features. When you
log into the Instant Messaging server, the Sametime log (stlog.nsf) shows
that a release 3.0 client logged in, instead of a 6.5.1 client. This
is preventing you from using the new security feature in release 6.5.1
(configured via INI parameters, see technote #1145812Link
for details) which allows you to block older Sametime client versions from
logging into the Sametime server.
|
| Content |
| This issue has been reported
to Lotus software Quality Engineering. To work around this issue,
you must set the Sametime server to allow 3.0 and higher clients, or not
use Notes clients to access the Instant Messaging server.
Note: This issue does not apply to Domino Web Access (DWA). The architecture of DWA's Sametime integration is different from Notes instant messaging. |
blog comments powered by Disqus
On Monday, May 24th, 2004 by Chris Miller
