Configuring Remedyforce for upgraded discovery licenses

For more information about adding a user, see Creating an Administrator in the BMC Client Management documentation.

Ensure that you provide correct security permissions and capabilities to these users in BMC Client Management based on their need to run CMDB actions and deploy operational rules. Then, share the BMC Client Management credentials with the staff members. Staff members need to provide these credentials only once.

To be able to manage discovered devices from Remedyforce, an agent must run on the discovered devices. You can create roll outs that will install agents on a group of devices. When you create roll outs, select the scanner to which the devices are visible as Rollout Server and parent as either the Discovery Server or one of the relay. Agents installed on discovered devices communicate with the parent. 

Relays are devices (with agents running) that can forward data in both upstream and downstream directions for software distribution and other operations to execute. Relays act as an intermediary between the devices that have agents running on them and the Discovery Server. For more information, see Architecture in the BMC Client Management documentation. Scanner installed by using installers provided on the Discovery Setup & Configuration > Scanner Roll-out page are relays by default.

For more information, see Configuring for agent rollout, Rolling out relay agents in a cloud environment, and Rolling out client agents in a cloud environment in the BMC Client Management documentation.

Note: To install agents, do not use the links to install scanners provided on the Discovery Setup & Configuration page. If you use these links to install agents, the devices start appearing in the Scanner List.

For communication between installed agent and its Relay, ports 1610 and 1611 are used by default. Therefore, you must open these ports on discovered devices on which an agent is rolled out.

For more information, see Relay List and Rolling out agents on site.

1. Create Operational rules. While creating an operational rule that you want to deploy from Remedyforce, in BMC Client Management ensure that you select Available in integrated solutions in the Deployment from External Integration list in the Operational Rule Creation wizard.
2. Map operational rule status with task status.
3. (Optional) Automate the deployment of operational rules in Remedyforce – Creating-a-Task-template-to-deploy-an-operational-rule, Creating an Incident template to deploy an operational rule, Creating-a-Request-Detail-template-to-deploy-an-operational-rule, and Creating-SRDs-that-require-operational-rule-deployment.
4. Create an approval process for deploying operational rules.

Mapping operational rules status with task status

When tasks with operational rules are executed, the status of operational rule is updated. To update the status of the tasks that deploy operational rules when the operational rules are deployed, map the operational rule status with task status. Remedyforce fetches the status of operational rules from BMC Client Management.

The following mapping is provided by default:

To map operational rule status with task status

1. On the Discovery Setup & Configuration page, click the Operational Rule Configurations tab.
2. In the Map Operational Rule Status to Task Status section, map the task status to operational rule status.
   You can retrieve operational rule status from the BMC Client Management Console and also fetch logs of the jobs run to deploy these operational rules.
3. Click .