So, i have filled our 55 users database today, created groups and assigned users to groups. It looks fine (especially nesting feature in Exodus). And after testing it for a while we’‘ve came to a problem. We’'ve installed latest Daily Build (2005-02-22), the problem is still there, though it act some what different now.
You can rename users in your roster in Exodus (or other clients). It’'s not a problem. But if this user is removed from this group (or moved to another). Roster do not updates correctly. Ex:
I have user in database (i mean in embedded):
name: John Doe
i have assigned it to Group1
Now i want to move it to Group2, it’'s simple, i just remove in Group1 and add in Group2 in Admin Console.
- same user. But i have renamed it in my client’'s roster to John Jork
Now i want to move it to Group2, so i remove jdoe user in Group1 (in Admin Console), and i assign jdoe to Group2. Now it mess up. John Jork user appears in Group2 and stays in Group1. You can delete it in client roster in Group1 only when there is no such user in any group in Admin Console. After deleting it in client’‘s roster, you assign it to any group and it appears in the right place but with the original John Doe name. Renaming is lost, though it’‘s not a vital lost:) But you have play a lot with roster and AC to move user in client roster. We have 55 employes now, and all of them could try to rename users in rosters. And if one user is moving to another department… well:) We’'ll have to play with every client. And if 10 users are moving. Not convinient.
We have found one solution, not good one, but better. You can delete user in database, so it for sure dissapears in all rosters and groups (even renamed). And then you can add this user again and assign to Group2, and it will appear correctly, with John Doe name of course, so renaming is lost anyway. But you dont have to play with every Exodus, just with AC.
Pff… It looks not so horrible at home though:) We were just planing to start installing Exodus clients tomorrow, and have found this problem accidentically, heh. I think we will start using it, though some solution will be appreciated:)