The powershell script works independently, but when I run it from the c# runspace I get the following error:
{"The term 'Get-RDConnectionBrokerHighAvailability' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."}
Any ideas why Powershell can't use this cmdlet when invoked via my c# app?
Thanks,
PowershellC#
Last Comment
SubSun
8/22/2022 - Mon
SubSun
My two cents :
Check the version of PowerShell when you invoke it from you app. I have see similar issues with our orchestrator server .net activity tasks, as it invokes/executes it’s commands still in PowerShell 2.0 instead of PS version installed on the computer.
As a work around, we are running the script in a sub process, example..
$Result = PowerShell { <Script Here> }
Check and see if there is a difference when you try these commands inside your app..
PowerShell {$Host.Version}
$Host.Version
Or it's possible that the RemoteDesktop module file is not accessible for the user account which you use to run the application/script.
To check the access issue, copy the module folder from default module path C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ to C:\Users\<UserName>\Documents\WindowsPowerShell\Modules and try to run app..
Dustin Saunders
ASKER
That seems to work for executing the code, but it doesn't pass the variables through- is there a way I can dump the variables I pass to the script in the sub process? (doesn't look like I can add any -args)
Check the version of PowerShell when you invoke it from you app. I have see similar issues with our orchestrator server .net activity tasks, as it invokes/executes it’s commands still in PowerShell 2.0 instead of PS version installed on the computer.
As a work around, we are running the script in a sub process, example..
$Result = PowerShell { <Script Here> }
Check and see if there is a difference when you try these commands inside your app..
PowerShell {$Host.Version}
$Host.Version
Or it's possible that the RemoteDesktop module file is not accessible for the user account which you use to run the application/script.
To check the access issue, copy the module folder from default module path C:\Windows\system32\Window