← Back to context Comment by flamtap 8 years ago Please say powershell... Please say powershell... 3 comments flamtap Reply naikrovek 8 years ago cmd.exe, but it is probably configurable, and you can always just type 'powershell' to get it. scott_karana 8 years ago Invoking via cmd is not comparable at all.If it was direct to Powershell, you could pipe objects directly into remote cmdlets. joeyaiello 8 years ago Posted above, but just in case, we also support this with PowerShell Core 6: https://github.com/powershell/powershell/tree/master/demos/S...
naikrovek 8 years ago cmd.exe, but it is probably configurable, and you can always just type 'powershell' to get it. scott_karana 8 years ago Invoking via cmd is not comparable at all.If it was direct to Powershell, you could pipe objects directly into remote cmdlets. joeyaiello 8 years ago Posted above, but just in case, we also support this with PowerShell Core 6: https://github.com/powershell/powershell/tree/master/demos/S...
scott_karana 8 years ago Invoking via cmd is not comparable at all.If it was direct to Powershell, you could pipe objects directly into remote cmdlets. joeyaiello 8 years ago Posted above, but just in case, we also support this with PowerShell Core 6: https://github.com/powershell/powershell/tree/master/demos/S...
joeyaiello 8 years ago Posted above, but just in case, we also support this with PowerShell Core 6: https://github.com/powershell/powershell/tree/master/demos/S...
cmd.exe, but it is probably configurable, and you can always just type 'powershell' to get it.
Invoking via cmd is not comparable at all.
If it was direct to Powershell, you could pipe objects directly into remote cmdlets.
Posted above, but just in case, we also support this with PowerShell Core 6: https://github.com/powershell/powershell/tree/master/demos/S...