Drift7.5 UserGuide

BMC Configuration Drift Management 7.5.
00
Users Guide
March 2009
www.bmc.com
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC Telephone 713 918 8800 or Fax 713 918 8000
2101 CITYWEST BLVD 800 841 2031
HOUSTON TX 77042-2827
USA
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000
If you have comments or suggestions about this documentation, contact Information Design and Development by email at
doc_feedback@bmc.com.
Copyright 2009 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent
and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and
logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
IT Infrastructure Library is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc.,
under license from and with the permission of OGC.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the
U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC.
Java and Javadoc are trademarks of Sun Microsystems, Inc., in the U.S. and other countries.
UNIX is the registered trademark of The Open Group in the U.S. and other countries.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is
subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted
rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF
THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to
restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and
DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX
77042-2827, USA. Any contract notices should be sent to this address.
Customer Support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer
Support by telephone or email. To expedite your inquiry, please see Before Contacting BMC Software.
Support website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at
http://www.bmc.com/support_home. From this website, you can:
Read overviews about support services and programs that BMC Software offers.
Find the most current information about BMC Software products.
Search a database for problems similar to yours and possible solutions.
Order or download product documentation.
Report a problem or ask a question.
Subscribe to receive email notices when new product versions are released.
Find worldwide BMC Software support center locations and contact information, including email addresses, fax
numbers, and telephone numbers.
Support by telephone or email

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or
send an email message to customer_support@bmc.com. (In the Subject line, enter
SupID:<yourSupportContractID>, such as SupID:12345.) Outside the United States and Canada, contact
your local support center for assistance.
Before contacting BMC Software

Have the following information available so that Customer Support can begin working on your issue immediately:
Product information
Product name
Product version (release number)
License number and password (trial or permanent)
Operating system and environment information
Machine type
Operating system type, version, and service pack
System hardware configuration
Serial numbers
Related software (database, application, and communication) including type, version, and service pack or
maintenance level
Sequence of events leading to the problem
Commands and options that you used
Messages received (and the time and date that you received them)
Product error messages
Messages from the operating system, such as file system full
Messages from related software
License key and password information
If you have a question about your license key or password, contact Customer Support through one of the following
methods:
E-mail customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>,
such as SupID:12345.)
In the United States and Canada, call 800 537 1813. Outside the United States and Canada, contact your local support
center for assistance.
Submit a new issue at http://www.bmc.com/support_home.
Contents
Preface 11
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Drift Management and Section 508 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 1 Introduction to Drift Management 17

What is drift?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
About Drift Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Drift Management and ITIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Basic concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Comparison job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Source dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Qualification set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Include set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Exclude set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Drift workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Common scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 2 Managing Drift Management permissions 27

Understanding Drift Management permission groups . . . . . . . . . . . . . . . . . . . . . . . . . 28
Using Drift Management with BMC Remedy Change Management and BMC
Remedy Incident Management permission groups. . . . . . . . . . . . . . . . . . . . . . . 29
Understanding instance permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Defining instance permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Examples of Drift Management instance permissions. . . . . . . . . . . . . . . . . . . . . . . 32
Creating users with Drift Management permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Creating groups to use with Drift Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using the Application Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Contents 5
Chapter 3 Getting started 39
Accessing Drift Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Example scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 1: Create a snapshot job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 2: Create a baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Step 3: Create a target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Step 4: Create a comparison job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Step 5: View detected drifts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 4 Creating snapshots 49

About snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Using an existing destination dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Creating a snapshot guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Overview of snapshot steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Creating a snapshot job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Modifying or deleting a snapshot job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Chapter 5 Creating baselines 57

About baselines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Overview of baseline steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Creating a baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Modifying or deleting a baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 6 Creating targets 63

About targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Overview of target steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Creating a target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Modifying or deleting a target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 7 Creating qualification sets and include and exclude sets 69

About Qualification Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Accessing Qualification Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating a qualification set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
AND or OR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Guidelines for qualification set option selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
About qualification sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Using classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Guidelines for using classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Guidelines for using attributes in a qualification set . . . . . . . . . . . . . . . . . . . . . . . . 74
Include and exclude sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6 Users Guide
About include sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Guidelines for using attributes in an include set . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Creating an include set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
About exclude sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Creating an exclude set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Guidelines for exclude sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 8 Creating and managing comparison jobs 79

