Planned for 2 years and no updates on it yet?
This would be extremely helpful for running scripts on a machine based on-the-fly. For example, if you have a managed install that is failing repeatedly, you can go into the inventory and right from the inventory choose to run a manual script that will correct the issue.
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.
501 votes for something that should already have happened years ago, and no further response since 02/2015. People are moving away from 32-bit. If anything, support for 32-bit should be the one getting the short end of the stick here!!
This isn't only recommended, it's practically mandatory. The amount of effort required to break out of the 32 bit windows environment is more than writing the original script most times and many software packages need to be called as 64-bit in order to function properly. Perfect example: the SPSS application installs fine as 32 bit, but it internally also calls a C++ redistributable install based on the detected OS. Since the KACE agent reports a 32-bit environment it runs the 32-bit installer instead of the 64-bit installer and the result is the application won't load. Please add this ASAP!!!
This would be an amazing thing to have. As it stands now I have to create a custom patch schedule and add the machines to it to force patching individually.
Thank you for your suggestion. I have put this in our product feature backlog. Please vote for this feature if you are interested so we can move it up the priority list. If a workaround is discovered, it will be posted here.
When I used MDT to image machines, we could trigger an OS reload by a VBS script that was built into the process. This same script allows us to run post-install tasks we had created for testing. While I love the K2000 and it is much easier than MDT (plus it images Mac OS), this is a huge loss in features for us. Please add this ASAP!!!
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.