How to map a network drive in Windows

If you’ve worked in a collaborative office before, then you’ll probably know about shared centralized storage and drives with role-based access control on a network. But how do you actually set up those network drives and control who can access them?

This guide shows you the easiest methods for mapping a network drive in Windows, from the simple GUI approach using file explorer to the more advanced command-line methods like PowerShell.

What to know before mapping a network drive in Windows

Before mapping network drives across your Windows environment, there are a few foundational elements to verify that determine whether connections will succeed, remain secure, and scale reliably. Windows environments enforce different drive mapping capabilities based on user roles, which affects both what users can accomplish and how IT teams should deploy mappings at scale.

More specifically:

• Standard users can map network drives when they possess appropriate access rights and network visibility to the shared resource. However, standard users can’t create persistent mappings that reconnect automatically at login without assistance from Group Policy or login scripts.
• Local administrators have more capabilities, including creating persistent mappings through the registry editor, managing shared resources on the local machine, and troubleshooting drive mapping issues through elevated command prompts.
• Domain users benefit from Group Policy Objects that automate drive assignments based on security group membership, organizational unit placement, or custom targeting criteria. For instance, finance department members automatically receive access to \fileserver\finance upon login, while engineering staff map to \fileserver\engineering.

» Learn about group policy management with Atera

Infrastructure and configuration requirements

Network drive mapping relies on a properly configured infrastructure where devices, servers, and authentication systems work in harmony. Without these elements in place, even perfectly executed mapping commands will fail.

Here’s what you need:

• Reliable network connectivity: Devices must connect via LAN or through a secure VPN tunnel that maintains stable communication with file servers. Remote workers attempting to map drives without VPN access will encounter connection timeouts or “network path not found” errors.
• SMB protocol activation: Windows uses SMB to communicate with file servers, and if SMB is disabled or blocked by security policies, drive mapping becomes impossible. Verify SMB 2.0 or SMB 3.0 is enabled (SMB 1.0 has significant security vulnerabilities).
• Correct folder sharing: Misconfigured permissions are the primary cause of “access denied” errors. The destination folder must grant appropriate read/write privileges to specific users or security groups. Be sure to validate user identity through domain trust relationships, local credentials, or Kerberos tickets
• Firewall configuration: You must allow SMB traffic through port 445. Corporate firewalls or Windows Defender Firewall rules that block this port prevent drive mapping entirely.

Security considerations for mapped drives

Network drive mappings create security exposures that require careful planning, especially in environments with shared workstations, remote users, or complex authentication scenarios.

The most critical ones to worry about include:

• Credential exposure: Represents the most significant risk. Windows stores network credentials in memory through the Local Security Authority Subsystem Service (LSASS), where they become vulnerable to memory-dumping attacks. You should enable SMB signing and encryption to reduce exposure, even though these features carry minor performance overhead.
• Unauthorized access on shared workstations: Occurs when drives remain persistently mapped across user sessions. If a mapped drive uses saved credentials and “Reconnect at sign-in” is enabled, the next user who logs into that workstation may inherit access to resources they shouldn’t see.
• Man-in-the-middle attacks: Attackers positioned between the client and file server can intercept credentials or modify data in transit. According to MITRE ATT&CK, adversaries frequently exploit mapped drives to exfiltrate sensitive data during breach scenarios.
• Cross-domain trust vulnerabilities: Inconsistent security policies between domains may allow unintended access patterns where users from one domain access resources in another domain beyond what administrators intended. It occurs more often in organizations with multiple Active Directory domains or forest trusts.

» Don’t miss these top cybersecurity tips

Easiest methods to map a network drive in Windows

Windows provides multiple pathways for mapping network drives, each optimized for different scenarios and user skill levels.

Remember that consistent naming conventions and properly formatted network paths prevent the configuration drift and user confusion that plague distributed IT environments:

• UNC path formatting follows the \server\share\folder structure where the server name must resolve through DNS and the share name must exist on that server. You should establish clear naming standards for both servers (like FS-DEPT-01 for departmental file servers) and shares (like Finance-Shared or Engineering-Projects) that make paths self-documenting.
• DNS names versus IP addresses present a critical choice. While \192.168.1.10\share works initially, it creates technical debt when server IP addresses change during infrastructure upgrades. DNS names like \fileserver.company.local remain stable even when the underlying IP address changes.

» Did you know you can change and assign specific drive letters in Windows?

1. Through File Explorer (the simple GUI approach)

File Explorer offers the most accessible route to network drive mapping, making it ideal for simple one-time configurations, users who need visual confirmation of each step, and those who feel intimidated by command-line utilities like Command Prompt.

