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.

Walkthrough: Dynamically organizing assets with smart groups

This topic walks you through the process of organizing servers into a dynamic groups using a BMC BladeLogic Server Automation (BSA) feature called smart groups. It includes the following sections:

The video demonstrates the process of creating smart groups and nested smart groups.



Smart groups are groups for which you define membership conditions based on object properties. You can create smart groups for most types of objects in BMC Server Automation, including servers, jobs, and depot objects. For example, you can define a condition saying a smart group contains all servers with an operating system of Windows.

Defining a dynamic collection of servers can be extremely useful. For example, you can define one group of servers with active RSCD agents running Windows 2008 and another group running Windows 2008 R2. Then you could use these groups as dynamic targets when you deploy patches for each of those operating system versions.For more information and details about smart groups, see Defining a smart group.

What do I need to do before I get started?

Make sure you have the BSA Console installed on your workstation, and that you've got the appropriate level of permissions to create smart groups.  

For this walkthrough, you log on as BLAdmin, the default superuser for BSA. Note that in live deployments, BMC recommends that you grant access based on roles with a narrower set of permissions. 

How to organize assets with a smart a group

This walkthrough demonstrates how to create a smart group that contains all Windows servers with an agent that is running.

 StepExample screen (click to enlarge)

In the Servers folder, select the location where you want to create a smart group, right-click, and select New > Server Smart Group.

A dialog opens that lets you define the rules for membership in the smart group. 


For Name, enter a name for the smart group. In this case, we call the smart group Windows. Optionally, enter a description.


In the bottom half of the dialog, there is a row that represents a rule for smart group membership. Using that row, take the following actions:

  1. Leave the first drop-down list alone. It should say Server.
  2. In the next drop-down list, click Select Property . A list appears. Scroll down and select OS.
  3. Leave the next drop-down list alone. It should say equals.
  4. In the next drop-down list, select Windows.
  5. In the next drop-down list, select AND.
    Selecting AND means we want all rules to be satisfied for membership in the smart group.
  6. Click Apply changes. The criteria appears in text form rather than a series of drop-down lists.

Create another rule by taking the following actions:

  1. Click Add New Condition. A new row appears that duplicates the previous row.
  2. Double-click the new row. The options for this row now appear as drop-down lists.
  3. In the second drop-down list, click Select Property and then select AGENT_STATUS.
  4. Leave the other drop-down boxes alone. They should say equals and agent is alive
  5. Click Apply changes .
5Click Finish. A smart group named Windows appears. If you expand it, the smart group shows all servers with a Windows operating system and a function RSCD agent.

Wrapping it up

You have now learned how to set up the rules necessary for using smart groups.

Where to go from here

Now that you know how to create smart groups, you can move on to provisioning servers with BSA.

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