Module 11:

Configuration Management and

Connectors

1
Lesson objectives
Understand Configuration Management
Plan what should go into the CMDB
Identify the CIs (put into CMDB)
Control the CIs
Verification and Audit (is the CMDB up to
date?)
Connectors
Active Directory
Operations Manager
Configuration Manager
Opalis
Import CSV files
2
Configuration Management

3
Configuration Management
Understand which CI types (objects) you
want to put in the CMDB
SQL Databases
Logical Desks
Workstations
Telephones
Projectors
Can be cost driven E.g.. Everything under
$100 does not go into the CMDB

4
Configuration Management
Start with most critical Systems / Services /
Servers
Everything under a CI is considered an
attribute e.g.. RAM, CPU
Rule: Everything you would like to manage
should be in the CMS (CMDBs)
Be pragmatic and take one step ad the
time.
Everything at once will not work.

5
Configuration Management
Don’t register anything that doesn't give
value (Support SACM vision)
Don’t register anything you can’t control /
update.
Investigate which CI you will get from your
connectors
Compare this list with your CI list
Prepare how the remaining CI should get
into the CMS and how you can update
these in an easy way. (Automatic vs.
Manual)
6
Service Manager Data Management

Data Management Infrastructure

SM DB, SM SDK, Object Model, Connector Framework
Service Manager Database
• Shared schema with OpsMgr
• IT assets/services as Configuration Items (CIs)
• Incidents/change requests/problems as Work Items (WIs)
• History is tracked for each CI or WI
• Connectors sync data with external systems
• ConfigMgr, OpsMgr, Active Directory connectors

7
Configuration Item Management
Viewing Configuration Items
Grid View, Forms
• Out-of-box CI forms and views: Computer, Software,
Software Updates, Printers, Services
• Custom Views, Generic Forms
History: property and relationship changes
Related Items: CI, Work Item, File, Knowledge
Work Items affecting CIs
Configuration Item Administration
Editing, Deleting, Creating CIs
Role-based Security

8
CI Properties and Relationships
CI Status
What state of management is the CI?
Uses AssetStatus property
Note: ObjectStatus property is for internal use to mark CIs for
deletion pending confirmation
CI Custodian
Who is responsible for supporting this CI?
Last Inventoried
When was latest SCCM inventory run on this computer?
Notes Tab
Work Items Affecting this CI
Work Items Related to this CI

9
Editing an Existing CI
Why edit a CI?
Add data to properties not populated by connectors
Correct errors in data
CI edits
Users edit data via CI forms: computer, software,
update, printer, service, generic
Limitation: User edits of properties populated by
connectors will be overwritten if any updates to object
Best Practice is to correct data at the data source

10
Deleting CIs
Processes for CI Deletion
Manual
Sync with Data Source
Connector Deletion
Two Steps to Remove CIs from SM DB
Status Property of CI: Active, Pending Delete
First step of delete process changes status property
Second step is for Admin to confirm deletion

11
CI History
History kept for each property or relationship change
For computer form, you only see changes to logical
computer class
For changes to OS or Hardware, need to create view & and then
look at form for associated instance

12
Grooming and Data Retention
Grooming is a background job
CI data is not automatically groomed
Work Item data is automatically groomed
Status must be "closed" (not active or resolved)
Data retention period settings
Data Warehouse includes data groomed from SM DB
History data is automatically groomed
Data retention period settings
Subscription workflows must have "looked at" the data
For auditing and governance, we recommend
using SM DB backups
13
Service Manager
Configuration Management

14
Configuration Management
Integrated CMDB

Manage IT objects as configuration

items (CIs) and relationships
Manage related work items (WIs)
such as incidents and change
requests that can be measured
against key performance indicators
(KPIs)
Automated population and update
of CMDB

Relationships

15
Connectors
Service Maps

16
Service Maps

Describe IT-related Business Services

e.g., “Email” (not “Exchange”)
Supports troubleshooting and impact analysis in V1
Includes business metadata related to IT Service
Management
Services are realized by technical components tied
together with dependency relationships
Foundation for Service Level Management processes

Service = Technical Data + Business Data

17
Using Service Maps
2 approaches:
Bottom-up
 Take individual CIs discovered in SCOM, SCCM
 OM MPs (Exchange, AD, SharePoint)
 LOB apps (Using Distributed App Designer)
 Add relevant business data
Top-down
 Start with team members identifying the important aspects of
the service (users/groups, key CIs, key dependencies)
 Populate CI instances
 Manually create the dependency tree
