Anavem
Languagefr
How to Deploy Network Locations via Group Policy in Windows Server 2025

How to Deploy Network Locations via Group Policy in Windows Server 2025

Configure and deploy network locations to Windows clients using Group Policy Objects, creating persistent UNC path connections without drive letters in This PC.

April 29, 2026 15 min
mediumgroup-policy 8 steps 15 min

Why Deploy Network Locations Instead of Mapped Drives?

Network locations offer a cleaner alternative to traditional mapped drives in modern Windows environments. Unlike mapped drives that consume drive letters (Z:, Y:, etc.), network locations appear in This PC as UNC paths without letter assignments. This approach eliminates drive letter conflicts, provides better integration with Windows 11's interface, and offers more flexibility for users who need access to multiple network resources.

What Makes Group Policy the Best Method for Network Location Deployment?

Group Policy Preferences provide centralized management and automatic deployment of network locations across your domain. This method ensures consistent access to shared resources, reduces helpdesk calls, and maintains security through Active Directory authentication. The item-level targeting feature allows precise control over which users receive specific network locations based on security groups, operating systems, or other criteria.

How Do Network Locations Differ from Traditional Mapped Drives?

The key difference lies in presentation and resource consumption. Mapped drives appear as separate drives with assigned letters, while network locations appear under the "Network locations" section in This PC. Network locations use UNC paths directly, making them more transparent and less likely to conflict with removable media or other drive assignments. This approach aligns better with Microsoft's modern file management philosophy and provides a more intuitive user experience.

Implementation Guide

Full Procedure

01

Install Group Policy Management Tools

First, ensure you have the Group Policy Management Console available on your domain controller or administrative workstation. On Windows Server 2025, GPMC is integrated by default. For Windows 11 workstations, install the RSAT tools.

Add-WindowsCapability -Online -Name Rsat.GroupPolicy.Management.Tools~~~~0.0.1.0

This command installs the latest RSAT Group Policy tools (version 10.3.0.0 as of March 2026). The installation takes 2-3 minutes and requires an internet connection.

Pro tip: You can also install RSAT tools through Settings > Apps > Optional features > Add an optional feature, but PowerShell is faster for bulk deployments.

Verification: Open the Start menu and search for "Group Policy Management" or run gpmc.msc from the Run dialog. You should see the Group Policy Management Console open without errors.

02

Create a New Group Policy Object

Open Group Policy Management Console and create a dedicated GPO for network locations. This keeps your configuration organized and makes troubleshooting easier.

gpmc.msc

In the GPMC console:

  1. Expand your domain in the left pane
  2. Right-click on Group Policy Objects
  3. Select New
  4. Name your GPO: Network Locations - Department Shares
  5. Click OK

The new GPO appears in the Group Policy Objects container. This GPO will contain all your network location configurations.

Warning: Don't link the GPO to an OU yet. Configure it first, then link it to avoid applying incomplete settings to users.

Verification: Your new GPO should appear in the Group Policy Objects list with a creation date of today and show "Not linked" in the Links tab.

03

Configure Drive Maps in Group Policy Preferences

Now edit your GPO to add network location configurations. Right-click your new GPO and select Edit to open the Group Policy Management Editor.

Navigate to: User Configuration > Preferences > Windows Settings > Drive Maps

Right-click on Drive Maps and select New > Mapped Drive. This opens the New Drive Properties dialog where you'll configure your network location.

In the General tab, configure these settings:

  • Action: Update (this creates or updates the connection without removing existing ones)
  • Location: \\fileserver\department (replace with your actual UNC path)
  • Reconnect: Checked (ensures the connection persists across logons)
  • Label as: Department Share (friendly name users will see)
  • Drive Letter: Select "Use" with no letter assigned for a pure network location
Pro tip: Use descriptive labels like "HR Documents" or "Engineering Files" instead of technical names. Users will see these labels in This PC.

Verification: The preview pane should show your UNC path and label. The "Use" option should show no drive letter assigned.

04

Configure Item-Level Targeting

Click the Common tab in the Drive Properties dialog. This is where you'll configure which users receive this network location.

Check Item-level targeting and click the Targeting... button. This opens the Targeting Editor where you can specify conditions.

Click New Item and select targeting criteria:

For Security Group targeting:

  1. Select Security Group
  2. Click the ... button
  3. Enter group name: Department-Users
  4. Select User is a member of the security group

For Operating System targeting (Windows 11 only):

SELECT * FROM Win32_OperatingSystem WHERE Version LIKE "10.0%" AND BuildNumber >= "22000"

Also check Run in logged-on user's security context in the Common tab. This ensures the network location uses the user's credentials for access.

Warning: If you don't enable "Run in logged-on user's security context," the connection might fail due to permission issues, especially with Kerberos authentication.

Verification: Click OK to close all dialogs. Your drive map should appear in the Drive Maps list with your specified targeting conditions.

05

Link the GPO to Target Organizational Unit

Close the Group Policy Management Editor and return to the main GPMC console. Now link your configured GPO to the appropriate Organizational Unit containing your target users.

