$cred = Get-Credential New-PSDrive -Name "Z" -PSProvider FileSystem -Root "\\server\share" -Credential $cred -Persist The Get-Credential dialog is secure, but for automation you can build a credential object (though storing passwords in scripts is still discouraged). PowerShell uniquely allows mapping a network share to a local folder path instead of a drive letter—something net use cannot do directly:
net use \\server\share That’s right—you can net use a UNC path with no drive letter. It won’t appear as a drive, but it will be an authenticated, persistent connection that applications can still access via the full UNC path. Mastering net use and New-PSDrive turns drive mapping from a point-and-click chore into a scriptable, repeatable, and automatable operation. Whether you are deploying 200 workstations, maintaining a headless server, or simply tired of typing passwords into a dialog box, the command line offers speed, control, and depth that the GUI never will. map drive from command line
But for IT professionals, power users, and automation enthusiasts, the graphical approach is a bottleneck. It’s slow, inconsistent across remote sessions, and impossible to script. The command line—specifically net use and, more recently, PowerShell’s New-PSDrive —offers speed, precision, and repeatability. Mastering net use and New-PSDrive turns drive mapping
For decades, the average Windows user has mapped network drives the same way: open File Explorer, right-click "This PC," select "Map network drive," pick a letter, type a path, and click "Finish." It’s visual, intuitive, and serviceable for the occasional connection. inconsistent across remote sessions