IntroductiontoSystemCenterConfigurationManager

Introduction to System Center Configuration Manager (SCCM) 2007

Microsoft® Virtual Labs


Table of Contents

Introduction to System Center Configuration Manager (SCCM) 2007 .................................. 1

Exercise 1 Exploring the Configuration Manager Console ........................................................................................... 2

Exercise 2 Exploring Software Distribution and Maintenance Windows ...................................................................... 8

Exercise 3 Exploring Software Updates and WSUS Integration ................................................................................. 10

Exercise 4 Exploring Operating System Deployment ................................................................................................. 13

Exercise 5 Exploring Desired Configuration Management ......................................................................................... 16


Page 1 of 17

Introduction to System Center Configuration

Manager (SCCM) 2007

Objectives

After completing this lab, you will be better able to:

� Use the Configuration Manager Console to verify the site configuration.

� Use the Configuration Manager Console to identify new features of

Configuration Manager including:

� Software distribution and maintenance windows

� Software updates and WSUS integration

� Operating system deployment of Windows Vista

� Desired configuration management

� And other miscellaneous Configuration Manager features

Scenario Scenario Description

Prerequisites Prerequisites

Estimated Time to Complete This Lab

75 Minutes

Computers used in this Lab Server

Denver

The password for the Administrator account on all computers in this lab is:

password


Page 2 of 17

Exercise 1 Exploring the Configuration Manager Console

Scenario In this exercise, you will use the Configuration Manager Console to view the Configuration Manager site

configuration. You will be using the Configuration Manager Console through the rest of this lab to identify new

features of Configuration Manager.

Tasks Detailed Steps

Complete the following

task on:

Server

1. To view the

Configuration

Manager home page

Note: Complete this procedure from the primary site server computer only.

a. If not already running, on the Start menu, click ConfigMgr Console.

The Configuration Manager Console window appears. Notice that the

Configuration Manager Console uses the Microsoft Management Console (MMC)

version 3, which provides a tree pane on the left of the window, a larger results

pane in the middle, and an Actions pane on the right side of the window.

b. In the tree pane, click System Center Configuration Manager.

The main System Center Configuration Manager home page appears in the results

pane. Notice that the home page includes information regarding the help available

in administering Configuration Manager.

Note: Was Configuration Manager able to connect to the default start page?

No, as identified by the last paragraph of text in the results pane.

c. In the tree pane, expand System Center Configuration Manager, and then click

Site Database.

The System Center Configuration Manager home page appears in the results pane.

Notice that the home page includes information helpful to complete the site

configuration to deploy Configuration Manager clients.

Note: What are the five steps identified to deploy Configuration Manager clients?

Configure the management point, determine if you need a server locator point,

configure the fallback status point and reporting point, install the ConfigMgr client,

and configure client agents.

Note: In the next five procedures, you will explore these five tasks to ensure your site

can deploy clients. This will help you to become familiar with the Configuration

Manager Console for the remainder of this lab, as well as the other Configuration

Manager labs. You will begin with validating the configuration of the management

point, which is listed as step #1.


task on:

Server

2. To verify the

management point

