We have an application that is deployed to a collection with a specific AD Group listed inside. AppCollection +DomainA\AppUsers
My account is a member of a different domain (we'll call it DomainB), we have added my "DomainB\Mike" account to "DomainA\AppUsers" in AD. I have run the following query to determine that SCCM does in fact know that I am a member of that AD Group. SELECT usr.Name0,User_Group_Name0 FROM v_RA_User_UserGroupName ugn inner join v_R_user usr on ugn.ResourceID=usr.resourceid where usr.Name0 like '%mike%' So I know that SCCM knows I'm a member of DomainA\AppUsers, but even after waiting several hours, running the user policy retrieval and the application deployment evaluation cycles, the application is never listed in the Application Catalog. It seems like the App Catalog is working because I can add a collection from DomainB that I am a member of and the application shows up. Even though the account from one domain is in a group in another domain, it seems like it should work as long as SCCM knows that my account is a member of the targeted group in the collection. I hardly ever work with the App Catalog, so I'm probably missing something obvious. I'm still digging into this, but I'm hoping that someone will have some ideas. *Mike*
