Module 4

Managing Inventory and

Software Metering
Module Overview
• Overview of Inventory Collection
• Configuring Hardware Inventory
• Configuring Software Inventory
• Managing Inventory Collection
• Configuring Asset Intelligence
• Configuring Software Metering
Lesson 1: Overview of Inventory Collection
• What Is Inventory Collection?
• Uses of Inventory Data
• The Inventory Collection Process
 What Is Inventory Collection?

Inventory collection is:

The process of gathering information that describes the

hardware and software installed on a client computer

Configured by using client settings for the hierarchy

or assigned on a per-collection basis

Hardware
Inventory Data

Software
Inventory Data

Asset
Intelligence Data
Uses of Inventory Data
Uses of hardware and software inventory data include:

Building queries based upon hardware configuration or

installed software

Building collections on the basis of queried inventory results

Creating reports to display hardware configuration or

installed software details

Maintaining corporate standards

Troubleshooting client problems

Collecting files (software inventory only)

The Inventory Collection Process

Site Site Database

Server Server
1 Collect inventory

Deliver data to management

2 point
Client
3 Deliver data to site server
Management
Point
4 Update site database

5 Replicate to the
central administration site

Inventory information can be viewed at a site after that site’s

database has been updated
Lesson 2: Configuring Hardware Inventory
• How Is Hardware Inventory Collected?
• Options for Collecting Hardware Inventory
• Extending Hardware Inventory
• Demonstration: Configuring Client Settings for Hardware
Inventory
How Is Hardware Inventory Collected?

Hardware inventory obtains inventory information by querying

the WMI database on the client computer

Hardware Inventory agent collects:

Initial full hardware inventory

Subsequent delta inventories

Options for Collecting Hardware Inventory
Extending Hardware Inventory

Methods used to extend hardware inventory include:

Modifying the default classes in the Client Settings

Connecting to a source computer to import specific

hardware inventory classes

Importing or exporting custom MOF files

Modifying the Configuration.MOF file

Configuring and collecting custom MIF files

Demonstration: Configuring Client Settings for
Hardware Inventory
In this demonstration, you will see how to:
• Configure hardware inventory
• Customize hardware inventory collection
Lesson 3: Configuring Software Inventory
• How Is Software Inventory Collected?
• The Process for Configuring Software Inventory File Types
• The Process for Configuring File Collection
How Is Software Inventory Collected?

The software inventory process:

Collects data directly from files by reading the file header

information

Can collect file system details even from unknown files that
may not have information in their file header

Collects copies of files that you specify and stores them on

the site server

Enables you to view collected inventory and collected file

information by using Resource Explorer or view software
inventory information in reports
 The Process for Configuring Software Inventory
File Types

To configure new software

inventory rules:
1 Create a new inventory rule

2 Type the file name or variable

3 Specify the location

4 Specify whether to exclude

encrypted and compressed files

5 Specify whether to exclude files

in the Windows directory

Specify the reporting detail for all rules

The Process for Configuring File Collection

To configure a file collection:

1 Create a new file collection entry

2 Type the name of the file that you

want to collect

3 Specify the path to the file

for which to search

4 Specify whether to exclude

encrypted and compressed files

5 Set the maximum total file size

for the files to be collected
Lesson 4: Managing Inventory Collection
• Initiating Inventory Cycle on a Client
• Viewing Inventory Results
• Demonstration: Initiating Inventory Collection on a Client
• Considerations for Securing Inventory Collection
• Troubleshooting Inventory Collection
Initiating Inventory Cycle on a Client

To initiate hardware inventory,

software inventory, or file
collection:
Select the appropriate inventory
action
1
Click Run Now to start the cycle

Note: Manually initiating

inventory collection is helpful
for testing and demonstration,
but is not usually performed on
a regular basis
Viewing Inventory Results
Use Resource Explorer and
inventory reports to view
hardware and software
inventory results
Demonstration: Initiating Inventory Collection
on a Client
In this demonstration, you will see how to:
• Initiate inventory collection on a client
• Use Resource Explorer to view hardware inventory
• View inventory by using reports
Considerations for Securing Inventory Collection

Consider implementing the following security options for client

inventory reporting:

Enable inventory
signing and encryption
encryption

Disable custom
MIF file MIF
collection
file collection

Do
Do not
not use
use file
file collection
collection to
to collect
collect critical
critical files or
or sensitive files
sensitive information

Use an appropriate deletion interval for aged inventory data

and collected files
Troubleshooting Inventory Collection

Inventory collection troubleshooting tasks:

Review Client log files: Review site server
InventoryAgent.log log files:
CcmExec.log Dataldr.log
Policyagent.log Sinvproc.log
FileSystemFile.log Management point log files:
Mifprovider.log MP_Hinv.log
MP_Relay.log
MP_Retry.log

Review other components:

Status message queries
Lab A: Configuring and Managing Inventory Collection
• Exercise 1: Configuring Hardware Inventory
• Exercise 2: Configuring Software Inventory

Logon information
Virtual 10747A-NYC-DC1-B 10747A-NYC-CFG-B
10747A-NYC-CL1-
machine B

User name Contoso\Administrator

Password Pa$$w0rd

Estimated time: 30 minutes

