« Live Free or Die Trying 2004 | Main| A fairly honest review of Lotus Sametime, WEBEX and Microsoft Placeware. »

A nice gotcha for people upgrading to Sametime 6.5.1while still keeping some earlier sametime server versions around.

Category
It's very possible, if you install a Sametime 6.5.1 server, and you have a Sametime 2.x, 3.x server lying around you won't get any awareness with the Sametime 6.5.1. In Sametime 6.5.1 a new Sametime.ini parameter was added "VP_SECURITY_LEVEL" which can limit the level of client that accesses the server, sadly this same parameter also limits the level of the server, so the default value of "25" needs to be changed to "0" if you want to get awareness across your old and new servers.

This technote "Sametime 6.5.1: Errors Occur when Sametime 6.5.1 Interacts with Sametime 2.x/3.x Server with Critical Fix 1 Applied" explains in a little more detail the situation. Hopefully this will save some of you some time trying to resolve awareness issues.

Posted by Carl Tyler On 06/07/2004 | | del.icio.us  Technorati  Digg This 

Comments

Gravatar Image1 - VP_SECURITY_LEVEL is new to CF1 for Sametime versions before 6.5.1.

The Sametime 3.x servers don't recognize "6.5.1" as a valid version number, so if you set VP_SECURITY_LEVEL to "25" a 6.5.1 client can't connect.

I don't remember the number, but there's a technote about copying the stsecurity.exe from a 6.5.1 server to a 3.x server to fix it.

Posted by Scott At 10:44:57 AM On 06/07/2004 | - Website - |


Gravatar Image2 - Since 6.5.1 presents itself at Sametime 3 it really defeats the purpose. Add in that the Java Connect and intergrated piece for DWA is architected entirely different also.

Posted by Chris Miller At 01:37:42 PM On 06/07/2004 | - Website - |


Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::rolleyes:;-)