New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE

Install executable action

Idea ID 2782203

Install executable action

As an administrator I want an action that is an "Install executable" action that allows me to specify the current executable launching options and the ability to upload the executable and optionally all files in the same directory (similar to Install MSI) and then I expect that the executable is run directly from cache.

Happy Path Scenario:
1) I create a bundle
2) I add an Install executable action and browse to an executable.
3) I can optionally choose to upload all of the content in the same directory as the executable
4) I specify the normal launch executable parameters
5) When the bundle is transacted the content is downloaded and then the executable is executed
6) The bundle cache is cleaned up as normal to remove the install files as necessary
9 Comments
Absent Member.
Absent Member.
Great idea! I see the following benefits when it is possible to launch a file directly from a bundle: - More efficient bundles - No more extra file share to manage. - Use one ecosystem (ZCM Control panel) with the benefits of (off site) satellite servers. - Use less hard disk space
Absent Member.
Absent Member.
Isn't this the same as this idea: Launch executable (or other file) from Bundle directly.
Absent Member.
Absent Member.
Yes, it is very much the same. Jason (the product manager) already confirmed this on the related idea: https://ideas.microfocus.com/MFI/novell-zcm/Idea/Detail/568.
Absent Member.
Absent Member.
Is this not already sort of possible? Right now what I sometimes do is make a install directory action (content from repo), then run the executable from the folder where I installed to, for example c:\windows\temp\mybundle. Then after successfull installation, i simply define a last step, file removal. I know, it is 3 steps instead of your proposed one step, but it works great.
Absent Member.
Absent Member.
Yes, Rene. This is exactly the same but the idea is to make this more automatic & efficient 😉
Absent Member.
Absent Member.
This would be awesome. This would simplify actions for a number of my bundles. Instead of the install directory then launch executable, this install executable would be easier to manage.
Knowledge Partner Knowledge Partner
Knowledge Partner
One more thing. It should be possible to use any file in the content cache of agiven bundle in any possible way ZCM supports, thish shouldn't be limited to run executable action. The way to make this work of course would be to introduce some sort of variable or special syntax to target a file inside the content of the current bundle. For instance, I want to upload the Groupwise Client directory *once*, including the mst file for groupiwse.msi, and I want to be able to: 1. Call any .msi that comes bundled in the GW directory, like .g wse3.msi. 2. Start any executable in an install action without having to seperatly download it again to the workstation, like the various VC runtime exes that come bundled. 3. Specify the already included mst that is in the uplodaed directory, instead of having to upload it again seperately. And so on...
Absent Member.
Absent Member.
Has there been any decision made on whether the "Install Executable" option will be implemented in ZENworks?
Absent Member.
Absent Member.
Install executable action has been implemented as part of ZENworks 2020. It is available as a separate action with-in Actions sets.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.