How to create a custom package to deploy software on Windows devices?

Components required for Software Distribution:

• Software Distribution License

• The administrator must be having View, Manage and Assign Capabilities for the Application Management Module

• The installation file for software (.exe,.msi,.vbs, etc) that is provided by the manufacturer.

• A command line to install the software manually.

It is recommended to use the package creation wizard as takes through the one by one step.

 1. Set the package Factory:

A Windows package must be built in a Windows package factory.

By default, the master will be set as the package factory but any windows device can be set as a package factory. In the SaaS environment, the master being a linux device, the package factory is usually the First Relay. The executable file must be kept on the package factory device
Select the Package Type as 'Custom"

2. On the next window, name the package and leave the other parameters as it is.

3. Installation Options:
The next window is about defining the destination path and command line.

• Destination Path: Set the path to which the files stored in the package should be extracted before the installation starts.

• Run Command: Enter the correct command line to run the file remotely. Make sure the command line consists of the path where the file is copied on target. In this example, the destination path is C:\temp and hence the command line is C:\temp\npp.8.4.2.Installer.x64.exe. For silent installation, give the appropriate option.
  This field can be left empty if one intends to use the "Execute Program" operational rule step later to deploy the application, An example of this is shown in the KA: Client Management: How to create a custom package to deploy an msi.

• Run in its context: This option allows the installer to run in its own environment (if checked) or not (if unchecked). This has an impact on the variables it could use to run. The first thing to do if a package fails at installation although the command line works manually is to go to the package in the packaging factory, change the status of the option "Run in its context" then republish the package and test it again. This is often the cause of the issue, along with the possible failure because the package should actually run as the current user and not as the System by default.

• Overwrite:  Proceed with caution as the package could contain a windows dll in an older version than the actual version of the system, as an example.

4. Then Add the executable file. Add files option opens the file explorer of the Package factory device where the file is placed.




5. Publish the package:
This will make it available in the main node 'Packages' and be ready to be assigned to devices.  It can be published to the master or the respective Relay of the target devices. In this example, the package is published on Master.



6. Select the 'Deploy the Package' option




7. The package distribution wizard will be opened. Select the target type as required. Device Groups/Devices.
Choose the required assignment type:

• Install that package on the assigned devices

• Publish the package to MyApps for on-demand installation

In this example, the package is installed on the devices. If the schedule for the installation is required, uncheck the  'Default Schedule' box.



Assign the required Devices/Device Groups on the next page and package transfer will start on them followed by the execution.

The package can also be published on master and distributed with the operational rule.

Here is an example:

After publishing the package, select 'Create an Operational rule' option from the below popup.



It will open up the Operational rule distribution Wizard.



In the next Window, 'Install Package' is added by default with the package created. Add one more step and select any of the below as required.



Put the correct command in the below path. Add a parameter for a quiet installation so that the remote user won't see any installation message box.



Then assign the rule to the target devices/Device groups.
See also:  BEST FAQ on BMC Client Management Package Deployment Issues