Example services:
Application-based services, Computer infrastructure
Integrate with Incident Management processes
Notifications
18
Example Service Map - Messaging
Defining Dependencies that Impact Availability
Antivirus
Develop OLAs with owners
Exchange Server 2007 Key Services
Windows 2003 Enterprise Server
Etc. AD
Applications
DNS
Network
Etc.
Services
Dell xxxx
HP yyyy
Other zzzz Develop SLAs with Key
E-mail Hardware
Customers
CEO
Management
Client Access
Hosted
Mailbox
Everyone else
Public Folder Customers
Settings Etc.
19
Service Maps vs. Distributed App
Service Maps can be imported from
Operations Manager
In Operations Manager Service Maps are
referred to as Distributed Applications
Only CI that are in Operations Manager will
be part of a distributed Application when
imported into Service Manager
Service Maps can be updated in Service
Manager after importing to Service
Manager

20
What Is A Distributed Application
Applications that interact
to provide a service
Runs on many physical
tiers—Scale out, over the
internet, disparate
networks
Heterogeneous
components—Legacy
applications, Partner Web
Services

21
Demonstration

Service Maps

22
Connectors
Active Directory Integration

23
Create CI from Active Directory
Import data from Domain or OU
Cross-forest support
Sync Active Directory data for:
Users
Groups
Printers
Computers
User contact information
Organizational information
Notification addresses
24
 How to Create a Connector
Go to Administration, Connectors
Create Connector, Active Directory Connector
Select domain or OU
Enter credentials
Select objects to synchronize

• Initial synchronization
then daily sync
− CIs are created for new objects
− For existing CI, data is merged
• Connector can be disabled to
stop automatic sync
• Deleting the connector also
deletes all CIs that were not
modified from other sources

25
Configuration Items created by AD connector

26
Filters in AD connector
Two types of connectors
Static
Dynamic

Filtering options
By OU
By Object

27
Connectors
Integration with System Center
Configuration Manager

28
What is synchronized?
Sync computer data into Service Manager
Configuration Items
Hardware Inventory
Software Inventory
Software Updates
Asset Intelligence top console user as
primary user of computer
Create incidents from Desired Configuration
Management (DCM) errors
Request software application installation
(machine-based provisioning)
29
 How to create a connector
Go to Administration, Connectors
Create Connector, Configuration Manager Connector
Select Configuration Manager Database
Select Collections to synch
Enter credentials
• Initial synchronization
then daily sync
− CIs are created for new objects
− For existing CI, data is merged
• Connector can be disabled to
stop automatic sync
− Will not stop already running
synchronization
• Deleting the connector also
deletes all CIs that were not
modified from other sources
30
What is “Desired Configuration
Management”?
From TechNet:
Desired configuration management enables you to define configuration
standards and policies, and audit compliance throughout the enterprise against
those defined configurations. Best practices configurations can be used from
Microsoft and vendors in the form of Microsoft® System Center Configuration
Manager 2007 Configuration Packs. These Configuration Packs can then be
refined to meet customized business requirements. This feature is designed to
provide data for use by many groups within the organization, including IT and
corporate security.

Examples of DCM Scenarios

Detect Server Configuration Drift
Report Compliance on Corporate Policy
Change Tracking and Verification
31
Why do I need DCM?
DCM provides the following important
benefits:
Lowers TCO of Windows environment
Shown to increases system reliability and
uptime
Assists in managing compliance and auditing
efforts
Powers the Corporate Compliance and
Governance component
Lowers risk of displacement of SCCM and used
to drive value of System Center (ECAL and
SMSE)
32
 DCM Process Flow
Imported Configuration
Imported
Knowledge
Knowledge
1
Items created by ConfigMgr
import
Database
Windows
Windows Line-of-business
Line-of-business Antivirus
Antivirus
Server 2003
Server 2003 Application
Application Software
Software
New CI
CI CI
CI CI
CI
2 Configuration Compliance
Compliance
Items authored State
State
ConfigMgr
ConfigMgr Line-of-business
Line-of-business Tables
Admin
Admin Application
Tables
Application
Console
Console Server
Server
3 Configuration Baseline
Baseline
Baseline defined
using
System Center
CIs
ConfigMgr Server

ConfigMgr 4 Configuration baseline

Managed assigned 6
WMI
Client WMI 5 to collection Compliance
DCM state sent to
Script XML
XML discovers ConfigMgr
Script
CIs and Database
Active
Active
Directory validates for reporting
Directory
Registry data Configuration
SQL
SQL Registry Configuration Manager
Manager Client
Client
File
against
File rules
Software
Software IIS
Updates IIS
Updates

MSI
MSI

33
Create Incidents from DCM
Create Incidents automatically from DCM
compliance errors
Need to select DCM Baselines and CIs from
which to create Incidents
Connector will sync all DCM compliance errors
Workflow will create Incidents only for the DCM
errors that were selected
One incident per computer and per
noncompliant CI
Can create a lot of incidents

