Always listen to what Jrv tells you as he is a super smart guy and has helped me out loads in the past.įirst of create a file containing a password that looks like garbage to the average jo Here is a kind of way (bare in mind anyone with a bit of knowledge can decrypt encryption) but if the process is not too sensitive. Then looking at firing off PowerShell by calling this dos batch file as it were, but this is messy (or at least I have not found a good enough dos based utility) I have seen some options for encrypting password when using DOS batch file RunAs option e.g. So I wanted a way to start powershell.exe but as a specific username and password The thing is when I wrap too much code in the invoke-command as above PowerShell does not like it } -credential $cred -computername $env:computername code to store credential without displaying password in clear readable format.

Therefore I thought about warping the whole script in an invoke-command like so I have seen a couple of ways to store the get the store the $cred in a way that is not easy (at least at first glance) to work out the password, so this helps to an extentįor example within the script where I need to connect to a remote machine (as above) I can store $cred and use as above, however there are lots of places in the script where I need to user (normal user) to have more rights, therefore this would mean Get-service -computer remote1 -credential $cred I know you can use the credential object like so I see some examples of user Start-Process with the RunAS option but this is to RunAs Administrator as far as I can see not a specific user I need a way to run a PowerShell script as a different user (I do not mean RunAs Administrator)

Powershell runas administrator