Follow these steps:

1. Open File Explorer by pressing Windows key + E, or clicking the folder icon in the taskbar

2. Click This PC in the left navigation pane

3. Select Map network drive from the Computer ribbon at the top (the three-dot menu in Windows 11)

4. Choose an available drive letter from the dropdown menu (Windows suggests the next available letter)

5. Enter the network path using UNC format: \\ServerName\SharedFolder

6. Check Reconnect at sign-in if you want the drive to reconnect automatically at each login, then check Connect using different credentials if you need to authenticate with an account other than your current Windows login

7. Click Finish

8. Enter your username and password if prompted (use DOMAIN\username format for Active Directory environments)

The drive now functions like any local storage, appearing in File Explorer with your chosen drive letter and remaining accessible until you disconnect it or restart without persistence enabled.

2 With Command Prompt (simple scriptable alternative to File Explorer)

Command Prompt provides a lightweight, scriptable alternative that excels in automation scenarios, legacy system support, and situations requiring quick repeatability without PowerShell’s learning curve. It’s great for automating drive mappings through login scripts, working on older Windows systems without PowerShell support, performing remote support where GUI access is restricted or unreliable, or needing quick, repeatable commands for batch deployment across multiple endpoints.

Follow these steps:

1. Open Command Prompt as an Administrator

2. Type the mapping command using this syntax: net use Z: \ServerName\SharedFolder /user:DOMAIN\username password /persistent:yes

Make sure you use the following replacements:

• Replace Z: with your desired drive letter
• Replace \ServerName\SharedFolder with the actual network path
• Replace DOMAIN\username with your authentication credentials (or use just “username” for workgroup environments
• Replace “password” with your actual password, but make sure you consider the security implications of putting passwords in scripts
• Use /persistent:yes to reconnect the drive automatically at login, or /persistent:no for temporary mappings

Here’s an example of what that might look like:

3. Press Enter to execute the command. You should see a message like “The command completed successfully”.

If you don’t have domain authentication in your environment, then you can just use this simplified command: net use Z: \\ServerName\SharedFolder /persistent:yes

3. With PowerShell (the advanced approach for enterprise-wide automation)

PowerShell delivers enterprise-grade control with advanced features like credential management, error handling, conditional logic, and integration with modern management platforms, making it the preferred choice for sophisticated automation scenarios.

Choose PowerShell when:

• Automating drive mappings across multiple endpoints with complex requirements
• Integrating with Group Policy or Intune deployment scripts
• Managing remote sessions or headless server deployments
• Implementing credential controls that separate sensitive data from script code
• Building maintainable automation with proper error handling and logging

Follow these steps:

1. Open PowerShell as an Administration

2. Use the New-PSDrive cmdlet with this basic syntax: New-PSDrive -Name “Z” -PSProvider “FileSystem” -Root “\ServerName\SharedFolder” -Persist

Make sure you use the following replacements:

• Replace “Z“ with your desired drive letter (without the colon)
• Replace “\ServerName\SharedFolder“ with the actual network path
• Include -Persist to make the drive reconnect at login (omit for temporary session-only mappings)

3. Press Enter to execute the command

What makes PowerShell better than the other methods is that you can implement sophisticated automation features that scale across distributed environments. IT teams can embed conditional logic, implement centralized credential management, and deploy scripts remotely to multiple endpoints through RMM platforms like Atera.

For example, instead of hardcoding passwords in scripts, PowerShell can prompt users securely or retrieve credentials from encrypted storage:

The best part is that you don’t even have to be a coding whizz to get the most out of PowerShell, thanks to a new technique called vibe coding (generating custom scripts and code with AI using natural language queries). For example, you could ask Atera’s AI Copilot for help writing a network mapping script for your specific environment with custom criteria like tracking diagnostic information or checking user attributes to map drives based on group memberships.

» Did you know you can paste in PowerShell?

Moving beyond manual configuration

Network drive mapping in Windows can be done with simple File Explorer clicks for individual users to sophisticated PowerShell automation for enterprise IT deployments. The right method depends on your environment’s scale, security requirements, and management infrastructure.

For IT teams and MSPs managing endpoints at scale, platforms like Atera transform drive mapping from repetitive manual tasks into centralized, auditable processes. Atera’s automation capabilities let you deploy PowerShell scripts across hundreds of devices simultaneously, store credentials securely, monitor execution results, and maintain consistent configurations across diverse client environments all from a unified management console.

» Get started with Atera for free