Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.
Drive Map preferences provide centrally managed SMB mappings with item-level targeting and update behavior.
Prerequisites
- Administrative access to the affected Windows Server hosts.
- A tested backup or documented rollback point.
- An approved maintenance window for production systems.
Step-by-step configuration
- Confirm the UNC path and share permissions.
- Create a user-side Drive Maps preference item.
- Choose Update action and an available drive letter.
- Apply item-level targeting to an approved security group.
- Pilot mapping, reconnection, and removal behavior.
PowerShell and command-line procedure
Test-Path "\\files01\Departments"
gpupdate /force
Get-SmbMapping
gpresult /scope user /rVerification
Authorized pilot users receive the mapping and unauthorized users do not.
Rollback
Set the preference item to Delete for the pilot scope, refresh policy, and then remove the item.
Security and operational guidance
- Apply least privilege and document every production change.
- Test the procedure in an isolated environment before broad deployment.
- Replace all example names, paths, and TEST-NET addresses with approved production values.
- Monitor relevant Windows event logs after the change.
Treat targeting and permissions as separate controls
Drive Maps is a user-side Group Policy Preferences setting. Configure it under User Configuration, Preferences, Windows Settings, Drive Maps in the GPO that reaches the intended users. Linking a user setting only to a server OU does not automatically make it apply to every person who signs in there; an RDS loopback design requires separate planning.
Use a stable UNC path and an available drive letter. The Update action can maintain the desired mapping without deliberately recreating it at every refresh. A Replace action can disconnect and recreate the mapping, which matters when an application has files open. Test that behaviour with the real application before choosing it.
Item-level targeting controls which users receive the preference item. It is not a security boundary: share and NTFS permissions still decide who can read the data. Test both an authorized and an unauthorized account, and confirm the result in the user policy report.
Decide what should happen when a user leaves the target group. Removing a GPO or changing a filter does not, by itself, guarantee that every previously created preference setting disappears. Test the configured removal behaviour and use a scoped Delete item when a controlled cleanup is needed. Keep the share in service while validating the mapping change.
Related resources
Deploy or manage Canadian Windows VPS infrastructure with managed Windows VPS hosting. Validate production decisions against the official Microsoft Windows Server documentation.