I use .NET's Thread.CurrentPrincipal.IsInRole function to restrict access to certain areas of my Windows applications based on AD security groups. My company is migrating these apps to RemoteApp.
When I first tested these apps after setup, they would report errors indicating that I was not in the correct security group. After the RemoteApp admins changed settings (something about "pass-through" security), it started working. Now a second user with the same permissions as me is having the exact problem I originally had.
Does RemoteApp have issues syncing up the AD security group information? It has been several days since I added the user to the necessary groups.
It turns out that Remote Desktop Connection Broker was caching credentials. A reboot solved the problem.