Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

How to use Compliance with site-specific values

This topic was edited by a BMC Contributor and has not been approved.  More information.

Contributor content

This topic was created by a BMC Contributor and has not been approved. More information.

This example demonstrates how to perform Compliance on the DNS Client Settings using site-specific values for each site.


The example shown here is for Windows target servers. It can be adapted to other platforms by making necessary adjustments. Various product-specific concepts around Component Instances and PSI Values remain the same.


When using Compliance, we often need to have the same Component defined on all servers with different site-specific values that are used for both Compliance and Remediation. This can be accomplished using PSI (Property Set Instance) values to create component instances based on a server property that defines each site or location. The PSI values defined per site can be used for both Compliance checking and for Remediation deployment in the case of non-compliance.

Component instances that use PSI values are typically used for multiple components on each target server. This use case typically will result in having a single component instance per server.


Knowledge of creating basic Component Template, Packages used for Remediation, and Discovery/Compliance Job Creation is assumed/required. This document includes only the key items that are required for the multiple component instance for site-specific values when used with Compliance and Remediation.


The following steps are the key items required to make the site-specific multiple components functional.


This example is based on using the Extended Object "Network Configuration" that can be found as a reference at the end of the document.


Adding Local Properties to the BLPackage first will make them available as local parameters when we attach the remediation package in the Component Template.

Add the Required Local Properties


Default value shown for local property LP_DNS_NAMESERVER-3 is OPTIONAL.

Define Local Properties in EXTERNAL CMD Item

Cmd Content

wmic nicconfig where (IPEnabled=TRUE and DHCPEnabled=FALSE) call setdnsserversearchorder ("LP_DNS_NAMESERVER-1","LP_DNS_NAMESERVER-2","LP_DNS_NAMESERVER-3")

Component Template

First, ensure that both the "Deploy" and "Compliance" options have been selected.

Note we are using the "Network Configuration" Extended Object in the included "Parts" in this example

Add the Required Local Properties


Default value shown for local property LP_DNS_NAMESERVER-3 is OPTIONAL.

Define PSI with values for each Site

Add the first "Site Specific" PSI with values


Here is where the defined values for the site that will be used for both Compliance and Remediation are specified.

Example of multiple PSI site-specific definitions

Add Local Property used for Discovery


Using a property value that is defined in each PSI in discovery is how the Component instances are created.

Examine Compliance rules

Add Local Properties to Compliance Rule

Define PSI Mapping in Auto-Remediation


The Property mapping defines what values are passed from the component to the parameters in the BlPackage.


Multiple Components will be created based on matching the PSI values defined in the CT Discovery rules.

Example of Component names for multiple instances;

  • DNS Settings (Windows) [USA Houston] (server1.bmc.com)
  • DNS Settings (Windows) [USA Houston] (server2.bmc.com)
  • DNS Settings (Windows) [USA Phoenix] (server3.bmc.com)

Format of Component name when multiple instances are used;

CT Name

Instance Name

Server Name

DNS Settings (Windows)

[USA Houston]


DNS Settings (Windows)

[USA Houston]


DNS Settings (Windows)

[USA Phoenix]



Compliance jobs should run normally and use the Site Specific values specified in the Compliance rule that are defined in the particular PSI used for each Component instance.


The trick to getting Remediation to use the PSI values is to make the Component instances the target of the Remediation Deploy job.


The option "Use Servers as Targets" in the Remediation job for Manual OR Automatic Remediation must be deselected. In other words, the Remediation Deploy job MUST target Components for this to work.

Reference - Network Connections Extended Object

The EO used in this example is defined below:

Was this page helpful? Yes No Submitting... Thank you