For weeks now we are having calls from users complaining about empty or half empty public Sametime groups. After a server reboot the issue will be gone for a while, but it comes back. We have the same behaviour in our proxy server
We have Sametime 8.5.2IFR1 deployed and we are using Domino LDAP with nested groups. I started of my search in the group structure, as we changed the group naming and nesting level a couple of weeks back (with some other unwanted consequences)
But I did not manage to find it. Until I found a forum post in the Sametime forum and the solution posted by Ben Timms.
The problem occurs in Sametime , where the “Base DN for searching people” is different than the “Base DN for searching groups” in the LDAP configuration. If groupA contains groupB1 and groupB2 then a client adding groupA will not get awareness on all the members.
A common scenario where this issue will occur is as follows:
1. In the directory: GroupA contains groupB1 and groupB2. Each group contains a different set of people (at least one person in each group).
2. Set up ST server 8.5.2 IFR1 LDAP. The base DN for searching people must be different than the base DN for searching groups.
3. From Connect client (or a test client) add groupA. Request the group contents of group A, and see that it displays a partial list.
This problem has been identified as a Lotus Sametime 8.5.2 IFR1 Community Server bug under SPR #RBLE8RPFEB and APAR LO67252.
This issue is only occurring in Sametime 8.5.2 IFR1 and has been fixed in Hotfix #RBLE-8RPFNQ.
All references to this issue are non-existing and the link Heather Currie references to in the same forum post does not exist anymore. I have seen this too many times that technotes dissapear, I still wonder why. And why is a fix like this not public in fix central? It is a pretty common one to happen for most customers.
If you are facing the issue then log a call with IBM Technical Support and request for the Hotfix #RBLE-8RPFNQ. I have opened a call, I hope I get it quickly (if it still exists)