There are a couple of ways to approach this – I think the current thinking would be to add a “type” to each script and allow users to define them and then use the View By function. Thoughts?
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.
Powershell support for SMA online scripting is targetted for a 2020 release.Adam Nerell commented
This really should be present in a client management solution year 2014...
Thank you for your interest in this feature request. Please continue to vote this up to move it up in priority for future release consideration.