I have an application which can execute a powershell script on remote windows machine. I am trying to map a network drive using a powershell script. When the same script executed at the endpoint, script works fine and able to map a network drive. But when the same script executed from my application, mapping a network drive done but as a disconnected network drive.

Now, my observations: I found that My application is executing the script with NT Authority\System account. May be because of this, mapped network drive is visible to a specific user as a disconnected drive. am I correct!!?

Now, the problem: What I can do to map a network drive available for all users? or Can I run my powershell script as a specific user, sothat drive will be mapped to that user only?

Anyhow, I have already tried running my powershell script as a different user from my application using Start-Process and Invoke-Command, it throws an error, says run winrm quickconfig which also did not work.

Any help? Appreciated!!

  • What is the Powershell version on the remote machine ? What OS and edition do you run there ? – Razvan Zoitanu May 22 '15 at 12:41
  • It's Windows 7 SP1 professional edition, Default version of powershell, it is v1.0 – Pydev May 22 '15 at 13:02
  • @Pydev: I believe the default version of PowerShell on W7 is v2.0. – James Ruskin May 29 '15 at 10:30

When mapped from NT Authority\System the drive will show as disconnected, but it should work: Map a network drive to be used by a service

NOTE: The newly created mapped drive will now appear for ALL users of this system but they will see it displayed as "Disconnected Network Drive (Z:)". Do not let the name fool you. It may claim to be disconnected but it will work for everyone.

Moreover, mapping a drive using NT Authority\System is the only (although not officially supported) way to make a network drive available for all users.

If you want to map a drive for specific user, you'd have to run PowerShell as a different user. But it also means that you'd have to get credentials for that user.

This can be mitigated using token manipulation, but it's tricky. See Invoke-TokenManipulation function and it's ImpersonateUser parameter.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.