locked
Sharepoint - Lookup in AD group RRS feed

  • Question

  • Hello,

    In a sharepoint list we have a user lookup field, which we would like to lookup a user in a AD group (without adding all the users to the site)

    For example if we have added a group called ACL_XX_Test group (which contains a lot of AD users) to the site and we have user lookup field in a sharepoint list where we would like to lookup for example the user Peter Larsson which it's in the list ACL_XX_TEST group - we enter the ID of Peter Larsson (PL) in user lookup field - but Sharepoint can't find the user - only the ACL group.  Is there some way that we can lookup a user in a group...?

    Tx

     

     

    Monday, November 29, 2010 9:58 AM

Answers

  • There's another way to oapproach this - if you can limit the whole site collection user population to a given Active Directory OU and subcontainers.  There's a settale property (need to be on SP2!) that lets you lock the People Picker to a given strucuture

    stsadm -o setsiteuseraccountdirectorypath -path "OU=Employees,DC=Company,DC=com" –url http://server/sites/teamsite 
    

    In case your admin accounts live elsewhere in AD, there's a parallel strucuture to allow those accoutj sot live there:

    stsadm -o setproperty -url http://server/sites/teamsite -pn peoplepicker-serviceaccountdirectorypaths -pv " OU=MOSS-Accounts,DC=Company,DC=com 
    

     

    Good luck!

    Chris McNulty MCSE/MCTS/MSA/MVTS http://www.kma-llc.net | blog http://blogs.kma-llc.net/microknowledge | twitter @cmcnulty2000
    • Marked as answer by Peng Lei Thursday, December 9, 2010 6:36 AM
    Monday, November 29, 2010 11:59 AM
  • Hi,

     

    The lookup column is looked up a existed list only, so AD users cannot be used in lookup column by SharePoint OOB.

    As an alternative, we provide the Person or Group column to retrieve uses in the AD and SharePoint groups.

    Hope the information can be helpful.

     

    I wish you every success in your important work.

    Best regards,

    David Hu

     

    • Marked as answer by Peng Lei Thursday, December 9, 2010 6:36 AM
    Wednesday, December 1, 2010 2:20 AM

All replies

  • Hi ,

    Lookup field only works on information which is there on site , please refer column description "Lookup (information already on this site) ", So if the user is not added on the site then you can not find his name using lookup field.

    Or

    you can create a SharePoint group instead of AD group and this SharePoint group consists of AD users and from that group you can try to fatch the user name.


    Regards, Pratik Vyas | SharePoint Consultant |
    Monday, November 29, 2010 11:52 AM
  • There's another way to oapproach this - if you can limit the whole site collection user population to a given Active Directory OU and subcontainers.  There's a settale property (need to be on SP2!) that lets you lock the People Picker to a given strucuture

    stsadm -o setsiteuseraccountdirectorypath -path "OU=Employees,DC=Company,DC=com" –url http://server/sites/teamsite 
    

    In case your admin accounts live elsewhere in AD, there's a parallel strucuture to allow those accoutj sot live there:

    stsadm -o setproperty -url http://server/sites/teamsite -pn peoplepicker-serviceaccountdirectorypaths -pv " OU=MOSS-Accounts,DC=Company,DC=com 
    

     

    Good luck!

    Chris McNulty MCSE/MCTS/MSA/MVTS http://www.kma-llc.net | blog http://blogs.kma-llc.net/microknowledge | twitter @cmcnulty2000
    • Marked as answer by Peng Lei Thursday, December 9, 2010 6:36 AM
    Monday, November 29, 2010 11:59 AM
  • Hi,

     

    The lookup column is looked up a existed list only, so AD users cannot be used in lookup column by SharePoint OOB.

    As an alternative, we provide the Person or Group column to retrieve uses in the AD and SharePoint groups.

    Hope the information can be helpful.

     

    I wish you every success in your important work.

    Best regards,

    David Hu

     

    • Marked as answer by Peng Lei Thursday, December 9, 2010 6:36 AM
    Wednesday, December 1, 2010 2:20 AM