Share This:


BMC Client Management (BCM) is an advanced endpoint management tool which provides a reliable and easy way to manage devices and Software deployment accross a network.


By leveraging the BCM connector in the DWP Catalog, we can choose to install Software on particular devices from a Service Request. In this Blog, I'm going to show you how to get started with a simple Firefox Software deployment.


Figure 1.


                   Mobile                                                                                                                             Desktop


BCM Configuration


As a first step, BMC Client Management must recognize the DWP user so make sure the relevant users are also present in BCM.


Figure 2.

Once the BCM Agents have been deployed to the managed end points you're ready to upload Software and create a package for distribution.

Select the option to associate an Operational rule as this is what's called within the Catalog Workflow

The easiest way to do this is by using the Package Creation Wizard.


Figure 3.


In the above example we use the following command to install Firefox in the background.


  C:\temp\FirefoxSetup.exe /S


Catalog Configuration


As BMC Client Management uses SSL, we'll need to copy it's certificate and import it to the java keystore on the Cataog Server.

By default, the certificate (bcm.crt) is located in "trusted\<ID>\" directory of the BCM Server

The following example imports the certificate into the java keystore which the Catalog Server is running against.

./keytool -import -alias bcm2alias -file "/opt/jdk-11.0.2/bin/bcm.crt" -keystore "/opt/jdk-11.0.2/lib/security/cacerts"

Once you have trusted the certificate from the command line, restart the Catalog Server and configure the BCM Connector with the URL of the BCM Server & credentials.


Figure 4.


Now that we have successfully connected to BMC Client Management, we need to import the available packages (Figure 3.) by choosing the Catalog Import Options for BCM, importing and publishing it.


Figure 5.


Workflow Design


Once we have imported the package, we can begin building our workflow.


Figure 6.


To make this example a little more realistic, I've added in an approval step to stop the Software from being deployed until it's approved by the person's Manager (as defined in BMC Remedy ITSM).


To learn more about configuring approvals, please refer to our Digital Workplace Advanced documentation.

Figure 7.


As I intend deploying on more than one device I'm using a sequential muti-instance loop here. You can see I've mapped the end user device question and we'll be referring to this question as "deviceloop" within the Deploy workflow action.


Figure 8.


The "Depoly Oprule On Device" action initiates the Software distribution by assigning the chosen device to the rule.

Make sure you use the service broker context > service > External ID for the Operational Rule and the local "deviceloop" variable for Device ID.


Figure 9.

Once we have deployed the Software we'll need to instruct the workflow to wait until the deployment has completed. We can do this by mapping the output from "Deploy Oprule on Device".


Figure 10.

As a optional step, we can update the Service Request title to reflect that the software has installed. In this example the Request name will change to "Sofware Deployed".


Figure 11.


Finally, once the Software has been installed we will will instruct the workflow to mark the Service Request as "Closed".


Figure 12.





Figure 13.


When creating the question make sure to choose the Dynamic option followed by "Map to Dataset". This will allow you to select "Devices Of User" which will retrieve the devices from BCM.


Once you have completed the questionaire, you should be ready to submit and deploy the Software !


Figure 14.


Let's take a look at the lifecycle of the Request submission.


  • User opens the "Firefox" Service Request and is presented with the available Devices.
  • Relevent devices are selected and the Request is submitted for Approval.
  • Manager Approves the Request.
  • Software is automatically deployed to the Devices.
  • Once the Software distribuition has completed, the Service request title name changes and the Request is closed.


Figure 15.



To check the progress from BCM select the package and choose "Devices". As each assingemnt has completed you'll see the status change from "Assigned" to "Executed".


Figure 16.



Further Reading


If you would like to learn more about this connector, please refer to our Service Connector documentation.


For information on BMC Client Automation documentation, please check here.