When an external drive is connected to the computer, PowerShell automaticallyĪdds a PSDrive to the file system that represents the new drive. For more information about dot-sourcing, see For best results, to forceĪ new drive to persist indefinitely, add the Scope parameter to your command, and set its Want the drive to persist indefinitely, you must dot-source the script. If you're running New-PSDrive inside a script, and you When your command is scoped locally, noĭot-sourcing, the Persist parameter doesn't persist the creation of a PSDrive beyond the

Mapped network drives must have a drive-letter nameĪnd be connected to a remote file system location. Tools, such as File Explorer and net use. They're saved in Windows and they can be managed by using standard Windows Unlike temporary PowerShell drives, Windows mapped network drives aren't You can use the Persist parameter of New-PSDrive to create Windows The following features were added to New-PSDrive in PowerShell 3.0: Windows Management Instrumentation (WMI), Component Object Model (COM), Microsoft. You can change locations into the drive,īy using Set-Location, and access the contents of the drive by using Get-Item orīecause temporary drives are known only to PowerShell, you can't access them by using File Explorer,

Store, just as you would do with any mapped network drive. You can use temporary PowerShell drives to access data in the associated data

They can have any name that is valid in PowerShell and can be mapped to any local Temporary drives exist only in the current PowerShell session and in sessions that you create in theĬurrent session. Registry key, and persistent Windows mapped network drives that are associated with a file system With a location in a data store, such as a network drive, a directory on the local computer, or a The New-PSDrive cmdlet creates temporary and persistent drives that are mapped to or associated Creates temporary and persistent drives that are associated with a location in an item data store.

Netdrive alternative