Hello. I’m going to update the client of my company to notes 8.01 (about 1200). I’ve see after upgrade the Sametime lost the info (the server is not stored in names anymore) and we must re enter the sametime name server.
In the desktop policy we have some setting but is working only for basic client and older.
In KB DB i’ve find the eclipse sametime configuration is stored in community-config.xml.
I encountered this exact problem a couple of months ago and reported it to IBM Lotus support. They could could not provide a solution but agreed to keep the PMR open until they came up with the answer. It’s been passed onto their developers.
With about 2000 users and one Notes admin to manage the upgrade, this issue is a show stopper for us when it comes to rolling out 8.0.1. I’d also be concerned about other nagging problems, like disappearing and wandering tool-bars, inconsistent presence awareness in the in-box and occasional delayed delivery of mail to the Notes client, none of which I’ve been able to find resolutions for.
Subject: plugin_customization.ini-auto log in & SSO
Hi Matteo
I tried what you suggested hoping hat “Remember password”, “Automatically log in”, and “Use Domino SSO if available” in ST Server community setting will be checked. However, after upgrade, they weren’t enabled. ST server name worked fine. (Btw…I wasn’t sure about “Remember password” & “Automatically log in”, but I was hoping to get at least “Use Domino SSO if available” checked)
We have developed a crude workaround to the is problem. Prior to the Notes 8 upgrade, we copy a skeleton community-config.xml file to the workstation into \Lotus\Notes\Data\workspace.metadata.plugins\com.ibm.collaboration.realtime.community.sametime.
The contents of the community-config.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<community alwaysEditActiveText="true" alwaysEditAwayText="true" alwaysEditDndText="true" authServerUrl="" authType="" autoAwayTimeout="10" availWhenUnlocked="true" email="" host="sametime.ibm.com" iconPath="" id=st555555555" "isAutoActiveEnabled="true" isAutoAwayEnabled="true" isAutoAwayTimeoutEnabled="true" keepAliveInterval="60" loginAtStartup="true" loginByToken="true" name="" partnerIdType="" port="1533" providerId="Sametime" savePassword="true" sendKeepAlive="true" useAuthServer="false" useCustomTextForAutoAway="false" useGlobalConnSettings="true" useOsPass="false" userid="" username="">
<connection connectionType="direct" proxyHost="" proxyPassword="" proxyPort="" proxyResolvesLocally="false" proxyUserName="" tokenHostUrl="" transport=""/>
<statusTexts>
<activeText>I am available</activeText>
<awayText>I am away from my computer now</awayText>
<inMtgText>I am in a meeting</inMtgText>
<dndText>Please do not disturb me</dndText>
<idleText>I am away from my computer now</idleText>
<lockText>I am away from my computer now</lockText>
</statusTexts>
</community>
The host field is modified to match our Sametime server name. The id field appears to need something in it otherwise the embedded client won’t start. Not sure of the consquences of having the id field be identical on multiple client’s community-config.xml file. Limited testing shows that it is not a factor. The userid and username fields are set to nothing and are populated by the client after the first login.
We have found that the users have to manually initiate the first Sametime login, but after that, it is automatic each time Notes is started.