34
Scenario: Automating Compliance with DCM

CLIENT DCM INCIDENT INCIDENT CHANGE REMEDIATION

MANAGED DRIFT CREATED DIAGNOSED REQUESTED ACTION

IT Analyst /
Operator

35
Filters in Configuration Manager
connector
Filter by collection (Only collections with
content will show)

36
Connectors
Integration with System Center
Operations Manager

37
What is Synchronized
Create CIs from Operations Manager
Discovered Objects
Create Service Maps from Distributed
Applications
Create Incidents from Operations Manager
Alerts
View alert details
Update Alert status when changing incidents
properties in Service Manager

38
Service Definition & Mapping
Service = Business definition + Technical
Definition
Technical Definition collected from
Operations Manager
Business Definition entered in Service
Manager Console or imported from other
sources
Helps for Troubleshooting and Impact
Analysis

39
 How to Create a CI Connector
Go to Administration, Connectors
Create Connector, Operations Manager CI Connector
Server Name
Enter credentials
• Initial synchronization
then daily sync
− CIs are created for new objects
− For existing CI, data is merged
• Connector can be disabled to
stop automatic sync
− Will not stop already running
synchronization
• Deleting the connector also
deletes all CIs that were not
modified from other sources
40
How to Create an Alert Connector
Go to Administration, Connectors
Create Connector, Operations Manager Alert Connector
Server Name
Incident Template
Enter credentials
Create a subscription in Operations Manager

• Alerts synchronized every

30 seconds
• Connector can be disabled
to prevent synchronizing
the alerts

41
Scenario: Automating SCOM Alert  Incident

SERVICE ALERT INCIDENT INCIDENT INCIDENT INCIDENT

MONITORED GENERATED CREATED DIAGNOSED RESOLVED CLOSED

CONNECTOR CONNECTOR

IT Analyst /
Operator

42
Connectors
Integration with Opalis

43
Service Manager Data Integration using
Opalis
Service Manager syncs data between its CMDB and other
product databases using Opalis to support data integration
and interoperability across the Enterprise
BMC Atrium CMDB HP Operations for UNIX
BMC Remedy AR System HP Operations Windows

BMC Event Manager HP Operations Solaris

BMC Patrol HP Network Node Manager

BMC BladeLogic Operations Manager HP Service Desk

CA AutoSys HP Service Manager

CA eHealth HP Asset Manager

HP iLO 2
CA Service Desk
CA SPECTRUM IBM Tivoli Enterprise Console

CA Unicenter NSM IBM Tivoli Netcool/Omnibus

VMware VI / vSphere IBM Tivoli Storage Manager

Symantec VERITAS NetBackup EMC Smarts InCharge

44
Practical Tips for Connectors
Connector Administration
Create New Connector: using ‘run as’ accounts
Edit Existing Connector: can’t change data source
Enable/Disable Connector: use this to prevent new data from data
source
Delete Connector: use this to remove data from data source
Sync Now: initiates request, does not mean sync is completed
Tracking Progress of Connectors
Connectors view shows connector status
Event viewer (Look for ‘LFx Service’ events)
Each connector sync is an asynchronous collection of multiple
“sessions”

45
SC Integration Overview
Configuration Items are synchronized
via connectors unidirectional into the Work Items are synchronized via
CMDB workflows
• CM – Computers with inventory, • CM – unidirectional into the CMDB
collections, DCM baselines for DCM baseline violation as
• OM – MP inventory, distributed Incidents
applications • OM – Bidirectional for Incidents
• AD – Users, groups, printers, generated from Alerts
computers CMDB

CONNECTORS

Active Directory

Changes to CI’s are manifested as manual activities or automated activities (e.g. software requests)
• Users can create workflows for custom automated activities using the authoring tool

46
CSV Import Tool
CSV data can imported via UI task
Needs XML format file and .csv data file
Can import any Class and Relationship data
http://blogs.technet.com/servicemanager/archive/2009/05
/26/using-the-csv-import-feature.aspx
Format file example:
<CSVImportFormat>
<Class Type="Microsoft.Windows.Computer">
<Property ID="PrincipalName"/>
<Property ID="IPAddress"/>
</Class>
</CSVImportFormat>

48
Summary and Class Discussion
Understand how Configuration Management can
be used with Service Manager
Data integration comes from connectors and .csv
import tool
Connectors are:
Active Directory Connector
Configuration Manager Connector
Operations Manager Connector

49
Configuration Management &
Connectors Review Questions
Which CIs should you put in the CMDB?

Which Connectors are supported by Service

Manager?

What is imported from AD?

50
Hands on Lab

Service Manager
Integration

51
 © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

52