Energize It - Intro to Configuration Manager 2007 Hands-On Lab Manual

Hands On Lab

Energize IT

June 16th, 2007

Hands on Lab Sponsored by the You’re In Control Forefront and

System Center Joint Launch

2

Lab: Introduction to System Center Configuration Manager (SCCM) 2007

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

Use the SCCM 2007 Administrator Console to verify the site configuration.

Use the SCCM 2007 Administrator Console to identify new features of SCCM 2007 including:

Software distribution and maintenance windows

Software updates and WSUS integration

Operating system deployment of Windows Vista

Desired configuration management

And other miscellaneous SCCM features

Prerequisites Before working on this lab, one virtual computer should be booted as a Microsoft Windows Server 2003 SP1

computer installed as an SMS primary site server (SMSServer in the Intro Server VPC). The second virtual

computer is booted as a Windows XP Professional SP2 client installed as an SCCM client in the SMS site

(SMSClient in the Intro Client VPC).

The SCCM site code for the installed site is SV4.

Estimated time to complete this lab: 75 minutes

3

Exercise 0 Preparing the Virtual Computer Clients for the Lab In this exercise, you will update the collection membership of the All Systems collection. When you do, you

will see the SMSClient computer appear twice in the membership list. This is due to Virtual PC 2007

virtualizing the SMBios serial number of the host computer, which SCCM detects as being different than the

original SMBios serial number. Because of this, SCCM generates a new GUID for the client, which causes a

new record to be generated.

Note

Complete this procedure from the primary site server computer only.

To update the collection membership

Log on as administrator with a password of password.

On the Start menu, click SMS Administrator Console.

The SMS Administrator Console window appears.

1. In the tree pane, expand SMSSERVER, expand Computer Management, and then expand

Collections.

The list of collections appears in the results pane.

2. 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.

3. In the Actions pane, click Update Collection Membership.

An All Systems message box appears prompting to update subcollection membership.

4. Click OK, and then in the Actions pane, click Refresh.

The collection membership is updated, and the current membership of the All Systems collection is

displayed. Notice that the SMSClient computer is now displayed twice. Notice also that one of the instances

is listed as being Obsolete and inactive. This is the old reference of the client.

In the details pane, click the obsolete record for the SMSClient computer, and then in the Actions pane,

click Delete.

A Confirm Delete message box appears prompting to delete the record.

Click Yes.

The collection membership is updated, and the current membership of the All Systems collection is

displayed. Notice that the SMSClient computer is now displayed only once and it is an Active record (not

Obsolete).

Delete any other Obsolete records from the All Systems collection.

Update the membership for the All Windows XP Systems collection.

You have now prepared your images for the lab and may proceed to Exercise 1.

4

Exercise 1 Exploring the SCCM 2007 Administrator Console In this exercise, you will use the SCCM 2007 Administrator Console to view the SCCM 2007 site

configuration. You will be using the SCCM Administrator Console through the rest of this lab to identify

new features of SCCM 2007.

Note

Complete this procedure from the primary site server computer only.

To view the SCCM home page

1. If not already running, on the Start menu, click SMS Administrator Console.

The SCCM Administrator Console window appears. Notice that the SCCM Administrator 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.

2. In the tree pane, click Systems Management Server.

The main SCCM home page appears in the results pane. Notice that the home page includes information

regarding the help available in administering SCCM.

3. Was SCCM able to connect to the default start page?

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

4. In the tree pane, expand Systems Management Server, and then click SMSServer.

The SMSServer home page appears in the results pane. Notice that the home page includes information

helpful to complete the site configuration to deploy SCCM clients.

5. What are the four steps identified to deploy SCCM clients?

Configure the management point, configure the client approval method, install the ConfigMgr client, and

configure client agents.

In the next four procedures, you will explore these four tasks to ensure our site can deploy clients. This will

help you to become familiar with the SCCM Administrator Console for the remainder of this lab, as well as

the other SCCM labs. You will begin with validating the configuration of the management point, which is

listed as step #1.

In following procedure, you will verify that the management point is configured, which is a requirement to

support all SCCM clients.

Note

Complete this procedure from the SCCM site server in the SCCM Administrator Console.

To verify the management point configuration

In the tree pane, expand SMSSERVER, expand Site Management, expand SV4, expand Site Settings, and

then click Site System Roles.

The list of site systems appears in the results pane.

1. How many SCCM site systems are listed for the site?

Two, SMSClient and SMSServer.

2. In the tree pane, expand Site System Roles, and then click SMSClient.

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

3. What site system roles are configured for SMSClient?

ConfigMgr distribution point and ConfigMgr site system.

5

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

distribution point – one of the new SCCM 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.

4. In the tree pane, under Site Systems, click SMSSERVER.

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

5. Is SMSServer configured as a management point?

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

6. 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 SCCM Administrator 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.

7. 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.

8. Does the management point support devices?

No

9. Does the management point support Internet-based clients?

No

10. Click Cancel.

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

11. 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.

12. 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.

13. Is SMSServer configured as the default management point for this site?

Yes

14. Click Cancel.

The list of configurable components appears in the results pane.

