Link to home
Start Free TrialLog in
Avatar of Christopher Perry
Christopher Perry

asked on

Group policy for drive maps

I have several group policies affected by this issue, but I'm only going to focus on one for this question.

I have a group policy that targets members of my "IT Users" group and it maps a drive (Action: replace; Drive: X). This policy is defined as a user configuration, not a computer configuration. There aren't any other policies that conflict with this drive mapping. This policy is linked to the OU where these users exist and has a security filter for members of my "IT Users" group in AD.

The drive map is never created (even if I switch the drive map action to CREATE). When I run "gpresult /r" on my machine (in this case, it's a Windows 10 machine but I also have the problem on Windows 7 machines), I see that the user account is a member of the correct group, but only the default domain policy is applied. The only policy that is filtered out is the local group policy (because it's empty). There is no change when I apply the policy to the OU containing the computer, even though this shouldn't matter since the drive map is configured as a user setting.

I have already tried restarting the computer and running "gpupdate /force"

This issue affects multiple users with other drive map policies (none of which overlap). I have to manually map drives for affected users instead.

I can't figure out why my group policies are ignored and why they aren't even listed as a "filtered out" policy when running gpresult /r
ASKER CERTIFIED SOLUTION
Avatar of oBdA
oBdA

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Christopher Perry
Christopher Perry

ASKER

I had no clue that the domain computers needed read permissions to GPOs, even if only user policies were defined. Your fix completely resolved my issues and has saved me hours of troubleshooting.