Description: This AppNote details different use cases for launching application installations through the ZENworks 10 Configuration Management bundles. This would help to understand how a ZENworks Configuration Management administrator can configure the Managed devices within the Zone, so that the workstation end users can launch the software/application installations on a need basis. All screen shots used in this AppNote are taken with ZENworks Configuration Management 10.0.1.0 release.
Use Case 1: To copy and launch windows installable files on a ZENworks Configuration Management workstation using the “Copy Files” action.
Note: Host Name of the source device need to be resolved on console and target workstations. Administrator can share the location of executable and can provide the UNC path of shared location.
In “Destination directory” field, provide the path on target workstations (where installable files need to be copied).
Note: Host Name of the source device need to be resolved on workstations. Administrator can share the location of executable and can provide the shared location.
Tip: Configure “Copy Option” such as “Copy If Does Not Exist” to avoid network traffic and redundancy
Example of “Select Files” dialog box is as shown Figure 1-B
Tip: For mandatory installations, configure Bundle Distribution, Launch and Availability Schedules so that the installation of application is triggered as per the schedule without any user intervention.
After the Bundle is distributed to the ZENworks Configuration Management device, Bundle Shortcut (locations are as per the configuration in Figure 1-D) is available to the user to launch the Installation. Example of the Bundle shortcut in ZENworks Application window is as shown in Figure 1-F.
Note: Host Name of the source device need to be resolved on console workstation. Administrator can share the location of executable and can provide the UNC path of shared location.
In “Destination directory” field, provide the path on target workstations (where installable files need to be copied).
Upload executable file to the primary server
Provide the Destination path on workstations
Tip: Configure “Copy Option” such as “Copy If Does Not Exist” to avoid network traffic and redundancy
Tip: For mandatory installations, configure Bundle Distribution, Launch and Availability Schedules so that the installation of application is triggered as per the schedule.
Figure 3-B UNC path input for “Launch Windows Executable” Action
Note: Folder containing the installable file on the source device should be shared.
Example: If “Jre_Inst.exe” is in “installables” folder (which is shared) of Source device 1.1.1.1, then the command should be input as shown in Figure 3-B.
Note: While associating Bundle to the Devices, Configure the Bundle Shortcut location, using which user can launch the installation.
Tip: For mandatory installations, configure Bundle Distribution, Launch and Availability Schedules so that the installation of application is triggered as per the schedule.
Assign the created bundle to ZENworks Configuration Management Devices/Users with shortcut location configured
Configure Distribution and Availability Schedules as per the requirement
If any mandatory installs are there, Administrator can configure the following: a) Self Extracting (Silent install) executable file path in “Command” field of Figure 3-B b) Bundle launch schedule.
It's beyond me why you opt for this option (especially if you use jre as an example), instead of using MSI technology which in the end then gives you all the options of uninstalling, self-repair, updating etc. Fire and forget never leads to proper application management on a Windows desktop. Just my 2 cents though :-)