The need to thaw to apply patches and updates greatly increases the complexity of this request. We will continue to watch the votes on this to see if this is something we will pursue.
We are investigating using OMCI to support this functionality
Phase one completed in SMA 9.0 on 8/20/2018. Please let us know what else you would like to see next after you check it out.
This is planned for this year.
Throwing my votes at this topic in general.
Powershell support for SMA online scripting is targetted for a 2020 release.
Specific features that involve PowerShell that I believe KACE could be more efficient with:
Managing PowerShell scripts using the Script UI.
- I have many PowerShell scripts sitting on an open fileshare because I cannot write PowerShell directly within KACE and push it to my end-points
- If I push a script with slow-performance due to network speed the agent will report back as a failure BEFORE the PS script has finished running, resulting in a false failure in the 'Run Now Status' page.
- Calling 64-bit processes within PowerShell using the 32-bit agent causes some really unreliable behavior. This is mostly due to the agent though, and I know there is another thread pushing heavily on a 64-bt agent.
Other ways I can see KACE managing our Win clients PowerShell is the ability to push PowerShell versions to machines through the patching service.
These of course are just some ways and I will be the first to say that calling PowerShell scripts through the agent works just fine. However.. I would really like to move away from relying on Batch files to call these scripts.
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.
I find that calling 64-bit processes through the 32-bit KACE agent results in broken functionality and "work arounds" are either hit or miss. One of my projects involved Bitlocker and this issue caused me much grief.
I am also understanding to the KACE teams reluctance to release a 64-bit agent. In the mean-time I believe other solutions (such as making the agent aware of 64-bit processes) would be a great step forward.