How to Deploy Network Locations Using Group Policy in Active Directory

Start by accessing the Group Policy Management Console on your Domain Controller. This is where you'll create and configure the GPO for network location deployment.

gpmc.msc

In the Group Policy Management Console, navigate to your domain structure. Right-click on the Organizational Unit (OU) where you want to apply the network locations policy. Select Create a GPO in this domain, and Link it here.

Name your GPO descriptively, such as "Network Locations - Department Shares" or "User Network Shortcuts". This helps identify the policy's purpose when managing multiple GPOs.

Right-click your newly created GPO and select Edit. This opens the Group Policy Management Editor where you'll configure the network location settings.

Navigate to User Configuration > Preferences > Windows Settings > Shortcuts. This is where network location shortcuts are configured, unlike mapped drives which use the Drive Maps section.

Right-click in the Shortcuts area and select New > Shortcut. This opens the New Shortcut Properties dialog where you'll define your network location.

Configure the shortcut properties:

• Action: Select "Create" (default)
• Name: Enter a descriptive name like "Company File Server" or "Department Resources"
• Target type: Select "File System Object"
• Location: Choose "Desktop" or "Start Menu" depending on where you want the shortcut to appear
• Target path: Enter the UNC path to your network share (e.g., \\fileserver01\shared\department)

Click on the Common tab in the shortcut properties dialog to configure advanced settings that control how and when the network location is deployed.

Essential Common tab settings:

• Run in logged-on user's security context: Check this box to ensure the shortcut uses the user's credentials when accessing the network location
• Remove this item when it is no longer applied: Check this to automatically clean up shortcuts when users are moved out of the GPO scope
• Apply once and do not reapply: Uncheck this to ensure shortcuts are recreated if deleted by users

For enhanced security and targeting, configure Item-level Targeting by clicking the Targeting... button. This allows you to apply the network location only to specific users or groups.

<!-- Example targeting configuration -->
<TargetingItem xsi:type="q1:SecurityGroup_Type">
  <q1:name>Domain\Department-Users</q1:name>
  <q1:userInGroup>true</q1:userInGroup>
</TargetingItem>

Click OK to save all shortcut configurations and return to the Group Policy Management Editor.

Repeat the shortcut creation process for additional network locations your users need access to. This might include department-specific shares, common resources, or application data folders.

Common network location examples to deploy:

For each additional shortcut, right-click in the Shortcuts area and select New > Shortcut. Configure each with appropriate names, target paths, and targeting criteria.

Consider creating shortcuts that point to different locations on the user's system:

• Desktop shortcuts: Most visible but can clutter the desktop
• Start Menu shortcuts: Organized under Programs menu
• Quick Access shortcuts: Appear in File Explorer's Quick Access area

Return to the Group Policy Management Console and select your network locations GPO. Click on the Scope tab to configure which users and computers will receive the network location shortcuts.

By default, the GPO applies to "Authenticated Users". To restrict deployment to specific groups:

1. Click Add under Security Filtering
2. Select the appropriate security groups (e.g., "Department-Users", "Project-Team-Alpha")
3. Remove "Authenticated Users" if you want to limit scope to specific groups

Configure WMI Filtering if you need to target specific operating systems or hardware configurations:

-- Example WMI filter for Windows 11 only
SELECT * FROM Win32_OperatingSystem WHERE Version LIKE "10.0.22%"

Link the GPO to additional OUs if needed by right-clicking the GPO and selecting Add Link. This allows the same network locations to be deployed across multiple organizational units.

Before deploying to all users, test the network location deployment on a few client machines. Log into a domain-joined computer with a user account that should receive the network locations.

Force an immediate Group Policy update on the test client:

gpupdate /force /target:user

Check if the network location shortcuts appear in the expected locations (Desktop, Start Menu, etc.). Open File Explorer and verify the shortcuts work correctly by clicking on them.

Use Group Policy Results to verify policy application:

gpresult /h C:\temp\gpresult.html /user DOMAIN\testuser

Open the generated HTML report and look for your network locations GPO in the applied policies section. This confirms the policy is being processed correctly.

Test network location functionality:

• Click on each network location shortcut
• Verify File Explorer opens to the correct network path
• Test file access permissions (read, write, delete as appropriate)
• Confirm shortcuts persist after user logout/login

Monitor the deployment across your environment using Group Policy Management Console's built-in reporting features. Check the Group Policy Results for different users to ensure consistent application.

Common troubleshooting steps for network location deployment issues:

If shortcuts don't appear:

gpupdate /force
rsop.msc

Use the Resultant Set of Policy (RSoP) tool to see which policies are being applied and identify conflicts.

If shortcuts appear but don't work:

• Verify network connectivity: ping fileserver01
• Test UNC path access: \\fileserver01\shared in Run dialog
• Check share permissions and user access rights
• Verify DNS resolution for server names

Check Group Policy event logs:

Get-WinEvent -LogName "Microsoft-Windows-GroupPolicy/Operational" | Where-Object {$_.TimeCreated -gt (Get-Date).AddHours(-1)}

Review Group Policy processing events to identify errors or warnings related to your network locations GPO.

Use Group Policy Management Console's Group Policy Results wizard to generate detailed reports for specific users experiencing issues. This shows exactly which policies applied and any errors encountered.