Every sysadmin knows the problem. An employee moves to a new workstation, notebook or takes over the duties of another employee. In all these cases, the need to take over the network drives of the old device or the colleague may arise.

In this tutorial you will learn how to transfer network drives from a source system / -profile to a target system / -profile in 2 simple steps.

Table of Content:

  1. Introduction
  2. Prerequisites
  3. Set the needed Execution Policy
  4. Export
  5. Import
  6. Conclusion


  • PowerShell 5.1 (tested version -> but I am sure it also works in other versions) - with Windows on board
  • the access right to the desired SMB (Server Message Block) network shares
  • the right to execute PowerShell scripts (see the next section)

Set the needed Execution Policy

  1. Select Start > All Programs > Windows PowerShell version > Windows PowerShell (as Administrator)
  2. Type Set-ExecutionPolicy Unrestricted to set the policy to Unrestricted.
  3. Type Get-ExecutionPolicy to verify the current settings for the execution policy.
  4. Type Exit.


Below you will find the script that has to be executed.

$TxtPath = "c:\temp\MappedDrive.csv"

#Export network drives to file
Get-ChildItem "HKCU:Network\" |
    ForEach-Object {
            DriveLetter = $_.PSChildName
            RemotePath = (Get-ItemProperty $_.PSPath).RemotePath
    } | Export-Csv $TxtPath -Force

Below you will find the result -> a CSV file.


Below you will find the script that has to be executed.

#Map network drives from file
$netdrives = Import-csv $TxtPath
foreach ($drive in $netdrives){
New-PSDrive -Persist -Name ($drive.DriveLetter) -PSProvider "FileSystem" -Root ($drive.RemotePath)

Enclosed is the displayed result:


In this short tutorial you learned how to migrate network drives easily.

If you want to learn more about the correct way to deal with network drives with PowerShell, then follow the link below:

Understanding and Building New PS Drives in PowerShell

And don't forget..... -> Share your knowledge.