We had the same problem. Adding the user's AD account to the local users group fixed the problem for us.