|
After narrowing down the issue to a number of specific groups and comparing the differences, it appears that the issue is related to residual SID history that may not have been removed from particular AD Security groups. Once SID history is removed from a problem group, the issue is then resolved for that group.
Now unfortunately we just renamed most of the groups so this will be a bit harder. Thanks to everyone for their help in isolating this issue.
| 
