• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 2740 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Managed Unit sort order

Lee Andrews
over 5 years ago

I have created a MU which displays selected OUs but they are not in any soprt order making it awkward for the SD to locate the OU they want.  I can't see any parameters of a MU to control teh sort order.  Is there a way to control the order in which they are displayed?  You can sort them only in the right hand pane not in the Tree.  

Parents
  • 0 over 5 years ago

    A test Managed Unit in my lab displayed all Organizational Units alphabetically by name. What are you seeing in your environment?

    LDAP doesn't offer the option to change Sort Order, and Dynamic Groups and Managed Units in Active Roles are basically just LDAP calls. There isn't currently an option to change the default sort order which is displayed in an Active Roles client.

  • 0 over 5 years ago in reply to Terrance.Crombie

    The order is completely random - I have tagged each OU with a value in the street attribute and then used a membership rule to include OUs using an LDAP query

    (&(objectCategory=organizationalUnit)(street=DisplayOUInMU))

    I then have a policy so that if someone creates a new child OU the street attribute is set to DisplayOUInMU and the OU is then displayed in the MU.  If I had included the OUs individually then it would require an additional step to add the OU to the MU, i.e. adding another membership rule so I was looking for an automated way of doing as much as possible.  

    I agree the LDAP query cannot be sorted but ARS is processing this and it seems like an option should be there to control the sort order.

Reply
  • 0 over 5 years ago in reply to Terrance.Crombie

    The order is completely random - I have tagged each OU with a value in the street attribute and then used a membership rule to include OUs using an LDAP query

    (&(objectCategory=organizationalUnit)(street=DisplayOUInMU))

    I then have a policy so that if someone creates a new child OU the street attribute is set to DisplayOUInMU and the OU is then displayed in the MU.  If I had included the OUs individually then it would require an additional step to add the OU to the MU, i.e. adding another membership rule so I was looking for an automated way of doing as much as possible.  

    I agree the LDAP query cannot be sorted but ARS is processing this and it seems like an option should be there to control the sort order.

Children
No Data