In GPMC:

  1. Navigate to your domain and expand the OU structure
  2. Right-click the target OU (e.g., Departments or Users)
  3. Select Link an Existing GPO...
  4. Choose your Network Locations - Department Shares GPO
  5. Click OK

The GPO link appears under the OU with a link icon. You can adjust the link order if you have multiple GPOs linked to the same OU.

Pro tip: Link to user-containing OUs, not computer OUs. Network locations are user-specific settings that apply during user logon, not computer startup.

Verification: In the OU's Linked Group Policy Objects tab, you should see your GPO listed with "Enabled" status and today's link date.

06

Test Network Location Deployment on Client

Log into a Windows 11 client computer with a user account that meets your targeting criteria. Force a Group Policy update to apply the new settings immediately.

gpupdate /force /target:user

This command forces an immediate update of user policies. The output should show "User Policy update has completed successfully."

Log off and log back on to ensure the network location is properly established. After logging back in, open This PC in File Explorer.

Your network location should appear under the Network locations section with the label you specified (e.g., "Department Share"). Click on it to verify access to the shared folder.

Verify the connection using command line:

net use

This shows all active network connections. You should see your UNC path listed without a drive letter assignment.

Pro tip: If the network location doesn't appear immediately, wait 5-10 minutes. Group Policy background refresh occurs every 90-120 minutes by default, but the initial application should be immediate after gpupdate.

Verification: The network location appears in This PC, is accessible when clicked, and shows in the net use output without errors.

07

Verify Group Policy Application

Generate a detailed Group Policy report to confirm your network location policy is being applied correctly to the target user.

gpresult /h C:\temp\gpreport.html /user %username%

This creates an HTML report showing all applied policies for the current user. Open the report in a web browser and look for your GPO under "Applied GPOs."

For command-line verification:

gpresult /r /user %username%

This displays a summary showing applied GPOs and their settings. Your network location GPO should appear in the "Applied Group Policy Objects" section.

Check the Windows Event Viewer for any Group Policy errors:

eventvwr.msc

Navigate to Windows Logs > Application and look for events from source "Group Policy" with Event ID 1006 (successful application) or any error events.

Warning: If gpresult shows your GPO as "Denied" or "Not Applied," check your item-level targeting conditions and ensure the user meets all criteria.

Verification: The HTML report shows your GPO under Applied GPOs, and no Group Policy errors appear in Event Viewer.

08

Troubleshoot Common Issues

If network locations aren't appearing or working correctly, follow these troubleshooting steps systematically.

Issue 1: Network location not appearing

Check if the GPO is linked to a user OU (not computer OU):

gpresult /scope:user /v

Verify the user is in the correct security group for item-level targeting:

whoami /groups | findstr "Department-Users"

Issue 2: Access denied errors

Test manual connection to verify permissions:

net use \\fileserver\department

If this fails, the issue is permissions, not Group Policy. Check NTFS and share permissions on the target folder.

Issue 3: Connection not persistent

Verify the "Reconnect" option is enabled in your GPO and check for conflicting Offline Files policies:

reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CSC" /v Start

If the value is 4, Offline Files is disabled, which can cause persistence issues.

Pro tip: Use the Group Policy Results Wizard in GPMC to simulate policy application for specific users and computers before deployment.

Verification: All network locations appear correctly, are accessible, and persist across logons without errors.

Frequently Asked Questions

What's the difference between network locations and mapped drives in Windows?+
Network locations appear in This PC without consuming drive letters, using UNC paths directly (like \\server\share). Mapped drives assign specific drive letters (Z:, Y:) and appear as separate drives. Network locations provide better integration with modern Windows interfaces and eliminate drive letter conflicts while maintaining the same access functionality.
Can I deploy network locations to specific user groups only?+
Yes, using item-level targeting in Group Policy Preferences. You can target based on security groups, organizational units, WMI queries for specific operating systems, or combinations of criteria. This allows precise control over which users receive specific network locations, making it ideal for department-specific shares or role-based access.
Why don't my network locations persist after reboot?+
This usually occurs when the 'Reconnect' option isn't enabled in the Group Policy drive map configuration, or when 'Run in logged-on user's security context' isn't checked. Also verify that Offline Files policies aren't conflicting with persistent connections. The network location should reconnect automatically using the user's cached credentials.
How do I troubleshoot network locations not appearing for some users?+
Run 'gpresult /r /user username' to verify the GPO is being applied. Check that the GPO is linked to a user OU, not a computer OU. Verify the user meets item-level targeting criteria using 'whoami /groups'. Test manual connection with 'net use \\server\share' to rule out permission issues. Use Group Policy Results Wizard for detailed analysis.
Can network locations work with DFS namespaces and modern authentication?+
Yes, network locations fully support DFS namespaces (\\domain\namespace\folder) and integrate seamlessly with Kerberos authentication and modern security protocols. They work with Azure AD joined devices when hybrid identity is configured. The UNC path approach actually provides better compatibility with DFS than traditional mapped drives in many scenarios.

Discussion

Share your thoughts and insights

Sign in to join the discussion