A Baseline GPO configured to Auto connect client drives is not mapping client drives for a user launching the desktop. Which could be the cause?

• A. gpupdate /force needs to be executed on all of the machines
• B. Loopback processing is NOT enabled
• C. The GPO needs to be linked to the User OU
• D. Desktops need to be restarted for the policy to be applied

Answer: (B)

Loopback processing is what controls whether the user session on a machine uses the computer’s GPOs (instead of the user’s GPOs) for policy settings like auto-mapping client drives. In a Citrix/VDI scenario, you want the drive-mapping policy defined on the machine (the Baseline GPO) to apply to the user when they log into that machine. If loopback processing is not enabled, Windows applies user policies from the user’s own OU, so the computer-based drive-mapping settings don’t take effect in the session. Enabling loopback processing (Merge or Replace) makes the computer’s GPOs govern the user session, so the client drives map as intended. Other options won’t fix the mismatch in how policies are applied during logon in this context.