Powershell support for SMA online scripting is targetted for a 2020 release.Matt Stork commented
Native to me would be similar to the option to run a batch file as a step in a script task. So I would hit the drop down and after "Run a batch file..." I would see "Run a PowerShell file..." I can then paste my PowerShell code in and KACE takes care of making sure all the flags to powershell.exe are correct.
A possible separate issue is when I call Powershell.exe on a 64-bit machine, the 32-bit Powershell.exe runs because KACE is a 32-bit process and Windows tries to be "helpful." 32-bit PowerShell does not have access to the Wow6432Node of the registry and other similar items. Very annoying.
Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.