You have now used the SCCM Administrator Console to verify that the site server computer, SMSServer, is

configured as the default management point for the site SV4. Step #2 is to configure the client approval

method. You will verify that in the next procedure.

In following procedure, you will verify that clients will be approved in the site. Clients must be approved in

order to retrieve policies that contain secrets, which are policies that contain account credentials, such as the

Network Access Account.

Note

6


To verify the client approval method

In the tree pane, under Systems Management Server, click SMSSERVER, and then in the Actions pane,

click Properties.

The SV4 – SCCM 2007 Primary Site Properties dialog box appears displaying general properties for the

site.

15. Click the Site Mode tab.

The SV4 – SCCM 2007 Primary Site Properties dialog box appears displaying configuration for the

security mode of the site.

16. What security mode is the site server computer configured to run in?

Mixed

Mixed mode does not require a PKI for certificate management nor does it use full mutual authentication

between clients and site systems, as native mode does. Mixed mode is essentially the advanced security

mode of SMS 2003.

17. How are clients that are assigned to this site approved?

The site is automatically approving all clients in trusted domains.

Click Cancel.

The SMS Administrator Console appears.

In the tree pane, expand SMSSERVER, expand Computer Management, expand Collections, and then

click All Systems.

The members of the All Systems collection appear in the results pane. Notice that there are two computers in

the site. Also notice that the information that is displayed includes a column for Approval, which identifies

whether the resources are approved or not.

18. Are the two computers in the site approved?

Yes

You have now used the SCCM Administrator Console to verify that the site is running mixed mode, and will

automatically approve clients from trusted domains. Step #3 is to install SCCM clients. You will verify that

this has been completed in the next procedure.

In following procedure, you will verify that the site is able to install and assign clients.

Note


To verify client installation

In the tree pane, expand SMSSERVER, expand Computer Management, expand Collections, and then

click All Systems.

The members of the All Systems collection appear in the results pane. Notice that there are two computers in

the site. Also notice that the information that is displayed includes a column for Client, which identifies

whether or not the resources are installed as clients.

19. Are the two computers in the site installed as clients?

Yes


then click Client Installation Methods.

The configurable client installation methods appear in the results pane.

20. What client installation methods are available for configuration?

Software Update Point Client Installation and Client Push Installation.

7

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.

21. 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 SCCM client through a SCCM

software update point, which uses WSUS 3.0 to install the client.

Click Cancel.

The configurable client installation methods appear in the results pane.

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.

22. Click the Accounts tab.

The Client Push Installation Properties dialog box appears displaying the account properties for the

installation method.

23. 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.

Click Cancel.

Even if no account was listed on the Accounts tab of the Client Push Installation Properties dialog box,

SCCM 2007 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.

You have now used the SCCM Administrator 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.

In following procedure, you will verify that the appropriate client agents are configured for the site.

Note


To verify client agent configuration


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

SCCM Setup program.

24. 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.

25. Can software applications be distributed to the clients?

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

26. 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.

8

You have now used the SCCM Administrator Console to verify that the site can successfully approve, install

and collect data from clients. You have also explored the SCCM Administrator Console. You will continue

to use it in the next exercise to validate some of the new features included in SCCM 2007. For the remainder

of this lab, a number of SCCM features have already been implemented, and to get you familiar with those

features, you will determine their implementation and status.

9

Exercise 2 Exploring Software Distribution and Maintenance Windows In this exercise, you will use the SCCM 2007 Administrator Console to identify SCCM software distribution

to determine why a client was unsuccessful in running an advertisement.

Note

Complete this procedure from the primary site server computer only in the SMS Administrator console.

To verify software distribution status

In the tree pane, expand SMSSERVER, expand Computer Management, and 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.

What is the status of the SMS Toolkit deployment?

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

Under Advertisement Name, click SMS Toolkit.

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

Toolkit advertisement. Notice that the report indicates that one client was successful running the

advertisement while one failed.

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 Toolkit advertisement.

What client failed to run the SMS Toolkit deployment successfully?

SMSServer

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.

In the tree pane, expand SMSSERVER, 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.

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 Systems collection. An easy

way to identify the maintenance windows available for a specific client is with a report.

1. In the tree pane, expand SMSSERVER, expand Computer Management, expand Reporting, and

then click Reports.

The list of reports appears in the results pane.

2. In the results pane, click Service Windows Available to a Particular Client, and then in the

Actions pane, under Service Windows Available to a Particular Client, click Run.

The Service 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.

10

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

An Internet Explorer window starts and display the Service 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.

When is this maintenance windows available?

It is no longer available, as it occurred in the past.

4. Close the SMS Report window.

The SMS Administrator Console window appears displaying the Service 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”.

11

Exercise 3 Exploring Software Updates and WSUS Integration In this exercise, you will use the SCCM Administrator Console to validate the deployment of software

updates in SCCM 2007, which integrates with WSUS 3.0 to provide greater coverage of updates for

deployment.

Note

Complete this exercise from the SMS Administrator console the primary site server.

To view the current software update compliance status

1. In the tree pane, expand SMSSERVER, 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.

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 SCCM database, you can view the update repository.

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