About the Job Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
About comparison jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Comparison service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Types of comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Output of a comparison job (Drift Reports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Before creating a comparison job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Creating a comparison job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Managing comparison jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Canceling a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Checking the status of a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Modifying or deleting a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Scheduling a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Viewing job details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Viewing job history, job logs, and Drift Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 9 Viewing Drift Reports 91

About the Drift Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing the Drift Console data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing Drift Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Searching Drift Reports and Drift Report details . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Viewing Comparison Job details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Deleting a Drift Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Refreshing the data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Viewing the details of a Drift Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Viewing Configuration Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Viewing the CI in BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Viewing CI Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Viewing drifts on relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Viewing business services affected by a drift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Viewing change requests correlated with a drift . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Viewing incident requests correlated to a drift. . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Customizing the Drift Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Managing or remediating drifts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Contents 7
Chapter 10 Remediating drifts 103
Determining what caused a drift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Correlating a drift with a change request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
How is a drift correlated with a change request? . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Configuring drift correlation with a change request . . . . . . . . . . . . . . . . . . . . . . . 105
Viewing drifts correlated with a change request . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Remediating a drift. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Acknowledging a drift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Creating a change request from the Drift Console . . . . . . . . . . . . . . . . . . . . . . . . . 108
Creating an incident request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Chapter 11 Viewing Drift Reports from the Drift Dashboard 113

About the Drift Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Viewing the data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Viewing the most recent Drift Report activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Viewing Drift Report activity within a specific date interval . . . . . . . . . . . . . . . . 116
Viewing bar chart data in text format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Viewing Drift Report details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Customizing the data display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Selecting business services to view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Selecting baselines to view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Changing Drift Reports per Day schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Chapter 12 Using preferences 119

About preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Configuring the comparison or snapshot service for better performance . . . . . . . . . 120
Filtering displayed change requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configuring drift correlation to a change request relationship . . . . . . . . . . . . . . . . . . 122
Time window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Changing the default BMC Remedy AR System Administrator password. . . . . . . . 123
Appendix A Comparison service 125

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Initial loading of CIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Processing qualification sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Processing related classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Processing exclude and include sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Identifying CIs for comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Compare regular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Compare recursive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
One-to-One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Many-to-One. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Performing the last load and comparing attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Tagging CIs with detected drift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
8 Users Guide
Appendix B Context-sensitive Help 131
Baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Qualification Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Include Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Exclude Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Select a drift component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Snapshot Job Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Baseline Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Target Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Comparison Job Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Glossary 147
Index 151
Contents 9
10 Users Guide
Preface
This guide describes how to use the BMC Configuration Drift Management
application. This application runs on the BMC Remedy AR System platform and
consumes data from the BMC Atrium Configuration Management Database
(CMDB) application. Drift Management also integrates with the BMC Remedy IT
Service Management (ITSM) solution, specifically with the BMC Remedy Change
Management application, and the BMC Remedy Incident Management
application.
Audience
This guide is intended for the following IT professionals:
Configuration managers
System administrators
Network managers
Related documentation
The following table lists the documentation available for Drift Management.
Unless otherwise noted, online documentation in Adobe Acrobat (PDF) format is
available on product installation CDs or DVDs, on the Customer Support web site
(http://www.bmc.com/support_home), or both. You can order printed
documentation from the Customer Support web site.
NOTE
To access the support web site, you need a support contract.
You can access application help by clicking on Help links within the application.
Preface 11
BMC Configuration Drift Management 7.5.00
Title Document provides Audience Format

BMC Configuration Drift Procedures for installing Drift Administrators Print and PDF
Management 7.5.00 Installation Management.
Guide
BMC Configuration Drift Information about Drift Management, Everyone Print and PDF
Management 7.5.00 Release and open and fixed issues.
Notes
BMC Remedy Action Request Procedures for installing BMC Remedy Administrators Print and PDF
System 7.5.00 Installation AR System.
Guide
BMC Remedy Action Request Contains information about Administrators Print and PDF
System 7.5.00 Configuration configuring BMC Remedy AR System
Guide servers and clients, localizing,
importing and exporting data, and
archiving data.
BMC Remedy Action Request Contains information about the mid Administrators Print and PDF
System 7.5.00 Mid Tier Guide tier, including mid tier installation and
configuration, and web server
configuration.
BMC Remedy Action Request Topics on installation and Users and Print and PDF
System 7.5.00 Approval Server configuration of the Approval Server, administrators
Guide how to use the Approval Server, and
understanding the approval workflow.
BMC Atrium Core 7.5.00 Information about CMDB concepts and Executives and Print and PDF
Concepts and Planning Guide best practices for planning your BMC administrators
Atrium CMDB implementation.
BMC Atrium Core 7.5.00 Information about installing and Administrators Print and PDF
Installation Guide configuring BMC Atrium CMDB,
including permissions, class
definitions, reconciliation, and
federation.
BMC Atrium Core 7.5.00 Information about creating API Administrators and PDF
Developers Reference Guide programs, C and Web Services API programmers
functions and data structures, and a list
of error messages.
BMC Atrium Core 7.5.00 Combined index of all books. Everyone Print and PDF
Master Index
BMC Atrium Core 7.5.00 Information about new features and Everyone Print and PDF
Release Notes known issues.
BMC Atrium CMDB 7.5.00 Information about using BMC Atrium Users Print and PDF
User's Guide CMDB, including searching for and
comparing CIs and relationships,
relating CIs, viewing history, and
launching federated data.
BMC Atrium CMDB 7.5.00 Information about normalizing data in Administrators Print and PDF
Normalization and BMC Atrium CMDB and reconciling
Reconciliation Guide CIs from different data providers into a
single production dataset.
12 Users Guide
Related documentation
Title Document provides Audience Format

BMC Atrium CMDB 7.5.00 Hierarchical diagram of all classes in Administrators PDF
Common Data Model Diagram the Common Data Model (CDM),
including unique attributes and
applicable relationships.
BMC Atrium CMDB 7.5.00 Description and details of superclasses, Administrators HTML
Data Model Help subclasses, attributes, and
relationships for each class.
BMC Atrium CMDB 7.5.00 Help for using and configuring BMC Users and Product Help
Online Help Atrium CMDB. administrators
BMC Atrium CMDB 7.5.00 Information about Java classes, Programmers HTML
Javadoc Help methods, and variables that integrate
with BMC Atrium CMDB.
BMC Remedy IT Service Procedures for installing the BMC Administrators Print and PDF
Management 7.5.00 Installation Remedy ITSM applications.
Guide
BMC Remedy IT Service Procedures for configuring the BMC Administrators Print and PDF
Management 7.5.00 Remedy ITSM applications.
Configuration Guide
Preface 13
Drift Management and Section 508

Drift Management provides basic support for accessibility in conformance with
Section 508 standards through the use of keyboard shortcuts and compatibility
with JAWS.
For an explanation of general Section 508 compliance features of BMC Remedy
AR System applications, see the Designing BMC Remedy applications for Section 508
compliance using AR System whitepaper, available on the Customer Support web
site at http://www.bmc.com/support_home. Of particular interest are the following
topics:
Settings to support Section 508
Shortcut keys for BMC Remedy AR System
Also see Keyboard Shortcuts for Windows (http://support.microsoft.com/kb/
126449) and JAWS Keystrokes (http://www.freedomscientific.com/fs_products/
JAWSkeystrokes.asp).
The following table provides an explanation of how many of the features of the
Drift Management screens can be navigated and activated with keyboard
shortcuts in the desktop and the web application.
How to Desktop Web
Select Job Type radio Comparison Job is selected Use TAB and SHIFT+TAB keys (for some
buttons by default. Press ENTER to reason, the sequence is reversed in Internet
select. Explorer).
To select Snapshot Job, Press SPACEBAR to select.
press RIGHT arrow key.
Select and clear Press ENTER to toggle Press SPACEBAR to toggle between selecting and
checkboxes in wizards between selecting and clearing the box.
and in the Qualification clearing the box.
Builder
Open menus such as the TAB to field and press TAB to field. TAB again to field control.
Accessible To field to ALT+M to open menu. Press ENTER to open menu. Navigate with
select access groups in the Navigate with arrow keys. arrow keys.
wizards Press ENTER to make Press ENTER to make selection.
selection.
View Expand box for text TAB to field and press TAB to field. TAB again twice to focus on
fields such as the SHIFT+ALT+F7. Expand control, and press ENTER.
Accessible To field in the To save with changes (Not To save with changes (Not Recommended),
wizards Recommended), TAB to TAB to Save button.
Save button. Press ESC to cancel and close.
Press ESC to cancel and
close.
14 Users Guide
Drift Management and Section 508
How to Desktop Web

Drop down lists such as TAB to field and use UP and In Internet Explorer, TAB to field and use UP
the Search Drifts Reports DOWN arrays to cycle and DOWN arrow keys to cycle through
By field on the Drift through options. options. TAB again to field control and use
Console ENTER to open and close the options list.
In Firefox, TAB to field and use UP and DOWN
arrow keys to cycle through options. TAB again
to field control and use ENTER to open the
options list and ESC to close the list.
Move in and out of left If you select an item in the left In browsers, focus goes to the item selected. So,
sidebar navigation sidebar, then when focused on if you select Baselines, focus moves to the
a page element use Create button on the Baseline page.
SHIFT+TAB to return to the SHIFT+TAB moves focus back to Baselines in
left sidebar, the focus goes to the left sidebar.
the top item in the sidebar.
Activate Select and Close From first tab, use RIGHT Same as desktop.
buttons in pickers with arrow keys to move through
tabbed Membership tables tabs. From focus on a table,
use SHIFT+TAB to return to
the tab. From the final tab,
TAB through the table to the
buttons.
Choose to select or create a TAB once to focus on Select TAB to focus on either radio button.
Destination Dataset in the radio button. TAB again to Press SPACEBAR to select radio button. Then
Snapshot Job Wizard focus on Create radio TAB to Dataset Name field.
button. From Dataset Name field, SHIFT+TAB to focus
Press ENTER to select and on Create radio button.
move focus to Dataset
Name field.
From Dataset Name field,
SHIFT+TAB to focus on
Create radio button.
Close Attributes window TAB through attributes to Press ESC.
for include sets and Close button and press
exclude sets in the ENTER.
Qualification Builder
Preface 15
16 Users Guide
Chapter
1 Introduction to Drift
Management
This section introduces the BMC Configuration Drift Management application.

The following topics are provided:
What is drift? (page 18)
About Drift Management (page 19)
Drift Management and ITIL (page 20)
Basic concepts (page 21)
Drift workflow (page 25)
Common scenarios (page 26)
Where to go from here (page 26)

What is drift?
Simply stated, drift is a change in your IT environment. Drift is the difference
between the current physical state of your IT environment and the expected or
correct state of your environment. At a more granular level, drift is a change in a
configuration item (CI), a CI attribute, or a relationship as defined in your BMC
Atrium COnfiguration Management Database (CMDB).
Drift is caused by adding, removing, or modifying CIs, CI attributes, or
relationships between CIs.
NOTE
BMC assumes you are familiar with basic configuration management and BMC
Atrium CMDB concepts such as CIs and the BMC Asset dataset. For more
information, see Related documentation on page 11.
BMC Atrium CMDB represents the correct or current states of your data center
configuration items. Sometimes, however, real-world issues appear in the form of
new releases, upgrades, new equipment, and unauthorized changes. After using
your discovery mechanism to scan your environment and to update BMC Atrium
CMDB, use Drift Management to monitor and detect changes in the state of your
CIs.
Drift Management is a consumer of, and works entirely from, the data in BMC
Atrium CMDB. Drift Management relies upon a discovery application to update
BMC Atrium CMDB.
18 Users Guide
About Drift Management
About Drift Management

BMC Configuration Drift Management is built on the BMC Remedy AR System
and is a consumer of the configuration data that is discovered by your discovery
applications and stored in your BMC Atrium CMDB.
Using the configuration management data in your BMC Atrium CMDB, Drift
Management focuses on the auditing, verification, and management of
infrastructure changes in your data center IT environment. The auditing activities
provided by Drift Management assist you in keeping your data center
operationally compliant with the business rules of your IT environment.
Drift Management also integrates with other BMC applications, such as BMC
Remedy Change Management and BMC Remedy Incident Management, to
provide the initial steps toward the automation of data center operations.
Integration with BMC Remedy Change Management plays an important role in
the automation of these operations by linking changes in the data center
environment to approved change requests. Integration with BMC Remedy Change
Management and BMC Remedy Incident Management also facilitates quick
resolution of infrastructure changes by manually or automatically creating
incident requests, or by manually creating change requests from Drift
Management.
Figure 1-1: Drift Management architectural overview

Drift Management and ITIL

Drift Management supports the verification and audit activities of configuration
management as defined by the IT Infrastructure Library (ITIL).
According to ITIL, periodic audits of your IT environment should be conducted to
verify that the BMC Atrium CMDB is up to date. The reverse is also true. Periodic
audits of your physical environment should be conducted to verify that the
physical environment has the correct and approved CIs as defined in BMC Atrium
CMDB.
For example, suppose you want to verify that all security servers have the same CIs
and configuration attributes. With Drift Management, you can establish a baseline
using a known security server that is in your BMC Atrium CMDB and that has the
appropriate configuration. You can then compare all other security servers (target
servers) with the baseline to detect whether any changes (drift) have occurred. The
drift might be due to the addition, removal, or modification of CIs or attributes on
your target servers.
With Drift Management, you can perform the audit and verification process as
needed or on a regular audit schedule. For example, you might want to audit the
servers most critical to your business on a daily or weekly basis and the less critical
servers on a monthly basis. If drift is detected, Drift Management enables you to
take corrective action (after proper research for the root cause) either by using a
change request or by correcting the target computer using an incident request.
ITIL makes the following recommendations for when you should do a
configuration audit in your IT environment:
Shortly after implementation of a new Configuration Management system
Before and after major changes to the IT infrastructure
Before a software release or installation
At random intervals
At regular intervals
When all is back to normal after a disaster recovery
When any unauthorized CIs are detected
20 Users Guide
Basic concepts
Basic concepts
This section describes the basic Drift Management concepts needed to understand
how to detect drift. Refer to Figure 1-2 as you read about the concepts.
Figure 1-2: Drift Management concepts
Comparison Job
Baseline Target
Name of source dataset Name of source dataset
containing baseline CIs. containing target CIs
Can be:
Snapshot destination dataset
OR
Dataset of current CIs
(BMC.ASSET) Qualification set (required)
Compare target with
baseline using a Applied to source dataset
comparison type
Qualification set (required)

Applied to source dataset
Include or exclude set

(optional)
Used during comparison

Comparison job
You detect drift by creating and running a comparison job. A comparison job
compares a baseline set of CIs and a target set of CIs in BMC Atrium CMDB and
identifies differences between the sets.
A comparison job contains the following components:
A baseline
A target
The type of comparison to perform
A schedule for running the comparison job (optional)
The automatic creation of an incident request ticket (optional)
Baseline
A baseline is a set of CIs and their associated attributes, having a known state, used
as the basis for comparison. You can view a baseline within Drift Management as
a saved BMC Atrium CMDB query that identifies the CIs that you want to use as
your baseline CIs
A baseline is created using the Drift Management Baseline Wizard and contains
the following components:
A source dataset of CIs (for example, the BMC Asset dataset)
A qualification set (to narrow the number of CIs in the baseline)
An include set of attributes to use in the comparison (optional)
An exclude set of attributes to exclude from the comparison (optional)
Target
A target is a set of CIs that you compare with the baseline. These CIs are the items
in your IT environment, as they currently exist, that you want to audit to verify that
they are at the correct state of configuration.
Like a baseline, you can view a target as a saved query that identifies the CIs that
you want to use as your target CIs.
A target is created using the Drift Management Target Wizard and contains the
following components:
A source dataset of CIs
A qualification set (to narrow the number of CIs in the target)
22 Users Guide
Basic concepts
Source dataset
The source dataset is the location of the CIs that you want to use for your baseline
or target.
For a baseline, the source dataset can be:
A snapshot (copy) of your BMC Atrium CMDB at a point in time. You can apply
qualifications to select the specific CIs that you want to copy into your baseline.
A regular dataset, which is typically BMC Asset. You can apply qualifications to
the dataset to select the specific CIs you want to use in your baseline.
Snapshot
A snapshot is a copy of a subset of CIs from a source dataset to another dataset (the
destination dataset).
A snapshot is created using the Drift Management Snapshot Job Wizard and
contains the following components:
A source dataset of CIs
A destination dataset
A qualification set (to narrow the number of CIs copied to the destination
dataset)
Options for copying CIs and their relationships
A schedule (optional)
You can create multiple (daily or monthly) snapshots of a particular set of CIs and
use these snapshots to determine whether the configuration of the CIs has
changed.
Qualification set
A qualification set is a query used to select the specific CIs that you want to use in
your baselines, targets, or snapshot jobs. A qualification set is required when you
create a snapshot, a baseline, or a target.
A qualification set is created using the Drift Management Qualification Builder
and contains the following components:
Query criteria
An include set (optional)
An exclude set (optional)

Include set
An include set defines CI attributes that you want to include in a comparison job
to determine whether the CI attribute value has changed or is not set at the correct
value. An include set can provide greater granularity during comparison because
of its variety of comparison operators (EQ, GT, LT, LE, and so on) and the ability
to specify attribute values (for example, a standard value) to compare against.
Using an include set is optional.
Exclude set
An exclude set defines CI attributes that you want to exclude or ignore when doing
a comparison. Using an exclude set is optional.
24 Users Guide
Drift workflow
Drift workflow
Data from a discovery application is reconciled by the BMC Atrium CMDB
Reconciliation Engine and placed in the BMC Asset dataset. This discovered data
is then used by Drift Management.
Figure 1-3: Drift Management workflow

Common scenarios
This section describes the most common scenarios for using Drift Management.
Comparison of the current state of BMC Atrium CMDB with a snapshot
You want to determine whether drift has occurred over a period of time. You
make a snapshot of BMC Atrium CMDB at a given point in time (this becomes
your baseline) and later (a day, a week, or a month, for example) compare the
current state (your target) with the baseline.
For more information about using Drift Management for this scenario, see
Getting started on page 39. The Getting Started tutorial helps you to become
familiar with the Drift Management workflow when creating a comparison job.
Comparison with a standard (for compliance)
You compare the state of BMC Atrium CMDB with a baseline to ensure that the
physical state is not drifting from the declared standard.
This scenario is commonly called the golden server or golden CI. Within BMC
Atrium CMDB, you have the CIs for a crucial business service (for example,
security) configured exactly as needed. The golden CIs are the baseline with
which the other security servers (targets) are compared to verify that they are
configured to match the declared standard (the baseline).
A golden CI is configured exactly as needed and is used as a basis of comparison
with your target CIs.
Comparison between a test dataset and BMC Atrium CMDB
You want to define a test or sandbox dataset on top of another dataset to
determine the impact of potential modifications in the test dataset on BMC
Atrium CMDB. In this scenario, BMC Atrium CMDB is the baseline and the test
dataset is the target. The comparison uses the BMC Atrium CMDB API to view
the equivalent of a merge between the two datasets.
Where to go from here

Now that you have an overview of Drift Management concepts you can:
See Getting started on page 39 to become familiar with the Drift Management
workflow when creating a comparison job. This is the scenario described in
Comparison of the current state of BMC Atrium CMDB with a snapshot on
page 26.
Begin creating Drift Management components (snapshots, baselines, targets,
qualification sets, and comparison jobs) for your production environment.
26 Users Guide
Chapter
2 Managing Drift Management

permissions
This section explains how to set up permissions for the BMC Configuration Drift
Management application, including access to different functions of Drift
Management.
Understanding Drift Management permission groups (page 28)
Understanding instance permissions (page 31)
Creating users with Drift Management permissions (page 34)
Creating groups to use with Drift Management (page 36)
Using the Application Administration Console (page 37)

Understanding Drift Management permission

groups
Drift Management offers a flexible permissions model that lets you grant role-
based permission to specific areas of Drift Management functionality.
Permission groups are used to grant users access to specific consoles and modules
within Drift Management. They are also used for notifications. In addition to
inheriting the instance access within BMC Atrium CMDB, Drift Management lets
you specify access to various Drift Management components (drift reports,
baselines, targets, jobs, qualification sets, include sets and exclude sets) on the basis
of group membership.
To give users access to Drift Management, you first must create a BMC Remedy
AR System user for each of them on the BMC Remedy AR System server where
Drift Management is installed. You can then make those users members of
multiple groups and assign those groups to roles that allow them access to
different parts of the application and its data.
The following table lists the default permission groups available for Drift
Management.
Table 2-1: Drift Management permission groups
Permission groups Description
Drift Master Grants full access to Drift Management with additional access to the
following Drift Management consoles, independent of any functional
roles or support group affiliations:
Authoring Console (edit or view access)
Job Console (edit or view access)
Drift Console (edit or view access)
Drift Dashboard (select or view access)
This permission supersedes the Drift Admin and Drift Viewer
permission groups.
Drift Admin Grants execution and management access to Drift Management with
access to the following Drift Management consoles, independent of
any functional roles or support group affiliations:
Authoring Console (view access)
Job Console (edit or view access)
Drift Console (edit or view access)
This permission supersedes the Drift Viewer permission group.
28 Users Guide
Understanding Drift Management permission groups
Table 2-1: Drift Management permission groups (Continued)

Permission groups Description
Drift Viewer Grants view access to Drift Management. With view access, users can
view reports on the Drift Console. These permissions also grant you
access to the following consoles:
Authoring Console (view access)
Job Console (view access)
This permission is superseded by the Drift Master and Drift Admin
permission groups.
Public If guest users are configured in the BMC Remedy AR System server,
the Public role grants select or view access to the Drift Dashboard, as
part of the BMC Remedy AR System Public group. With select or
view access to the Drift Dashboard, you can perform the following
tasks:
Change the date range to refresh the charts.
Select Business Services that you have permission to view.
Select baselines that you have permission to view.
For more information about the Public group and its role in BMC
Remedy AR System, see the BMC Remedy Action Request System 7.5.00
Concepts Guide.
For information about creating users, see the BMC Remedy Action Request System
7.5.00 Configuration Guide. For information about working with groups and roles in
general, see the BMC Remedy Action Request System 7.5.00 Form and Application
Objects Guide.
Using Drift Management with BMC Remedy Change

Management and BMC Remedy Incident Management
permission groups
Because Drift Management integrates with BMC Remedy Change Management
and BMC Remedy Incident Management, application roles and permissions for
integration are also provided to control who can create BMC Remedy Change
Management and BMC Remedy Incident Management forms and submit change
requests or incident requests.
The following table lists BMC Remedy ITSM permission roles that are important
for integrating Drift Management with BMC Remedy Change Management and
BMC Remedy Incident Management.

NOTE
Use the BMC Remedy ITSM Application Administration Console to grant these
permissions to users. For more information, see the BMC Remedy IT Service
Management 7.5.00 Configuration Guide.
Table 2-2: Permission groups for BMC Remedy Change Management and BMC Remedy Incident Management
Permission groups Description Form access
Infrastructure For integration between Drift Management and BMC Remedy Provides access to:
Change Master Change Management. Infrastructure Change
Grants access to BMC Remedy Change Management with form
additional privileges to modify infrastructure change requests Approval Mappings
and tasks independent of any functional roles or support group form
affiliations. This permission group also grants access to users to
create and modify approval mappings.
This permission supersedes the Infrastructure Change User and
Infrastructure Change Viewer permission groups. Requires an
application fixed or floating license.
Infrastructure For integration between Drift Management and BMC Remedy Provides access to the
Change User Change Management. Infrastructure Change
Grants general access to open, query, submit, and modify form.
change requests in BMC Remedy Change Management.
Note: Modification access can be restricted through the
additional use of functional roles and support group
relationships.
This permission is superseded by the Infrastructure Change
Master permission group and supersedes the Infrastructure
Change Viewer permission group. Requires an application
fixed or floating license.
Incident Master For integration between Drift Management and BMC Remedy Provides access to the
Incident Management. Incident form.
Grants access to BMC Remedy Incident Management, with
additional privileges to modify incidents independent of any
functional roles or support group affiliations.
This permission supersedes the Incident User, Incident
Submitter, and Incident Viewer permission groups. Requires an
application fixed or floating license.
Incident User For integration between Drift Management and BMC Remedy Provides access to the
Incident Management. Incident form.
Grants access to open, query, submit, and modify incidents in
BMC Remedy Incident Management.
Note: Modification access can be restricted through the
additional use of functional roles and support group
affiliations.
This permission is superseded by the Incident Master
permission group and supersedes the Incident Viewer
permission group. Requires an application fixed or floating
license.
30 Users Guide
Understanding instance permissions

Multitenancy enables you to control which records and configuration data are
exposed to a user, based on the users membership in a company, business unit, or
other group. To support multitenancy, Drift Management offers a flexible
permissions model that lets you grant read permission to instances of drift data in
the Drift Console.
Within BMC Atrium CMDB, multitenancy means that one BMC Atrium CMDB
holds data about the IT environments of multiple companies, usually in the case of
an IT service provider, and each company has access only its own data. Each
companys data is represented in the BMC Atrium CMDB as an account.
For each class in each account, you can specify default read and write permissions
to be applied to newly created instances. You can also specify default permissions
to be applied to all classes that do not have specific permissions defined. You can
override these default permissions for a particular instance by specifying
permissions for the instance.
IMPORTANT
Drift Management inherits the instance access as currently defined within BMC
Atrium CMDB. Drift Management does not make any changes to this level of
access.
To have read or write access to drift components, users must belong to the
appropriate base groups (Drift Master, Drift Admin, or Drift Viewer) and belong to
at least one of the groups identified by the Drift Master when the component is
being created or modified.
Drift Management provides the ability to control who can view and modify the
following Drift Management components:
Drift Reports
Snapshot or comparison jobs
Authoring components: baselines, targets, qualification sets, include sets and
exclude sets
The Drift Master defines instance access to the Drift Management components
when the components are created, by using the Accessible To field. This field is on
all Drift Management wizards, authoring components, and job components.
Defining instance permissions

In the Accessible To field, the Drift Master selects the groups that can have access
to that data. More than one group can have permission to view instances in Drift
Management components.

To define instance permissions

1 As a Drift Master, open one of the Drift Management wizards, authoring
components, or job components.
2 Use the Accessible To field to select the groups who can have access permission.
3 Continue defining the Drift Management components.
IMPORTANT
Be careful when deleting groups from the Accessible To field for a comparison job,
because you might lose permissions to the underlying baselines and targets.
Examples of Drift Management instance permissions

Access to specific Drift Management components is defined when the Drift Master
creates a new job, baseline, or target. This section provides examples of how Drift
Management roles work in conjunction with instance permissions. The examples
use the users and group memberships shown in Table 2-3.
Table 2-3: Example Drift Management permission groups

User Belongs to these groups
Frank Field Drift Master, Cisco, Juniper
Tom Target Drift Master, AMD, Intel, IT
Betty Baseline Drift Master, Cisco
Johnny Job Drift Admin, Cisco
Colin Column Drift Admin, Juniper
Jennifer Java Drift Viewer, Cisco
Cheryl Change-Request Juniper, Intel, Cisco, IT, AMD
Jessica Drift Admin, AMD
Example 1
When creating a baseline, Drift Master Frank Field grants the Cisco and Juniper
groups data access to the baseline.
Question: From the list of users, who can view and modify the baseline?
Answer: Frank and Betty. Tom has Drift Master permission, but no permission to
Cisco and Juniper. Betty has Drift Master and Cisco permission. Johnny Job has
Cisco permission, but belongs to the Drift Admin (not Drift Master) group.
Example 2
When creating a target, Tom provides access to the AMD group.
Question: Who can view and modify the target?
Answer: Tom, Cheryl, and Jessica.
32 Users Guide
Example 3
Frank and Betty want to create a comparison job.
Question: When using the Comparison Job Wizard, will they see the target listed
in the target library that Tom created?
Answer: No. Although Frank and Betty are Drift Masters, Frank and Betty do not
belong to the same groups as Tom. They do not have AMD, Intel, or IT
permissions.
Example 4
Frank and Betty create a job and select Cisco as the access group.
Question: Who can execute the job?
Answer: Frank, Betty, and Johnny
Question: Who can view the Drift Reports created by the job?
Answer: Frank, Betty, Johnny, and Jennifer
Example 5
Tom creates a job and selects AMD as the Accessible To group.
Question: Who can execute the job?
Answer: Only Tom and Jessica can execute the job.
Question: Who can view the Drift Reports created by the job?
Answer: Only Tom and Jessica can view the Drift Reports. Cheryl only has access
to the Drift Dashboard.

Creating users with Drift Management

permissions
If you do not have BMC Remedy Change Management or BMC Remedy Incident
Management installed, create Drift Management users in the User form.
If you do have BMC Remedy Change Management or BMC Remedy Incident
Management installed, create Drift Management users in the People form through
the Application Administration Console.
If you have any of the BMC Remedy ITSM application installed, you should always
configure users by opening the People form from the Application Administration
Console. Information that you add or modify on the People form automatically
updates the User form, but information updated on the User form does not update
the People form.
WARNING
Do not modify the Demo users Fixed Write license or Administrator group
membership until you have created another Administrator user first, or you will
lose administrator privileges.
To create a user with Drift Management permissions in the User form

1 Using BMC Remedy User or a browser, log in to BMC Remedy AR System as an
administrator.
2 From the AR System Administration Console, choose Application >
Users/Groups/Roles > Users.
The User form opens in Search mode.
3 Choose Actions > New to switch to New mode.
4 Enter information in the appropriate fields, including required fields.
5 Depending on the users role in the company, specify the appropriate license type.
6 From the Group List field, make sure that the user is a member of the group that is
mapped to the role, or map one of the users existing groups to the role.
For example, the Drift Master role requires that you assign that person to the Drift
Master group. This individual can also be assigned to other groups.
7 Save your changes.
If adding the user causes you to exceed your license limit, an error message
appears.
NOTE
For more information about the User form, see the BMC Remedy Action Request
System 7.5.00 Configuration Guide. For more information about BMC Remedy
AR System application roles and computed groups, see the BMC Remedy Action
Request System 7.5.00 Form and Application Objects Guide.
34 Users Guide
Creating users with Drift Management permissions
To create users with Drift Management permissions in the People form

NOTE
The application administrator must have a BMC Remedy AR System license. You
can log in as appadmin to define the application administrator.
1 Open the Application Administration Console.

2 From the Standard Configuration tab, select the appropriate company.
3 Click the Create link next to Step 4 People.
The People form appears.
4 Enter all the required information, as marked by bold field labels.
5 Depending on the users role in the company, specify his or her license type.
6 Click the Login/Access Details tab.
a In the Unrestricted Access field, select Yes.
b In the Application Permission area, click Update Permission Groups.
The Permission Group dialog box appears.
c In the Permission Group field, select each appropriate permission group to
which this user should belong.
d Select a license type.
e Click Add/Modify for each permission group, as needed.
For example, the Drift Master role requires that you assign that person to the
Drift Master group.
7 To enable this user to create change requests (with the Drift Management
integration), add the user to the Change Master or Change User permission group.
8 To enable this user to create incident requests (with the Drift Management
integration), add the user to the Incident Master or Incident User permission
group.
9 Click Close.
The application administrators information is stored in the User form and the
application People form.
If adding the user causes you to exceed your license limit, an error message
appears. In this case, either reassign existing licences or contact BMC for additional
licenses.
NOTE
For more information about the People form, see the BMC Remedy IT Service
Management 7.5.00 Configuration Guide.

Creating groups to use with Drift Management

This section briefly describes how to create BMC Remedy AR System access
control groups to use in conjunction with Drift Management. If you want Drift
Management to support multitenancy without using BMC Remedy Change
Management and BMC Remedy Incident Management, you might want to create
a group to represent each company.
If you need more detailed information about creating BMC Remedy AR System
groups, see the BMC Remedy Action Request System 7.5.00 Form and Application
Objects Guide.
The groups you create here are in addition to the default groups provided with
Drift Management. See Table 2-1 on page 28 for more information.
To create groups to use with Drift Management

1 Using BMC Remedy User or a browser, log in to BMC Remedy AR System as an
administrator.
2 From the AR System Administration Console, choose Application > Users/
Groups/Roles > Groups.
3 Open the Group form in New mode.
4 Enter information for the following fields:
Table 2-4: Group form fields for Drift Management

Field Description
Group Name Name of the access control group. Use this name in the Group list
field in the User form and in the Permission and No Permission lists
when you are defining object permissions.
Every group name should be different. For example, if you want to
create a group that represents a company, you could use the
company name in Group Name.
Group ID Integer ID that uniquely identifies the group. Select an ID within
the range of 1000-14999.
If you use the same ID with multiple group names, you must also
use the same group type for each name because you are creating
aliases for the same group.
Group Type Maximum permission type intended for the group:
None (no access)
View (view field contents)
Change (modify field contents).
For Drift Management, choose View or Change.
Long Group Name Additional information about a group. The text should be
descriptive of the group because it appears by default in the Results
pane in BMC Remedy User when listing groups.
Group Category The BMC Remedy AR System group category, such as Regular,
Dynamic, or Computed. For Drift Management, choose Regular.
36 Users Guide
Using the Application Administration Console
5 Save your changes.

6 In the User form, assign users to the group that you created.
Using the Application Administration Console

If you have BMC Remedy Change Management or BMC Remedy Incident
Management installed, configure Drift Management permissions by using the
Application Administration Console. The configuration forms are available only to
BMC Remedy AR System administrators and application administrators.
IMPORTANT
Always open forms from the console. If you open the forms directly from the object
list in BMC Remedy User, you might not see all the information that you need, or
you might experience unexpected results.
Use the forms accessed from the Custom Configuration tab to go beyond the
standard configuration.
Figure 2-1: Application Administration ConsoleCustom Configuration tab
For information about configuration, see the BMC Configuration Drift Management
7.5.00 Installation Guide and the BMC Remedy IT Service Management 7.5.00
Configuration Guide.

38 Users Guide
Chapter
3 Getting started
This section provides instructions for accessing Drift Management and a sample
scenario for detecting drift.
To quickly walk you through a common scenario for detecting drift, the sample
scenario introduces you to the Drift Management workflow and Drift
Management components that detect drift. Detailed steps are provided in later
sections. The scenario does not use and explain every feature of the Drift
Management components.
Read Basic concepts on page 21 before beginning the quick start.
IMPORTANT
You must have Drift Master access privileges to perform the tasks. Drift Master
gives you full access to Drift Management features, including the Authoring items.
For information about setting up Drift Master access privileges, see Managing
Drift Management permissions on page 27.

Accessing Drift Management (page 40)
Example scenario (page 41)

Accessing Drift Management

After you install the BMC Remedy AR System, BMC Atrium CMDB, and Drift
Management applications, and they are running on the host computers, you can
access Drift Management using the following methods:
Using a browser
Using BMC Remedy User
NOTE
When accessing Drift Management for the first time, no data is displayed in the
Drift Dashboard or the Drift Console.
To access Drift Management using a browser

1 Launch your browser and enter the following URL in to your browsers address
bar:
http://<web_server>:<port>/arsys
<web_server> is the fully qualified name of the BMC Remedy Mid Tier server,
specified in the format <server_name>.company.com.
<port> is an optional port number, which is needed if the web server is not on the
default port (port 80).
2 Enter your user name and password, and then click Login.
The BMC Remedy AR System home page appears.
3 From the navigation pane, locate BMC Configuration Drift Management and select
Drift Console.
Figure 3-1: Navigation pane
40 Users Guide
Example scenario
To access Drift Management from BMC Remedy User

1 Open BMC Remedy User:
The Login dialog box appears.
2 Enter your user name and password, and then click OK.
The BMC Remedy AR System home page form is displayed. If the home page does
not appear:
a Choose Tools > Options.
b In the Options dialog box, click the Home page tab.
c Select the check box to open the home page automatically.
3 Click one of the Drift Management links in the navigation pane: Drift Dashboard
or Drift Console.
Example scenario
You want to know whether your hardware or software assets (CIs) are the same
today as they were last week. You want to determine whether drift has occurred.
To do this, you first create a snapshot (copy) of your BMC Asset dataset at a point
in time, for example, Monday morning. This snapshot is used to create a baseline.
At a later time (for example, Friday morning), you create a target using the current
state of your BMC Asset dataset. This data becomes your target.
You then create and run a comparison job to compare the current state of your
BMC Asset dataset (target) with the Monday morning snapshot (baseline) to
determine whether changes occurred during the week (drift).
Step 1: Create a snapshot job

Use the Snapshot Job Wizard to make a copy (snapshot) of part of your BMC Asset
dataset (source) and store in a destination dataset. You reduce the number of CIs
that are copied from the BMC Asset dataset source to the destination dataset by
applying a qualification set to the source data. This is accomplished by using the
Drift Management Qualification Builder, which is included in the Snapshot Job
Wizard workflow. At the end of this step, you will have a copy of your assets (CIs)
at a given point in time.
IMPORTANT
For this quick start, unless otherwise specified, use the default options provided.
For more information about creating snapshots, see Creating snapshots on

page 49.

To create a snapshot
1 From the Drift Management navigation pane, choose Management > Job Console.
2 From the Job Console, click Create.
3 For Specify Type of Job, select Snapshot Job.
The Snapshot Job Wizard appears.
4 From the Specify General Information pane, specify a name (for example,
MySnapshotJob) and description for the snapshot job.
5 Click Next.
6 From the Specify a Destination Dataset pane, choose Create to create a destination
dataset (for example, MySnapshotDataset), and then click Next.
This is the dataset to which you will copy your BMC Asset data.
7 From the Specify Source Dataset pane, choose a source dataset (BMC Asset), and
then click Next.
8 From the Select Source Qualification Set pane, specify a qualification set to apply
to the source dataset to narrow the number of CIs to be copied. (At this point, you
do not have any existing qualification sets to select, so you need to create one.)
a Click Create.
The Qualification Builder is displayed.
b Specify a name (for example, MySnapshotQualification) and description for the
qualification set.
c For Qualification Set, select Custom Qualification Set from the menu.
d From the Select Class Name menu, select BMC_ComputerSystem.
Figure 3-2: Selecting a class for a qualification set
This narrows the data by selecting one class from BMC Asset.
e Click Save & Close.
The Qualification Builder closes and the details of the qualification set you
created are displayed on the Snapshot Job Wizard pane.
f Click Next.
9 Click Done to skip setting a schedule for the job. (Later, you are instructed to start
the job manually from the Job Console after the snapshot job is created.)
The Job Console appears and your newly created snapshot job is listed.
10 Select the job and click Start Job.
11 On the Job Console, click Refresh to view the status of the job in the Job Run
History pane.
42 Users Guide
Example scenario
You have completed creating a snapshot and have copied a class of CIs from BMC
Asset into My Snapshot Dataset. You do not need to wait for the snapshot to
complete, before continuing to the next step.
Step 2: Create a baseline

When you use the Baseline Wizard, the snapshot of data you created (My Snapshot
Dataset) becomes the source for the baseline you must create for the comparison
job.
In addition, by using the Qualification Builder, which is in the Baseline Wizard
workflow, you can further refine the number of CIs by adding additional
qualifications and defining which CI attributes to compare (exclude and include
sets).
IMPORTANT
For more information about creating a baseline, see Creating baselines on

page 57.
To create a baseline
1 From the Drift Management navigation pane, choose Authoring > Baselines.
The Baselines List of Items appears. (This pane is empty until you create and save
some baselines.) After you create a baseline, it is saved in a baseline library,
available for use in other comparison jobs.
2 Click Create.
The Baseline Wizard is displayed.
3 Specify a name (for example, MyBaseline) and description for your baseline, and
then click Next.
4 Select a source dataset to use for the baseline, and then click Next.
Use the My Snapshot Dataset you created in Step 1: Create a snapshot job on
page 41.
5 Provide a qualification set to apply to My Snapshot Dataset.
a Click Create.
b Provide a name (for example, MyBaselineQualification) and description for the
qualification set.
c Accept all defaults, including All Objects.
All Objects means all CIs in the My Snapshot Dataset are used in the comparison
job.
d Click Save & Close.

The Qualification Builder closes and the details of the qualification set you
created are displayed on the Baseline Wizard pane.
e Click Next.
6 Click Next to skip Specify an Include Set.
7 Click Done to skip Specify an Exclude Set.
The Baselines List of Items appears and your newly created baseline is listed.
You will use this baseline later when creating a comparison job. If you choose
Authoring > Qualification Sets, you will see My Baseline Qualification listed.
Step 3: Create a target

Use the Target Wizard to create a target set of CIs of your configuration data in its
current state. This target is later used in a comparison job.
You can refine your target by creating qualification sets using the Qualification
Builder in the Target Wizard workflow.
IMPORTANT
For more information about creating a target, see Creating targets on page 63.
To create a target
1 From the navigation pane of Drift Management, choose Authoring > Targets.
The Targets List of Items appears. (This pane is empty until you create and save
some targets.) After you create a target, it is saved here in a target library, available
for use in other comparison jobs.
2 Click Create.
The Target Wizard is displayed.
3 Provide a name (such as MyTarget) and description for your target, and then click
Next.
4 Specify a source dataset, and then click Next.
Select the BMC Asset dataset to compare your configuration data in its current
state to a prior state (the snapshot data created in a previous step that is now your
baseline).
5 Provide a qualification set for the target.
a Click Select.
The Qualification Sets List of Items is displayed.
b Highlight MySnapshotQualification, and then click Select Item.
Details of the qualification set you selected are displayed on the Target Wizard
pane.
44 Users Guide
Example scenario
6 Click Done.
The Targets List of Items pane appears and your newly created target is listed.
You are now ready to compare your two sets of CIs, using a comparison job, your
target (MyTarget) to your baseline (MyBaseline).
Step 4: Create a comparison job

To assure you will see drift at the end of the quick start, before beginning the steps
to create a comparison job, follow the steps in the following section.
Before continuing the quick start

Because you are probably doing this quick start in one session, before continuing
you must make a change to a CI to assure a drift is visible at the end of this exercise.
You will simulate a CI change by changing the owner of a CI instance in the
BMC_ComputerSystem class. For more information about Atrium Explorer, see
the BMC Atrium CMDB 7.5.00 User's Guide.
To modify a computer system CI

1 Access the BMC Atrium Core Console.
2 Open Atrium Explorer.
3 Open the Find section of the navigation pane to view the Query list.
4 In the Query list, select the arrow next to Computers.
A list of variable qualifications expands.
5 Click Search.
6 From the list of query results, drag a CI to the display pane.
7 BMC Asset is not an editable dataset. BMC Atrium CMDB provides a sandbox
dataset that allows you to make changes before propagating those changes to BMC
Asset.
a In the display pane, right-click the CI and select Copy to Sandbox.
b In the Select View dialog box, leave the default values and click OK.
A new view containing the CI is opened in the display pane.
8 Right-click the CI and select Edit.
The BMC_ComputerSystem class form opens in a new window.
9 Change the value of the OwnerName attribute to BMC Quick Start.
10 Click Save, and then click Close.
11 In Atrium Explorer toolbar, click the Promote Sandbox Changes icon.
A Reconciliation Engine job propagates the change in the Sandbox dataset to the
BMC Asset dataset.

12 After the promote action has completed, click OK in the dialog box, and then close
Atrium Explorer.
You can now continue the quick start and create a comparison job.
Creating a comparison job

Use the Comparison Job Wizard to create a comparison job to compare MyBaseline
and MyTarget. If the comparison job detects any additions, deletions, or
modifications of the target CIs, as compared to the baseline CIs, a Drift Report is
generated and displayed on the Drift Console. If no drift is detected, a Drift Report
is not generated.
From the Comparison Job Wizard, you determine the type of comparison to apply
to the CIs in the baseline and target: 1:1, 1:many, compare normal, or compare
recursive. In a 1:1 comparison, each CI in the target is compared against the
corresponding CI in the baseline.
IMPORTANT
For more information about creating jobs and the comparison types, see Creating
and managing comparison jobs on page 79.
To create a comparison job

1 From Drift Management, choose Management > Job Console.
2 From the Job Console, click Create.
3 For Specify Type of Job, select Comparison Job.
The Comparison Job Wizard appears.
4 For General Information, do the following steps:
a Enter a job name (such as MyComparisonJob) and description.
b Verify that the Comparison Type options are not selected.
The default values, which are not visible on the pane, are one-to-one and
compare regular.
c Click Next.
5 Select a target for the comparison job.
a On the Specify a Target pane, click Select Target.
b From the Targets List of Items, highlight MyTarget and click Select Item.
The target pane appears, displaying the details of MyTarget.
c Click Next.
6 Select a baseline for the comparison job.
a On the Specify a Baseline pane, click Select Baseline.
46 Users Guide
Example scenario
b From the Baseline List of Items, highlight MyBaseline and click Select Item.
The baseline pane appears, displaying the details of MyBaseline.
c Click Next.
7 Click Next to skip Specify an Incident Template.
8 Click Done to skip Schedule.
The comparison job you created is displayed on the Job Console under Jobs.
9 Select the comparison job and click Start Job.
10 On the Job Console, click Refresh to view the status of the job in the Job Run
History pane.
The Status Description column displays the current status of the job. Upon
successful completion of the job, a message is displayed, indicating a Drift Report
was generated and the number of CIs affected.
11 To view the Drift Report, click View Drift.
The Drift Console is displayed, showing details about the detected drift.
Step 5: View detected drifts

When the comparison job detects a difference between the baseline and target CIs,
this is a drift. All detected drifts are displayed in the Drift Console.
To view drifts
To view drifts using the Drift Console, choose Management > Drift Console.
For information about viewing the displayed drift data from the Drift Console,
see Viewing Drift Reports on page 91 or read Help.
To view drifts using the Drift Dashboard, choose Management > Dashboard >
Executive Overview.
For information about viewing the displayed drift data from the Dashboard, see
Viewing Drift Reports from the Drift Dashboard on page 113 or read Help.

48 Users Guide
Chapter
4 Creating snapshots
This section describes how to use the Drift Management Snapshot Job Wizard to
create a snapshot (copy) of your configuration management data directly from
BMC Atrium CMDB.
About snapshots (page 50)
Overview of snapshot steps (page 51)
Creating a snapshot job (page 52)
Modifying or deleting a snapshot job (page 54)

About snapshots
A snapshot is a full or partial copy of CIs and their relationships from one dataset
to an auxiliary or destination dataset. A snapshot can be used to store the current
state of the production dataset (for example, BMC Asset) at a particular point in
time. You can create multiple snapshots of the production dataset over a period of
time. The snapshot is usually stored in its own dataset within BMC Atrium CMDB.
This captured data is later used, depending on your particular scenario for
detecting drift, as your baseline or target data in a comparison job.
For a scenario about how to use snapshots, see Getting started on page 39.
IMPORTANT
You must have Drift Master privileges to create, edit, and delete snapshot jobs.
Using an existing destination dataset

The destination dataset is where you want to copy the snapshot data.
When copying to an existing destination dataset that contains data from a previous
snapshot job, use the following guidelines:
Existing CIs that match the currently used qualification set are overwritten.
If a CI matching the qualification set does not exist in the destination dataset, the
CI is added to the dataset.
The remaining CIs are untouched. They are not removed from the destination
dataset.
You also have the option of using the BMC Atrium CMDB Delete Dataset or Purge
Dataset activities to clean out the destination dataset before running the next
snapshot job. For more information, see the BMC Atrium CMDB 7.5.00
Normalization and Reconciliation Guide.
50 Users Guide
Overview of snapshot steps
Creating a snapshot guidelines

The Drift Management snapshot function copies your configuration data using the
following guidelines:
If the Copy Child CIs option is selected on the Snapshot Job Wizard, the parent
CI and only weak relationships are copied.
This means if the CI is the source member of a weak relationship, the destination
member and the relationship between them are also copied. Because this action
is recursive, all weak relationships and their members below the selected CI are
copied.
If the Copy Child CIs option is not selected, only the CIs selected by the
qualification set (created in Qualification Builder) are copied.
If the All Objects option is specified in the qualification set, all CIs including
weak and strong relationships, are copied from the source dataset to the
destination dataset. When the All Objects option is selected, the Copy Child CI
option on the Snapshot Job Wizard becomes irrelevant.
If the Custom Qualification Set option is specified in the qualification set, only
the selected CIs are copied. If the Copy Child CI option is selected, on the
Snapshot Job Wizard, weak relationships are copied as well.
The snapshot function copies all CIs, including those that have not been given a
reconciliation identity.
Overview of snapshot steps

You create a snapshot of your configuration data by creating a snapshot job using
the Snapshot Job Wizard. An overview of the steps for creating a snapshot job
follows. Each step is described in detail in subsequent sections.
Step 1 Using the Drift Management Snapshot Job Wizard, provide general information
(such as name, description, status, and permissions) about your snapshot job.
Step 2 Create or select a destination dataset to which you want to copy your snapshot
data.
Step 3 Provide a source dataset from which you copy the configuration data CIs of
interest and their relationships.
Step 4 Create or select a qualification set to narrow the number of CIs in the snapshot. To
do this, use the Drift Management Qualification Builder, which is included in the
Snapshot Job Wizard workflow.
Step 5 (Optional) Assign a schedule for running the snapshot job.

Creating a snapshot job

A Snapshot Job Wizard is provided for easy creation of snapshot jobs and is
accessed through the Drift Management Job Console. The Job Console is described
in About the Job Console on page 80.
To access the Snapshot Job Wizard

1 From the Drift Management navigation pane, click Job Console.
The Job Console is displayed.
2 Click Create.
3 From the Specify Type of Job dialog box, select Snapshot Job.
The Snapshot Job Wizard appears.
To create a snapshot job

1 Provide the following general information about the snapshot job, and then click
Next.
Table 4-1: General information options for snapshot job

Field Description
Name and Description Provides a meaningful name and description for the job.
Status Indicates if the job can be executed. Two options exist:
Active (default)Choose Active if you want the job to run. The job can be
submitted manually (Start Job) or set to run on a schedule.
InactiveChoose Inactive if you do not want the job to run. For example, you
might make a job inactive after several runs, but you want to keep it around for
historical or record keeping purposes. If later you need to run the job, you can
change the status to Active.
For information about modifying a job, see Modifying or deleting a snapshot job
on page 54.
Accessible To: Specifies the permission group(s) that can see the job on the Job Console. In
conjunction with role permissions, this field determines who can view, execute,
modify, and delete the job.
For example, if this field is set to Drift Master, all users belonging to the Drift
Master group can see the job and only they have execution privileges. (Execution
privileges are controlled by who can see the job. If you do not see a job displayed,
you do not have permission to execute the job.)
More than one group can be specified. You can delete the default (Public).
For more information about Drift Management roles and permissions, see
Managing Drift Management permissions on page 27.
Copy Child CIs Copies the selected CI (parent) and all weakly related child CIs.
52 Users Guide
Creating a snapshot job
2 From the Specify Destination Dataset pane, provide a dataset to which to copy
your snapshot data, and then click Next.
a Select an existing destination dataset or create a new destination dataset.
If you select an existing dataset, the Dataset Name menu is populated from
BMC Atrium CMDB and the dataset names displayed depend on your Drift
Management permissions.
If you create a new dataset, enter the dataset name. The destination dataset is
created when the snapshot job runs (not when the snapshot job is created) and
is saved in BMC Atrium CMDB for reuse in a future run of the snapshot job.
There are no special constraints when naming datasets, however, it is
suggested you follow BMC Atrium CMDB naming conventions.
b In the Accessible To: field, specify the permission groups who can see the
destination dataset.
More than one group can be specified. You can delete the default (Public).
Permissions to see the contents of the destination dataset are controlled by BMC
Atrium CMDB permissions and any additional permissions you applied using
instance permissions, as described in Managing Drift Management
permissions on page 27.
3 From the Specify Source Dataset pane, provide a source dataset from which to
copy your snapshot data, and then click Next.
Your source dataset can come from a variety of data sources: BMC Asset, BMC
Configuration Import, BMC Topology Import, a backup or archive, or another
snapshot dataset. Only datasets you have permission to view are displayed.
WARNING
If you create a dataset, using the Reconciliation Console, to use as the source
dataset for a snapshot, baseline, or target, you must add Drift Master permissions
to the CMDBRowLevelSecurity attribute of the dataset for the dataset to be visible
from the Snapshot Job, Baseline, or Target Wizards.
The menu is populated from BMC Atrium CMDB, which has a list of all available
datasets. The dataset names displayed are based on your Drift Management
permissions. As a result, different users might see different dataset names.

4 From the Specify Source Qualification Set, specify a qualification set to apply to the
source dataset to narrow the number of CIs of interest. Do one of the following
actions:
Table 4-2: Creating or specifying a qualification set

Action Instruction
Create a new Use the Qualification Builder Help or follow the instructions in
qualification set Creating qualification sets and include and exclude sets on
page 69 to create a new qualification set to apply to the source
dataset.
Saving the qualification returns you to the Select Source
Qualification Set pane and the details of the qualification set are
displayed.
Select an existing The List of Items displays the available qualification sets.
qualification set Select the qualification set you want to use and click Select Item.
The Select Source Qualification Set screen appears and the details
of the qualification are displayed.
5 (Optional) Assign a schedule for running the snapshot job by clicking Time Driven
and specifying the days of week and time.
Skip this step if you are not providing an automatic run schedule for the job. After
the job is created, you can manually start the job from the Job Console by clicking
Start Job.
IMPORTANT
If you assign a schedule, the destination dataset is overwritten with each job run.
6 Click Done.
The job you created appears in the Job Console.
Modifying or deleting a snapshot job

You must be the owner of the job or have the appropriate role and group
permissions to modify or delete a snapshot job.
You can quickly modify or update the components of an existing snapshot job
instead of creating a new job from scratch.
54 Users Guide
If you modify a job and run it, the job runs using the access permissions of the
owner. These permissions may not be consistent with your permissions and the job
may fail or the job results may vary.
NOTE
Deleting a snapshot job deletes only the job information from the Drift Job Console,
including all previous runs of the job from the Job Run History pane. Deleting the
snapshot job does not delete the destination dataset created by the snapshot job.
For more information about the destination dataset, see Using an existing
destination dataset on page 50.
To modify a snapshot job

1 Choose Job Console > Jobs, and then select the snapshot job you want to modify.
2 Click Edit.
3 Using the Snapshot Job Wizard, make your changes.
The Job Console Details pane is updated to display the date the job was last
modified and who made the modification.
To delete a snapshot job

1 Choose Job Console > Jobs, and then select the snapshot job you want to delete.
2 Click Delete.
A confirmation dialog box appears.

You are now ready to use your snapshot data to create a baseline or target as
described in the following sections:
Creating baselines on page 57
Creating targets on page 63

56 Users Guide
Chapter
5 Creating baselines
To determine whether drift has occurred in your IT environment, you compare

two sets of CIs and their attributes. One set of CIs is identified as a baseline
representing a known or correct state and the other set of CIs is identified as targets
that you compare to the baseline. This section describes how to create a baseline.
About baselines (page 58)
Overview of baseline steps (page 58)
Creating a baseline (page 59)
Modifying or deleting a baseline (page 61)

About baselines
A baseline, according to ITIL, is the recorded state of something at a specific point
in time. This baseline is the correct configuration for your IT infrastructure. For
Drift Management, a baseline defines a set of CIs, their relationship across classes
and associated attributes, used as the basis for comparison to detect drifts in your
IT environment. Simply stated, a baseline is the basis for comparison with other
CIs.
Baselines are stored in BMC Remedy AR System tables, not in BMC Atrium
CMDB.
IMPORTANT
You must have Drift Master privileges to create, edit, and delete baselines.
Overview of baseline steps

An overview of the steps required for creating a baseline follows. Each step is
described in detail in subsequent sections.
Step 1 Using the Drift Management Baseline Wizard, associate a name, description, and
access (permission) groups for your baseline.
Step 2 Specify the name of the source dataset that contains your designated baseline CIs.
Step 3 Specify a qualification set to narrow the number of CIs in the baseline. To do this,
use the Drift Management Qualification Builder, which is included in the Baseline
Wizard workflow.
Step 4 (Optional) Specify include and exclude sets to be used as the basis for comparing
CI attributes. You will use the Drift Management Qualification Builder, which is
included in the Baseline Wizard workflow.
Drift Management uses a Qualification Builder to build qualifications that narrow

a subset of CIs. Drift Management also enables you to group several qualifications
into a qualification set, and provides the ability to select a set of CIs based on a
relationship. For example, you can select the CIs of computer systems that are
related to a particular business service.
58 Users Guide
Creating a baseline
Creating a baseline
Use the Baseline Wizard to create a baseline of CIs.
To access the Baseline Wizard

1 From the navigation pane of Drift Management, choose Authoring > Baselines.
The Baselines List of Items appears. If you have not yet created and saved a
baseline, the List of Items is empty.
2 In the List of Items pane, click Create.
The Baseline Wizard is displayed.
To create a baseline
1 Provide the following general information about the baseline you are creating, and
then click Next.
Name and DescriptionA meaningful name and description.
Accessible To:Controls who can see the baseline you are creating.
NOTE
The access or permission groups assigned through the Accessible To: field only
allow you to view the baseline in a list, not the data contained in the baseline.
Permissions to view the contents of the baseline are controlled by BMC Atrium
CMDB permissions and any additional permissions you applied using instance
permissions as described in Managing Drift Management permissions on
page 27.
2 Select a dataset or a snapshot of a dataset, which you previously created using the
Snapshot Job Wizard, and then click Next.
This dataset can be BMC Asset (accessing directly from BMC Atrium CMDB) or
any auxiliary datasets, or it can be a dataset you created when running a snapshot
job. Which dataset you use depends on your particular scenario for detecting drift.
Only datasets you have permission to view are displayed.
WARNING
If you create a dataset using the Reconciliation Console console to use as the source
to the CMDBRowLevelSecurity attribute of the dataset for it to be visible from the
Snapshot Job, Baseline, or Target Wizards.

3 Specify the qualification set to apply to the baseline, and then click Next.
You can do this in one of the following ways:
Click Create to create a new qualification set.
The Qualification Builder appears. Use Help or follow the instructions in
Creating qualification sets and include and exclude sets on page 69.
Click Select to use an existing qualification set.
The Qualification Sets List of Items appears.
a Highlight the qualification set you want to use.
Details about the qualification set are displayed, as well as other Drift
components using the qualification set.
b Click Select Item.
You are returned to the Specify Qualification Set pane and the details of the
selected qualification set are displayed.
4 (Optional) From the Specify Include Set pane, specify an include set to use with the
qualification set, and then click Next.
Provide an include set by either creating a new set or selecting an existing set.
a To create a new include set, click Create.
The Qualification Builder appears. Use help or follow the instructions in
Creating qualification sets and include and exclude sets on page 69.
b To use an existing include set, click Select Item.
The Include Sets pane appears.
c Highlight the include set you want to use.
Details about the include set are displayed as well as other baselines in which
the include set is used.
d Click Select Item.
You are returned to the Specify Include Set screen and the details of the selected
include set are displayed.
5 (Optional) From the Specify Exclude Set pane, specify an exclude set to use with
the qualification set, and then click Next.
Specify an exclude set by either creating a new set or selecting an existing set.
a To create an exclude set, click Create.
Use Help or follow the instructions in Creating qualification sets and include
and exclude sets on page 69.
b To use an existing exclude set, click Select Item.
The Exclude Sets List of Items appears.
60 Users Guide
Modifying or deleting a baseline
c Highlight the exclude set you want to use.

Details about the exclude set are displayed, as well as other baselines in which
the exclude set is used.
d Click Select Item.
You are returned to the Specify Exclude Set pane and the details of the selected
exclude set are displayed.
6 Click Done.
You are returned to the Baseline List of Items pane where the baseline you just
created is listed.
Modifying or deleting a baseline

To modify or delete a baseline, you must be the owner of the baseline or have the
appropriate role and group permissions. For more information about roles and
permissions, see Managing Drift Management permissions on page 27.
You can modify the components of an existing baseline instead of creating a
baseline from scratch. You can modify all components of the baseline.
To delete a baseline, you must either delete all jobs using the baseline or modify
the jobs to use a different baseline. You can see which jobs use the baseline in the
Job Membership table in the Baselines List of Items.
To modify a baseline
1 From the navigation pane of Drift Management, select Authoring > Baselines.
2 From the Baselines List of Items pane, select the baseline to modify.
3 Click Edit.
4 Using the Baseline Wizard, make your changes.
All console detail screens are updated to display the date the baseline was last
To delete a baseline
1 From the navigation pane of Drift Management, select Authoring > Baselines, and
then select the baseline you want to delete.
2 Click Delete.

You are now ready to create a target as described in Creating targets on page 63.

62 Users Guide
Chapter
6 Creating targets
This section describes how to create a target that you want to compare with a
baseline.
About targets (page 64)
Overview of target steps (page 64)
Creating a target (page 65)
Modifying or deleting a target (page 66)

About targets
A target defines the set of CIs that you want to compare with a baseline. The target
CIs can be accessed directly from BMC Atrium CMDB or they can be in an
auxiliary dataset you created when running a snapshot job.
IMPORTANT
You must have Drift Master privileges to create, edit, and delete targets.
Overview of target steps

You create a target using the Target Wizard. Each step is described in detail in
subsequent sections.
Step 1 Using the Target Wizard, provide a name, a description, and access permissions
for the target.
Step 2 Select a source dataset name containing your target CIs.
Step 3 Specify a qualification set to narrow the CIs of interest in the target, using the Drift
Management Qualification Builder, which is included in the Target Wizard
workflow.
IMPORTANT
Include and exclude sets are selected only in the Baseline Wizard.
64 Users Guide
Creating a target
Creating a target
The steps for creating a target are similar to the steps used to create a baseline. For
targets, you are primarily interested in the current state of your CIs. When defining
your target, select items that are consistent with the baseline. For example, do not
try to compare a Windows computer in a target with UNIX computers in a
baseline.
To access the Target Wizard

1 From the left navigation pane of Drift Management, choose Authoring > Targets.
The Targets List of Items appears.
2 Click Create.
The Target Wizard is displayed.
To create a target
1 Provide the following information, and then click Next.
Name and DescriptionA meaningful name and description for the target set
of CIs you are defining.
Accessible To:Controls who can later view, execute, modify, and delete the
target.
NOTE
Groups assigned using the Accessible To: field allow you to see only the target
listed, but not the target contents. Permissions to see the contents of the target are
controlled by BMC Atrium CMDB permissions and any additional permissions
you applied using instance permissions as described in Managing Drift
Management permissions on page 27.
2 From the Select a Dataset pane, select a dataset, and then click Next.
This dataset can be BMC Asset (accessing directly from BMC Atrium CMDB) or
any auxiliary datasets, or it can be a dataset you created when running a snapshot
job. Which dataset you use depends on your particular scenario for detecting drift.
Only datasets you have permission to view are displayed.
WARNING
If you create a dataset, using the Reconciliation Console, to use as the source
to the CMDBRowLevelSecurity attribute of the dataset for it to be visible from the
Snapshot Job, Baseline, or Target Wizards.

3 From the Specify a Qualification Set pane, specify a qualification set to apply to the
target. Do one of the following actions:
To create a new qualification set, click Create.
The Qualification Builder appears. Use the Qualification Builder help or follow
the instructions in Creating qualification sets and include and exclude sets on
page 69 to create a new qualification set to apply to the target.
Saving the qualification returns you to the Specify a Qualification Set pane and
the details of the qualification set are displayed.
To select an existing qualification set, click Select.
The List of Items displays the available qualification sets.
Select the qualification set you want to use and click Select Item.
The Specify a Qualification Set screen appears and the details of the
Qualification set are displayed.
4 Click Done.
You are returned to the Targets List of Items and the target you created is listed.
Modifying or deleting a target

You must be the owner of the target or have the appropriate role and group
permissions to modify or delete a target. For more information, see the BMC
Configuration Drift Management 7.5.00 Installation Guide.
You can quickly modify or update the components of an existing target instead of
creating a new one from scratch. You can modify all components of the target.
A target can be deleted easily if it is not used in a comparison job. To delete a target
that is part of a job, you must either delete all jobs using the target, or modify the
jobs to use a different target. You can view the job in which the target is used from
the Job Membership pane in the Targets List of Items.
To modify a target
1 From the navigation pane of Drift Management, choose Authoring > Targets, and
then select the target you want to modify.
2 Click Edit.
3 Using the Target Wizard, make your changes.
All screens are updated to display the date the job was last modified and who
made the modification.
To delete a target
1 From the navigation pane of Drift Management, choose Authoring > Targets, and
then select the target you want to delete.
2 Click Delete.
66 Users Guide

You are now ready to associate the baseline and the target to a comparison job, as
described in Creating and managing comparison jobs on page 79.

68 Users Guide
Chapter
7 Creating qualification sets

and include and exclude sets
This section describes how to use the Qualification Builder to create qualifications
sets, exclude sets, and include sets.
About Qualification Builder (page 70)
About qualification sets (page 73)
Include and exclude sets (page 75)
About include sets (page 76)
About exclude sets (page 77)

About Qualification Builder

The Qualification Builder is the Drift Management tool used to interactively create
queries in the form of qualifications sets, include sets, and exclude sets.
Qualification sets allow you to specify a single CI or groups of CIs and are used in
snapshot jobs, baselines, and targets. When a qualification set is applied to a
dataset specified for a snapshot job, all CIs matching the query are included in the
snapshot. When a qualification set is applied to a dataset of CIs specified for a
baseline or target, all CIs matching the query are included in the comparison job
that uses the baseline or target.
Include sets enable you to specify attributes that should be included in the Drift
Report if drift is detected. Include sets are managed as part of the baseline.
Exclude sets allow you to specify which attributes should not be included in the
Drift Report if drift is detected. Exclude sets are also managed as part of the
baseline. The use of include and exclude sets is optional.
Each qualification, include, and exclude set you create is saved in BMC Remedy
AR System data forms.
IMPORTANT
You must have Drift Master privileges to create, edit, and delete qualification sets,
include sets, and exclude sets.
Related topics
Accessing Qualification Builder on page 71
About qualification sets on page 73
About include sets on page 76
About exclude sets on page 77
70 Users Guide
About Qualification Builder
Accessing Qualification Builder

Access Qualification Builder from the Authoring menu item of Drift Management
by choosing any one of the following options: Qualification Sets, Include Sets, or
Exclude Sets.
The Qualification Builder is also accessible from the Snapshot Job, Baseline, and
Target Wizards, allowing you to create qualification, include, and exclude sets as
part of the wizard workflow.
Using the Authoring menu item gives you the option of creating your
qualification, include, or exclude sets before using the Snapshot Job, Baseline, and
Target Wizards.
To access Qualification Builder for qualifications sets

1 Choose Authoring > Qualification Sets.
The Qualification Sets List of Items is displayed. This is a library of previous
created and saved qualifications sets that you can reuse.
The Details pane displays information, such as the owner of the qualification set
and what group can access or view the qualification.
The Baseline, Target, and Job Membership pane shows which baseline, target, or
snapshot job uses the qualification set.
2 Click Create.
Creating a qualification set

With Qualification Builder, you can create a qualification set containing several
selected classes, related classes, and their attributes. To support this functionality,
a qualification set can be comprised of one or more qualifications. In turn, each
qualification can contain one or more qualification entries. A qualification entry
consists of a class name, and may include related classes and attributes.
This section provides a quick introduction to the Qualification Builder by
describing how to:
Create a qualification set using the All Objects option. This option specifies that
all classes, all CI instances, and all attributes in your snapshot job, baseline, or
target source datasets should be used.
Create a qualification set using the Custom Qualification option. This option
allows you to specify which CI instances you want to use in your source datasets
based on a qualification.
To create a qualification set using the All Objects option

1 Provide a meaningful name and description for the qualification set.
2 Specify the access groups that can use this qualification set.

3 For Qualification Set, select All Objects.

All Objects is the default qualification build method. The qualification set is
defined.
4 Click Save & Close.
The new qualification set is displayed on the Qualification Sets List of Items pane.
Later when you build a baseline, target, or snapshot job, you can apply this
qualification to the dataset you are using for your baseline, target or snapshot CIs.
To create a qualification set using the Custom Qualification Set option

1 Provide a name and description for the qualification set.
2 Specify the access groups that can use this qualification set.
3 For Qualification Set, select Custom Qualification Set.
The Select Class Name and Select Action fields are displayed.
4 From the Select Class Name field, select a class.
When a class is selected, other options are made available from the Select Action
field, for example, Add Attribute and Add Related Class.
The options displayed depend on the item that is selected, which is marked by a
green highlight.
5 From the Select Action field, select Add Attribute.
The Select Attribute Name field is displayed, as well as, an operator field and a
value field.
6 From the Select Attribute Name field, select an attribute, provide an operator, and
enter a value.
7 Add additional classes and attributes and related classes to your qualification.
8 When your qualification set is defined, click Save & Close.
Your new qualification set appears in the Qualification Sets List of Items.
AND or OR
In a qualification set, the AND conjunction is used between a class and its related
classes and attributes.
The OR conjunction is used between the main classes in the qualification. In the
preceding example, the main classes are BMC_ComputerSystem and
BMC_Application.
72 Users Guide
About qualification sets
Guidelines for qualification set option selection

Be aware of the following option selection behavior when using the Qualification
Builder. Similar behavior is provided for include and exclude sets.
The Delete Selected Class option is only available if there is more than one main
class because a qualification must have at least one class. This option is always
available for a related class, whether it is selected or not.
The Add Attribute and Add Related Class options are not available until the
class is selected.
The Delete Selected Attribute option is always available, whether an attribute is
selected or not.
About qualification sets

The Qualification Builder uses a dynamic tree-like structure for selecting classes
and attributes. You can create multiple levels of classes and each class can have
multiple related classes.
NOTE
Related classes only apply to qualification sets.
Using classes
The following scenarios are supported.
Scenario A
Class A has two related classes: Class B and Class C
CLASS A
RELATED TO Class B
RELATED TO Class C
You could also say, Class B and Class C are related to Class A.
Scenario B
Class A has one related class, which in turn, has its own related class.
CLASS A
RELATED TO Class B
RELATED TO Class C
Class A has one related class, Class B and Class B has one related class, Class C.

Scenario C
This scenario is a combination of scenario A and B.
CLASS A
RELATED TO Class B
RELATED TO Class C
RELATED TO Class D
RELATED TO Class E
Class A has two related classes, Class B and Class D, which in turn have their own
related classes.
Guidelines for using classes

Keep the following guidelines in mind when using classes in a qualification set:
Classes can be added in any order.
A new related class can be added anywhere in the tree, but the related class is
always added as the last child of its parent.
NOTE
You can not reorder classes.
From each class and related class, any number of attributes, attribute values, and
conditions can be specified.
Related classes apply only to qualifications sets.
When a related class is added to a selected class, the comparison service checks
for a relationship between the two classes. If there is no specific relationship
between the two classes, the comparison service uses the Base Relationship
class.
Guidelines for using attributes in a qualification set

Be aware of the following guidelines when using attributes in a qualification set:
A newly added attribute, like related class, is always added as the last child of
its parent class.
The attribute name, operator, and value are mandatory.
The value entered for an attribute must be appropriate for the selected operator.
74 Users Guide
Include and exclude sets
Valid operators for attributes in a qualification set are as follows.

Table 7-1: Operators in a qualification set
Attribute operator Description
== equal to, numeric or a string
!= not equal to, numeric or a string
< less than, numeric only
> greater than, numeric only
<= less than or equal to, numeric only
>= greater than or equal to, numeric only
LIKE numeric
string
supports SQL %
IN or NOT IN numeric
string
comma delimited list
rangethe range operator is .. with no spaces before or after. For
example, 10..50.
NOTE
These attribute operator values are only valid in a qualification set. Different
operators are used in an include set.
Best practice
When creating qualifications sets for the BMC_Product class, be sure to qualify the
baseline and target with the name of the product. Using the name of a product
prevents the comparison of unlike products, for example, comparing Adobe
Acrobat Reader with Windows Word.
Qualifications on other CI types should follow a similar approach.
Include and exclude sets

It is important to understand the distinction between qualifications sets and
include or exclude sets. Qualifications are used to narrow the CIs in the baseline or
target to a given subset of CIs instances. These instances reflect the classes and
attributes you specified in the qualification set and are later compared using a
comparison job.
Include and exclude sets apply only to CI attributes. Includes and excludes allow
you to specify the attributes that should be included or excluded, thus filtering the
number of attributes that are to be considered for comparison when the
comparison job runs.

About include sets

Include sets allow you to manage the results of a comparison job as follows:
Limits the display of drifts detected to only those attributes selected in the
include set.
Allows the default comparison operator EQ (equality) to be overridden. When
a baseline and target are compared by the comparison job, the default
comparison operator is EQ (equality). If the target attribute value does not equal
the baseline attribute value, the attribute is flagged as a drift.
Allows the value of the target attribute to be compared against a value entered
by you in the include attribute fields. By default the target attribute is compared
with the baseline attribute. You can override the default by supplying a value to
compare the target attribute with instead of the baseline attribute value.
Guidelines for using attributes in an include set

Be aware of the following guidelines when using attributes in an include set:
The attribute name and operator are mandatory.
The attribute value is optional. When used, the value must be appropriate for
the selected operator.
The operator options for include sets are: EQ, NE, GT, LT, GE, LE, IN, NOT IN.
If the Boolean expression to evaluate two attributes returns TRUE, then no drift
is detected. If the expression returns FALSE, then the comparison service flags
this as a drift and the attribute is displayed in the Drift Report.
Creating an include set

This section describes how to use the Qualification Builder to create an include set.
To create an include set

1 Select Authoring > Include Sets.
2 When the Include Set List of Items displays, click Create.
The Qualification Builder for an include set appears.
3 In the Select Class Name field, select a class name.
4 Click Show to display the attributes for this class.
5 Select the attributes to include in the include set, overriding the default
comparison operator and attribute value as needed.
6 Click Close to save the attributes.
7 Click Save & Close to save the include set.
Your new include set appears in the Include Sets List of Items.
76 Users Guide
About exclude sets
Examples
This section provides examples showing how to customize an include set.
Default behavior
Select Class = BMC_ComputerSystem, Attribute = memory, Operator = EQ
The default operator (EQ) is selected. The comparison service compares the
memory value of the target CI to the memory value of the baseline CI. If the values
are not equal, the attribute has drifted and it is displayed in a Drift Report on the
Drift Console.
Overriding the default operator

Select Class= BMC_ComputerSystem, Attribute = memory, Operator = LT
The selected operator LT (less than) overrides the default operator (EQ). The
comparison service compare the memory value of the target CI to the memory
value of the baseline CI. If the target attribute value is not less than the baseline
attribute value, the attribute is flagged as a drift.
Overriding the default operator and attribute value

Select Class= BMC_ComputerSystem, Attribute = diskcapacity, Operator = GT,
Value=20
The selected operator GT (greater than) overrides the default operator (EQ). The
user-supplied Value (20) overrides the baseline value, which means the
comparison service uses this value instead of the baseline value. If the target
attribute value is not greater than 20, the attribute is flagged as a drift.
About exclude sets

Exclude sets are much simpler than include sets. Any attribute selected in an
exclude is not displayed in the Drift Report, thus allowing you to filter the drift
results to show only those attributes of interest. When a comparison job runs and
compares the CIs in the baseline and target, excluded attributes are not used in the
comparison.
Scenario
The following scenario illustrates when using an exclude set would be useful.
When you are comparing your business criteria computers (targets) to a computer
(baseline) that is configured exactly as needed for the business, the computer name
of each target differs from the computer name of the baseline. This is flagged as a
drift. Excluding the computer name attribute would filter its display as a drift in
the Drift Report.

Creating an exclude set

This section describes how to use the Qualification Builder to create an exclude set.
To create an exclude set

1 Choose Authoring > Exclude Sets.
2 When the Exclude Set List of Items displays, click Create.
The Qualification Builder for an exclude set is displayed.
3 Select a class name.
4 To see a list of all the attributes for the class, click Show.
5 Select the attributes to exclude, and then click Close.
You can add additional classes to your exclude set with attributes selected for
exclusion.
6 When finished, click Save & Close.
Guidelines for exclude sets

Keep the following guidelines in mind when creating an exclude set:
Use an exclude set when you want to include most attributes but not all in the
comparison. You can specify which attributes to ignore (exclude) by using an
exclude set.
Using only an exclude set (no include set) to specify the attributes to be
displayed in the Drift Report, is equivalent to including all attributes but
excluding what is specified.
An exclude set takes precedence over an include set. For example, if you are
using both an include set and an exclude set and the exact same attribute is
specified in both, the result is that no attribute is selected.
For an exclude set, selecting attributes is optional. If no attributes are selected for
an exclude, all attributes for the class are used in the comparison.
78 Users Guide
Chapter
8 Creating and managing

comparison jobs
This section describes how to create, view, and manage comparison jobs.
About the Job Console (page 80)
About comparison jobs (page 81)
Before creating a comparison job (page 83)
Creating a comparison job (page 83)
Managing comparison jobs (page 86)

About the Job Console

The Job Console is the primary interface for creating new snapshot and
comparison jobs, and checking on existing jobs. It provides a listing of all jobs that
have been created.
Figure 8-1: Job Console
When you select a job in the Jobs pane, details about the job are displayed in the
Details and Job Run History panes.
The Details pane shows information about the job, including the name of the
baseline and target used by the comparison job, date last modified, the current run
schedule for the job (if not manual), and other job actions.
The Job Run History pane displays the run history of the job. You can view more
details about a selected job by clicking the View Log button.
To view details on a detected drift in a job run, you can access the Drift Console
from the Job Run History pane by clicking the View Drift button.
IMPORTANT
You must have Drift Master or Drift Admin privileges to use the Job Console. Drift
Admin can create and modify jobs, and view and use the authoring items
(baseline, target, and so on). Only Drift Master can create or modify authoring
items.
80 Users Guide
About comparison jobs
Related topics
About comparison jobs on page 81
Before creating a comparison job on page 83
Creating a comparison job on page 83
Managing comparison jobs on page 86
About comparison jobs

A comparison job identifies and compares the CIs in your target with the CIs in
your baseline. The comparison job identifies which baseline CIs and target CIs to
use based on the qualification sets you provided in the baseline and target that you
created earlier. After the CIs for the baseline and target are uniquely identified, the
comparison job compares a list of attributes based on the exclude and include sets
you defined in your baseline. The actual comparison of CIs is performed by
comparing the target CIs and their attributes with the baseline CIs.
In addition to comparing CI attributes, a comparison job can be configured to
identify drift in a relationship between CIs by comparing your target set of CIs
with your baseline set of CIs.
Comparison service
For detailed information about how the comparison job, and the underlying
comparison service, identifies and compares CIs, see Comparison service on
page 125.
Types of comparisons
The comparison job performs the following types of comparisons:
Compare Regular (default)Compares the top level CIs only.
NOTE
This comparison type is not displayed on the Comparison Job Wizard pane.
Compare RecursivelyCompares the top level CIs and their children CIs until
there are no more CIs to compare.
Compare CI RelationshipsCompares relationships between target CIs with
the relationships between CIs in the baseline.
Only outward relationships from the source of the relationship to the
destination of the relationship are tracked.
Only relationships of the BMC_BaseRelationship class are compared.

These comparisons can be enhanced by specifying one of the following types of

cardinality for the compare:
One-to-one (default)A one-to-one comparison of CIs from the baseline and
the target. For a one-to-one comparison, all CIs must have a
ReconciliationIdentity attribute that is created during a BMC Atrium CMDB
reconciliation process. CIs without this attribute are ignored during a one-to-
one comparison.
If comparing relationships between CIs, only one level of relationships are
compared.
NOTE
This cardinality type is not displayed on the Comparison Job Wizard pane.
Many-to-oneA many-to-one comparison of the target CIs with a single CI in

the baseline. You use this option if, for example, you are comparing many CIs
with a standard or golden CI to which all other CIs must conform. For a many-
to-one comparison, the CIs are identified using the Reconciliation Engine rules.
If you have more than one CI in the baseline, a many-to-one comparison will fail.
If comparing relationships, all levels of relationships are compared.
IMPORTANT
The default comparison performed by Drift Management is a one-to-one
comparison of the top level CIs only.
Combining comparison types

You can combine comparison types in a single comparison job to provide more
detailed information about a drift. For example, you might create a comparison job
that combines a Compare Recursively type with a Compare CI Relationships type
to create a very detailed report about the drift between the CIs and relationships in
your target.
Output of a comparison job (Drift Reports)

Any difference in the target as compared with the baseline is considered to be a
drift. All drifts detected by a comparison job are presented as a Drift Report on the
Drift Console. A Drift Report can have one or more drifted CIs. If the comparison
job did not detect drift, a Drift Report is not generated.
All CIs and their relationships that are modified, added, or removed are
considered to be detected drifts and are displayed, depending on the comparison
type chosen, as Drift Reports on the Drift Console as output of a comparison job.
82 Users Guide
Before creating a comparison job
Drift types
A detected drift is classified as one of the following types:
AddedCI exists in the target dataset of CIs but does not exist in the baseline.
A drift of this type can be the result of the addition of new hardware to the
network, addition of memory added to a computer, or the addition of new
software.
ModifiedCI in the target has a different attribute value as compared with the
attribute value in the baseline. A drift of this type can be the result of the change
in an attribute value.
RemovedCI does not exist in the target set of CIs but does exist in the baseline,
for example, the removal of hardware or memory.
RelationshipDrift A change in the relationship between CIs in the target set
as compared with the relationship between the same CIs in the baseline set.
In addition, each RelationshipDrift has an associated Drift Type of added,
modified, or removed to show exactly what caused a drift in the relationship.
Before creating a comparison job

Before creating a comparison job, you must create a baseline and a target, using the
Baseline and Target Wizards as described in the following sections:
Creating baselines on page 57
Creating targets on page 63
After you have created a baseline and target, you wrap the baseline and target
together in a comparison job, select the type of comparison to perform, and add a
run schedule (and other possible job actions), as described in Creating a
comparison job.

A Comparison Job Wizard is provided so you can easily create comparison jobs.
To access the Comparison Job Wizard

1 From Drift Management, choose Management > Job Console.
The Job Console appears.
2 Click Create.
3 From the Specify Type of Job dialog box, select Comparison Job.
The Comparison Job Wizard is displayed.

To create a comparison job

1 Provide the following general information about the comparison job, and then
click Next.
Table 8-1: General information options for comparison job

Field Description
Name and Description Provides a meaningful name and description for the
comparison job.
Priority Defines the fix priority for drifts detected by the job. The
priority selected here is displayed on the Drift Console for each
Drift Report resulting from a run of this job.
Status Indicates if the job can be executed. Two options exist:
Active (default)Use active if you want the job to be
executed. The job can be submitted manually (Start Job) or set
to run on a schedule using the Comparison Job Wizard.
InactiveUse inactive if you do not want the job to be
executed. For example, you might make a job inactive after
several runs, but you want to keep it around for historical or
record-keeping purposes. If later you need to run the job, you
can change the status to active and submit.
Compare Recursively Compares the top level CIs and their children CIs until there are
no more CIs to compare.
The default comparison type is Compare Regular, not shown
on the wizard pane, which only compares the top level CIs.)
For additional information about compare recursively and one-
to-many, see Types of comparisons on page 81.
Many-to-One Provides a many-to-one comparison of CIs from the target to
the baseline.
The default cardinality is a one-to-one comparison (not shown
on the wizard pane.)
Compare CI Compares the relationship between CIs.
Relationships For additional information about comparing CI relationships,
see Types of comparisons on page 81 and Combining
comparison types on page 82.
Accessible To: Specifies the groups that can have access to this job. For more
information about permissions, see Managing Drift
2 Select a target for the comparison job, and then click Next.
NOTE
If you have not created a target for this job, do so now as described in Creating
targets on page 63.
a From the Target pane, click Select Target.
84 Users Guide
b From the Targets List of Items, highlight the target you want to use.
In the Details and Job Membership panes, details about the target are displayed,
as well as a list of other jobs using this target.
c Click Select Item.
The target pane of the wizard appears, displaying the details of the target you
selected.
3 Provide a baseline for the comparison job, and then click Next.
NOTE
If you have not created a baseline set of CIs for this job, do so now as described in
Creating baselines on page 57.
a From the Baseline pane, click Select Baseline.

b From the Baselines List of Items, select the baseline you want to use, and then
click Select Item.
The Baseline pane appears, displaying the details of the baseline.
4 (Optional) Create an (automatic) incident request ticket.
If you want the comparison job to create an incident request ticket (if drift is
detected), enter the following information, and then click Next. Otherwise, just
click Next to continue.
a From the Incident pane, click Select Incident Template.
b Select the appropriate template (software or hardware), and then click Select.
The Comparison Job Wizard Incident pane appears, displaying the details of the
incident template you selected.
5 (Optional) Assign a schedule for running the job.
If you do not want to provide an automatic run schedule for the job, you can skip
this step. (After the job is created, you can manually start the job from the Job
Console by clicking Start Job.)
6 Click Done.
The job appears on the Job Console as the first entry in the Jobs pane list.

Managing comparison jobs

After a comparison job is created, the job is displayed on the Job Console. This
section describes the tasks you can perform from the Job Console.
Related topics
Canceling a job on page 86
Checking the status of a job on page 86
Modifying or deleting a job on page 86
Scheduling a job on page 87
Viewing job details on page 88
Viewing job history, job logs, and Drift Reports on page 88
Canceling a job
To cancel a job, select the job from the Jobs pane and click Cancel Job. A job must
be running to cancel it.
Checking the status of a job

Check the status of a job in the Jobs pane. Click Refresh to refresh the Jobs pane.
The Last Job Run Status column displays one of the following job run statuses:
canceled, failed, running, successful.
Modifying or deleting a job

To modify or delete a job or job run, you must be the owner of the job or have the
appropriate role and group permissions. For more information about roles and
permissions, see Managing Drift Management permissions on page 27.
If you modify a job and run it, the job runs using the access permissions of the
owner. These permissions may not be consistent with your permissions and the job
may fail or the job results may vary.
Deleting a job deletes all job runs and Drift Reports generated by the job. This
action does not delete the baseline, target, or qualification sets associated with the
job because those might be used in another job.
86 Users Guide
Managing comparison jobs
To modify a job
1 On the Job Console, select the job you want to modify, and then click Edit.
2 Using the Comparison Job Wizard, make your changes, and then click Done.
You can modify the information on all screens including the addition of a job
schedule to a job that did not have one previously.
The Job Console Details pane is updated to display the date the job was last
To delete a job
On the Job Console, select the job you want to delete, and then click Delete.
To delete a job run

On the Job Console, select the job run in the Job Run History pane and click
Delete.
This action deletes the job run and the Drift Report, if any, associated with the
job run.
Scheduling a job
You can schedule a comparison job using one of the following methods:
Manually
Time Driven
Manually
If you did not configure the job to run automatically, you can start the job manually
from the Job Console by clicking Start Job.
Time driven
When using a time driven schedule, the job is triggered based on the time zone of
the BMC Remedy AR System server host computer. If the BMC Remedy
AR System client is running in a different time zone, the time you specify is
adjusted accordingly.

Viewing job details

From the Job Console, select the job you want to view. The details of the job are
displayed in the Details pane.
Figure 8-2: Details pane
The Details pane shows information about the job, including the target and
baseline used by the job. You can view those in more detail by selecting View
Target or View Baseline.
Viewing job history, job logs, and Drift Reports

NOTE
You can use the Job Run History options with Drift Viewer privileges.
1 From the Jobs pane, select a job.

Previous runs of the job are displayed in the Job Run History pane.
Figure 8-3: Job Run History pane
2 Select the job run.

3 To view the Drift Reports created by a comparison job, click View Drift.
The View Drift button is available only if a snapshot job is selected.
The Drift Console displays the Drift Reports associated with the job run.
4 To view the comparison job log, click View Log, and then select the status Log file
and click Display or Save to Disk.
88 Users Guide

The output of a comparison job, Drift Reports, is displayed on the Drift Console as
described in Viewing Drift Reports on page 91.

90 Users Guide
Chapter
9 Viewing Drift Reports
This section describes how to view Drift Reports and their associated details using
the Drift Console.
About the Drift Console (page 92)
Viewing the Drift Console data (page 92)
Viewing the details of a Drift Report (page 95)
Managing or remediating drifts (page 101)

About the Drift Console

The Drift Console is the primary interface for viewing and taking actions to
manage or resolve drifts. The console is used by the individual responsible for
maintaining the data center environment, or their portion of it, at a known or
correct state. The Drift Console might also be used to view the details of a drift
displayed in the Drift Dashboard.
The Drift Console provides drift information at a more detailed level than the Drift
Dashboard by listing detailed information about each drift, such as, the type and
priority of the drift and the number, name, and attributes of the CIs affected by the
drift.
When you access the Drift Console, all detected drifts from all of your comparison
jobs are displayed. Each time you refresh the Drift Console, any new Drift Reports
created by running comparison jobs are displayed.
Viewing the Drift Console data

When a comparison job runs, and if drift is detected, the results are presented as a
Drift Report on the Drift Console. One Drift Report is generated per comparison
job. A Drift Report shows details about the detected drift, such as the number of
CIs and attributes affected and the type of drift detected. In addition, if you are
using BMC Remedy Change Management or BMC Remedy Incident Management,
detailed information correlating a drift to a change request or incident is also
shown.
A Drift Report is created only if a drift is detected. If you run a comparison job and
no drifts were detected, there is no Drift Report.
IMPORTANT
You must have Drift Master, Drift Admin, or Drift Viewer privileges to use the
following features: View Details, View Job, View Baseline, and View Target.
92 Users Guide
Viewing the Drift Console data
Figure 9-1: Drift Reports in the Drift Console
Viewing Drift Reports

The Drift Reports pane displays a list of Drift Reports detected by comparison jobs.
The Priority field displays the priority that should be used when remediating the
drift and is assigned when the comparison job is created or modified. The actions
that should be taken are determined by your organization.
Searching Drift Reports and Drift Report details

You can search for specific Drift Reports or Drift Report Details or you can filter
the number of reports displayed on the Drift Console. The search categories are
populated from data stored in the BMC Remedy AR System tables. For example,
the baselines displayed in the search selection list are the same baselines displayed
in the Authoring > Baselines > List of Items table.

To search or filter Drift Reports or Drift Report Details

1 Do one of the following actions:
On the Drift Console, from the Search Drift Reports By menu, select a search
category.
On the Drift Report Details pane, from the Search Drift Details By menu, select
a search category.
2 From the displayed Selection list dialog box, select a specific search item, and then
click Search.
If you are searching for a change or incident request, you are prompted for the
change or incident ID number.
Only Drift Reports or Drift Report Details for the selected search category are
displayed.
Viewing Comparison Job details

To quickly research the details of a comparison job that generated a Drift Report,
select a Drift Report and take the following actions:
Click View Job to view only that job in the Job Console with associated details.
Click View Baseline to view details about the baseline used in the job.
Click View Target to view details about the target used in the job.
Viewing Baselines and Targets

The View Baseline and View Target panes display details (for example, date
created, dataset name, access groups, and last modified date) about the baseline or
target used in the comparison job selected from the Drift Console.
The name of the qualification set, and optionally include and exclude sets,
included in the baseline or target are listed and low-level details (classes,
attributes, and logic) can be viewed by clicking the View link.
Job Membership lists all other comparison jobs using this baseline.
Deleting a Drift Report

IMPORTANT
To delete a Drift Report, you must have Drift Master or Drift Admin privileges.
Deleting a Drift Report also deletes all job runs, and associated drift information,
for that report.
To delete a Drift Report from the Drift Console, click Delete.
94 Users Guide
Viewing the details of a Drift Report
Refreshing the data

The Drift Console is not updated automatically. To refresh the data displayed, click
Refresh.

You can view the details of a Drift Report in the following ways:
Highlight an entry in Drift Reports. Additional details about the Drift Report are
displayed in the smaller panes at the bottom.
Click the View Details button. The Drift Report Details for the highlighted Drift
Report is displayed.
Figure 9-2: Drift Report Details

Related topics
Viewing Configuration Items on page 96
Viewing the CI in BMC Atrium CMDB on page 97
Viewing CI Attributes on page 97
Viewing drifts on relationships on page 98
Viewing business services affected by a drift on page 99
Viewing change requests correlated with a drift on page 99
Viewing incident requests correlated to a drift on page 100
Searching Drift Reports and Drift Report details on page 93
Viewing Configuration Items

You can view details about CIs showing drift.
1 In the Drift Reports pane of the Drift Console, highlight an entry.
The CIs showing drift are displayed in the Configuration Items (CIs) pane.
2 On the Drift COnsole, click View Details.
The Drift Report Details for the highlighted Drift Report is displayed, showing an
expanded view of the CIs showing drift.
Table 9-1 describes the column names and associated data for the CIs pane.
Table 9-1: Description of the CI data
Column Description
Name Name of the CI showing drift.
Computer System Name of the parent computer system.
Name For example, if a product CI is reflecting drift, this tells you which
computer the product is on.
Drift Type Determined by comparing the target CI or attribute with the
baseline CI or attribute. The types of drift are:
AddedCI is present in the target but not in the baseline.
RemovedCI is present in the baseline but not in the target.
ModifiedAn attribute value on the target does not match the
value in the baseline.
RelationshipDriftOne or more relationships between CIs has
changed.
CI Instance Class Id Data model class type of the drifted CI.
If a Drift Report shows two CIs named Setting, this column tells
you which class the CIs belong to. For example, one CI belongs to
the Class Apache Setting and the other CI belongs to the Class
VMWare Setting.
96 Users Guide
Viewing the CI in BMC Atrium CMDB

IMPORTANT
You must have Drift Master or Drift Admin privileges to view the CI in BMC
Atrium CMDB.
You can view additional details about the CI showing drift by viewing the CI
directly from the BMC Atrium Core Console. Highlight a CI, and then click View
CI in CMDB.
Viewing CI Attributes
When defining your baseline, if you specified CI attributes to be included in the
comparison using the include set, only those attributes showing drift are
displayed. If you used the exclude set, only those attributes not excluded are
shown (if they show drift). If you did not specify an include or exclude set, all
attributes showing drift are displayed.
To view CI attributes
1 From the Drift Console, highlight a Drift Report.
2 Click the View Details button.
The Drift Report Details pane is displayed. From the CI Attributes tab, the CI
attributes showing drift are displayed.
Table 9-2 describes the column names for attribute data.
Table 9-2: Description of Attributes data

Column Description
Name Name of the CI attribute that has changed.
Baseline Value Expected or correct value of the CI attribute.
Operator The comparison operator used to compare attributes. This
operator was defined by you in the include set.
If an include set was not defined, then the default operator (EQ) is
shown.

Table 9-2: Description of Attributes data (Continued)

Column Description
Observed Value Value of the CI attribute detected by the comparison job.
Status For each CI attribute showing drift, the status can be one of the
following values:
NewThe drift is new and cannot be correlated to a change
request created from Drift Management. If the drift is correlated
to a change request created outside of Drift Management, the
results are shown in the Change Requests tab.
AddressedThe change request correlated with the drift was
created, within Drift Management, to resolve the drift when
found in a previous comparison job.
AcknowledgedThe drift is acknowledged using the Drift
Console Acknowledge option. For more information about
acknowledging drifts, see Acknowledging a drift on page 108.
Viewing drifts on relationships

You can view details about the change in the relationships between CIs. For more
information about relationship drift, see Drift types on page 83.
To view relationship drifts

1 From the Drift Console, highlight a Drift Report.
2 Click the View Details button.
The Drift Report Details pane is displayed. From the Relationships tab (lower left),
the CI relationships showing drift are displayed.
NOTE
The View Details button for relationship drifts is active only when a modified
relationship drift type is selected.
Table 9-3 describes the column names for relationship data.
Table 9-3: Description of Relationships data

Column Description
Source Name The name of the source CI.
Source Class Id The class to which the source CI belongs.
Destination Name The name of the destination CI for which a relationship has been
added, modified, or removed.
Destination Class Id The class to which the destination CI belongs.
Relationship Name The name of the relationship added, modified, or removed.
Relationship Class The class to which the relationship belongs.
Id
Drift Type The type of drift, either Added, Modified, or Removed.
98 Users Guide
Viewing business services affected by a drift

IMPORTANT
You must have Drift Master, Drift Admin, or Drift Viewer privileges to view
Business Services.
When drift is detected on a CI, or any of the child CIs, the comparison job looks for
a business service associated with the CI.
To view business services that are affected by a drift, from the Drift Console or the
Drift Reports Detail screen, click the Business Services tab.
Viewing change requests correlated with a drift

You can view change requests that might be correlated to a drift or change requests
submitted to take action on a drift.
IMPORTANT
change request information. To view Details, in addition to Drift Management
privileges, you must have Change Master or Change User privileges.
Figure 9-3: Change requests associated with a drift
To view change requests correlated to a drift

1 From the Drift Console or the Drift Reports Detail screen, select the Change
Requests tab.

Table 9-4 describes the columns for change request data.
Table 9-4: Description of change request data

Column Description
Change ID The ID of the change request.
Correlation Type When a change request is correlated with a drift, the change
request can have one of the following correlation types:
ManualChange request was submitted, within Drift
Management, to take action on the drift.
AutomaticChange request (submitted independent of Drift
Management) is related to as the possible cause of the drift.
Status The status of the change request used by Drift Management to filter
the display of correlated change requests. For more information,
see Filtering displayed change requests on page 121.
2 To view the change request, click Details.

For more information about correlating a drift to a change request, see
Correlating a drift with a change request on page 104.
Viewing incident requests correlated to a drift

IMPORTANT
incident requests. To view Details, in addition to Drift Management privileges,
you must have Incident Master or Incident User privileges.
To view incident requests correlated to a drift

1 From the Drift Console or the Drift Reports Detail screen, select the Incidents tab.
The Incident Number and Correlation Type are displayed.
2 Click Details.
Customizing the Drift Console

You can customize the panes in the Drift Console by:
Sorting by a column
Rearranging the column order by dragging and dropping
WARNING
You can customize the form using the BMC Remedy Developer Studio, but do so
at your own risk. Do not remove existing columns due to underlying associated
workflow.
100 Users Guide

Managing or remediating drifts
Managing or remediating drifts

See the following actions to address or remediate a detected drift from the Drift
Console:
Creating a change request from the Drift Console on page 108
Creating an incident request on page 110
Acknowledging a drift on page 108

102 Users Guide

Chapter
10 Remediating drifts
This section describes how to determine what caused a drift and what actions you
can take to acknowledge or remediate the drift.
Determining what caused a drift (page 104)
Correlating a drift with a change request (page 104)
Remediating a drift (page 107)

Determining what caused a drift

A drift is caused by one of the following events:
An unauthorized change, such as changing a configuration setting from the
business required value, installing unauthorized software, or removing or
adding hardware from a computer without prior approval.
For any of these situations, you would research if the drift can be correlated to a
change request as described in Correlating a drift with a change request on
page 104.
If a drift cannot be correlated to a change request and if it would be appropriate
to do so, you can create a change request or an incident request as described in
Remediating a drift on page 107.
An authorized change initiated through a BMC Remedy Change Management
Change Request form can cause drift if the baseline of the comparison job is
outdated. A scenario describing how this could occur and how to correlate a
drift with a change request is explained in Correlating a drift with a change
request on page 104.
Correlating a drift with a change request

A drift displayed on the Drift Console might be the result of a change request that
has been submitted, as described in the following scenario.
At your company, a newly approved business standard requires all laptops in the
Technical Support Group to be upgraded from 1 GB of memory to 4 GB. Change
request 007 for the installation of the additional memory was submitted,
approved, and implemented. Your daily discovery application scanned the
laptops and updated the memory attribute of the CIs for those laptops in BMC
Atrium CMDB. A few days later, an existing comparison job, scheduled to run
periodically, checks all laptops against a baseline defining the memory standard to
be 1 GB memory. Drift is detected by the comparison job for all the Technical
Support laptops because BMC Atrium CMDB shows a value of 4 GB in the CI
memory attribute. The comparison job detects this change as a drift because the
baseline that the comparison job is using is outdated. In this case, the baseline was
not updated to reflect the new memory standards.
How is a drift correlated with a change request?

A comparison job detects and displays all drifts regardless of whether the drift is
due to an approved (also called trusted change) or unapproved change. An
approved change is one that has been submitted, approved, and implemented
through the BMC Remedy Change Management change request process.
104 Users Guide

Correlating a drift with a change request
To determine whether a drift is due to an approved change request, the Drift

Management change request correlation service compares all CIs that show drift
to all change requests in the BMC Remedy Change Management database
containing that CI.
The change correlation service only considers the CIs associated with a change
request and the tasks associated with a change request pertaining to a CI.
If the change request is referencing a CI that has drifted, then you know the drift
can be correlated to a change request. This checking applies to all drift types:
modified, added, and deleted.
Configuring drift correlation with a change request

You can configure how change correlation relates a drift with a change request in
the following ways:
Configure relationship types in the change request that are related to a CI. For
details, see Configuring drift correlation to a change request relationship on
page 122.
Configure how long a change request is eligible for correlation to a drift. For
details, see Time window on page 123.
Viewing drifts correlated with a change request

After a comparison job detects a drift, the Drift Management change correlation
service checks if the drift can be related to a change request. Any change request
correlated to a drift is displayed on the Drift Console > View Details screen.

Figure 10-1: Change requests associated with a drift
For each drift correlated to a change request, the following information is

provided:
Status (displayed in the Attributes pane)
Change request ID, correlation type, and change request status (displayed
under the Changes Request tab)
Status
Table 10-1 describes the Status field.
Table 10-1: Status of a drift correlated with a change request

Status Description
New The drift is new and cannot be correlated to a change request created
from Drift Management. If the drift is correlated to a change request
created outside of Drift Management, the results are shown in the
Change Requests tab.
106 Users Guide

Remediating a drift
Table 10-1: Status of a drift correlated with a change request (Continued)

Status Description
Addressed The change request correlated with the drift was created, within Drift
Management, to resolve the drift when found in a previous comparison
job.
Acknowledged The drift is acknowledged using the Drift Console Acknowledge
option. For more information about acknowledging drifts, see
Acknowledging a drift on page 108.
Change request ID, correlation type, and change request

status
The change requests displayed under the Change Requests tab can be filtered
depending on how you configured the correlated drift to the change request status
(using Preferences > Change Status Filter).
For example, if you have configured for the change request statuses of Scheduled
and Completed, only change requests in Scheduled and Completed status are
displayed.
IMPORTANT
Only drifts with a Status of New are displayed.
For more information about the change request ID, correlation type, and change
request status, see Viewing change requests correlated with a drift on page 99.
To view the change request form in detail, go to Drift Console > View Details >
Change Requests tab > click Details.
Within the Change Request form, select the Relationships tab. You will see the
same CIs that are displayed in the Drift Reports Detail window.
Remediating a drift
Remediating a drift involves one of the following scenarios:
You create an incident request to investigate why a drift occurred.
You create a change request to change BMC Atrium CMDB to the correct
baseline state.
You can acknowledge or begin the process of remediating an unapproved drift in
one of the following ways:
Acknowledging a drift on page 108
Creating a change request from the Drift Console on page 108
Creating an incident request on page 110

Acknowledging a drift
You can choose to acknowledge a drift and defer taking any remediation action in
the following scenarios:
In your IT environment, you can perform pre-approved changes, such as weekly
scheduled upgrades or patches, without initialing a change request. The
upgrade or patch changes are scanned into BMC Atrium CMDB. Drift is
detected when a regularly scheduled comparison job runs.
Due to an off-hours escalation, a patch to a server had to be quickly applied
without a change request.
IMPORTANT
You must have Drift Master or Drift Admin privileges to acknowledge a drift.
To acknowledge a drift
1 You can acknowledge drifts in one of the following ways:
From the Drift Console, select the Drift Report containing the drifts you want to
acknowledge
From the Drift Report Details pane
2 Click Acknowledge.
The Acknowledge Drifts pane appears.
3 Select a CI or a group of CIs.
4 Click Acknowledge.
From the Attributes pane of the Drift Report Details screen, you can see the Status
column shows a status of Acknowledged.
NOTE
The attribute status of Acknowledged is overwritten by the next run of the
comparison job. To avoid seeing these drifts again with the next comparison job
run, you must update the baseline of the job to reflect the current state of BMC
Atrium CMDB. For the off-hours escalation scenario, create a change request (to
make an approved change) and update the baseline of the comparison job.
Creating a change request from the Drift Console

You can create a change request directly from the Drift Console.
The advantage of creating a change request from the Drift Console is that the CIs
experiencing drift are automatically related to the change request. Using BMC
Remedy Change Management directly, you must manually associate each CI to the
change request.
108 Users Guide

Remediating a drift
IMPORTANT
You must have Change Master or Change User and Drift Master or Drift Admin
privileges to create a change request.
Before creating a change request

A change request template must exist before you can create a change request
through Drift Management. You do not need to create a new template if existing
templates are available.
To create a change request template, use the following procedure.
NOTE
Only a Change Manager, or users with Change Configuration permissions, can
create change templates for their support group. See Managing Drift
Management permissions on page 27 for instructions on how to set up these
permissions.
WARNING
Drift Management does not support a change request template in which the
Timing field is set to Expedited. All other Timing field values are supported.
To create a change request template

1 From the home page, log in to the Application Administration Console.
2 Click the Custom Configuration tab.
3 From the Application Settings list, choose Change Management > Template >
Template, and then click Open.
The Change Template form appears in New mode.
4 Press F2 to open the form in Create mode.
The Infrastructure Change Templates form appears.
5 After configuring all your settings, click Save to add the new template to the list of
available change templates.
For more information, see the BMC Remedy IT Service Management 7.5.00
Configuration Guide.
To create a change request from the Drift Console

1 From the Drift Console, highlight the Drift Report for which you want to create a
change request.
2 Choose the Change Requests tab, and then click Create Change.
The Create Change Request dialog box appears. The CIs displayed in the Specify
CIs pane of the change request are the same CIs displayed on the Configuration
Items (CIs) pane of the Drift Console.
3 Select a Change Template.

4 From the Specify CIs pane, select the CIs for which you want to create a change
request.
You can select multiple CIs at the same time.
WARNING
When selecting CIs, select only CIs with a drift type of Added or Modified to place
in a single change request. CIs with a drift type of Removed must be placed in a
separate change request and not combined with CIs of drift type Added or
Modified. This is because, depending on the drift type, a different dataset (baseline
or target) is used.
5 Click Create.
After a few moments, a change request ID is created and displayed.
6 Click OK.
After a few moments, the BMC Remedy IT Service Management Change
Management Infrastructure Change Request Information page appears.
The change request, with a status of Draft, is created.
7 To see the CIs associated with this change request, click the Relationships tab.
8 Click Close.
The change request you created using Drift Management goes through the
standard process flow for a new change request.
Sometime after the change request is implemented, if you run the same
comparison job, you will see a different status on the Drift Console for that
particular attribute. The status will be Addressed instead of New.
Creating an incident request

IMPORTANT
You must have Incident Master or Incident User and Drift Master or Drift Admin
privileges to create an incident request.
To create an incident request from the Drift Console

1 From the Drift Console, highlight the Drift Report for which you want to create an
incident request.
2 Choose the Incidents tab (lower right pane), and then click Create Incident.
The Create Incident pane appears.
The CIs displayed in the Specify CIs pane are the same CIs displayed on the
Configuration Items (CIs) pane of the Drift Console.
3 Select an Incident Template.
110 Users Guide

Remediating a drift
4 From the Specify CIs pane, select the CIs for which you want to create an incident
request.
You can select multiple CIs at the same time.
5 Click Create.
After a few moments, an incident request ID is created and displayed.
6 Click OK.
After a few moments, the BMC Remedy IT Service Management Incident
Management Incident Request Information page appears.
The incident request, with a status of Assigned, is created.
7 To see the CIs associated with this incident request, select the Relationships tab.
8 Click Close.
The incident request you created using Drift Management goes through the
standard process flow for a new incident request.
Incident request creation does not affect the status of a drift.

112 Users Guide

Chapter
11 Viewing Drift Reports from

the Drift Dashboard
This section describes the Drift Dashboard and how to view or customize the
displayed data.
About the Drift Dashboard (page 114)
Viewing the data (page 116)
Customizing the data display (page 117)

About the Drift Dashboard

The Drift Dashboard provides a high-level view of current Drift Report data for
individuals requiring a quick status about their data center environment.
Use the Executive Overview to monitor drift in the business services having the
most impact on the overall business or on critical business units. The overview
shows the number of Drift Reports by business service, priority, and compliance
to business baselines. The number of Drift Reports generated per day is also
displayed. The dashboard data is the output of comparison jobs that have detected
drift. If a comparison job does not detect drift, a Drift Report is not generated.
Figure 11-1: Drift Dashboard Executive Overview
114 Users Guide

About the Drift Dashboard
Table describes the dashboards available on the Executive Overview
Table 11-1: Flashboards on the Executive Overview

Flashboard Description
Drift Reports by The number of Drift Reports per business service for a maximum of three business
Business Service services.
In the previous example, the business service is payroll service and is the only service
selected for display. This business service shows six Drift Reports.
By default, randomly any three business services in your organization are displayed
spanning the last 30 days.
The displayed data is filtered by access permissions of the viewer. As a result, you
may not be able to see all Drift Reports due to access permissions to the business
service.
Drift Reports by The number of Drift Reports per baseline for a maximum of three baselines.
Baseline In the previous example, the Security, Unix Servers, and Installed Products
baselines show three, thirteen, and eight Drift Reports respectively.
By default, randomly any three baselines are displayed spanning the last 30 days.
The displayed data is filtered by access permissions of the viewer. As a result, you
may not be able to see all Drift Reports due to access permissions to the baseline.
Drift Reports by The number of Drift Reports by fix priority. The fix priority level is assigned when
Priority the comparison job is created or modified.
In the previous example, eight Drift Reports show a fix priority of Urgent, 16 Drift
Reports show a fix priority of Medium, and 3 Drift Reports show a fix priority of Low.
The displayed data is system-wide data and is not filtered by access permissions of
the viewer.
Drift Reports per Day The number of Drift Reports generated each day for the last seven days.
The displayed data is system-wide data and is not filtered by access permissions of
the viewer.
Related topics
Viewing the data on page 116
Customizing the data display on page 117

Viewing the data

You can refresh or refine the data displayed on the dashboard. You can also view
the details of a Drift Report by drilling down to the Drift Console from the
dashboard.
Viewing the most recent Drift Report activity

By default, the data displayed in the flashboards is for the past thirty days. The
Last Refresh field shows the date and time of the last refresh. The dashboard is not
automatically refreshed. To view the most recent activity, click Refresh.
Viewing Drift Report activity within a specific date interval

You can change the date interval on the Drift Dashboard to narrow or expand the
data displayed.
To view Drift Report activity within a specific date interval

1 Click the Start Date calendar icon and enter a new start date.
2 Click the End Date calendar icon and enter a new end date.
3 Click Refresh.
The new date interval is applied to all flashboards except the Drift Reports per
Day.
Viewing bar chart data in text format

To view the bar chart data in text format, hover the cursor over a bar. Placing the
cursor on a different bar of the chart displays results pertaining to that bar.
116 Users Guide

Customizing the data display
Viewing Drift Report details

To view the details of a Drift Report, you can access the Drift Console from the
Drift Dashboard.
NOTE
The Drift Reports per Day flashboard does not support this feature.
To view the details of a Drift Report

1 Click on any bar within the bar chart.
The Drift Console is displayed showing a summary of all associated Drift Reports
for the selected bar.
Clicking on a different bar of the chart displays different results.
2 From the Drift Console, click View Details to view details about the drifted CIs
listed in the Drift Report.
The Drift Report Details pane displays information about the CIs showing drift.
For information about the fields displayed in the Drift Console and Drift Report
Details panes, see Viewing the Drift Console data on page 92.
Customizing the data display

You can customize the dashboard to display specific business services and
baselines for which you want to view drift activity. You can also change the
schedule for the job supporting the Drift Reports per Day flashboard.
See the following topics:
Selecting business services to view on page 118
Selecting baselines to view on page 118
Changing Drift Reports per Day schedule on page 118

Selecting business services to view

For the Drift Reports by Business Service flashboard, you can specify which
business services to view.
If a Drift Report does not have any business services associated with it, the Drift
Report does not show up in the flashboard data.
To select business services

1 Click the Select Business Services link under the Drift Reports by Business Service
flashboard.
2 From the dialog box displayed, select the Business Services for which you want to
view potential drift events.
3 Click Close.
Selecting baselines to view

For the Drift Reports by Baseline flashboard, you can specify which baselines to
view. This is particularly useful if you want to monitor that your business-critical
computers do not drift from a defined business requirement configuration. This
business requirement configuration is defined in a baseline that has been created
and used in a comparison job. The baseline is stored in your BMC Remedy
AR System database.
To select baselines
1 Click the Select Baselines link under the flashboard.
2 From the dialog box displayed, select the baselines you want to display on the
flashboard.
3 Click Close.
Changing Drift Reports per Day schedule

The Drift Reports per Day flashboard is scheduled to run daily at 11:59 P.M. Using
BMC Remedy Developer Studio, you can change this schedule by modifying the
Flashboard variable on the underlying BMC Remedy AR System form. For more
information, see the BMC Remedy Action Request System 7.5.00 Form and Application
Objects Guide.
118 Users Guide

Chapter
12 Using preferences
This section describes how to set Drift Management preferences for selected
functions.
About preferences (page 120)
Configuring the comparison or snapshot service for better performance
(page 120)
Filtering displayed change requests (page 121)
Configuring drift correlation to a change request relationship (page 122)
Changing the default BMC Remedy AR System Administrator password
(page 123)

About preferences
You can set application preferences for certain functions of Drift Management. As
these preferences are application preferences, not user preferences, any changes
made affect the Drift Management application for all users.
IMPORTANT
You must have Drift Master or Drift Admin privileges to set preferences.
Configuring the comparison or snapshot

service for better performance
To improve the performance of a comparison or snapshot job, you can configure
the following parameters:
Number of CIs retrieved (with one call) from BMC Atrium CMDB for initial
loading into memory
Number of CIs that are compared or copied at a time
Number of processor threads to use
NOTE
For a detailed description of the comparison service, see Comparison service on
page 125.
To configure the comparison or snapshot service

1 From Drift Management, choose Preferences, and then click the General tab.
2 If necessary, adjust the default values as described in Table 12-1.
Table 12-1: Comparison and snapshot service performance options
Option Description
Chunk size during Specifies the number of CIs retrieved from BMC Atrium CMDB in one call when the
initial loading comparison or snapshot job performs an initial load of CIs into memory.
The CIs that are loaded into memory are those that match the qualifications applied to
the baseline and the target. In the case of a snapshot job, the qualification applied to the
source dataset.
If you see database query timeouts, and then lower the size.
Note: An initial load loads each CI with only three attributes (ClassId, InstanceId, and
ReconciliationIdentity).
120 Users Guide

Filtering displayed change requests
Table 12-1: Comparison and snapshot service performance options (Continued)

Option Description
Chunk size during Specifies the number of CIs retrieved from BMC Atrium CMDB in one call after a
comparison determination is made regarding which CIs are eligible for comparison.
The eligible CIs are reloaded into memory with all attributes needed for comparison.
Number of threads Specifies the number of comparison threads that can be active at the same time.
During the initial load of CIs, two threads were used: one to load the baseline CIs and
one to load the target CIs.
3 Click Save Preferences.

The new preferences take effect in the next job run.
Filtering displayed change requests

You can configure Drift Management to filter the display of change requests
correlated with a drift. This filtering is based on the status of the change request.
For example, you want to see the change requests correlated with a drift that are in
Completed status only. You can filter on this status and only those change requests
are displayed on the Drift Console Change Request tab.
The default filtering displays change requests with the following statuses:
Implementation In Progress
Pending
Completed
IMPORTANT
This filtering applies only to New drift that is detected. It does not apply to
Addressed drifts.
To filter by a change request status

1 Select Preferences, and then click the Change Status Filter tab.
The Change Correlation pane is displayed.
2 Add a status by selecting the status in the left pane, and then click Add.
3 Remove a status by selecting the status in the right pane and click Remove.
The Active status indicates which filters are selected.
Your changes are saved when you click Add or Remove.

Configuring drift correlation to a change

request relationship
A change request can be related to several different objects. Because Drift
Management works only with BMC Atrium CMDB data, when the Drift
Management correlation service correlates a drift to a change request, only the
change request relationship with a CI is considered.
You can refine how the correlation service correlates drifts to a change request by:
Using the CI relationship type, for example, Related To, Upgrades, and Repairs.
Specifying a time window for defining how long (in days) a completed change
request is eligible for correlating to a drift.
Use this configuration option when you want a more accurate and detailed view
of the correlation of change requests to a drift. For example, consider a scenario in
which you created a change request to add a new printer to your network. Under
the Relationships tab on the change request, you can select the new CI (printer) and
a relationship type indicating that this CI is a new installation.
In Drift Management, you can indicate the same relationship. The correlation
service uses this information when correlating the drift to the change request,
providing a more detailed view of the drifts correlated to a change request.
Table 12-2 lists the out-of-the-box configurations for relationships with drift types:
Table 12-2: Drift types and relations

Drift Type Related to:
Added Upgrades, Impacts, Installs, and Changes
Modified Upgrades, Repairs, Impacts, Moves, and Changes
Removed Changes and Removes
A change request can also have associated tasks which defines the relationship
with certain types of objects in the parent change request, such as Configuration
Item, LDAP Object, and Software Library Item. The type of relationship is limited
to Related To, but you can specify more attributes for the relationship, such as
Attribute Type which can be Source or Target, Action Attribute such as Install or
Uninstall. This information is used in the change request correlation service.
Use the following guidelines when correlating relationships at the task level:
Relationships at the Task Level are considered only for ADDED and REMOVED
drifts.
ADDED CIs that have a relationship at the Task Level, must have an Attribute
Type of TARGET and an Attribute Action of INSTALL to qualify for the
correlation list.
REMOVED CIs that have a relationship at the Task Level, must have an
Attribute Type of SOURCE and an Attribute Action of UNINSTALL to qualify
for the correlation list.
122 Users Guide

Changing the default BMC Remedy AR System Administrator password
To configure drift correlations to a change request relationship

1 Select Preferences, and then click the Change Correlation Filter tab.
2 Select the change request relation, for example, Installs.
3 Click the appropriate CI relationship button, for example, CI Added.
4 To remove a relationship, select the relationship and click Remove.
Your changes are saved when you click the buttons (CI Added, CI Modified, CI
Removed, and Remove.)
Time window
You can also specifying a time window for defining how long (in days) a change
request is eligible for correlation to a drift. In the Time Window field, enter the
number of days after a change request has reached Completed status that it should
still be considered as a possible source for drift.
Changing the default BMC Remedy AR System

Administrator password
Because Drift Management uses BMC Remedy AR System, you need an
underlying administrator user to communicate with the BMC Remedy AR System
server when running comparison or snapshot jobs. A default BMC Remedy
AR System Administrator User and password, DCA_Drift_Job_Mgr, is provided
with Drift Management.
BMC recommends changing the default password.
IMPORTANT
This option is available only to a user with BMC Remedy AR System
Administrator privileges. The Job Manager Password (tab) is hidden for all other
users.
To change the BMC Remedy AR System Administrator password

1 Select Preferences, and then click the Job Manager Password tab.
2 Enter the new password.
The password cannot be greater than 30 characters in length.
3 Click Change Password.
WARNING
No password verification exists so take care when entering the new password.

124 Users Guide

Appendix
A Comparison service
This section provides details about the comparison service, which is the execution
engine supporting a comparison job.
Overview (page 126)
Initial loading of CIs (page 126)
Identifying CIs for comparison (page 128)
Performing the last load and comparing attributes (page 129)
Tagging CIs with detected drift (page 130)

Overview
When you create a comparison job, you provide a baseline and a target both with
a qualification set. Optionally, for the baseline, you can provide an include and
exclude set that dictates which attributes of a CI to include in the comparison and
which attributes to exclude. You also provide information about the type of
comparison that should be performed: a one-to-one comparison or a many-to-one
comparison; a compare or a compare recursively. With this information, the
comparison job contains the details of the comparison that needs to be performed.
All of the comparison job information is stored in Drift Management-specific BMC
Remedy AR System forms. When you start a comparison job, the job manager is
activated. The job manager is a BMC Remedy AR System plug-in that manages the
running, cancelling, and querying of jobs. After some background processing by
the job manager, the comparison service is called to do the following tasks:
Initial load of the CIs from the source dataset
Identify the CIs to be compared
Load the matched CIs with attributes
Perform the comparison
Identify if drift has occurred between qualifying CIs
Each of these tasks are described in the following sections.
Initial loading of CIs

The first task the comparison service performs is to get a list of all the CIs that
match the qualification set you applied to the baseline and target source datasets.
During the initial loading into memory, the qualified CIs are fetched with only
three core attributes: ClassId, InstanceId, and ReconciliationIdentity. Because
the loading of the baseline CIs and the target CIs can be done separately, the
comparison service creates two separate processing threads to load the CIs.
Processing qualification sets

Qualification sets can have zero (All Objects option of Qualification Builder) or
more qualifications (Custom Qualification Set option of Qualification Builder). If
there are no qualifications (All Objects) to be applied to the source dataset, all CIs
specified in the baseline or target are included.
If qualifications are to be applied, the comparison service creates a query that is
applied to the BMC Atrium CMDB. (When there are no qualifications, the query is
null.) The BMC Atrium CMDB API returns a set of CIs matching the criteria in the
qualification.
The result is the identification of two sets (baseline and target) of CIs for
comparison. The baseline and target CIs are stored in memory ordered by ClassID.
126 Users Guide

Initial loading of CIs
Processing related classes

One of the distinguishing features of Drift Management is the ability to select a set
of CIs based on relationships. This feature is very useful when the selected CIs are
logically related to other CIs. For example, you can select computer systems
related to a particular business service or select products related to a computer
system. The product CIs are only used to filter the computer system CIs. The
product CIs do not take part in the comparison.
WARNING
The Drift Management Qualification Builder allows arbitrary levels of nesting of
related classes. This is an I/O intensive operation, with more levels of nesting
resulting in longer execution of the query takes.
Processing exclude and include sets

After the qualified CIs are loaded into memory, the comparison service addresses
the exclude and include sets.
Included and excluded attributes are uniquely identified by a class-attribute
combination.
The excluded attributes are used to ignore attributes, thus making the comparison
quicker and the Drift Report more relevant. For example, if you are comparing a
set of servers against a golden server, you would likely exclude the host name
attribute because it is different from the golden server.
The included attributes identify the attributes to be included in the comparison
and the conditions that define a drift. The conditions are designated by the
comparison operator and value entered for each included attribute. With included
attributes, you can override the default comparison of equality (==) with other
comparisons, such as LT (less than) and GT (greater than). In addition, you can
override the baseline attribute value with your own value against which to
compare the target attribute.

Identifying CIs for comparison

After the initial loading and setup of the CIs is completed, the next step is to
identify the CIs to be compared. The comparison service performs two types of
comparisons: compare regular and compare recursive. These comparisons are
further enhanced by specifying the cardinality for the compare: one-to-one and
many-to-one.
Each of the comparisons and how they work together is described.
Compare regular
A compare regular refers to the comparison of top level CIs only. No other related
CIs are compared.
Compare recursive
A compare recursive compares the top level CIs and their weakly related children.
The qualification set you apply to your baseline or target, only selects the top-level
CIs. The comparison service loads all the weakly-related children for a CI and
compares them as well. All child CIs, at all levels, are loaded.
One-to-One
The comparison service must identify which two CIs (one from the baseline and
one from the target) represent the same instance. To do this, the comparison
service uses the ReconciliationIdentity attribute created by the Reconciliation
Engine. Any CIs in the baseline or target that have not been identified by the
Reconciliation Engine are not compared. The comparison service stores this new
set of matching CIs in memory.
A one-to-one comparison can be combined with a compare regular and a compare
recursive.
Many-to-One
A many-to-one comparison is used when you want to check a pre-defined
configuration (golden server) against all CIs of the same kind. For example, you
might want to perform a comparison to verify all your web servers have the same
standard configuration.
128 Users Guide

Performing the last load and comparing attributes
With a many-to-one comparison, you compare many target CIs with one baseline
CI. Each CI in the target is compared with the single CI in the baseline. The number
of CIs in the baseline cannot be more than one. If the qualification set you apply to
the baseline evaluates to more than one CI, the comparison service stops execution
and displays the following error message:
Many to one specified: Baseline must have a single CI. This baseline has
<NN> CIs.
There are no restrictions on the number of CIs in the target.

The difficulty with a many-to-one comparison is identifying the CIs instances. The
ReconciliationIdentity attribute cannot be used in a many-to-one comparison
because the same CI instances are not being compared.
Instead, the top-level CI is identified by class type. For example, if the baseline CI
belongs to the BMC_ComputerSystem class, then all CIs in the target are compared for
that class. All others are ignored.
Unfortunately, if the compare recursive option is selected when creating a
comparison job, the same logic cannot be used to identify the child CIs. To
correctly identify the child CIs, the comparison service uses the Reconciliation
Identification Rules located in the RE:Identify_Rules form. These rules specify the
attributes per class that need to match to be identified. For example, the
Reconciliation Engine rule states that for products the class type, the name, and the
version number must match.
Performing the last load and comparing

attributes
Although CIs have been identified for comparison, because those CIs were initially
loaded with just three attributes, the comparison service needs to reload the CIs
with all the attributes needed for comparison. Based on the include and exclude
attribute set, the comparison service launches multiple threads to load and
compare the attributes needed for each class. The baseline and target CIs are
loaded in parallel and another thread compares the CIs. By default, 500 CIs are
loaded at time, but you can configure this number from the Preferences menu
option of Drift Management. The Compare thread performs the comparison of
attributes values based on the comparison operator specified, for example, NE, EQ,
GT, LT.

Tagging CIs with detected drift

The comparison service compares the CIs as defined by the comparison job and if
any of the CIs fail to meet the comparison criteria, this failure (change) is flagged
as a drift. A drift is defined in one of the following ways:
All unmatched CIs in the baseline are tagged with drift type Removed.
All unmatched CIs in the target are tagged with drift type Added.
The remainder of the CIs that are matched by the ReconciliationIdentity
attribute are compared. If any CI fails the operation comparison, the CI is tagged
as drift type Modified.
A Drift Report for the job is written to an BMC Remedy AR System form that the
Drift Console and Dashboard can display and query. Each drift can contain drift
details showing the attributes of a CI that failed to meet the comparison criteria.
For all CIs with detected drift, the comparison service identifies all the business
services that are affected by the drift as well.
130 Users Guide

Appendix
B Context-sensitive Help
Baselines
The Baselines List of Items pane displays a list of available baselines, and
associated details, that you or your group has created.
Description
The List of Items is a library of baselines. Only persons belonging to the group
displayed in the Accessible To field are able to see the baseline and its associated
details.
The Details pane displays the name of the qualification, and any include and
exclude sets, used by the baseline. Click the View link to display the
low-level details (classes, attributes, logic) of a baseline component
(qualification, include, exclude) within the Qualification Builder.
The Job Membership pane shows which comparison jobs use the baseline and
the status of the job. The job status can be Active or Inactive. Active means the
job is scheduled to run or can be run manually. Inactive means the job is not
scheduled to run nor can it be run manually. The status can be changed from the
Job Console.
Actions
You can:
Click Create to create a new baseline by using the Baseline Wizard.
Click Edit to modify a baseline by using the Baseline Wizard. You can modify
any part of a baseline.
Click Delete to delete a baseline. A baseline is easily deleted if not used in a job.
If the baseline is part of a comparison job, before you can delete the baseline, you
must delete all jobs containing the baseline or modify those jobs to use a
different baseline.

Targets
The Targets List of Items pane displays a list of available targets and associated
details that you or your group has created.
Description
The List of Items is a library of targets. Only persons belonging to the group
displayed in the Accessible To field are able to see the target and its associated
details.
The Details pane displays the name of the qualification used in the target.
Clicking the View link displays the qualification within Qualification Builder
allowing you to see the low-level details (classes, attributes, logic) of the target.
The Job Membership pane shows which comparison job uses the target and the
status of the job. Job Status can be Active or Inactive. Active means the job is
scheduled to run or can be run manually. Inactive means the job is not scheduled
to run nor can it be run manually. The status can be changed from the Job
Console.
Actions
You can:
Click Create to create a new target by using the Target Wizard.
Click Edit to modify a target by using the Target Wizard. You can modify any
part of a target.
Click Delete to delete a target. A target is easily deleted if not used in a job. If the
target is part of a comparison job, before you can delete the target, you must
delete all jobs containing the target or modify those jobs to use a different target.
132 Users Guide

Qualification Sets
Qualification Sets
The Qualification Sets List of Items pane displays a list of available qualification
sets and their associated details.
Description
The List of Items is a library of qualification sets.
The Details pane displays information, such as the owner of the qualification set
and what group can access or view the qualification.
The Baseline, Target, and Job Membership pane shows which baseline, target, or
snapshot job uses the qualification set.
Actions
You can:
Click Create to create a new qualification using the Qualification Builder.
Click Edit to modify a qualification using the Qualification Builder.
Click Delete to delete a qualification. Before you can delete the qualification, you
must delete all jobs containing the qualification or modify those jobs to use a
different qualification.

Include Sets
The Include Sets List of Items pane displays a list of available include sets and their
associated details.
Description
The List of Items is a library of include sets.
When an include set is selected, additional information is displayed in the
Details and Baseline Membership panes.
The Details pane displays information, such as the owner of the include set,
which group has access permissions, and last modified date.
The Baseline Membership pane shows which baselines use the include set.
Actions
You can:
Click Create to display the Qualification Builder to create an include set.
Click Edit to display the Qualification Builder to modify the selected include set.
Click Delete to delete an include set.
134 Users Guide

Exclude Sets
Exclude Sets
The Exclude Sets List of Items pane displays a list of available exclude sets and
their associated details.
Description
The List of Items is a library of exclude sets.
When an exclude set is selected, additional information is displayed in the Details
and Baseline Membership panes.
The Details pane displays information, such as the owner of the exclude set, which
group has access permissions, and last modified date.
The Baseline Membership pane shows which baseline uses the exclude set.
Actions
You can:
Click Create to display the Qualification Builder to create an exclude set.
Click Edit to display the Qualification Builder to modify the selected exclude set.
Click Delete to delete an exclude set.

Select a drift component

Depending on which wizard (comparison job, snapshot job, baseline, or target)
you are using, you can select an existing drift component (target, baseline,
qualification set, include, or exclude set) from the displayed List of Items.
Description
The Details pane displays information, such as the owner, create date, last
modified date, and access groups of the drift component.
For targets and baselines, to view the details of any subcomponent, click the
View link.
The Membership pane shows which baseline, target, or job uses the drift
component.
Actions
You can:
Select an item from the List of Items and click Select Item.
The component is displayed on the wizard pane and is available for use.
Cancel the action.
136 Users Guide

Snapshot Job Wizard
Snapshot Job Wizard

Use the Snapshot Job Wizard to create a copy or snapshot of your BMC Atrium
CMDB configuration data. The data is stored in a dataset that, depending on your
use, can become your baseline or target dataset used in a comparison job.
For example, you might schedule a snapshot job to run every week to make a copy
of a particular set of CIs. After a period of time, you have a series of snapshots
(such as Snapshot1, Snapshot2, Snapshot3, Snapshot4). On the first of each month,
you run a comparison job comparing Snapshot4 against Snapshot1 to determine
whether there has been any drift. In this case, Snapshot1 is your baseline and
Snapshot4 is the target.
Depending on the volatility of your data, you might compare the most recent
snapshot (Snapshot4) with the second most recent (Snapshot3). In this scenario,
Snapshot3 would be the baseline for your comparison job and Snapshot4 would be
the target.
Topics
Provide General Information on page 137
Specify a Destination Dataset on page 138
Specify a Source Dataset on page 138
Specify a Source Qualification Set on page 139
(Optional) Assign a Schedule for Running the Job on page 146
Provide General Information

Provide the following general information about the snapshot job:
Table B-1: General Information Options for Snapshot Job
Field Description
Name and Description A meaningful name and description for the snapshot job.
Status Indicates if the job is flagged for execution. You have two
options:
Active (default)Choose Active if you want the job to run.
The job can be submitted manually (Start Job) or set to run on
a schedule.
InactiveChoose Inactive if you do not want the job to run.
For example, you might make a job inactive after several runs,
but you want to keep it around for historical or record keeping
purposes. If later you need to run the job, you can change the
status to Active.

Table B-1: General Information Options for Snapshot Job (Continued)

Field Description
Accessible To: Specifies the permission group(s) that can see the job on the Job
Console. In conjunction with role permissions, this field
determines who can view, execute, modify, and delete the job.
For example, if this field is set to Drift Master, all the users
belonging to the Drift Master group can see the job and only they
have execution privileges. (Execution privileges are controlled
by who can see the job. If you do not see a job displayed, you do
not have permission to execute the job.)
More than one group can be specified. You can manually delete
the default (Public).
For more information about Drift Management roles and
permissions, see Managing Drift Management permissions on
page 27.
Copy Child CIs Copies the selected CI (parent) and all weakly related child CIs.
Note: The default is to copy only the top level CIs.
Specify a Destination Dataset

The destination dataset is where you want to copy the data.
To specify a destination dataset

1 Specify a destination dataset using one of the following actions:
Click Select.
From the Dataset Name menu, choose the dataset to use. This menu is
populated from BMC Atrium CMDB and the dataset names displayed depend
on your Drift Management login permissions.
Click Create.
In the Dataset Name field, enter a name for the dataset you are creating.
2 In the Accessible To field, select which groups can view or write to the dataset.
You can select more than one group.
Specify a Source Dataset

Provide a source dataset from which to copy your data. This menu is populated
from BMC Atrium CMDB, which has a list of all available datasets. The dataset
names displayed are based on your Drift Management permissions. As a result,
different users might see different dataset names.
138 Users Guide

Snapshot Job Wizard
WARNING
If you create a dataset using the Reconciliation Console to use as the source dataset
for a snapshot, baseline, or target, you must add Drift Master permissions to the
CMDBRowLevelSecurity attribute of the dataset for it to be visible from the Snapshot
Job, Baseline, or Target Wizards.
Specify a Source Qualification Set

A qualification set is a query that returns a specific set of CIs. Use a qualification
set to refine the CIs of interest in your source dataset.
To specify a source qualification set

1 Specify a qualification set to apply to the source dataset using one of the following
actions:
Click Create.
The Qualification Builder appears.
Use the Qualification Builder, and associated Help, to create a new qualification
set. Saving the qualification returns you to the Select Source Qualification Set
pane and the details of the qualification set are displayed.
Click Select.
The Qualification Sets List of Items displays the available qualification sets.
Select the qualification set you want to use and click Select Item. The Select
Source Qualification Set screen appears and the details of the qualification set
are displayed.
(Optional) Assign a schedule for running the job

If you do not want to provide an automatic run schedule for the job, you can skip
this step. After the job is created, you can manually start the job from the Job
Console by clicking Start Job.
Assign a schedule by specifying the days of week and time.
The job you created appears on the Job Console.

Baseline Wizard
A baseline defines a set of CIs used as the basis for comparison for detecting drift.
Topics
Select a Baseline Dataset on page 140
Specify a Qualification Set on page 141
Specify an Include Set on page 141
Specify an Exclude Set on page 142

The baseline you create is used in a comparison job, and is stored in the baseline
list of items to be used by others or by yourself in other comparison jobs.
To provide general baseline information

1 Provide a meaningful name for the baseline you are creating.
2 Use the default description or provide your own.
3 In the Accessible To field, define group permissions.
Group permissions allow you to control who can view, modify, or use the baseline.
You can add more than one group.
NOTE
The access or permission groups assigned through the Accessible To field only
allow you to view the baseline in a list, not the data contained in the baseline.
Permissions to view the contents of the baseline are controlled by BMC Atrium
CMDB permissions and any additional permissions you applied using instance
permissions as described in Managing Drift Management permissions on
page 27.
Select a Baseline Dataset

A dataset is a logical collection of CIs in BMC Atrium CMDB. A dataset can
represent data from a particular source or a snapshot from a particular date.
To select a baseline dataset

From the Dataset menu, select the dataset to use as the source for your baseline CIs.
This menu is populated from BMC Atrium CMDB, which has a list of all available
datasets. The dataset names displayed are based on your Drift Management
permissions. As a result, different users might see different dataset names.
140 Users Guide

Baseline Wizard
The source dataset for your baseline can be:

BMC Asset or any BMC Atrium CMDB dataset
A snapshot of a dataset
WARNING
Specify a Qualification Set

A qualification set is a query that returns a set of CIs based on the query. Use a
qualification set to refine the CIs in your baseline.
To specify a qualification set

Specify a qualification set to apply to the baseline using one of the following
actions:
Click Create.
set. Upon saving the qualification, the Specify a Qualification Set screen and the
details of the qualification set are displayed.
Click Select.
Select the qualification set you want to use and click Select Item. The Specify a
Qualification Set screen and the details of the qualification set are displayed.
Specify an Include Set

An include set contains the attributes to include (consider) during the comparison
of CIs by the comparison job.
To specify an include set

Specify an include set using one of the following actions:
Click Create
The Qualification Builder appears. Use the Qualification Builder, and associated
Help, to create a new include set. After you save the include set, the Specify an
Include Set screen and the details of the include set are displayed.
Click Select
The Include Sets List of Items displays the available include sets.

Select the include set you want to use and click Select Item. The Specify Include
Set screen and the details of the selected include set are displayed.
Specify an Exclude Set

An exclude set contains the attributes to ignore during the comparison of CIs. Any
attribute in the exclude set is not included in the Drift Report details of a
comparison job.
To specify an exclude set

Specify an exclude set using one of the following actions:
Click Create
The Qualification Builder appears. Use the Qualification Builder, and associated
Help, to create a new exclude set. After saving the exclude, the Specify Exclude
Set screen and the details of the exclude set are displayed.
Click Select
The Exclude Sets List of Items displays the available exclude sets. Select the
exclude set you want to use and click Select Item. The Specify Exclude Set screen
and the details of the selected exclude set are displayed.
142 Users Guide

Target Wizard
Target Wizard
A target defines a collection of CIs that you are comparing to a known or correct
baseline.
Topics
Select a Target Dataset on page 143
Specify a Qualification Set on page 144

The target you create is used in a comparison job to detect drift, as well as stored
in the target library to be used by others or by yourself in other comparison jobs.
To provide general information

1 Provide a meaningful name for the target you are creating.
2 Use the default description or provide your own.
3 In the Accessible To field, define access permissions.
Access permissions allow you to control who can view, modify, or use the target.
You can add more than one group.
Select a Target Dataset

The source dataset contains a collection of CIs that you want to compare against
the baseline.
To select a target dataset

From the Dataset menu, select the source dataset for your target CIs.
Your source dataset can be:
A BMC Atrium CMDB dataset, for example, BMC Asset.
A snapshot of a dataset at a given point in time
WARNING

Specify a Qualification Set

A qualification set is a query that returns a set of CIs matching the query. You use
a qualification set to narrow the CIs in your target dataset.
To specify a qualification set

Specify a qualification set to apply to the target dataset using one of the following
actions:
Click Create
set. Upon saving the qualification, the Specify Qualification Set screen and the
details of the qualification set are displayed.
Click Select
Select the qualification set you want to use and click Select Item. The Specify
Qualification Set screen and the details of the qualification set are displayed.
144 Users Guide

Comparison Job Wizard
Comparison Job Wizard

Use the Comparison Job Wizard to wrap the baseline and target datasets together
in a job, select the type of comparison to perform, add a job run schedule, and other
possible job actions.
Topics
Specify a Target on page 146
Specify a Baseline on page 146
(Optional) Create an automatic incident request on page 146
(Optional) Assign a Schedule for Running the Job on page 146

Provide the following general information about the comparison job:
Table B-2: General Information Options for Comparison Job
Field Description
Name and Description Provides a meaningful name and description for the comparison
job.
Priority Defines the fix priority for drifts detected by the job. The priority
selected here is displayed on the Drift Console for each Drift
Report resulting from a run of this job.
Status Indicates if the job is flagged for executed. There are two options:
Active (default)Use active if you want the job to be executed.
The job can be submitted manually (Start Job) or set to run on
a schedule using the Comparison Job Wizard.
InactiveUse inactive if you do not want the job to be
executed. For example, you might inactive a job after several
runs, but you want to retain it for historical or record keeping
purposes. If you need to run the job later, you can change the
status to active and submit.
Compare Recursively Compares the top level CIs and their children CIs until there are
no more CIs to compare. (The default is Compare which only
compares the top level CIs.)
For additional information on compare recursively and one-to-
many, see Before creating a comparison job.
Many-to-One A many-to-one comparison of CIs from the target to the baseline.
(The default is a one-to-one comparison.)
Accessible To: Specifies the groups that can have access to this job. For more
information about permissions, see Managing Drift

Specify a Target
NOTE
If you have not created a target for this job, do so now using the Target Wizard.
1 On the Select Target pane, click Select Target.

2 From the Target List of Items, highlight the target you want to use.
In the Details and Job Membership panes, details about the target are displayed, as
well as a list of other jobs using this target.
3 Click Select Item.
The target pane appears displaying the details of the target you selected.
Specify a Baseline
NOTE
If you have not created a baseline for this job, do so now using the Baseline Wizard.
1 From the Baseline pane, click Select Baseline.

2 From the Baselines List of Items, select the baseline you want to use; click Select
Item.
3 The Baseline pane appears displaying the details of the baseline.
If you selected an incorrect baseline, click Select Baseline to return to the Baseline
List of Items.
(Optional) Create an automatic incident request

If you want the comparison job to create an automatic incident request ticket if drift
is detected, enter the following information, and then click Next. Otherwise, click
Next to continue.
1 From the Incident pane, click Select Incident Template.
2 Select the appropriate template (software or hardware), and click Select.
The Comparison Job Wizard incident pane appears, displaying the details of the
incident template you selected.
(Optional) Assign a Schedule for Running the Job

If you do not want to provide an automatic run schedule for the job, skip this step.
After the job is created, you can start the job manually from the Job Console by
clicking Start Job.
To assign a time schedule for the job, select the Time Driven icon and choose the
day(s) of week and time.
The job you created appears on the Job Console.
146 Users Guide

Glossary
action CI class
Specific steps that can be taken when A class that defines a type of CI, such as a
unapproved drift is detected. Steps include computer system or software application.
sending email, generating help desk class
notifications using BMC Remedy Incident Metadata in the BMC Atrium CMDB defining
Management, or taking corrective actions a type of object, usually a CI or relationship.
using BMC Remedy Change Management. Either of these types of class can store data as
approved change a regular class, categorization class, abstract
Changes in an IT environment that have class, or abstract class with data replication.
passed an approval or certification process or You can apply the final class and singleton
can be associated with a change request. class options to it as well.
Currently approved configuration is Common Data Model (CDM)
comprised of configuration baselines plus The object-oriented, hierarchical set of classes
approved changes to those baselines. in the BMC Atrium CMDB used to represent
attribute types of CIs and relationships. The CDM is
A property or characteristic of a class, such as based on industry standards such as the
the IP address of a computer system. An Common Information Model (CIM) and
attribute equates to a column on a database Microsofts Windows Management
table or a field on an BMC Remedy AR System Instrumentation (WMI).
form. compare
Authoring A comparison task type that performs a
The component of Drift Management used to top-level comparison between uniquely
create a baseline, target, qualification set, include identifiable CIs determining which CIs have
set, or exclude set definitions. been removed, added, or modified. You set
baseline the comparison task type when creating a
A set of CIs and their associated attributes used comparison job.
as the basis for comparison to detect if drift has compare recursive
occurred. A comparison task type that performs a
Baseline Wizard comparison of CIs and a comparison between
An interface that guides you through the steps the children of each CI until the leaf CIs are
needed to create a baseline. The baseline is reached. You set the comparison task type
comprised of a source dataset, qualification set, when creating a comparison job.
and optionally, an include set and exclude set. comparison job
CI The action of detecting differences between a
See configuration item (CI). baseline and a target. The job performs a
comparison between two sets of CIs (baseline
CIs and target CIs).
Glossary 147
Comparison Job Wizard discovery application

The interface that guides you through the An application that scans your environment
steps needed to create a comparison job. for configuration data and can act as a provider
comparison service to the BMC Atrium CMDB.
The component of Drift Management that drift
evaluates the qualification sets used to compare The difference between the current state and
a baseline and a target. A drift is the generated the expected or correct state of a CI, attribute or
output of the comparison service. relationship. Drifts are caused by the addition,
comparison type removal, or modification of CIs, CI attributes,
See compare or compare recursive. or CI relationships.
configuration data Drift Console
Data about your IT environment, consisting of The component of Drift Management from
CIs and relationships. which you view Drift Reports detected by the
running of a comparison job and from which
configuration discovery you take the appropriate action to correct a
The process of scanning your IT environment drift.
to collect system and configuration data to
provide up-to-date information about the drift monitoring
infrastructure. This information is stored in Viewing drift events for acknowledgement or
the BMC Atrium CMDB. action.
configuration item (CI) Drift Report
A physical, logical, or conceptual entity that is The output of a comparison job. A Drift Report
part of your IT environment and has lists all the differences detected during the
configurable attributes. Examples include comparison of the target CIs with the baseline
computer systems, buildings, employees, as defined in the comparison job.
software, and business services. One of the exclude set
two types of classes in the BMC Atrium The attributes to exclude (ignore), on a class
CMDB. See also relationship. basis, during the comparison of two CIs for
Configuration Management Database (CMDB) that class.
A database that stores information about your include set
IT configuration, including both CIs and The attributes to include (consider), on a class
relationships. basis, during the comparison of two CIs for
correlation service that class.
The component of Drift Management that metadata
associates a drift with a change request. Definitions that describe the data stored in the
dataset BMC Atrium CMDB. Examples include a class
A logical group of data, a collection of CIs, in in the data model and a special class to define
the BMC Atrium CMDB. A dataset can things such as datasets.
represent data from a particular source, a monitoring
snapshot from a particular date, or other See drift monitoring.
purpose. The dataset used by BMC Software multitenancy
products for reconciled production data is The separation of data and access so that a
named BMC Asset. single BMC Atrium CMDB can contain the
discovery data of multiple parties, but each party can
See configuration discovery. access only their own data.
148 Users Guide

Glossary
qualification unapproved change

A Boolean statement that is evaluated to Changes in the configuration of an IT
determine whether an instance should be environment that have not been approved or
included in an activity, such as a return of certified and can not be correlated with a
query results. change request.
qualification set weak relationship
A group of qualifications that allows you to An optional characteristic for relationship
specify a single CI or groups of CIs. classes, signifying that the members of a
Qualification sets are used in snapshot jobs, relationship form a composite object that can be
baselines, and targets. reconciled as one. The destination member is
reconciliation considered the weak member of a weak
The process of managing data in multiple relationship, existing as part of the source
datasets using the Reconciliation Engine. The member.
main activities of reconciliation are
identifying, comparing, and merging
datasets.
Reconciliation Engine
The component of the BMC Atrium CMDB
that reconciles data from different datasets.
relationship
A connection between two CIs such as a
dependency or membership. An instance of a
relationship class. See also configuration item
(CI).
relationship class
A class that defines a type of relationship
between CIs, such as a dependency or
membership.
snapshot
A set of data that represents a configuration at
a certain point in time, usually stored in its
own dataset. There can be multiple snapshots
of a given configuration.
Snapshot Job Wizard
The interface that guides you through the
steps needed to create a snapshot job.
target
The CIs in your data center environment that
you are comparing with a known or correct
baseline.
Target Wizard
The interface that guides you through the
steps required to create your target CIs using a
dataset and a qualification set.
Glossary 149
150 Users Guide

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A BMC Software, contacting 2

business services, viewing 99
Accessible To 52, 59, 65, 84
acknowledging a drift 108
Active status 84 C
All Objects 51 change request
AND conjunction 72 correlated to a drift 99
Application Administration Console correlation 104
about 37 creating 109
Custom Configuration tab 37 Chunk size
application preferences during comparison 121
BMC Remedy AR System Admin password 123 during initial loading 120
filtering displayed change requests 121 CI Instance Class Id 96
performance 120 Compare Recursively 84
attributes comparison job
about 24 about 81
processing of 129 access permissions 84
auditing 19 before creating 83
automation 19 canceling 86
checking status 86
B creating 45
definition 22
baseline 58 deleting 86
creating 43 details 80
defined by ITIL 58 fix priority 84
definition 22 history 80
deleting 61 modifying 86
modifying 61 output 82
permissions 59 scheduling 87
Baseline Wizard 59 viewing job details 88
BMC Asset 41, 59 viewing job history and job logs 88
BMC Remedy AR System Comparison Job Wizard 83
Administrator User 123 comparison service 81, 125
tables 58 comparisons, types of 81, 128
BMC Remedy Change Management Computer System Name 96
about 19 configuration items
permission groups 30 identifying for comparison 128
BMC Remedy Incident Management viewing 96
about 19 viewing attributes 97
permission groups 30 Copy Child CIs option 51, 52
Index 151
correlated change requests Drift Reports per Day 115

configuring drift 122 Drift Viewer permission group 29
filtering by status 121
filtering by time 123
correlation types 100 E
creating exclude sets
change request 108 about 77
incident request 110 creating 78
customer support 3 definition 24
guidelines 78
D processing 127
Execution privileges 52, 138
dataset permissions 59
destination dataset 42, 50, 53
discovery 18 F
drift filtering the display of correlated change
caused by 18, 104 requests 121
correlating with a change request 104 fix priority 115
correlation statuses 106 forms
correlation to a change request 122 Group 36
definition 18 home page 41
remediating 107 opening 37
status of 98 People 35
types of 83, 96, 130
viewing 47
viewing drifts correlated with a change G
request 105
Group form 36
Drift Admin permission group 28
groups. See permission groups
Drift Console
customizing 100
viewing data 92
viewing the Drift Console data 92
H
Drift Dashboard home page form 41
about 114
accessing Drift Console 117
changing Drift Reports per Day schedule 118
I
modifying the date interval 116 Inactive status 84
refreshing the data 116 incident request
selecting baselines 118 automatic creation 85
selecting business services 118 correlated to drift 100
Drift Master permission group 28 creating 110
Drift Reports include sets
about 92 about 76
comparison jobs 82 creating 76
deleting 94 definition 24
Drift Dashboard overview 114 guidelines 76
filtering 93 processing 127
viewing 93, 95 Infrastructure Change
Drift Reports by Baseline 115 Master permission group 30
Drift Reports by Business Service 115 User permission group 30
Drift Reports by Priority 115
152 Users Guide

J Q
Job Console 52, 80 qualification sets
job status definition 23
Active 52, 84 processing 126
Inactive 52, 84
R
M Reconciliation Console 53, 59, 65
many-to-one comparison 84 Reconciliation Engine 25
multitenancy 31 related classes, processing 127
N S
Number of threads 121 scenarios 26
snapshot 50
snapshot job
O creating 41
opening definition 23
forms 37 deleting 55
home page form 41 details 80
OR conjunction 72 history 80
modifying 54
scheduling 54
P Snapshot Job Wizard 52
source dataset
People form 35
definition 23
performance parameters for jobs 120
snapshot job 53
Permission Group dialog box 35
support, customer 3
permission groups
about 28
Drift Admin 28
Drift Management
T
about 28 tab, Custom Configuration 37
creating 36 target 64
default 36 creating 44
Drift Admin 28 definition 22
Drift Master 28 deleting 66
Drift Viewer 29 modifying 66
Drift Master 28 permissions 65
Drift Viewer 29 steps for creating 64
Incident Master 30 Target Wizard 65
Incident User 30 technical support 3
Infrastructure Change Master 30
Infrastructure Change User 30
snapshot job 52, 138
U
permissions, Drift Management URL, main console 40
creating users in users
People form 35 creating in User form 34
User form 34
groups, about 28
product support 3
Index 153
W
wizard
baseline 59
comparison job 83
snapshot job 52
target 65
154 Users Guide

*100645*
*100645*
*100645*
*100645*
*100645*

Drift7.5 UserGuide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Drift7.5 UserGuide

Încărcat de

Drepturi de autor:

Formate disponibile

BMC Configuration Drift Management 7.5.

Copyright 2009 BMC Software, Inc.

Restricted rights legend

Support by telephone or email

Before contacting BMC Software

Chapter 1 Introduction to Drift Management 17

Chapter 2 Managing Drift Management permissions 27

Chapter 4 Creating snapshots 49

Chapter 5 Creating baselines 57

Chapter 6 Creating targets 63

Chapter 7 Creating qualification sets and include and exclude sets 69

Chapter 8 Creating and managing comparison jobs 79

Chapter 9 Viewing Drift Reports 91

Chapter 11 Viewing Drift Reports from the Drift Dashboard 113

Chapter 12 Using preferences 119

Appendix A Comparison service 125

Title Document provides Audience Format

Title Document provides Audience Format

Drift Management and Section 508

How to Desktop Web

This section introduces the BMC Configuration Drift Management application.

Chapter 1 Introduction to Drift Management 17

About Drift Management

Figure 1-1: Drift Management architectural overview

Chapter 1 Introduction to Drift Management 19

Drift Management and ITIL

Figure 1-2: Drift Management concepts

Qualification set (required)

Include or exclude set

Chapter 1 Introduction to Drift Management 21

Chapter 1 Introduction to Drift Management 23

Figure 1-3: Drift Management workflow

Chapter 1 Introduction to Drift Management 25

Where to go from here

2 Managing Drift Management

Chapter 2 Managing Drift Management permissions 27

Understanding Drift Management permission

Table 2-1: Drift Management permission groups (Continued)

Using Drift Management with BMC Remedy Change

Chapter 2 Managing Drift Management permissions 29

Understanding instance permissions

Defining instance permissions

Chapter 2 Managing Drift Management permissions 31

To define instance permissions

Examples of Drift Management instance permissions

Table 2-3: Example Drift Management permission groups

Chapter 2 Managing Drift Management permissions 33

Creating users with Drift Management

To create a user with Drift Management permissions in the User form

To create users with Drift Management permissions in the People form

1 Open the Application Administration Console.

Chapter 2 Managing Drift Management permissions 35

Creating groups to use with Drift Management

To create groups to use with Drift Management

Table 2-4: Group form fields for Drift Management

5 Save your changes.

Using the Application Administration Console

Figure 2-1: Application Administration ConsoleCustom Configuration tab

Chapter 2 Managing Drift Management permissions 37

The following topics are provided:

Chapter 2 Getting started 39

Accessing Drift Management

To access Drift Management using a browser