PowerShell: How to map network drive

June 13, 2024

Here’s how I map a network path to a drive letter using PowerShell. I usually start with the Z drive for consistency, but if it’s already taken, the script automatically finds the next available letter.

Mapping a network drive this way is a fast and reliable method to access shared folders — especially when you want to avoid manual setup or GUI clicks.

PowerShell makes this process easy to automate. Whether you’re a system administrator or just someone who frequently connects to network resources, this script can save time and reduce errors.

Let’s take a look:

# Define some variables here
$folderPath = "\\server\folder"
$driveLetter = "Z"
#If drive letter exists get next available letter
if (Test-Path -Path $driveLetter":\") {
	$taken = Get-WmiObject Win32_LogicalDisk | Select -expand DeviceID
	$letter = 65..90 | ForEach-Object{ [char]$_ + ":" }
	$driveLetter = ((Compare-Object -ReferenceObject $letter -DifferenceObject $taken)[1].InputObject ).trim(":")
}
# Attempt to map the folder path to the new drive letter
try {
	New-PSDrive -Name $driveLetter -PSProvider FileSystem -Root $folderPath -Persist
	Write-Host "Successfully mapped $folderPath to drive $driveLetter"
} catch {
	Write-Host "Failed to map $folderPath to drive $driveLetter"
	Write-Host "Error: $_"
}

How this works:

1. Define Your Folder Path
$folderPath = "\\server\folder"
$driveLetter = "Z"

Start with your preferred drive letter. If it’s taken, the script will find the next free one.

2. Check for Conflicts
if (Test-Path -Path $driveLetter+":\") {
    $taken = Get-WmiObject Win32_LogicalDisk | Select -Expand DeviceID
    $letter = 65..90 | ForEach-Object { [char]$_ + ":" }
    $driveLetter = ((Compare-Object -ReferenceObject $letter -DifferenceObject $taken)[1].InputObject).Trim(":")
}

This block checks all drive letters from A to Z and picks the first one that’s not in use.

3. Map the Drive
try {
    New-PSDrive -Name $driveLetter -PSProvider FileSystem -Root $folderPath -Persist
    Write-Host "Successfully mapped $folderPath to drive $driveLetter"
} catch {
    Write-Host "Failed to map $folderPath to drive $driveLetter"
    Write-Host "Error: $_"
}

If mapping fails, the script logs the error — no silent failures.

Use Cases

  • Login scripts for roaming profiles
  • Automated deployments in server farms
  • Quick access to shared folders without a GUI
  • Disaster recovery scripts where drive letters vary

Mapping a network drive using PowerShell is a simple yet powerful process — one that can be automated and tailored to fit your workflow. Whether you’re managing network resources or just need fast access to shared folders, this skill can save time and reduce manual effort.

Keep in mind: this script will continue assigning new drive letters to the same network path if run multiple times. Therefore, it’s best to run it only once or include logic to check if the mapping already exists.

Additionally, always ensure you have the proper permissions to access the network share. And most importantly, handle credentials securely — especially in professional or multi-user environments.

If you want to learn more about New-PSDrive