I've seen this issue discussed in a couple of forums and folks on the Sametime Support team are getting a lot of calls on this. A change was made in Sametime 7.5.1 that is catching some Sametime administrators by surprise, and is causing them confusion.
Sametime 7.5.1 offers a new policy setting on the server: "Must set this community as the default community." If this policy is enabled on the server, it will force users to have this Sametime server as their default Sametime server. This policy is enabled by default. This is definitely a good feature that admins have asked for (as you can force users to connect to one server in your community, over another), but it is something worth knowing ahead of time, to prevent confusion.
Let me give you an example. You have a Sametime 6.5.1 server running and you have Sametime 7.5 clients out there that are configured to connect to the Sametime 6.5.1 server first (default community). You add a Sametime 7.5.1 server as a second community and suddenly users can't log in; they get an error.
More details, along with a solution, were just published in this technote (#1259456).
Jennifer Kelley | 11 May 2007 06:19:00 AM ET | | Comments (4)
