SharePoint 2013: Active Directory Groups not providing site permission.

Product: SharePoint 2013

I am trying to manage SharePoint permissions with Active Directory groups.   When I add an AD group to the SharePoint Members group on the site, the members of the AD Group do not get permissions to the site.

If I add the member directly to the SharePoint group and skip the AD Group, the member gets permissions quickly.

Any Clue why?
TerryZumwaltAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jayaraja JayaramanSharepoint Architect ConsultantCommented:
did you add the add the users after the AD group is added to sharepoint ? if yes did you run a rull crawl with UPS ?
0
TerryZumwaltAuthor Commented:
I started and completed a Crawl from with in the Search Application.  When it was done all permissions were the same as before.   I am not sure what UPS is referring to.
0
Jayaraja JayaramanSharepoint Architect ConsultantCommented:
am not talking about search full crawl. am refereing to User Profile Sync.
Go to CA- > Service applications -> user profile Service -> start profile sync(under sync) -> start full sync
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

TerryZumwaltAuthor Commented:
After running the UPS as suggested  there was still no change to the permissions. I Added the Group to a sub site as well and no change.
0
Jayaraja JayaramanSharepoint Architect ConsultantCommented:
ok please try running IISReset and then
SharePoint will cache this group membership info for about 24 hours.

The time out can be configure to a lower value:

$sptokensvc= Get-SPSecurityTokenServiceConfig
$sptokensvc.FormsTokenLifetime = (New-TimeSpan -minutes 2)
$sptokensvc.WindowsTokenLifetime = (New-TimeSpan -minutes 2)
$sptokensvc.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1)
$sptokensvc.Update()
iisreset

This script will tell the token service that the claims will be valid for 1 minute and after that it will get the latest membership information from the Active Directory.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Walter CurtisSharePoint AEDCommented:
Here are a few basic questions -
Are SharePoint servers in the same AD Domain as the users AD Domain?
Any issues when you add an AD group to a SharePoint group with the AD group name resolving through People Picker?
Are you using AD security groups and not AD Distribution Groups?

Keep in mind that User Profile Sync has nothing to do with adding AD groups to SharePoint groups.

Hope that helps
0
TerryZumwaltAuthor Commented:
I just ran the Token script- I will test the result.

1. Yes they are in the same AD.
2. NO Issues adding the group.
3. We are using AD Security Groups.
0
TerryZumwaltAuthor Commented:
I just tested and the user in the AD Group is allowed to access the site.  Thanks for you assistance.  The last change I made was my Jayaraja above.  (Copied below.)



ok please try running IISReset and then
 SharePoint will cache this group membership info for about 24 hours.

 The time out can be configure to a lower value:

 $sptokensvc= Get-SPSecurityTokenServiceConfig
 $sptokensvc.FormsTokenLifetime = (New-TimeSpan -minutes 2)
 $sptokensvc.WindowsTokenLifetime = (New-TimeSpan -minutes 2)
 $sptokensvc.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1)
 $sptokensvc.Update()
 iisreset

 This script will tell the token service that the claims will be valid for 1 minute and after that it will get the latest membership information from the Active Directory.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Services

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.