I want to see an option to Mark Bundles as already installed on some devices.
So I can prevent big installation-bundles from beeing applied when they are already installed.
This could be helpfull in diffrent situations where the the software of a client is not clean installed with zcm.
Examples are when you clone a workstation, or when you install zcm on a new machine where some software is already installed out of the box.
by: Christian K. | over a year ago | Application Mgmt
Comments
also usefull wenn zcm reports the installation incorrect. happens with some buggy installers.
I know this would require editing bundles but how about adding another tab for "Installed Rules".
In this tab we could enter how ZENworks knows the bundle is installed. Maybe add the same options are in the Requirements tab. Ex. If this file exists and is version X.XX then the bundle is installed. Or If this registry key exists and this file exists then the bundle is installed.
Update 3 - still not possible.
please vote.
I do not see why this should be implemented as a new feature while you already have anything you need to accomplish this at your hands.
Simple approach: use system requirements for the bundle and check for the presence / version of an executable file your bundle would install.
I would plainly "un-vote" this, if I could.
If I put a system requirement to disable the bundle if the software is already installed (e.g. EXE file exist) than the whole bundle is blocked and neither launch nor repair nor deletion could be performed.
The same happens if I roll out e.g. an Office bundle and after installation on 200 out of 2000 PCs I notice a typing error in a message box or missed the acceptance of a return code for reboot than I have no possibility to change anything on the install tab without reinstalling on 200 PCs.
Granted, but this is a different requirement. You basically want to change the content of a bundle without bumping up its version.
https://www1.v1ideas.com/MFI/novell-zcm/Idea/Detail/592
See also:
https://ideas.microfocus.com/MFI/novell-zcm/Idea/Detail/592
I definitely see a valid use case for this. Just one example: On some machines, Office is already installed before they are integrated into the system. Now, with the way things are now, I can do two things: 1) Uninstall Office and let my Office bundle reapply. 2) Change System requirements so bundle is not applicable if already installed. 2) has its caveats. In reporting, Office will be listed under "not applicable", even though it's installed. Setting my Office Bundle to "uninstall" will do nothing on said machines, since ZENWorks thinks Office is not installed there. If I want to create another bundle (e.g. an Office add in) and want to install it using a "only install after Office installation has run" rule, I can't do it that way.