Lab Scenario
Based upon the latest organizational requirements, you
need to modify your hardware and software inventory
strategy. The first mandate requires all Configuration
Manager clients to report hardware inventory. The default
hardware inventory should take place every two days using
a simple schedule. You also need to configure a custom
hardware inventory configuration for all Windows 7
workstations. Windows 7 workstations will use the default
two-day reporting schedule; however, several additional
reporting classes are required for additional reporting
requirements. The latest organizational requirements also
state that Windows 7 workstations must provide a software
inventory of any log files stored on local hard disks.
Lab Review
• How can you configure hardware and software inventory
to minimize network impact?
• How can you determine whether hardware has changed on
a managed computer?
• You have configured software inventory to collect a large
number of log files. However, you have noticed that no
files are being collected. How can you troubleshoot and
correct the issue?
• How can you determine the last time that hardware and
software inventory was reported from a client?
Lesson 5: Configuring Asset Intelligence
• Overview of Asset Intelligence
• The Asset Intelligence Catalog
• Configuring Asset Intelligence Data Collection
• Demonstration: Enabling the Collection of Asset
Intelligence Data
• Managing Asset Intelligence
Overview of Asset Intelligence

Asset Intelligence enhances hardware inventory and includes the

following components:

Asset Intelligence catalog

Asset Intelligence synchronization point

Asset Intelligence home page

Asset Intelligence reports

The Asset Intelligence Catalog

Asset Intelligence catalog features:

Over 300,000 software titles

Ability to import software license

information

Periodically updated through System

Center Online Services

Administrators can add custom

categories, families, and labels
 Configuring Asset Intelligence Data Collection

Configuring Asset Intelligence can include the following tasks:

Enabling Hardware Inventory and Software Metering

Enabling Asset Intelligence Inventory Reporting Classes

Enabling Windows Event Log settings

Importing software license information

Installing an Asset Intelligence synchronization point

Configuring Asset Intelligence maintenance tasks

Configuring Asset Intelligence security

Demonstration: Enabling the Collection of Asset
Intelligence Data
In this demonstration, you will see how to:
• Enable Asset Intelligence Reporting Classes
• Import Software License Information
• Install an Asset Intelligence Synchronization Point
Managing Asset Intelligence

Managing Asset Intelligence includes:

Viewing Asset Intelligence reports

Updating the Asset Intelligence catalog

Requesting software categorization

Resolving software details conflicts

Lab B: Configuring and Managing Asset
Intelligence
• Exercise 1: Preparing the Site for Asset Intelligence
• Exercise 2: Configuring Asset Intelligence
• Exercise 3: Customizing Asset Intelligence
• Exercise 4: Viewing Asset Intelligence Reports

Logon information
Virtual 10747A-NYC-DC1-B 10747A-NYC-CFG-B 10747A-NYC-CL1-B
machine
User name Contoso\Administrator
Password Pa$$w0rd

Estimated time: 15 minutes

Lab Scenario
After evaluating Asset Intelligence, you decide to
implement the feature to take advantage of the extensive
hardware and licensing reports. You need to configure all
prerequisites, configure Asset Intelligence reporting classes,
and configure the Asset Intelligence Catalog to integrate
with System Center Online.
Lab Review
You run an Asset Intelligence report to find computers
that are used by multiple users, but the report displays no
records. How can you troubleshoot and correct the issue?
Lesson 6: Configuring Software Metering
• Overview of Software Metering
• How Software Metering Works
• Configuring the Software Metering Agent and Rules
• Demonstration: Configuring Software Metering Rules
• Software Metering Maintenance Tasks
Overview of Software Metering

Software metering is the process of gathering detailed data on

program usage from client computers in a Configuration
Manager site

Types of data collected:

Program usage information

File information

Program information
How Software Metering Works

Monitored Software
program 1 Metering
Monitored Agent
program
Monitored
program
3
2
4

When the Software Metering Agent is enabled, data is:

Site
1 Collected each time a monitored program runs and terminates
Server
2 Uploaded to the management point on a scheduled basis

3 Forwarded to the site server

4 Added to the site database

Configuring the Software Metering Agent and Rules

Enable the Software Metering

Agent and configure a reporting
schedule

When enabled, software

metering will:
To create a software metering rule:
Automatically
1 Navigate to the Softwaregenerate
Metering node
disabled rules from recent
usage history
2 Create a new software metering rule
Generate automatic rules
3 Provide relevant information
on the basis for the file
of a specified
that you want to meter
percentage of computers
using a program
4
Apply the rule to other sites if applicable
Demonstration: Configuring Software Metering
In this demonstration, you will see how to:
• Configure the Software Metering Agent
• Configure a software metering rule
• Configure automatic software metering rule generation
• View software metering reports
Software Metering Maintenance Tasks

Software metering maintenance tasks help manage collected

usage data

Summarize software metering tasks:

Summarize Software Metering File Usage Data

Summarize Software Metering Monthly Usage Data

Delete software metering data tasks:

Delete Aged Software Metering Data

Delete Aged Software Metering Summary Data

Lab C: Configuring Software Metering
• Exercise: Configuring Software Metering

Logon information
Virtual 10747A-NYC-DC1-B 10747A-NYC-CFG-B 10747A-NYC-CL1-B
machine
User name Contoso\Administrator
Password Pa$$w0rd

Estimated time: 15 minutes

Lab Scenario
You are implementing the Software Metering feature
of Configuration Manager 2012. You need to configure
software metering and create appropriate software
metering rules.
Lab Review
• You have created a new software metering rule for a
specific application that is installed on both Windows XP
and Windows 7 clients. You notice that only Windows 7
clients are reporting usage data. What might be the
problem?
• What is the advantage of using the Browse button as
opposed to manually entering the file name?
• Can software metering account for the same application
running locally as well as from a Terminal Services or
Remote Desktop session?
Module Review and Takeaways
• Review Questions