Create adds a new mapped drive, Update changes the settings of an existing mapped drive without removing it, and Replace deletes the current mapping and then recreates it. The practical difference is control over disruption. Update is usually safer for minor changes, while Replace is better when you need to reset a mapping completely or enforce a fresh configuration.
What each drive action actually changes in Group Policy
Create is the least disruptive option because it only adds the mapping if it does not already exist. Update is a modify-in-place action, so it preserves the existing mapping and changes only the settings you edit. Replace is the most forceful option because it removes the current mapping first, then creates it again with the new configuration.
That difference matters because group policy preferences treats the action as part of the control behavior, not just the destination path. The same drive letter and UNC path can produce very different user impact depending on whether the action preserves state, edits state, or resets state.
How the three actions behave on an existing mapped drive
If no mapping exists, Create adds one and leaves it alone on later refreshes unless the item is missing again. If a mapping already exists, Create does not overwrite it, which makes it useful for initial deployment but not for enforcing change. Update changes the existing entry, which is usually the best fit when you want to adjust the target, label, reconnect setting, or other properties without breaking the user experience.
Replace is different because it deliberately clears the old mapping before applying the new one. That gives you a clean reset when a drive mapping has drifted, been manually altered, or needs to be rebuilt from scratch. The tradeoff is a brief interruption while the old mapping is removed and recreated, which can be visible to the user.
This is why the practical choice is often about state management rather than syntax. If you only need to tune a setting, Update is the normal choice. If you need a guaranteed reset, Replace is the safer enforcement option. If you only want to provision a mapping once, Create is enough.
When to choose Create, Update, or Replace
Create is best for first-time deployment or when you want to avoid touching an existing mapping. Update is best when the mapping should stay in place and only its properties should change. Replace is best when consistency is more important than continuity, for example when you need to remove stale settings or eliminate a mapping that may have been modified outside policy.
In practice, the biggest operational distinction is disruption. Update tends to preserve session continuity, while Replace can momentarily break access before rebuilding the mapping. That is usually acceptable for administrative reset scenarios, but it is unnecessary for simple path changes.
For a reliable policy design, Windows drive mapping behavior and the underlying preference item logic should be reviewed together, because the action type determines whether the client treats the item as a new setting, an edit, or a delete-and-recreate event.
Practitioner Guidance
What to verify: Check whether you are trying to preserve user continuity or deliberately reset the mapping. That decision should drive the action choice, not convenience. If the mapping is already in production and only one or two fields need adjustment, Update is usually the correct starting point.
Decision rule: If the existing mapping is trusted and only needs a minor change, use Update. If the mapping may contain stale, user-modified, or inconsistent settings, use Replace. If the mapping should appear only when absent, use Create.
Common mistake: Using Replace for every change because it seems “cleaner.” That can create avoidable interruption and make the drive briefly disappear, which is unnecessary when the original mapping can be edited safely in place.
Practitioner takeaway: The right action is the one that matches the lifecycle of the mapping, Create provisions, Update preserves, and Replace reinitializes when you need a full reset.
Related resources from NHI Mgmt Group
- What is the difference between an ALFA policy defined inside a policy set and one referenced from outside it?
- What is the difference between direct access and effective access in Active Directory?
- What is the difference between managing human identities and non-human identities?
- What is the difference between delivering birthright access through an onboarding workflow and through group membership?
