We're using Horizon View 5.3.0 in one of our environments. I have noticed some inconsistencies when setting entitlements on pools. The majority of our A.D. groups are in a container called Security Groups. If I create a group here, and entitle it through the View Manager, everything works as expected. If, however, I create the group in another container in A.D., the View Manager can see the group, and entitle it to the pool, but Members of that group cannot see the pool when logging into the View client. If I move that group into the Security Groups container though, everything begins working as I would expect.
Is there a setting or reason why View Administrator can see but not properly assign rights to a group in certain OUs? Everything I've read shows it shouldn't matter where the group resides in A.D.
Just an update, I have been testing and have found a number of groups in other OUs that work just fine. But anything under this AppSec container does not seem to work.