Filed under: General, IBM Software, Notes/Domino, Sametime, Technical Support, Technology
The certificates which were used to sign the Sametime Applets (Meeting Room client, Sametime Java Connect, Directory Applet, Sametime Links), will expire on May 18th this year. IBM has been working to resign these applets as quickly as possible. All of the applets from Sametime 7.0 to 8.0.2 have been resigned with the updated certificate. If you do not update the applet files on the server, users will see a Java security prompt asking them to approve the execution of the applet. However, users will still be able to use the applet.
Here’s the best news though. You do not need to open a support ticket with IBM to download the updated applets. They are available on IBM Fix Central for immediate download! For installation instruction and download information, see IBM Technote 1390778.
The Domino Applets will also expire on May 18th. Information on downloading the Domino Applets is available in IBM Technote 1381298.
Filed under: Sametime, Technical Support, Technology
There are a couple updates to this cross chat issue. First, if you have already downloaded this cross-chat fix you should download it again and redeploy it in your environment. A small issue around business cards behavior was discovered and it has been corrected.
We are also an update for the Sametime Standard 8.0.2 client. This optional update contains additional diagnostic prints and defensive code to prevent the cross-chat issue from occurring.
IBM Technote: http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21375473
Filed under: Sametime, Technical Support, Technology
Anyone out there who is running Sametime Standard Connect 8.0.1 or Notes 8.0.2, read on and pay attention. It looks like one of the quarky bugs has finally resurfaced. The infamous cross chat bug.
Cross chat is when one user sends a message to another user and the message instead reaches an unintended recipient. Kudos to the IBM development team for quickly isolating the problem and correcting it. All Notes Standard 8.0.2 Clients running below the CCH3 level will need to be patched to CCH3 or higher. Any organization which is running Sametime Standard 8.0.1 will need to apply a hotfix to the clients. This can be done using an update site.
Both of these hotfix packages are available on IBM Fix Central. Full details of the problem can be found in the following technote: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21375473
Filed under: Sametime, Technical Support, Technology
In 7.5.1 and above, a new feature was added to manage the size of the various meeting diagnostics files. This registry setting can be used to split C++ diagnostics into module specific files, and they will respect the size limit specified.
MaxLogSizeMb=dword:00000400
ModuleLogEnabled=dword:00000001
Enabled in [HKEY_LOCAL_MACHINESOFTWARELotusSametimeMeetingServerDiagnostics]
The example above enables the splitting of the modules, and will limit them to 1024mb each as defined by the MaxLogSizeMb parameter. When the 1024mb limit is reached, the current file is renamed/backed up, and a new one created. The server will then keep the current and the immediate prior file. Files older than that will be removed.
The summary.diag file can also be disabled altogether by setting the “SummaryLogEnabled” to 0. However this is not recommended as it does help with troubleshooting issues.
Filed under: Sametime, Technical Support, Technology
Recently our support center has received a flurry of calls regarding performance of Sametime Meetings. After some in-depth investigations by our development team and network engineer, we have found something can really boost performance. Windows 2003 SP1 introduced the scalable network pack. Sound impressive doesn’t it? Actually this feature can reduce the performance of the network to a point where network apps will run slower and meetings may sporatically disconnect. We have found that after disabling this feature, network app performance improves dramatically.
So how do you disable it?
To Disable TCP Chimney, navigate to the following registry key and set the value to 0. (Note: You have to reboot the server after this registry change)
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters]
”EnableTCPChimney”=dword:00000000
If that does help with the situation, you could also try disabling the following offloading keys under the above registry hive to disable the RSS features.
”EnableTCPA”= dword:00000000
”EnableRSS”= dword:00000000
Posted on May 14th, 2009 by Andy Yiu
No Comments »