Forum Discussion
Solved
Map drive group policy Preferences not applying consistently
Hi everyone, We deployed Several drive via GPP. We use the update option and don't use the user context option. Unfortunately, it doesn't get applied consistently. We use RDS 2019 and our domain con...
- Thank you all for your replies they helped me with my troubleshooting.
To begin with I tried to help the server by enabling server caching which might caused this problem. I did several things which hopefully resolve this:
1. I removed the caching policies
2. Restarted my farm.
3. Moved all my disabled map drives (I have several which I merged from other policies which I want to delete in the future to reduce the amount of policies) to a lower priority.
Hopefully this will be the answer. I will keep this unanswered maybe someone has better ideas.
konaylintun09 thanks,
I have 28 mapped drives with a configuration that look like this:
We also use groups and users for other network drives.
As you are using Item-Level-Targeting, a common problem can be that the evaluation of group membership cannot be done before applying the GPO.
2 possible reasons you could check for:
1. Network connection to a domain controller with global catalog is not possible before user-login (user-vpn, network-level filtering, WLAN,...)
2. The user is member in a group across your domain-boundary (you mentioned a two-way-trust to an old domain) and the evaluation of universal group membership takes to long or has errors for some users.
2 possible reasons you could check for:
1. Network connection to a domain controller with global catalog is not possible before user-login (user-vpn, network-level filtering, WLAN,...)
2. The user is member in a group across your domain-boundary (you mentioned a two-way-trust to an old domain) and the evaluation of universal group membership takes to long or has errors for some users.
- The trust is not in play here. when a user is signing in to a RDS of the 2016 domain and not the 2008 r2 domain - I brought it up just to explain why still use a low functional level.
As for network connectivity, We are talking about a RDS server which is in the same subnet as the domain controller. The problem occurs to some users and not all.