locked
Group shows under target audience but not under site permissions RRS feed

  • Question

  • While setting target audience we see two groups under "Distribution/Security Groups" tab but we cannot get reference to those groups while adding permissions to some list item.

     

    Any idea what could be going wrong?


    Nitin Sablok - Posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, December 21, 2010 6:14 PM

Answers

  • Hi Nitin

     

    I will think so. In our organisation we set up distribution list as security groups in AD so that the same can be used in SharePoint to provide permissions as well. Since this task is done by experts having domain admin permission, there is little or no risks involved. I'll suggest that you take into account someone having that knowledge and permission level before making any changes.


    xwindow
    • Marked as answer by Nitin Sablok Wednesday, December 22, 2010 2:25 PM
    Wednesday, December 22, 2010 6:24 AM
  • These are presumably the AD group types that can't be used for access permissions to SharePoint sites (etc.)

    (I can never remember which ones you can't use but I have a strong feeling that distribution groups were one)

    The question I suppose is if you can use these when specifying permissions for anywhere else in your site.


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    • Marked as answer by Nitin Sablok Wednesday, December 22, 2010 2:25 PM
    Tuesday, December 21, 2010 6:46 PM

All replies

  • These are presumably the AD group types that can't be used for access permissions to SharePoint sites (etc.)

    (I can never remember which ones you can't use but I have a strong feeling that distribution groups were one)

    The question I suppose is if you can use these when specifying permissions for anywhere else in your site.


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    • Marked as answer by Nitin Sablok Wednesday, December 22, 2010 2:25 PM
    Tuesday, December 21, 2010 6:46 PM
  • Thanks Mike for the reply.

     

    We cannot use them anywhere else in the site other than target audience. That might be because, we don't get option of both Distribution/Security Groups anywhere other than audience.

     

    Do you think this is my only option: http://technet.microsoft.com/en-us/library/cc782613(WS.10).aspx


    Nitin Sablok - Posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, December 21, 2010 6:55 PM
  • Well I wouldn't. It seems a bit risky to mess around with AD groups even if there is an MS article telling you how to do it.

    But then I prefer not to take *any* risks.

    Maybe someone else has used this technique and it worked well for them ...  (if so, they get their chance here to tell us all about it)

     

    Mike


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Tuesday, December 21, 2010 6:59 PM
  •  If you are working on permission model, then firstly you have to activate "Sharepoint Server Publishing Infrastructure" from site action-> site Collection Administration -> site Collection Feature.  If you are appling to List then go to List Setting-> Permission for this list->  stop inheriting parent. Then delete group whch you dont want to show. 

     
     

    Wednesday, December 22, 2010 6:09 AM
  • Hi Nitin

     

    I will think so. In our organisation we set up distribution list as security groups in AD so that the same can be used in SharePoint to provide permissions as well. Since this task is done by experts having domain admin permission, there is little or no risks involved. I'll suggest that you take into account someone having that knowledge and permission level before making any changes.


    xwindow
    • Marked as answer by Nitin Sablok Wednesday, December 22, 2010 2:25 PM
    Wednesday, December 22, 2010 6:24 AM
  • Thanks xwindow.
    Nitin Sablok - Posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, December 22, 2010 2:25 PM