configuration (step

#1)

Note: In following procedure, you will verify that the management point is configured,

which is a requirement to support all Configuration Manager clients.

Note: Complete this procedure from the Configuration Manager site server in the

Configuration Manager Console.

a. In the tree pane, expand Site Database, expand Site Management, expand MCM,

expand Site Settings, and then click Site Systems.

The list of site systems appears in the results pane.

Note: How many Configuration Manager site systems are listed for the site?

Two - SMSClient and SMSServer.

b. In the tree pane, expand Site Systems, and then click SMSClient.


Page 3 of 17


The list of site system roles for SMSClient appears in the tree pane.

Note: What site system roles are configured for SMSClient?

ConfigMgr distribution point and ConfigMgr site system.

SMSClient is running Windows XP Professional as the operating system, and is

configured as a branch distribution point – one of the new Configuration Manager

features. SMSClient is not configured as a management point, so you need to

verify that the other site system is configured as a management point.

c. In the tree pane, under Site Systems, click SMSServer.

The list of site system roles for SMSServer appears in the tree pane.

Note: Is SMSServer configured as a management point?

Yes, the ConfigMgr management point role is listed for SMSServer.

d. In the results pane, click ConfigMgr management point.

Notice that there are two different sets of actions available in the Actions pane.

The top set of actions are appropriate for the items that is selected in the tree pane

(in this case SMSServer as a site system) and the bottom set of actions are for the

item selected in the results pane (in this case, the ConfigMgr management point).

When using the Configuration Manager Console’s Actions pane, it is important

that you use the appropriate action – sometimes the same action will be available

for both selected objects.

Often you will also notice an information section at the bottom of the Actions

pane providing information on the item selected in the results pane.

e. In the Actions pane, under ConfigMgr management point, click Properties.

The ConfigMgr management point Properties dialog box appears displaying the

current configuration of the management point.

Note: Does the management point support devices?

No

Note: Does the management point support Internet-based clients?

No

f. Click Cancel.


g. In the tree pane, under Site Settings, click Component Configuration.

The list of configurable components appears in the results pane. Notice that one of

the components that you can configure is the management point.

h. In the results pane, click Management Point Component, and then in the Actions

pane, under Management Point Component, click Properties.

The Management Point Properties dialog box appears displaying the current configuration of the management point.

Note: Is SMSServer configured as the default management point for this site?

Yes

i. Click Cancel.

The list of configurable components appears in the results pane.

You have now used the Configuration Manager Console to verify that the site

server computer, SMSServer, is configured as the default management point for

the site MCM. Step #2 is to determine if the site requires a server locator point.

You will verify that in the next procedure.


Page 4 of 17



task on:

Madrid

3. To verify the site is

publishing to Active

Directory (step #2)

Note: In following procedure, you will determine if the site requires a server locator

point. A server locator point should only be required if the site is not publishing its

data to Active Directory or if the site contains non-Active Directory clients.

Note: Complete this procedure from the site server in the Configuration Manager

Console.

a. In the tree pane, under System Center Configuration Manager, expand Site

Database, expand Site Management, click MCM, and then in the Actions pane,

click Properties.

The MCM – SCCM 2007 Primary Site Properties dialog box appears displaying

general properties for the site.

b. Click the Advanced tab.

The MCM – SCCM 2007 Primary Site Properties dialog box appears displaying

advanced properties for the site.

Note: Is the site configured to publish to Active Directory?

Yes

If the site is publishing to Active Directory, then there is no requirement for the

site to have a server locator point, unless the site will contain clients that cannot

retrieve data from Active Directory, such as workgroup clients.

c. Click Cancel.

The Configuration Manager Console appears.

d. On the Start menu, point to Administrative Tools, and then click Active

Directory Users and Computers.

The Active Directory Users and Computers window appears.

e. In the tree pane, expand smsdomain.smsdemo.microsoftcom, expand System,

and then click System Management.

The data published to the System Management container appears in the details

pane. This is where Configuration Manager publishes its data to Active Directory.

Note: Is the site successfully publishing data to Active Directory?

Yes, there is data in the System Management container.

f. Close Active Directory Users and Computers.

The Configuration Manager Console appears.

You have now used the Configuration Manager Console to verify that the site is

publishing data to Active Directory, and thus no server locator point is required.

Step #3 is to verify that the site has a fallback status point and reporting point to

generate client deployment reports. You will verify that this has been completed in

the next procedure.


Page 5 of 17



task on:

Sydney

4. To verify site system

configuration (step

#3)

Note: In following procedure, you will verify that the site has a fallback status point as

well as a reporting point.


Console.


expand Site Settings, and then expand Site Systems.

Note: How many site systems are listed for the site?

Two, SMSClient and SMSServer.

b. In the tree pane, expand Site Systems, and then click SMSClient.

The list of site system roles for SMSClient appears in the tree pane.

Note: What site system roles are configured for SMSClient?

ConfigMgr distribution point and ConfigMgr site system.

SMSClient is running Windows XP Professional as the operating system, and is

configured as a branch distribution point – one of the new Configuration Manager

features. SMSClient is not configured as either a fallback status point or reporting

point, so you need to verify that the other site system is configured as a

management point.

c. In the tree pane, under Site Systems, click SMSServer.


Note: Is SMSServer configured as a fallback status point and reporting point?

Yes, the ConfigMgr fallback status point and ConfigMgr reporting point roles are

listed for SMSServer.

d. In the Actions pane, under ConfigMgr fallback status point, click Properties.

The ConfigMgr fallback status point Properties dialog box appears displaying

the current configuration of the fallback status point.

Note: How often are messages forwarded from the fallback status point to the site

server?

Every 300 seconds (five minutes)

e. Click Cancel.


You have now used the Configuration Manager Console to verify that the site is

running mixed mode, and will automatically approve clients from trusted domains.

Step #4 is to install Configuration Manager clients. You will verify that this has

been completed in the next procedure.

5. To verify client

deployment (step #4) Note: In following procedure, you will verify that clients have been installed in the

site.


Console.

a. In the tree pane, expand Site Database, expand Computer Management, and

then expand Collections.

The list of collections appears in the results pane.

b. In the tree pane, click All Systems.

The members of the All Systems collection appear in the details pane. Notice that

the site server computer (SMSServer) and the Windows XP Professional client

computer (SMSClient) appear as members. Notice also that another computer,

TestComputer1, is a member of the collection.


Page 6 of 17


Note: Are all the computers in the site installed as clients?

No, TestComputer1 is not a client

c. In the tree pane, expand Site Database, expand Site Management, expand MCM,

expand Site Settings, and then click Client Installation Methods.

The configurable client installation methods appear in the results pane.

Note: What client installation methods are available for configuration?

Software Update Point Client Installation and Client Push Installation.

d. In the results pane, click Software Update Point Client Installation, and then on

the Actions menu, click Properties.

The Software Update Point Client Installation Properties dialog box appears.

Note: Could either of the clients have been installed by the Software Update Point

Client Installation method?

No, as it is not enabled.

Software Update Point Client Installation allows the installation of the

Configuration Manager client through a Configuration Manager software update

point, which uses WSUS 3.0 to install the client.

e. Click Cancel.

The configurable client installation methods appear in the results pane.

f. In the results pane, click Client Push Installation, and then on the Actions menu,

click Properties.

The Client Push Installation Properties dialog box appears. Notice that the

Client Push Installation method is not enabled. However, the client still could have

been installed via this method, when forced using the Client Push Installation

Wizard.

g. Click the Accounts tab.

The Client Push Installation Properties dialog box appears displaying the

account properties for the installation method.

Note: Can any clients be installed through client push?

Yes, even though the automated client push installation method is not enabled, an

account is configured, so the Client Push Installation Wizard can be used.

h. Click Cancel.

Even if no account was listed on the Accounts tab of the Client Push Installation

Properties dialog box, Configuration Manager could use the site server’s computer

account as the Client Push Installation account. Without looking at log files or

status messages, you cannot identify how a client was installed. Clients can also be

installed through manual installation as well as Group Policy deployment. For

your information, these two clients were installed using the Client Push

Installation Wizard.

i. In the tree pane, expand Site Database, expand Computer Management, expand

Reporting, and then click Reports.

The list of reports appears in the results pane.

j. In the results pane, click Client Deployment Success Report, and then in the

Actions pane, under Client Deployment Success Report, click Run.

The Client Deployment Success Report results appear in the results pane.

Note: What clients were configured to send state messages to the fallback status

point?


Page 7 of 17


SMSClient and SMSServer

You have now used the Configuration Manager Console to verify that the site has

clients installed and reporting successfully to the site. The final step is to configure

the client agents. You will verify that this has been completed in the next

procedure.

6. To verify client agent

configuration (step

#5)

Note: In following procedure, you will verify that the appropriate client agents are

configured for the site.

Note: Complete this procedure from the Configuration Manager site server in the



expand Site Settings, and then click Client Agents.

The list of client agents appears in the results pane. Notice that there are new client

agents in addition to those that were included in SMS 2003. The agents were

enabled using default configuration through the Configuration Manager Setup

program.

Note: Will hardware inventory, software inventory, software update compliance and

desired configuration compliance data be collected from the clients?

Yes, as those four client agents are enabled for the site.

Note: Can software applications be distributed to the clients?

Yes, the Advertised Programs Client Agent is enabled for the site.

Note: Can clients be quarantined due to network access protection policies not being

met?

No, the Network Access Protection Client Agent has not been enabled for this site.

You have now used the Configuration Manager Console to verify that the site can

successfully install and collect data from clients, including inventory and

deployment state messages. You have also explored the Configuration Manager

Console. You will continue to use it in the next exercise to validate some of the

new features included in Configuration Manager. For the remainder of this lab, a

number of Configuration Manager features have already been implemented, and to

get you familiar with those features, you will determine their implementation and

status.


Page 8 of 17

Exercise 2 Exploring Software Distribution and Maintenance Windows

Scenario In this exercise, you will use the Configuration Manager Console to identify software distribution to determine why

a client was unsuccessful in running an advertisement.



task on:

Server

1. To verify software

distribution status

Note: Complete this procedure from the primary site server computer only in the



then click Software Distribution.

The software distribution home page appears in the results pane displaying the

status of the current advertisements. The home page provides a quick view at the

status of the most active advertisements in the site. Notice that the home page

provides a listing of deployments as well a graph of the selected deployment’s

status.

Note: What is the status of the SMS 2003 Toolkit 2 deployment?

One client was successful in the deployment, while the second client reported a

failure.

b. Under Advertisement Name, click SMS 2003 Toolkit 2.

The Status of a specific advertisement report appears in the results pane

displaying the status of the SMS 2003 Toolkit 2 advertisement. Notice that the

report indicates that one client was successful running the advertisement while one

failed.

c. Click the arrow next to Failed.

The All systems resources for a specific advertisement in a specific state report

appears in the results pane displaying the list of clients that failed to successfully

run the SMS 2003 Toolkit 2 advertisement.

Note: What client failed to run the SMS 2003 Toolkit 2 deployment successfully?

SMSServer

Note: What was the last status message from this client for this advertisement?

Program may never run due to Service Window Constraints.

This status message indicates that the client (SMSServer in this case) could not run

the program due to maintenance window restrictions.

d. In the tree pane, expand Site Database, expand Computer Management, and

then click Collections.

The list of collections appears in the results pane. Notice that there is a new

column in the results pane, that for Maintenance Windows.

Note: You may have to scroll to the right in the results pane to view the Maintenance

Windows column.

Note: What collections have maintenance windows assigned to them?

All Windows Server 2003 Systems and All Windows XP Systems.

SMSServer is the site server, so is a member of the All Windows Server 2003


Page 9 of 17


Systems collection. An easy way to identify the maintenance windows available

for a specific client is with a report.

e. In the tree pane, expand Site Database, expand Computer Management, expand

Reporting, and then click Reports.

The list of reports appears in the results pane.

f. In the results pane, click Maintenance Windows Available to a Particular

Client, and then in the Actions pane, under Maintenance Windows Available to

a Particular Client, click Run.

The Maintenance Windows Available to a Particular Client Report

Information report appears in the results pane. As this is a prompted report, you

must supply the computer name of the client you wish to view the maintenance

windows for.

g. In the Client Name box, type SMSServer, and then click Display.

An Internet Explorer window starts and display the Maintenance Windows

Available to a Particular Client report. Notice that there is one maintenance

window available to the client. Notice also that this report shows the start time,

duration, and other values for the maintenance window.

Note: When is this maintenance window available?

It is no longer available, as it occurred in the past and is not a recurring window.

h. Close the ConfigMgr Report window.

The Configuration Manager Console window appears displaying the Maintenance

Windows Available to a Particular Client Report Information report in the

results pane.

With the maintenance window in the past, the client (SMSServer) will not be able

to receive any deployments unless they are configured to ignore maintenance

windows, or another maintenance window is assigned to a collection this computer

is a member of. You can explore maintenance windows further in the lab

“Implementing Maintenance Windows in System Center Configuration Manager

(SCCM) 2007”.


Page 10 of 17

Exercise 3 Exploring Software Updates and WSUS Integration

Scenario In this exercise, you will use the Configuration Manager Console to validate the deployment of software updates in

Configuration Manager, which integrates with WSUS 3.0 to provide greater coverage of updates for deployment.

Note: Complete this exercise from the Configuration Manager Console the primary site server.



task on:

Server

1. To view the current

software update

compliance status


then click Software Updates.

The home page for software updates appears in the results pane. Notice that the

home page displays current compliance for Microsoft security updates for the

current month.

Note: Are there any results available for the default view?

No, there are no Microsoft security updates for the current month.

To identify what updates are synchronized in the Configuration Manager database,

you can view the update repository.

b. In the tree pane, expand Software Updates, and then click Update Repository.

The list of update categories synchronized with Configuration Manager are

displayed in the results pane. Notice that there are three update categories that

have been synchronized with Configuration Manager from WSUS. This lab uses

synthetic updates instead of using real Microsoft updates to make synchronization

quicker.

Note: What three update categories have been synchronized from WSUS?

Critical Updates, Security Updates, and Service Packs.

Configuration Manager can manage any update categories that are configured for

management in WSUS 3.0. In this case, these are the only three categories that

have updates published in WSUS 3.0 for this lab environment.

c. In the tree pane, expand Software Updates, expand Update Repository, expand

Critical Updates, and then click All Updates.

The critical updates synchronized with Configuration Manager are displayed in the

results pane.

Note: How many synthetic critical updates have been added to the site database?

40

d. In the tree pane, expand Software Updates, expand Update Repository, expand

Service Packs, and then click All Updates.

The service packs synchronized with Configuration Manager are displayed in the

results pane.

Note: How many synthetic service packs have been added to the site database?

Six

e. In the tree pane, expand Software Updates, expand Update Repository, and then

click Security Updates.

The security update vendors synchronized with Configuration Manager are

displayed in the results pane. Remember that there were no Microsoft security


Page 11 of 17


updates available in the home page.

Note: What Category is listed for the security updates?

SCCM Lab

f. In the tree pane, expand Software Updates, expand Update Repository, expand

Security Updates, and then click SCCM Lab.

The synthetic security updates synchronized with Configuration Manager for the

vendor SCCM Lab are displayed in the results pane. Notice that there is only one

security update, that being the Synthetic Software. This was actually published as

a custom update using the System Center Updates Publisher, which is essentially

the same as the Custom Updates Publishing Tool from SMS 2003 R2.

g. In the tree pane, expand Site Database, expand Computer Management, and

then click Software Updates.

The home page for software updates appears in the results pane. Notice that the

home page displays current compliance for Microsoft security updates for the

current month.

h. In the results pane, configure the Vendor to SCCM Lab, configure the Update

classification to Security Updates, configure the Month and year to September,

2007, and then click Go.

The Software Update Compliance Status Summary information appears in the

details pane. Notice that the update status now reflects that the update is installed

on one client and not required for the second client.

i. In the results pane, configure the Vendor to Lab, configure the Update

classification to Critical Updates, configure the Month and year to August,

2007, and then click Go.


details pane for English Update 1. Notice that the update status for English Update

1 reflects that the update is compliant for all clients.

j. Under Bulletin ID, click CM07-701.


details pane for Universal Update 1MB. Notice that the update status for Universal

Update 1MB reflects that the update is required for all clients.

k. In the results pane, scroll to the right to view the Total, Installed, Required, Not

Required and Unknown values.

Note: How many clients require this update?

Two

Note: How many clients have installed this update?

Zero

Note: How many clients have not reported status for this update?

Zero

You have now verified that both Microsoft and custom updates can be deployed

through Configuration Manager. You can explore managing Microsoft updates

further (including configuration of WSUS, synchronization of updates with

WSUS, and deployment of updates from Configuration Manager) in the lab

“Managing Microsoft Updates in System Center Configuration Manager (SCCM)

2007”. You can also use the “Managing Custom Application Updates in System


Page 12 of 17


Center Configuration Manager (SCCM) 2007” lab to explore creating custom

catalogs for updates, importing 3rd

party catalogs and deploying custom or 3rd

party updates.


Page 13 of 17

Exercise 4 Exploring Operating System Deployment

Scenario In this exercise, you will explore the operating system deployment feature of Configuration Manager.



task on:

Server

1. To view operating

system deployment

configuration

Note: Complete this procedure from the Configuration Manager Console the primary

site server.


then click Operating System Deployment.

The home page for operating system deployment appears in the results pane.

Notice that the home page displays current status of operating system deployments

for the past 7 days.

Note: Have there been any OS deployments?

There is one configured and targeted to one client but it has not started yet.

To identify what system was targeted for the deployment, you can view a

Configuration Manager report.

b. In the results pane, under Advertisement, click Install Windows Vista.

The Status summary of a specific task sequence advertisement report appears

in the results pane displaying the status of the Install Windows Vista task sequence

advertisement. Notice that the report indicates that one client was targeted, but has

not returned any status.

c. Click the arrow next to No Status.

The All system resources for a specific task sequence advertisement in a

specific state report appears in the results pane displaying the list of clients that

have not returned any status messages for the Install Windows Vista task sequence

advertisement.

Note: What client is targeted for this deployment?

TestComputer1

d. In the tree pane, expand Site Database, expand Computer Management, expand

Collections, and then click Bare Metal Systems.

The members of the Bare Metal Systems collection appear in the details pane. This

is not a default collection, but one created for this lab. Notice that there is one

computer listed as a member (TestComputer1).

e. In the results pane, click TestComputer1, and then in the Actions pane under

TestComputer1, click Properties.

The TestComptuer1 Properties dialog box appears displaying discovery data for

TestComputer1. Notice that Agent Name[0] shows a value of Manual Machine

Entry. This indicates that this computer was not discovered, but rather added by

importing data manually using a new feature of Configuration Manager, the

manual machine import of bare metal systems for OS deployments.

f. Click Cancel.

The Configuration Manager Console appears displaying the members of the Bare

Metal Systems collection.


Page 14 of 17


g. In the tree pane, expand Site Database, expand Computer Management, expand

Operating System Deployment, and then click Computer Association.

The configured computer associations appear in the results pane. Notice that there is an association created.

Note: What two computers have an association?

SMSClient is the source computer and TestComputer1 is the destination computer.

Computer associations are used to move state information from a source computer

(in this case SMSClient) to a target computer (in this case TestComputer1) through

an Configuration Manager site system called a state migration point during a

machine replacement scenario.

h. In the tree pane, expand Site Database, expand Computer Management, expand

Operating System Deployment, and then click Boot Images.

The boot images in the site appear in the results pane. Notice that there are two

default boot images available – one for x86 and one for x64.

i. In the tree pane, expand Site Database, expand Computer Management, expand

Operating System Deployment, and then click Operating System Images.

The operating system images in the site appear in the results pane. Notice that

there is one operating system image available, that for Windows Vista.

j. In the results pane, click Windows Vista.

The basic properties for the Windows Vista operating system image appear in the

results pane.

k. Click the Images tab.

The images contained in the Windows Vista operating system image appear in the

results pane. Notice that there is only one image in the .operating system image

file. Notice also that the image is almost 7 GB in size.

l. Click the Disk Configuration tab.

The disk information for the Windows Vista operating system image appears in

the results pane. Notice that there was only one partition in the reference computer

that was captured.

m. In the tree pane, expand Site Database, expand Computer Management, expand

Operating System Deployment, and then click Task Sequences.

The list of task sequences for the site appears in the results pane. Notice that there

is one task sequence available.

n. In the results pane, click Install Windows Vista.

The general properties for the Install Windows Vista task sequence appear in the

results pane.

o. Click the References tab.

The packages used by the Install Windows Vista task sequence appear in the

results pane. Notice that the task sequence uses five different packages – one a

boot image (x86), one to install an SMS program (SMS 2003 Toolkit 2), one to

install the Configuration Manager client on the target system, one to migrate the

user state information (USMT), and the actual operating system image.

p. In the results pane, click Install Windows Vista, and then in the Actions pane

under Install Windows Vista, click Edit.

The Install Windows Vista Task Sequence Editor dialog box appears displaying

the steps in the configured task sequence that will be run to install Windows Vista


Page 15 of 17


on targeted computers. In this editor, you can select tasks in the left pane, and then

configure the task in the right pane.

You will notice the following tasks and settings in this task sequence (you will not

look at all of the tasks in this lab):

Capture Windows Setting to migrate the computer name, registration information,

and time zone configuration.

Capture Network Settings to migrate the network adapter configuration.

Capture User Files and Settings to migrate user profile information.

Apply Network Settings to have the new computer assigned to the SMSDomain

and to use the domain’s administrator account to join the computer to the domain.

Apply Device Drivers from all categories.

Setup Windows and SMS to install the Configuration Manager client on the new

computer.

Install Software to install the SMS 2003 Toolkit 2 package after the operating

system has been installed.

Restore User Files and Settings to restore all user profile information.

q. Click Cancel.

The list of task sequences for the site appears in the results pane.

r. In the tree pane, expand Site Database, expand Computer Management, expand

Operating System Deployment, and then click Drivers.

The list of drivers for the site appears in the results pane. Notice that there are

three drivers available. These drivers may be applied as part of the Apply Device

Drivers task sequence action.

You have now verified the configuration of operating system images using the

operating systems deployment features of Configuration Manager. You can further

explore deploying operating systems in the lab “Deploying Microsoft Windows

Vista using System Center Configuration Manager (SCCM) 2007”.


Page 16 of 17

Exercise 5 Exploring Desired Configuration Management

Scenario In this exercise, you will explore the desired configuration management feature of Configuration Manager.



task on:

Server

1. To view desired

configuration

management

Note: Complete this procedure from the Configuration Manager Console the primary

site server.


then click Desired Configuration Management.

The home page for desired configuration management appears in the results pane

displaying all desired configuration management. baselines that have a severity

level of Error.

Note: Are there any configuration baselines with a severity of error?

No

b. In the results pane, in the Minimum severity box, click None.

The home page for desired configuration management appears in the results pane

displaying all desired configuration management. baselines that have a severity

level of None, which would include all baselines.

Note: What baselines are created?

One for SCCM Client and one for Client Operating Systems

Note: What is the status of the SCCM Client baseline?

One system is compliant, one system is noncompliant, and one is unknown.

Note: What is the status of the Client Operating Systems baseline?

Two systems are compliant and one is unknown.

c. In the results pane, under Name, click SCCM Client.

The Summary compliance by configuration baseline report appears in the

results pane. Notice that it reports that you have one compliant and one non-

compliant system, as well as one unknown system, listed for this baseline.

d. Click the arrow to the left of SCCM Client.

The Compliance details for a configuration baseline by configuration item

report appears in the results pane. Notice that this report displays each

configuration item and the state of each configuration item at each client.

e. Click the arrow to the left of the SCCM Client configuration item.

The Summary compliance for a configuration item by computer report appears

in the results pane. Notice that it displays an entry for each SCCM client reporting

status for this baseline. Notice that it displays the baseline name, version,

configuration item, configuration type, desired state, compliance state, and

applicability and detected states for each client.

Note: What system is listed as compliant for the SCCM Client baseline?

SMSClient

Note: What system is listed as not compliant for the SCCM Client baseline?


Page 17 of 17


SMSServer

Note: What system is not listed with any results for the SCCM Client baseline?

TestComputer1, which is not a client computer yet however was in the targeted

collection for this baseline.

f. In the tree pane, expand Site Database, expand Computer Management, expand

Desired Configuration Management, and then click Configuration Baselines.

The list of configuration baselines appears in the results pane. Notice that there are

two baselines available.

g. In the results pane, click Client Operating Systems.

Additional information for the Client Operating Systems configuration baseline

appears in the lower portion of the results pane. On the General tab, you can view

the date the baseline was created and last modified. On the Rules tab, you can see

the configuration items that were created and added to the baseline. On the

Relationships tab, you can see any other baselines that this baseline is related to.

On the Assignments tab, you can see what collection this configuration baseline is

assigned to.

Note: Is the Client Operating Systems configuration baselines related to any other

baselines?

Yes, the SCCM Client configuration baseline.

h. In the tree pane, expand Site Database, expand Computer Management, expand

Desired Configuration Management, and then click Configuration Items.

The list of configuration items appears in the results pane. Notice that there are

three configuration items available. Notice that there are two configuration items

for operating systems, and one for Configuration Manager client configuration.

You have now verified the configuration of the desired configuration management

feature of Configuration Manager. You can further explore managing desired

configurations in the lab “Implementing Desired Configuration Management in

System Center Configuration Manager (SCCM) 2007”.

In this lab, you explored some of the new features of Configuration Manager, from

configuration of client deployment, to verifying some of the new core features of

Configuration Manager. There are many other features available in Configuration

Manager.

Documents

IntroductiontoSystemCenterConfigurationManager