Sametime 8.5.1 8.5.1.1 is cumulative of any previously released fixes for 8.5.1 Direct Link to 8.5.1.1 download on Fix Central (Login Required)
Sametime 8.5.1 8.5.1.1 is cumulative of any previously released fixes for 8.5.1 Direct Link to 8.5.1.1 download on Fix Central (Login Required)
I guess the delay was less
Sametime and what happened to the nice file names? we seem to be back to the part numbers as file names
There is a nice break out of the part numbers and the files they represent here (thanks Dennis)
If you are running the Sametime
This issue was first reported to Sametime Support on October 21, 2009. Sametime support established the root cause to be a recent change to Hostnames Google used for their incoming connection server IP’s (talkz.l.google.com). The following is one example of the change: Remote Host IP = 209.85.162.129″ HostName = el-out-f129.google.com”. was changed to Remote Host IP = 209.85.162.129″ HostName = el-out-f129.1e100.net”. This change broke the handshake sequence that Sametime Gateway follows to establish the XMPP connection and impacts all sametime gateway versions. A fix has been developed for Sametime Gateway Gateway version 8.0.2 and can be downloaded from Fix Central. Sametime Support strongly recommends upgrading to Sametime Gateway 8.0.2 HF3 before applying this fix.
You can download Hot Fix 3 for version 8.0.2 from Fix Central and there is a fix in test for 8.0.1. If you are on an earlier version of the gateway it looks like there is an upgrade in your future.
HF1 2. Upgrading WAS 3. Manually copying over new .Jar files 4. Installing SIP Container fixes 5. Deploying new Gateway EAR and WAR Files The PDF also contains a list of knows OCS issues Sametime Gateway 8.0.2 Hot-Fix One (HF1) is now available Happy Upgrading
My good friend Andy
Sametime quickfind, Notes Inbox awareness, and many other features can generate a substantial number of name resolutions requests. These requests can severely impact performance and capacity in a production environment. Join us on Wednesday, June 10, 2009, at 10:00 a.m. EDT (14:00 GMT) in this IBM Webcast as we talk about several recommendations and solutions you can implement today to reduce impact of name lookups on your Sametime infrastructure.
Webcast: Sametime resolve, Notes IM, and LDAP performance considerations – 10 June 2009
One of the items on my radar right now is Sametime Advanced, not having the resources to install it right now, I am playing with it at bleedyellow.com. After a Brief chat with Chris Miller and Chris Whisonant it was determined that if I simply un-check the features which lacked the correct pre-requisite the plugins would install fine in Notes 8.0.1 as pictured here
Well this worked, but Sametime Advanced automatically attaches itself to the Primary Community in Sametime, and I have yet to find a way to have it use one of the other defined communities, so for now I am back to using Sametime Advanced with Sametime Connect 8.0.. This highlights once again a long running problem in Notes 8, simply that the version of Sametime even though it is 8.0, is not identical to the Sametime 8.0 Connect client, why is that? Shouldn’t the same version of Sametime simply run as a plugin with in Lotus Notes. In order for Sametime to be properly embedded in Notes 8.0 and forward, Sametime needs to be decoupled from Notes, and truly be a plug in so that organizations can run the version of Sametime they have standardized on not what it embedded in the product, and that upgrades can be done to Sametime without a Notes upgrade and vice versa. If you want the Sametime Advanced Plug-ins for BleedYellow you can find all the details here
Adam
If you are using the Sametime Gateway and connected to Yahoo make sure you read Technote