The list of update categories synchronized with SCCM are displayed in the results pane. Notice that there are

three update categories that have been synchronized with SCCM from WSUS. This lab uses synthetic

updates instead of using real Microsoft updates to make synchronization quicker.

What three update categories have been synchronized from WSUS?

Critical Updates, Security Updates, and Service Packs.

SCCM 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.

3. In the tree pane, expand Software Updates, expand Update Repository, expand Critical Updates,

and then click All Updates.

The critical updates synchronized with SCCM are displayed in the results pane.

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

42

4. In the tree pane, expand Software Updates, expand Update Repository, expand Service Packs,

and then click All Updates.

The service packs synchronized with SCCM are displayed in the results pane.

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

Six

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

Updates.

The security update vendors synchronized with SCCM are displayed in the results pane. Remember that

there were no Microsoft security updates available in the home page.

What vendor is listed for the security updates?

SCCM Lab

6. In the tree pane, expand Software Updates, expand Update Repository, expand Security

Updates, and then click SCCM Lab.

The security updates synchronized with SCCM for the vendor SCCM Lab are displayed in the results pane.

Notice that there is only one security update, that being the Synthetic Software Update. 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.

12

7. In the tree pane, expand SMSSERVER, 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.

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

Security Updates, configure the Month and year to February, 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 required for one client and not required for the second client.

9. In the results pane, configure the Vendor to Lab, configure the Update classification to Critical

Updates, configure the Month and year to August, 2006, and then click Go.

The Software Update Compliance Status Summary information appears in the details pane for English

Update 1. Notice that the update status for English Update 1 reflects that the update is compliant for all

clients.

10. Under Bulletin ID, click CM07-701.

The Software Update Compliance Status Summary information appears in the details pane for Universal

Update 1MB. Notice that the update status for Universal Update 1MB reflects that the update is required for

all clients.

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

Unknown values.

12. How many clients require this update?

Two

13. How many clients have installed this update?

Zero

14. 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 SCCM. You can

explore managing Microsoft updates further (including configuration of WSUS, synchronization of updates

with WSUS, and deployment of updates from SCCM) in the lab “Managing Microsoft Updates in System

Center Configuration Manager (SCCM) 2007”. You can also use the “Managing Custom Application

Updates in System Center Configuration Manager (SCCM) 2007” lab to explore creating custom catalogs for

updates, importing 3rd

party catalogs and deploying custom or 3rd

party updates.

13

Exercise 4 Exploring Operating System Deployment In this exercise, you will explore the operating system deployment feature of SCCM 2007.

Note

Complete this procedure from the SMS Administrator console the primary site server.

To view operating system deployment configuration

1. In the tree pane, expand SMSSERVER, expand Computer Management, and 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.

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 an SCCM report.

2. 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.

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.

What client is targeted for this deployment?

TestComputer1

3. In the tree pane, expand SMSSERVER, 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).

4. 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 SCCM, the manual machine

import of bare metal systems for OS deployments.

Click Cancel.

The SCCM Administrator Console appears displaying the members of the Bare Metal Systems collection.

5. In the tree pane, expand SMSSERVER, expand Computer Management, expand Operating

System Deployment, and then click Computer Associations.

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

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 SCCM site system called a state migration

point during a machine replacement scenario.


System Deployment, and then click Boot Images.

14

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

available – one for x86, one for x64, and one for ia64.


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.

8. In the results pane, click Windows Vista.

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

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.

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.


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.

In the results pane, click Install Windows Vista.

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

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

Toolkit 2), one to install the SCCM client on the target system, one to migrate the user state information

(USMT), and the actual operating system image.

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 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 SCCM client on the new computer.

Install Software to install the SMS 2003 Toolkit package after the operating system has been

installed.

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

Click Cancel.

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


System Deployment, and then click Drivers.

The list of drivers for the site appears in the results pane. Notice that there are four 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 SCCM. You can further explore deploying operating systems in the lab “Deploying

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

15

Exercise 5 Exploring Desired Configuration Management In this exercise, you will explore the desired configuration management feature of SCCM 2007.

Note

Complete this procedure from the SMS Administrator console the primary site server.

To view desired configuration management

1. In the tree pane, expand SMSSERVER, expand Computer Management, and 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.

Are there any configuration baselines with a severity of error?

No

2. 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.

What baselines are created?

One for SCCM Client and one for Client Operating Systems

What is the status of the SCCM Client baseline?

One system is compliant and one system is noncompliant.

What is the status of the Client Operating Systems baseline?

Both systems are compliant.

3. In the tree pane, expand SMSSERVER, 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.

4. 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.

Is the Client Operating Systems configuration baselines related to any other baselines?

Yes, the SCCM Client configuration baseline.

5. In the tree pane, expand SMSSERVER, 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 SCCM client

configuration.

You have now verified the configuration of the desired configuration management feature of SCCM. 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 SCCM 2007, from configuration of client deployment,

to verifying some of the new core features of SCCM. There are many other features available in SCCM

2007.

Documents

Energize It - Intro to Configuration Manager 2007 Hands-On Lab Manual