I find the way the association is working, not very clear.
Generaly, in NDS, administrators can see association in 2 ways. Lets take groups as an exemple.
If UserA.Acme is member of Group_GWFormativ.Acme, I will see him in “Memberlist” of .Group_GWFormativ.Acme and I will see Group_GWFormativ.Acme in “Group membership” of UserA.Acme, making it clear and easy to manipulate group assignment.
With the Formativ association process, we just get a reply saying “association was made”, and we could see from the client side what configuration we are linked to, but I can’t review this association from NWAdmin.
Currently we are etsting, and some users are associated via OU, groups, or their relative user object.
Unless we start the client, it makes it very difficult to see what is the current valid association.
I should be able to do 2 things:
1/ See who/what is currently associated to a configuration.
2/ See what configuration is associated to an object (requires a new TAB under this object).
- You must be logged in to reply to this topic.