Supporting SCCM 2007 Lab Manual

Supporting System Center Configuration
Manager 2007
Lab Manual
FINAL
Published: August 13, 2007

Microsoft Confidential - For Internal Use Only
DISCLAIMER
Microsoft Confidential - For Internal Use Only
© 2007 Microsoft Corporation. All rights reserved.
Microsoft®, Internet Explorer, and Windows® are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.
THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND TRAINING PURPOSES ONLY
AND ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
No part of the text or software included in this training package may be reproduced or transmitted in
any form or by any means, electronic or mechanical, including photocopying, recording, or any
information storage and retrieval system, without permission from Microsoft®. 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 presented after
the date of publication. The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
To obtain authorization for uses other than those specified above, please visit the Microsoft
Copyright Permissions Web page at http://www.microsoft.com/permission/copyrgt/img-req.htm.
This content is proprietary and confidential, and is intended only for users described in the content
provided in this document. This content and information is provided to you under a Non-Disclosure
Agreement and cannot be distributed. Copying, disclosing all or any portion of the content and/or
information included in this document is strictly prohibited.
Table of Contents
Lab 1: Upgrade an Existing SMS 2003 site .......................................................................... 1
Before You Begin.................................................................................................................................1
What You Will Learn ...........................................................................................................................1
Setting Up Your Lab Environment.......................................................................................................1
Exercise 1: Installing Microsoft SCCM 2007 ........................................................................................3
Exercise 2: Preparing Active Directory for SCCM 2007 Integration ....................................................6
Exercise 3: Installing an SCCM 2007 Client .........................................................................................9
Exercise 4: Installing an SCCM 2007 Reporting Point .......................................................................14
Lab 2: Deploy a Branch DP ...............................................................................................17
Exercise 1: Creating and Configuring a Branch Distribution Point....................................................17
Exercise 2: On-Demand Package Distribution ..................................................................................22
LAB 3: Implementing Desired Configuration Management ................................................25
Objectives .........................................................................................................................................25
Exercise 1: Enable the DCM Client agent ..........................................................................................25
Exercise 2: Create Configuration Items.............................................................................................25
Exercise 3: Establishing DCM Baselines ............................................................................................27
Exercise 4: Reviewing CI information on the server and client ........................................................29
Exercise 5: Check that the Windows Firewall is Enabled Using Desired Configuration Management
..........................................................................................................................................................31
Exercise 6: Check for the Presence of the Client Installation Properties Registry Key Using Desired
Configuration Management..............................................................................................................34
Lab 4: Deploying Software Updates ..................................................................................37
Exercise 1: Configuring SCCM 2007 Integration with WSUS.............................................................37
Exercise 2: Generating Update Status on the SCCM Client ................. Error! Bookmark not defined.
Exercise 3: Generating Software Update Compliance Reports ........... Error! Bookmark not defined.
Exercise 4: Distributing Software Updates Using SCCM Software Update Management .......... Error!
Bookmark not defined.
Exercise 5: Validating Current Software Update Compliance.............. Error! Bookmark not defined.
Lab 5: Working with Operating System Deployment .........................................................46
Exercise 1: Capturing an OSD reference image ................................................................................46
Exercise 2: Configuring and deploying a captured image .................................................................48
Exercise 3: Import sample drivers.....................................................................................................52
Exercise 4: Creating a deployment task sequence ...........................................................................53
Exercise 5: Install and configure the PXE service point ....................................................................57
Exercise 6: Creating and distributing a non-OSD task sequence ......................................................58
Exercise 7: Importing Windows Device Drivers into the Driver Catalog .......................................... 60
Lab 6: Implementing Service Windows ............................................................................. 63
Exercise 1: Configuring Maintenance Windows on Collections ....................................................... 63
Exercise 2: Implementing the Maintenance Windows on the SCCM Clients ................................... 66
Exercise 3: Distributing Software to the SCCM Clients ..................................................................... 68
Exercise 4: Create two Maintenance Windows to control software distribution ............................ 76
Exercise 5: Create an advertisement to verify the first Maintenance Window permits software
distribution ....................................................................................................................................... 77
Exercise 6: Create an advertisement that will run outside of a Maintenance Window ................... 80
Exercise 7: Create an advertisement that runs past the Maintenance window .............................. 81
Instructor Notes .............................................................................................................. 83
Answers to Lab Exercises .................................................................................................................. 83
Lab Manual Lab 1: Upgrade an Existing SMS 2003 site
Lab 1: Upgrade an Existing SMS 2003 site

During this lab, you will extend the Active Directory for SCCM, upgrade an existing
SMS 2003 server, upgrade the client, configure Configuration Manager, and deploy a
Reporting Point,
Estimated time to complete this lab: 2 hours
Before You Begin

Before starting this lab, you should:
■ Complete Modules 1 and 2
■ Configure your computer(s) as described in Setting Up Your Lab

Environment.
What You Will Learn

After completing this lab, you will be able to:
■ Extend the Active Directory schema for SCCM specific data.
■ Create an Active Directory site for integration with Microsoft® System Center
Configuration Manager 2007.
■ Upgrade an Existing Configuration Manager 2003 server
■ View status message activity related to site server installation.
■ Configure basic SCCM options
■ Discover computer resources from Active Directory.
■ Install an SCCM 2007 Client on the Windows XP Professional client.
■ Install a Reporting Point
Setting Up Your Lab Environment

To complete the labs, you will need the following:
■ A virtual machine running Windows 2003 SP2 and a virtual machine running
Windows XP SP2.
□ Server is configured as a Domain Controller and has the following software

installed:
FINAL 1
Microsoft Confidential - For Internal Use Only © 2007 Microsoft Corporation. All rights reserved.
Supporting System Center Configuration Manager 2007
● IIS with BITS and WebDAV enabled
● SQL 2005 SP2
● MMC 3.0
● KB914389
● .NET Framework 2.0
● Working Configuration Manager 2003 Primary Server installed and

configured
● Configuration Manager Toolkit 2
■ Windows XP SP2 client has the Configuration Manager 2003 Advanced Client
installed.
□ .NET Framework 2.0
□ Configuration Manager Toolkit 2
Note: These prerequisites are already installed in the VM
You must log on as an administrative user in order to perform some of the tasks in
this lab.
■ Administrative username and password for Server and client
□ Username = Administrator
□ Password = !LS1setup
□ ADRestore Password: !LS1setup
■ Site, Server and Client information
□ Domain = SCSBeta.local
□ SCCM Sitecode=S00
□ Server name: SCCMSRV1
● FQDN = SCCMSRV1.SMSBeta.local
□ Client name: SCCMXP01
● FQDN = SCCMXP01.SMSBeta.local
■ Normal username and password
2 FINAL
© 2007 Microsoft Corporation. All rights reserved. Microsoft Confidential - For Internal Use Only
□ Username = Student01
□ Password = Pass0word1
□ Domain = SCSBeta.local
Additional Software located on the 2nd drive in a LABS folder:
■ WSUS 3.0
■ SCCM 2007 RC1
Exercise 1: Installing Microsoft SCCM 2007

Scenario
In this exercise, you will install SCCM 2007 using the upgrade option to upgrade the
existing SMS 2003 SP3 Primary site. SQL Server 2000 has already been upgraded to
SQL 2005 SP2.
Before beginning this exercise please increase the memory for the server VM to 1
and a half gigs.
Caution!
The upgrade process can take as long as 2 hours. This lab must be started at a break during
the lecture portion so it can be completed in a time that allows students to complete the rest of the
labs.
Tasks
Install SCCM 2007
1. Navigate to E:\Lab Files\Configuration Manager 2007 RC double-click on
splash.hta. The System Center Configuration Manager 2007 Start screen
appears.
2. Under Prepare select Run the Prerequisite checker.
3. Leave the option checked for Upgrade and click on OK. The prerequisite
checker will run and display results.
4. After checking to make sure there are no deployment blockers click on OK.
5. Double-click splash.hta and under Install click on Configuration Manager

2007.
6. At the Welcome screen click Next.
FINAL 3
7. On the Available Setup Options screen leave the default Upgrade an existing
Configuration Manager or SMS 2003 Installation selected and click Next.
8. Accept the license terms and click Next.
9. On the Customer Experience screen leave the defaults and click Next.
10. On the Product Key screen click Next.
11. On the Settings Summary screen click Next. The prerequisite check will run
again.
12. Once the prerequisite check is complete, if there are no deployment blockers
click on Begin install.
13. Setup will begin and progress will be displayed on the Setup Action Status
Monitoring screen.
14. When setup completes click Finish.
View Status Messages

In the following procedure, you will use Configuration Manager status messages
generated by the site server installation to verify that the site server installation was
successful. You can use this same procedure to view status messages generated by
any Configuration Manager processes.
1. On the Start menu, click on All Programs, click on Microsoft Systems Center,
click on Configuration Manager 2007, then click on ConfigMgr Console..
2. The Microsoft Management Console (MMC) starts, and then the

Configuration Manager Console windows appears.
3. In the tree pane, click Site Database - S00 - SCCMSRV1. The Configuration
Manager home page appears in the results pane. Notice that information is
provided on completing the site configuration in order to support SCCM client
deployment.
4. In the tree pane, expand Site Database, expand System Status, expand Site
Status, expand S00, and then click Site System Status. The list of
Configuration Manager site system roles appears in the results pane with the
current status of each site system.
5. Verify that each site system has a status of OK.
6. In the tree pane, click Component Status. The list of Configuration Manager
components and their status appears in the results pane.
4 FINAL
7. In the Results pane, click Configuration

Manager_SITE_COMPONENT_MANAGER, and then in the Actions pane, click
Show Messages. A new menu appears.
8. Click All. The Configuration Manager Status Message Viewer for Configuration
Manager window appears. Notice the message with the ID of 1027. It mentions
that the site server was configured to receive Configuration Manager server
components.
9. Click the message, and then on the View menu, click Detail.
10. The Status Message Details dialog box appears. Notice the header information
for the message, as well as the text under Description.
11. Click OK.
12. The Configuration Manager Status Message Viewer window appears.
13. On the File menu, click Exit.
14. The list of Configuration Manager components appear in the results pane.
15. Display the status messages for Configuration

Manager_SITE_CONTROL_MANAGER. The Configuration Manager Status
Message Viewer window appears. Notice the message with a message ID of
2819. This message indicates that Configuration Manager retain the 100 most
recent copies of the site control file. At this point, Configuration Manager has
just been installed, however there will have already been some site control file
modifications processed.
16. Look for the message ID of 2866. This message indicates the actual site control
file copy has been sent to the Configuration Manager Hierarchy Manager for
addition to the Configuration Manager site database. NOTE: You may only see
these status messages from the first install, but not from the upgrade.
17. There should also be messages with IDs of 2808, 2814, 2813, 2811, and 2865 in
each set of Site Control File modification requests. You will view these
messages in later labs.

Manager_HIERARCHY_MANAGER.
19. The Configuration Manager Status Message Viewer window appears. Notice
the messages with message IDs of 3306. These messages indicate that
Hierarchy Manager has successfully processed a site control file modification
and updated the site database.
FINAL 5

Manager_WINNT_SERVER_DISCOVERY_AGENT. The Configuration Manager
Status Message Viewer window appears. Notice the message with a message
ID of 4202. This message indicates one server was discovered and discovery
data was written for it. This occurred as a result of installing Configuration
Manager site components on the site server computer.
Exercise 2: Preparing Active Directory for SCCM 2007

Integration
Scenario
In this exercise, you will prepare Active Directory for use with SCCM 2007. You will
use a utility to extend the Active Directory schema for use by SCCM. You will also
grant rights for the SCCM site server to publish data to Active Directory. Finally, you
will create an Active Directory site that will be added to the SCCM boundaries for
client management. Complete this exercise on the Windows 2003 server where
Active Directory is installed.
Steps to take before beginning this lab:

1. Shut down the VM you just upgraded.
2. Locate the VPC in the folder labeled Second VM in the root of C: on the host
machine.
3. Boot up that VPC and log into it with the same credentials used in the first lab.
This will be the Server VPC you work with for the remainder of this manual.
Tasks
Extend the Active Directory schema
1. Run E:\Lab Files\extadsch.exe. A command prompt window appears as you
extend the Active Directory schema for use by SCCM. When the schema
extension process has completed, the command prompt window closes.
2. Open C:\Extadsch.log using Trace32. This file is created by the Extadsch.exe

utility and reports on the Active Directory schema extension process.
3. Was the schema extension process successful?

_____________________________________________________________________________
4. How many classes and attributes were added to Active Directory as a result of
extending the schema for SCCM 2007?
6 FINAL
_____________________________________________________________________________
5. Verify that there are no errors listed in the log, and then close Trace.
Create an Active Directory site

1. On the Start menu, point to Administrative Tools, and then click Active
Directory Sites and Services.
2. The Active Directory Sites and Services window appears.
3. In the console tree, click Sites. The list of AD sites appears in the results pane.
Notice the default site name of Default-First-Site-Name.
4. On the Action menu, click New Site.
5. The New Object – Site dialog box appears.
6. In the Name box, type Configuration ManagerSite
7. Under Link Name, click DEFAULTIPSITELINK, and then click OK.
An Active Directory message box appears listing steps that may be required to
complete the creation of the new site.
8. Click OK. The list of sites appears in the details pane. Notice the new site is
listed.
9. In the console tree, expand Sites, click Subnets, and then on the Action menu,
click New Subnet. The New Object – Subnet dialog box appears.
10. In the Address box, type 192.168.250.0
11. In the Mask box, type 255.255.255.0
12. Under Select a site object for this subnet, click Configuration ManagerSite,
and then click OK. The list of subnets appears in the details pane. Notice the
new subnet and its associated site.
13. In the console tree, expand Configuration ManagerSite, and then click
Servers. The list of servers for this site appears in the details pane. Notice that
there are no servers in this new site.
14. In the console tree, expand Default-First-Site-Name, expand Servers, and

then click SCCMSRV1. This is your Primary Domain Controller. You will move
this to your new site as its server.
15. On the Action menu, click Move. The Move Server dialog box appears
displaying all sites available.
FINAL 7
16. Under Site Name, click Configuration ManagerSite, and then click OK. The
list of servers for the default site appears in the details pane. Notice that there
are no servers in the default site.
17. In the console tree, expand Sites, expand Configuration ManagerSite, and
then click Servers. The list of servers for the new site appears in the details
pane. Notice that your Primary Domain Controller has been moved to the new
site.
18. Close Active Directory Sites and Services.
Add the Active Directory site to the Configuration Manager Boundaries.

1. In the tree, expand Site Database - SCCMSRV1, expand Site Management,
expand S00, expand Site Settings, and then click Boundaries.
2. The list of boundaries for the local site appears in the results pane. Notice that
there no default boundaries added to the site.
3. In the Actions pane, click New Boundary.
4. The New Site Boundary dialog box appears allowing the creation of a new
boundary.
5. In the Description box, type Active Directory site for SCCM
6. In the Type box, click Active Directory Site Name, and then click Browse.
7. The Browse Active Directory sites dialog box appears displaying the
available Active Directory sites. Notice that both the default AD site (Default-
First-Site-Name) as well the AD site you created earlier (Configuration
ManagerSite) are displayed.
8. Under Site Name, click Configuration ManagerSite, and then click OK.
9. The New Site Boundary dialog box appears displaying the information
specified for the new boundary.
10. Under Network Connection, verify that Fast (LAN) is selected, and then click
OK.
11. An Information message box appears indicating that the new boundary will
take up to a minute to update.
12. Click OK, and then in the Actions pane, click Refresh. Notice that the new AD
site (ConfigurationManagerSite) now appears as a boundary.
8 FINAL
Other Post Installation Tasks

There are additional steps that will need to be taken to complete the configuration
of the SCCM site, including enabling new client agents, approving clients so they can
join the site.
1. Open the Configuration Manager Help file.
2. In the Contents pane expand the section How to Configure Configuration

Manager 2007.
3. Click on Checklist for Required Post Setup Configuration Tasks. Complete

the following Mixed Mode tasks in this list:
a. Configure your Management Point
b. Determine if you need a Server Locator Point
c. Configure Your Client Agents
4. To set approval status for the clients use the search feature in the help file to
find the section titled How to Approve Configuration Manager Clients, then
follow the steps listed.
Exercise 3: Installing an SCCM 2007 Client

Scenario
In this exercise, you will install the SCCM 2007 client on the
Windows XP Professional client computer. You will begin by using Active Directory
System Discovery to discover the computer from Active Directory. Complete this
exercise on the Configuration Manager site server.
Tasks
Discover computers from Active Directory
1. In the tree pane, expand Site Database - S00, expand Site Settings, and then
click Discovery Methods.
2. The list of discovery methods for the local site appears in the results pane.
Notice that there are four discovery methods related to Active Directory.
3. In the results pane, click Active Directory System Discovery, and then in the
Actions pane, click Properties. The Active Directory System Discovery
Properties dialog box appears.
FINAL 9
4. Select Enable Active Directory System Discovery, and then click New (the
icon resembles a starburst).
5. The New Active Directory Container dialog box appears allowing you to
specify the use of a local domain, local forest, or custom query for the
discovery.
6. Verify that Local domain is selected, and then click OK.
7. The Select New Container dialog box appears allowing you to specify the
container to use for discovery.
8. Select SMSBeta, and then click OK.
9. The Active Directory System Discovery Properties dialog box appears.

Notice the distinguished name for the container to search. Also notice that a
recursive search will be performed on that container and that groups are
excluded.
10. Click the Polling Schedule tab.
11. The Active Directory System Discovery Properties dialog box displays the
default polling schedule for Active Directory System Discovery. Notice that by
default, this polling will occur daily.
12. Click Schedule.
13. The Custom Schedule dialog box appears.
14. Under Recurrence pattern, click None, and then click OK.
15. The Active Directory System Discovery Properties dialog box appears
displaying the current schedule.
16. Click Run discovery as soon as possible and then click OK.
17. The Configuration Manager Administrator Console window appears.
18. Wait a few minutes for the discovery process to complete then go to task 2.
Verify Active Directory System Discovery

1. In the tree pane, expand Computer Management, and then click Collections.
2. The list of collections appears in the results pane.
3. In the tree pane, expand Collections, and then click All Systems.
4. Notice that there are no members of the All Systems collection at this time.
10 FINAL
5. In the Actions pane, click Update Collection Membership.
6. An All Systems message box appears prompting to update sub-collection

membership.
7. Click OK.
8. The collection is updated. It takes a minute before the database is updated with
the new collection membership information.
9. In the Actions pane, click Refresh.
10. The collection membership is updated, and the current membership of the All
Systems collection is displayed.
a. Are there any new members in the All Systems collection?
____________________________________________________________________________________________
____________________________________________________________________________________________
b. Are each of the systems assigned to the site?
____________________________________________________________________________________________
____________________________________________________________________________________________
11. If the assigned status remains listed as No, then verify that you have correctly
listed Configuration Manager Site as a boundary for the site.
12. In the results pane, click the Windows XP Professional client, and then in the
Actions pane, under Configuration Manager Client, click Properties.
13. The Configuration Manager Client Properties dialog box appears displaying
discovery properties.
a. What is the discovered AD site name?
____________________________________________________________________________________________
14. Click Close.
Create the account required to install the Advanced Client

1. From Administrative Tools, start Active Directory Users and Computers.
2. The Active Directory Users and Computers window appears.
a. Create a new user with the name of ClientInstall, assign it a password of

Password, and then make this user a member of Domain Admins. This is
the account that will be used to push the SCCM 2007 client installation to
FINAL 11
the Windows XP Professional client. It must be a local admin on the client

computer. Being a member of Domain Admins is not a requirement, but
simplifies the configuration in the lab environment.
Configure the SCCM 2007 Client account

1. In the tree pane, expand SCCMSRV1, expand Site Management, expand S00,
expand Site Settings, and then click Client Installation Methods.
2. The list of client installation methods appears in the results pane.
3. In the results pane, click Client Push Installation, and then in the Actions
pane, click Properties.
4. The Client Push Installation Properties dialog box appears. Notice that the
installation method is not enabled. It does not need to be enabled for our push
installation.
5. Click the Accounts tab.
6. The Client Push Installation Properties dialog box displays accounts to be

used to push out the Configuration Manager client software. Notice that there
are no accounts listed.
7. Click New (the icon resembles a starburst).
8. The Windows User Account dialog box appears.
9. In the User name box, type smsdomain\ClientInstall
10. In the Password and Confirm password boxes, type password and then click
OK.
11. The Client Push Installation Properties dialog box displays accounts to be
used to push out the SCCM client software. Notice that the new account is
listed.
12. Click OK. The Configuration Manager Administrator Console window appears.
Install the SCCM Client

1. In the tree pane, expand Collections, and then click All Windows XP Systems.
The members of the All Windows XP Systems collection appear in the results
pane. Notice that there are no members of the collection.
2. In the Actions pane, click Update Collection Membership. The All Windows
XP Systems message box appears prompting to update subcollection
membership.
12 FINAL
3. Click OK. The collection is updated.
4. In the Actions pane, click Refresh. The collection membership is updated, and
the current membership of the All Windows XP Systems collection is displayed.
This should include the Windows XP Professional client computer,
Configuration Manager Client.
5. In the Actions pane, click Install Client. The Client Push Installation Wizard
dialog box appears.
6. Click Next. The Client Push Installation Wizard Installation options dialog
box appears displaying options for the client installation.
7. Click Next to accept the default configuration to install the client to assigned
resources. The Completing the Client Push Installation Wizard dialog box
appears indicating it is ready to complete the installation.
8. Click Finish. The SCCM 2007 client is remotely installed on the Windows XP
Professional client computer. It will take a few minutes before the installation
completes.
Verify the SCCM 2007 Client installation

Complete this procedure on the Windows XP Professional client computer only . It
will take a few moments for the installation of the SCCM 2007 client to complete.
You can use Task Manager to verify the installation. While ccmsetup.exe is running,
the client is being installed. When ccmsetup.exe terminates and Ccmexec.exe starts,
the SCMM 2007 client has been successfully installed.
1. Log on as administrator with a password of password.
2. In Control Panel, double-click Administrative Tools, and then start Services.

The Services window appears.
3. Verify that the Configuration Manager Agent Host service has been started.
4. Close Services.
Verify the reporting of the SCCM 2007 Client

Perform these steps on the site server.
1. In the tree pane, expand Collections, and then click All Windows XP Systems.
The members of the All Windows XP Systems collection appear in the results
pane. Notice that the Windows XP Professional computer appears. Also notice
that the computer is not listed as being an Configuration Manager client.
FINAL 13
2. In the Actions pane, click Update Collection Membership. The All Windows
XP Systems message box appears prompting to update sub-collection
membership.
3. Click OK. The collection is updated.
4. In the Actions pane, click Refresh. The collection membership is updated, and
the current membership of the All Windows XP Systems collection is displayed.
Notice that the Windows XP Professional client computer now is listed as being
installed as an SCCM 2007 client.
Exercise 4: Installing an SCCM 2007 Reporting Point

Scenario
In this exercise, you will install a Reporting Point for your SCCM site and then run a
report to verify the Reporting Point is running successfully. Complete this on the site
server.
Tasks
Install a Reporting Point
1. In the tree pane, expand SCCMSRV1, expand Site Management, expand S00,
and then expand Site Settings.The list of configurable site settings appears in
the results pane.
2. In the tree pane, expand Site System Roles, and then click \\SCCMSRV1. The
list of site system roles for the site server appears in the results pane. Notice
that there are six site system roles assigned to the computer.
3. In the Actions pane, click New Roles. The New Site Role Wizard General
dialog box appears.
4. Click Specify a fully qualified host name for this site system on the
intranet. This is required for native mode and for publishing in DNS.
5. In the Intranet FQDN box, type SCCMSRV1.SCSBeta.local
6. Click Next.
7. The New Site Role Wizard System Role Selection dialog box appears
displaying the list of site system roles that can be assigned to this computer.
14 FINAL
8. Under Available roles, select Reporting Point, and then click Next. The New
Site Role Wizard Reporting Point dialog box appears allowing you to
configure the reporting folder and port to use for the Reporting Point.
9. Click Next to use the default values. The New Site Role Wizard Summary
dialog box appears indicating that you have successfully completed the wizard.
10. Click Next. The New Site Role Wizard Wizard Completed dialog box appears
indicating that Configuration Manager is now ready to begin installation of the
Reporting Point.
11. Click Close. The Configuration Manager Administrator Console window

appears displaying the site system roles for the computer SCCMSRV1. Notice
that the Reporting Point role has been added to the list.
12. From Administrative Tools, start Services.The Services window appears.

Verify that the Configuration Manager Reporting Point service is installed and
running.
13. Close Services.
Report SCCM data

1. In the tree pane, expand SCCMSRV1, expand Computer Management, expand
Reporting, and then click Reports. The list of reports appears in the results
pane.
2. In the results pane, click Computers assigned but not installed for a
particular site, and then in the Actions pane, under Computers assigned but
not installed for a particular site, click Run. The Report Options message
box appears prompting for the Reporting Point to use to run the report.
3. Click OK to use the only Reporting Point in our site. The Computers assigned
but not installed for a particular site Report Information report appears in
the results pane. As this is a prompted report, you must supply the site code of
the site you wish to view computer information for.
4. In the Site Code box, type S00, and then click Display. An Internet Explorer
window starts and display the Computers assigned but not installed for a
particular site report. Notice that there are two computers discovered and
assigned to the site that are not yet clients, those being the domain controller
(SCCMSRV1) and the site server (SCCMSRV1).
5. Close the Configuration Manager Report window. The Configuration Manager

Administrator Console window appears displaying the site system You have
FINAL 15
now successfully deployed SCCM 2007 in your AD environment, including

installing a client computer and Reporting Point.
16 FINAL
Lab Manual Lab 2: Deploy a Branch DP
Lab 2: Deploy a Branch DP

Exercise 1: Creating and Configuring a Branch Distribution
Point
Scenario
■ Configure a standard Distribution Point to support BITS downloads.
■ Configure a branch Distribution Point.
■ Configure a protected site system.
■ Distribute software to a client to access a branch Distribution Point.
Estimated time to complete this lab: 90 minutes
Important
Existing DISTRIBUTION POINT should not be BITS enabled.
Tasks
1. Set up site boundaries:
a. Remove the AD boundary if necessary
b. Create bogus subnet 1.1.1.0
c. Create actual subnet 65.53.64.0
d. Under roles for the Site Server
e. Modify ConfigMgr site system as "Enable this site system as a protected

site system" and select 1.1.1.0
2. Create a Branch Distribution Point
a. On SCCMSRV1:
1.) Right click site systems under site settings and add a new server
2.) Setup a BDISTRIBUTION POINT w/ the following settings:
3.) Name: SCCMXP01 (uncheck FQDN option)
FINAL 17
4.) Select Distribution Point and Enable as a branch Distribution Point
5.) Modify the ConfigMgr site system as "Enable this site system as a
protected site system" and select 65.53.64.0
b. On SCCMXP01:
1.) Initiate a “Machine Policy Retrieval & Evaluation Cycle” from

Control Panel\Configuration Manager
2.) Run wbemtest
3.) Connect to root\ccm\policy\machine\actualconfig
4.) Click Enum Classes, check Recursive, and click OK
5.) Double click CCM_DistributionPoint and then Instances
6.) Once you see the following instance, you’ll know that your
BDISTRIBUTION POINT has received its policy:
a.) CCM_DistributionPoint.DummyKey=1
3. Create an Admin Provisioned Package:
a. On SCCMSRV1:
1.) In the ConfigMgr console navigate to Computer

Management\Software Distribution
2.) Right click Packages and select Distribute - Software
3.) Select "Create a new package and program without a definition

file" with the following selections (Use defaults if not specified):
a.) Name: BDISTRIBUTION POINTPkg
b.) Always obtain files from a source directory
c.) A Local drive on Site Server of C:\BDISTRIBUTION POINTPkg
4.) On the Distribution Points window
a.) Do not specify any Distribution Points
b.) Click OK
5.) Complete the Distribute Software Wizard with the following settings:
a.) Program Identification:
18 FINAL
(1.) Name: BDISTRIBUTION POINTProgram
b.) Command line: calc.exe
(1.) Do not advertise the program
4. Disable distmgr and policypv:
a. Open a cmd prompt and type “cd c:\sms\bin\i386”
b. Rename DistMgr.dll to DistMgr.old
c. Rename PolicyPv.dll to PolicyPv.old
d. Type “net stop sms_executive”
e. Type “net start sms_executive”
FYI
Leave this cmd prompt open for the rest of the exercise.
4. Add the content to the DISTRIBUTION POINT:
a. In the Admin console, navigate to BDISTRIBUTION POINTPkg under

Software Distribution\Packages
b. Right-click Distribution Points and select “Manage Distribution Points”
c. Select Copy the package to New Distribution Points
d. On the Package section of the wizard, select SCCMXP01,
e. Click Next
f. Review the error
g. Return back and select the Distribution Point of the Site Server
h. Click Next
f. Why are we still seeing the error?

______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
_____________________________________________________________________________________
FINAL 19
g. Cancel the wizard and make the appropriate correction to the Distribution
Point role under Site Systems\SCCMSRV1
1.) Return to the Manage Distribution Points wizard and add the
package to both the Site Server and Branch Distribution Point
2.) Complete the wizard
h. Navigate to the C:\sms\distmgr.box from Explorer
1.) Note the 0k PKN (package notification) file
i. Run the following commands from the command prompt:
1.) Rename distmgr.old distmgr.dll
2.) net stop sms_executive & net start sms_executive
j. Review distmgr.log and note the following
1.) SCCMXP01 is assigned a DISTRIBUTION POINTID
2.) Adds info regarding the BDISTRIBUTION POINT to the database
3.) Finally, you will see distmgr create a policy for the BDISTRIBUTION
POINT
Note
DistMgr does not copy any content to SCCMXP01. It simply creates a PkgID.PKN file
in policypv.box
k. Navigate to C:\SMS\Inboxes\policypv.box
1.) Note the PKN file
2.) Open the policypv.log file
l. From the command prompt, run the following:
1.) Rename policypv.old policypv.dll
2.) net stop sms_executive
3.) net start sms_executive
m. Review the policypv.log
20 FINAL
n. After the SMS_Executive is started back up, you’ll see policypv initializing
and then the following:
1.) “Looking for Branch DISTRIBUTION POINT package policy and policy
assignments that should be created”
2.) After this you will see STATMSG with Site Server, SCCMXP01, etc
3.) policypv then creates the policy that will be sent to SCCMXP01
o. On the client workstation (SCCMXP01):
1.) Note that the PKG share on the root of the C:\ drive has not yet been
created
2.) Initiate machine policy retrieval
3.) Note that this does not initiate download of the content.
FYI
We are only retrieving the policy that tells the client about the content.
4.) Once machine policy has been retrieved, initiate a “Branch

Distribution Point Maintenance Task”
5.) Assuming, the policy was received, you will almost immediately see
that we create the following temp directory:
a.) C:\BDISTRIBUTION POINT\TmpWrkFldr
6.) Note that only local system has rights to this directory
7.) Once the package is downloaded, you’ll see the following directory:
a.) C:\SMSPKGC$
Note
This can take some time, continue on with the exercise and verify the share makes it
later
8.) Navigate to c:\windows\system32\ccm\logs and review the

PeerDISTRIBUTION POINTAgent.log
FINAL 21
9.) Here you can view the packages that are being copied to the
BDISTRIBUTION POINT
10.) Review the information regarding the PKGID, site, Source Version, etc.
11.) Open wbemtest and connect to root\ccm\peerDistribution

Pointagent on SCCMXP01
a.) Enum Classes, click recursive, and click OK
b.) Double click the CCM_PeerDISTRIBUTION POINT_Job and

click instances
c.) Double click the job and click Show MOF
d.) Review the job details
Exercise 2: On-Demand Package Distribution

1. Create a new package:
a. Right click packages under software distribution and select New Package
b. Name: OnDemand
c. Set “This package contains source files” path to C:\BDISTRIBUTION

POINTPkg
d. On the Distribution Settings section, put a check in the “Make this

package available on protected Distribution Points when requested
by clients inside the protected boundaries”
2. Finish the package creation
3. Create a program for the OnDemand package with the following settings:
a. Name: OnDemanDistribution Pointrog
b. Command line: calc.exe
c. Accept the defaults for the rest of the program options
d. Navigate to the Distribution Points node under your newly created

package
e. Right click and select New Distribution Point
f. In the copy package section, select SCCMSRV1 and SCCMXP01
22 FINAL
4. Create an advertisement for the OnDemand package with the following

settings:
a. Name: OnDemandAdvert
b. Package: OnDemand
c. Program: OnDemanDistribution Pointrog
d. Collection: BDISTRIBUTION POINTCollection
e. On the Distribution Points section, select download content for both

options and clear the check in the “Allow clients to fallback” option.
5. Finish creating the Advertisement
6. Go back to the cmd prompt and type the following:
a. rename distmgr.dll distmgr.old
b. net stop sms_executive
c. net start sms_executive
7. Enable Verbose and Debug level logging for the MP/CCM
a. Open the registry editor and navigate to

HKLM\Software\Microsoft\CCM\Logging\@GLOBAL
b. Modify the permissions to the key to give Administrators Full Control
c. Change the LogLevel value from 1 to 0
d. Create the following new key:
e. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\DebugLogg
ing
f. Create a new REG_SZ called "Enabled" and set the value to "True"
8. Close the registry editor
9. At the command prompt type:
a. net stop ccmexec
b. net start ccmexec
10. On SCCMXP01:
a. Initiate a Machine Policy Retrieval & Evaluation Cycle

FINAL 23
b. Once OnDemand’s advertisement shows up run it
c. Note that our content isn’t available
11. On SCCMSRV1:
a. Navigate to the MP logs, located at c:\sms_ccm\logs
b. Open the MP_Location.log
1.) Review the ContentLocationRequest data
c. Now open the MP_Relay.log
1.) You will be able to see the demand file (*.DMD) being created
2.) You will see “FileType=Demand” and the file is placed in the
distmgr.box\incoming directory.
3.) If you navigate to C:\SMS\inboxes\distmgr.box\incoming

directory, you’ll see the DMD file that has been created
12. Restart Distribution Manager by going back to the command prompt and
typing:
a. rename distmgr.old distmgr.dll
b. net stop sms_executive
c. net start sms_executive
13. Review the C:\SMS\inboxes\distmgr.box\incoming directory and note that as

soon as the DMD file is processed, Distribution Manager creates a PKN file in
C:\SMS\inboxes\distmgr.box that is then processed
14. Open the distmgr.log and review the DMD file being processed
24 FINAL
Lab Manual LAB 3: Implementing Desired Configuration Management
LAB 3: Implementing Desired Configuration

Management
Objectives
■ Create a configuration item for compliance.
■ Import pre-created configuration items.
■ Create baselines for assignment.
■ Assign baselines to collections.
■ Verify compliance for the assigned baselines.
Scenario
In the following exercises you will enable the DCM agent, create and deploy
Configuration Items, use DCM to check for certain conditions on the client machine
and review Configuration Item information and compliance.
Exercise 1: Enable the DCM Client agent

1. Open the Configuation Manager Administrator Console.
2. Highlight Client Agents, under Site settings.
3. Right click on Desired Configuration Management Client Agent and choose

properties.
4. Check the box to enable Desired Configuration Management on computers and

click, OK.
Exercise 2: Create Configuration Items

1. Create an application CI for instances of a file.
a. Open the Configuation Manager Administrator Console.
b. Expand Desired Configuation Management, under Computer Management.
FINAL 25
c. Right click on Configuration Items and choose New -> Application

Configuation Item.
d. Set the name to be Notepad CI
e. Under Detection Method, always assume application is installed.
f. On the object page, select new -> File
1.) On the general tab, choose type: file
2.) For the path, type 'C:\Windows\'
3.) For the filename, type '*Notepad.exe'
4.) For search depth, select 'Specified path and all subfolders'
g. For validation, check the box 'Report a non-compliance event when this
instance count fails.
h. Instance count operator should be 'less than or equal to' and count should
be 3. Severity should be set to warning.
i. Click ok, then accept all other defaults until wizard completes.
2. Create an application CI for a registry value.
b. Expand Desired COnfiguation Management, under Computer Management.
c. Right click on Configuration Items and choose New -> Application

Configuation Item.
d. Set the name to be CCM CI
e. Under Detection Method, always assume application is installed.
f. On the object page, Click Next.
g. On the settings page, select new -> Registry.
1.) On the general tab, set the display name to be 'CCMExec rule'
2.) For the Hive, leave HKLM
3.) For the key, type 'system\currentcontrolset\services\ccmexec'
4.) Leave all other boxes blank and click next.
26 FINAL
h. For validation, check the box 'Report a non-compliance event when this
instance count fails.
i. Instance count operator should be 'not equals' and count should be 1.

Severity should be set to error. Click ok, then next.
j. For Applicability, choose all check boxes for x86 and Windows Server
2003.
3. Review XML definitions of CIs
a. Right click on the Notepad CI and select 'view XML Definition'
b. The XML should open with Internet Explorer. Locate the validation criteria.
c. Close internet explorer.
d. Right click on the CCMExec CI and select 'view XML Definition'
e. Locate the validation criteria.
f. Close internet explorer.
4. Export and import Notepad rule
a. Right click the notepad CI and choose 'export configuration data'
b. Save the cab file to the desktop.
c. Open the CAB file and extract the file '1.xml'
d. Review the file with Internet Explorer. Close IE when done.
e. Go back to the Admin console and delete the notepad Configuration Item.
f. Import the cab file back from the desktop.
g. Review the settings of the imported rule to verify that they match the
original CI.
Exercise 3: Establishing DCM Baselines

1. Create a new baseline
b. Expand Desired COnfiguation Management, under Computer Management.
c. Right click on Configuration baselines and choose New configuration

baseline.
FINAL 27
d. Give the baseline the name 'notepad baseline'.
e. Under rules, click on the link 'These applications and general configuration
items...'
f. Select the Notepad CI. Right click and view the XML Definition in IE.
g. Note the Logical name and version values under the requireditems tag.
Does this match the same values for the Notepad CI from the previous
exercise?
2. Assigning Baselines
a. Right click on the Notepad baseline and choose 'assign baseline to a

collection'.
b. Select the notepad baseline and assign to the 'all systems' collection.
3. Evaluating compliance on the client agent.
a. Open the Configuration Manager Agent control panel tool on the site
server.
b. Go to the actions tab and initiate a Machine Policy retreival cycle.
c. Close the control panel tool and reopen it after a minute.
d. On the Configurations tab, highlight the notepad baseline and click the
'evaluate' button.
e. When the task completes, click the 'view report' button.
4. Exporting and Importing baselines
a. Right click the notepad baseline and choose 'export configuration data'
b. Save the cab file to the desktop.
c. Open the CAB file and extract the two xml files.
d. Review both files in notepad. What are the contents of the two files?
e. Go back to the Admin console and delete the notepad baseline.
f. Import the notepad baseline cab back from the desktop. Is the baseline the
only CI that is imported?
g. Review the settings of the imported baseline to verify that they match the
original CI.
28 FINAL
h. Is the re-imported baseline still assigned to a collection?

____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
5. Configure a child baseline
a. Create a new baseline named 'MP Baseline'.
b. Assign the CCMExec CI as an optional appliction CI.
c. Assign the MP Baseline to the collection 'All windows server 2003 systems'
d. Run a machine policy update cycle on the agent and verify that this
baseline is now applied to the site server.
e. Evaluate the baseline and view the report.
f. Go back to the Admin console and highlight the MP baseline.
g. Right click and choose 'add -> configuration baseline'.
h. Add the notepad baseline as a rule of the MP Baseline.
i. Update the policy on the site server's client agent. Verify that the version
has incremented. Is the notepad baseline added or not?
j. Evaluate the baseline and view the report.
Exercise 4: Reviewing CI information on the server and client

1. Review the Configuration items in SQL
a. Open the SMS database in SQL Management Studio.
b. Find the table 'CI_ConfigurationItems' and right click to open table.
c. Expand column 'CI_UniqueID'. Based on the names, which items appear to

be stored in this table?
d. Highlight one of the cells from the column 'SDMPackageDigest'. Copy and
paste the contents into notepad. What data does this column contain?
e. Under views, open 'v_ConfigurationItems'. Note the contents of this view.
f. Open the view 'v_CIAssignmentToCI'. Note that one CI is assigned. The

CI_ID can be compared to the previous view to identify which CI is
assigned.
FINAL 29
g. Open 'v_CIAssignment' and note the Assignment ID from the previous view.
Scroll to the collectionID and CollectionName column and note the
collection this CI is assigned to. This can also be found in the view
'CITargetedCollections'.
2. Review DCM policy on client
a. Open WBEMTest on the site server.
b. Connect to root\ccm\policy\machine\actualconfig
c. Enum all classes and double click on 'CCM_DCMCIAssignment' to open the

object editor.
d. Click on the instances button to show each assignment for this client.
e. Double click on the instance and then the 'Show MOF' button on the
instance property dialog.
f. Under the property 'AssignedCIs', note the values of the <ID> and
<Version> XML Tags.
3. Review DCM Evaluation on client logs
a. On the site server, go to E:\SMS_CCM\Logs and open DCMAgent.log in

Trace32
b. From the Configuration Manager Agent Tool in Control Panel, start an

evaluation cycle of the MP Baseline and follow the progress in the
DCMAgent.log.
c. Note the entries for the 'ProcessDiscovery' stage. The Baseline IDs should
match those found in SQL and WMI.
d. Highlight the entries that contain the string 'PartCIComplianceState'. From

the details panel, can you tell if this CI was compliant or not?
e. Review 'CIAgent.log'. Did the CI agent need to download any policy or

definitions during this evaluation cycle?
f. Review 'SDMAgent.log'. Which baselines were added to the SDM Package?
g. Open Discovery.log. Note the operating system discovery steps when

logging begins for this evaluation cycle.
h. Note the registry query for CCMExec.
30 FINAL
i. Highlight the string 'notepad.exe'. Due to the number of errors that will
already be highlighted, change the highlight color under 'preferences' in
Trace32. Note the number of properties that are discovered for each
instance of notepad.exe during an evaluation cycle.
Exercise 5: Check that the Windows Firewall is Enabled

Using Desired Configuration Management
If you need to check the firewall settings for both Operating Systems, configure the
first configuration item and then duplicate it. Then modify the duplicate so that it
has a unique name, unique description, the correct WQL query, and the correct
Operating Systems specified for applicability.
These configuration items can also be used as a simple test to ensure that Desired
Configuration Management is working as expected.
1. In the Configuration Manager console, navigate to System Center

Configuration Manager / <site server name>/ Computer Management /
Desired Configuration Management.
2. Expand the Desired Configuration Management node
a. Right-click Configuration Items
b. Click New
c. Click General Configuration Item.
3. On the Identification page of the Create General Configuration Item

Wizard, specify the following:
a. Name: Specify a unique and descriptive name for the configuration item,
such as Security Setting for Windows XP: Windows Firewall Enabled.
b. Description: Specify a description for the configuration item, such as This

configuration item determines whether the firewall service is started and
set to automatically start on computers running Windows XP.
4. Click Next twice.
5. On the Settings page of the Create General Configuration Item Wizard, click
New, and then click WQL Query.
6. In the New WQL Query Settings Properties dialog box, specify the following
on the General tab:
a. Display name: Windows Firewall is running
FINAL 31
b. Description: Checks if Windows Firewall service is running
c. Namespace: Root\CIMV2
d. Class: Win32_Service
e. Property: Started
f. WQL query WHERE clause: Name="sharedaccess"
7. Click the Validation tab, and then specify the following:
a. Data Type: String
8. Rules: Click the New icon.
9. In the Configure Validation dialog box, specify the following:
a. Name: Started=true.
b. Description: Service should be started.
c. Operator: Equals
d. Value: true
e. Severity: Warning
10. Click OK twice to close the New WQL Query Setting Properties dialog box.
New, and then click WQL Query.
12. In the New WQL Query Settings Properties dialog box, specify the following
on the General tab:
a. Display name: Windows Firewall starts automatically
b. Description: Checks if Windows Firewall service starts automatically
c. Namespace: Root\CIMV2
d. Class: Win32_Service
e. Property: StartMode
f. WQL query WHERE clause: Name="sharedaccess"
13. Click the Validation tab, and then specify the following:
a. Data Type: String
32 FINAL
14. Rules: Click the New icon.
15. In the Configure Validation dialog box, specify the following:
a. Name: StartMode=Auto.
b. Description: Service should start automatically.
c. Operator: Equals
d. Value: Auto
e. Severity: Warning
16. Click OK twice to close the New WQL Query Setting Properties dialog box.
Next.
18. On the Applicability page of the Create General Configuration Item Wizard,
specify the following:
a. All x64 Windows XP Professional
b. All x86 Windows XP
c. x64 Windows XP Professional SP1
d. x64 Windows XP Professional SP2
e. x86 Windows XP Professional Service Pack 2
19. Click Next twice, and close the Wizard Completed page.
20. Now that you have created these general configuration items, they can be
added to a configuration baseline using the following configuration baseline
rule:
21. These application and general configuration items are required and must be
properly configured
22. Assign this configuration baseline to Windows XP Professional computers that

should have the Windows Firewall started automatically, and investigate the
computers that report noncompliance.
FINAL 33
Exercise 6: Check for the Presence of the Client Installation

Properties Registry Key Using Desired Configuration
Management
This task guides you through the process of using Desired Configuration
Management in Configuration Manager to create a general configuration item with
an object setting to determine whether the registry key
Hkey_Local_Machine\Software\Policies\Microsoft\Ccmsetup\SetupParameters is
found on client computers.
1. In the Configuration Manager console, navigate to System Center

Configuration Manager / Site Database / Computer Management /
Desired Configuration Management.
2. Expand the Desired Configuration Management node
a. Right-click Configuration Items
b. Click New
c. Click General Configuration Item.
3. On the Identification page of the Create General Configuration Item

Wizard, specify the following:
a. Name: Specify a unique and descriptive name for the configuration item,
such as Client setup parameters registry check.
b. Description: Specify a description for the configuration item, such as This

configuration item determines whether client computers have instances of
the registry
keyHkey_Local_Machine\Software\Policies\Microsoft\Ccmsetup\SetupPar
ameters
4. Click Next.
5. On the Objects page of the Create General Configuration Item Wizard
a. Click New
b. Click Registry Key.
6. In the New Registry Key Properties dialog box, specify the following in the
General tab:
a. Hive: From the drop-down list, select HKEY_LOCAL_MACHINE.
34 FINAL
b. Key: Specify the path

Software\Policies\Microsoft\Ccmsetup\SetupParameters.
c. Is this registry key associated with a 64-bit application? Select No.
d. Select the option Report a non-compliance event when this instance

count rule fails.
e. Instance count operator: Select Greater than.
f. Values: Specify the value 0.
g. Severity: From the drop-down list, select Warning.
7. Click OK to close the New Registry Key Properties dialog box.
8. Click Next.
Next.
10. On the Applicability page of the Create General Configuration Item Wizard,
specify the following:
a. Under Windows Platforms, select All Windows Platforms.
11. Click Next.
12. On the Summary page of the Create General Configuration Item Wizard, review
the settings for the configuration item you have created, and then click Next.
13. View the Progress page of the Create General Configuration Item Wizard. When
this is complete, view the summary of actions taken on the Wizard Complete
page.
14. Click Close.
15. Now that you have created this general configuration item, it can be added to a
configuration baseline using the following configuration baseline rule:
a. These application and general configuration items are required and must
be properly configured
Assign this configuration baseline to computers that should not have this registry
key present, and investigate the computers that report non-compliance.
FINAL 35
Lab Manual Lab 4: Deploying Software Updates
Lab 4: Deploying Software Updates

■ Configure integration between WSUS 3.0 and SCCM 2007.
■ Analyze required updates.
■ Distribute an update using SCCM 2007.
■ Use Configuration Manager Reporting to report update status.
Estimated time to complete this lab: 4 hours
Exercise 1. Working with WSUS

Note
For the software updates labs WSUS has been preinstalled and the updates synchronized
from the internet to save time. We will review the WSUS installation and how to configure
config Mgr to work with WSUS.
Scenario
Config Mgr requires WSUS 3.0 for software updates. The WSUS server must be
dedicated to Config Mgr but must be installed ahead of time. Let's review the WSUS
install.
Tasks
1. Installing WSUS
a. Launch the WSUS console by clicking Start > All Programs > Administrative
Tools > Microsoft Windows Server Update Services.
b. Explore the console. Note that the synchronization schedule settings,

update category settings, proxy settings, etc. may all be configured under
the 'options' node of the console.
Note
For Config Mgr it is recommended to run WSUS 'headless' meaning that WSUS will be
installed without the administrator console. When using Config Mgr we are in total control of
the WSUS server. All configurations to WSUS will be done through the Config Mgr Software
FINAL 37
Update Point and will enforce these policy settings on WSUS. There is generally no reason to
use the WSUS console for administrative purposes. For troubleshooting it can be useful.
Note
In Config Mgr, the WSUS server is modified to ONLY provide software update
synchronization and scanning on Config Mgr clients. Software Updates are NOT delivered from
the WSUS server - they are delivered via SMS.
c. In the file system, open the C drive and navigate to Program Files > Update
Services. Explore the folders located here. Note that the WSUS logs are
stored under the LogFiles folder. We will look at the WSUS logs in the next
exercise.
2. Installing a Config Mgr Software Update Point
a. To install a Software Update Point, navigate to Site Management > S00 - MS

> Site Settings > Site Systems. Right-click the \\SCCMSRV1 node and select
'new role'. In this case, the site system has already been installed for you.
Do NOT remove and readd it.
b. Right 'click on the ConfigMgr software update point' and select properties.
The options presented here allow configuration of proxy server settings.
c. Next, navigate to Site Management > S00 - MS > Site Settings > Component
Configuration. Right-click the 'Software Update Point Component' node
and select properties. This is where the main configuration of the Software
Update Point is done. Review the settings here and close the window.
Note
The settings seen in step 2 and 3 above are all configurable through the Software Update
Point installation wizard when performing initial configuration.
d. Review the SUPSetup.log which records the installation of the software

update point. This log is located at e:\Lab Files\WSUS - SUP INstall and
config logs\SUP LogFiles. Also review the WSUSCtrl.log located int he
same location. This log is responsible for ongoing interaction with the
WSUS server to ensure it remains configured as Config Mgr expects.
38 FINAL
Exercise 2. Synchronizing software updates

Scenario
To retrieve a list of software updates for use in Config Mgr you must synchronize
with the WSUS server. This is a two step process - first, the WSUS server must sync
updates from the internet. When complete, the Config Mgr server must import
those updates from the WSUS server.
Tasks
1. To initate update synchronization navigate to Computer Management >
Software Updates > Update Repository. Right-click on the 'Update Repository'
node and select 'Run Synchronization'. A warning window will display
indicating the sync process can be time-consuming. Select 'Yes' on the warning
window.
Note
The update sync will very likely fail due to the config of the VM's we are using.
Note
All updates have been pre-synchronized for the lab to avoid synchronization wait time.
When synchronizing normally be aware that the process can take hours - particularly if multiple
categories/languages are selected. Note that we have limited our updates in the lab to just
security updates for Windows XP systems.
2. The synchronization process can either be a scheduled operation or by

initiated manually. Navigate to E:\SMS\Inboxes\Sitectrl.box and open the
sitectrl.ct0 file in notepad. Search for 'sync now'. When a manual
synchronization is intiated this field in the site control file is updated. The sync
manager thread watches for updates here and will initate the sync.
3. Review the logs showing the synchronization process. As mentioned above, the
synchronization starts by Config Mgr requesting the WSUS server to update it's
list of software updates from the internet. The softwaredistribution.log shows
this process for the WSUS server and is located at e:\Lab Files\WSUS - SUP
install and config logs\WSUS log files. The initial request to WSUS to
synchronize and then the second step of synchronizing Config Mgr from the
WSUS server is recorded in the WSyncMgr.log located at E:\Lab Files\WSUS -
SUP install and config logs\SUP LogFiles.
FINAL 39
Note
Searching through the softwaredistribution.log can be confusing at first. To see the sync
recorded here search for '729 config updates, 725 are new' in the log files. Do a top down
search. Review the log entries starting at this line down.
4. Software updates are loaded into the database and stored as configuration
items. Configuration items are used by several Config Mgr components. In the
SQL database, review the various potential CI types. Expand the SMS_S00
database and navigate to tables. Find the CI_Types table. Right click on the
tables and open it. This table defines the various types of CIs that might be
imported. Note tye type IF of the SoftwareUpdate CI's - it should be 1.
5. Still in the database, open the CI_ConfigurationItems table. This is where the
various imported CI's are stored. Note that the CIType_ID field is mostly filled
with Software Updates based on the type ID.
Exercise 3. Creating and deploying a software update

Tasks
1. Enable the Software Updates Client Agent
a. In the Config Mgr console, navigate to Site Management > S00 - MS > Client
Agents. Right-Click on the 'Software Updates Client Agent' and select
properties.
b. On the 'General' tab, place a check mark beside 'Enable Software Updates
on clients'. Review the settings on the remaining tabs and click OK.
c. On the SCCMXP01 VM, navigate to the control panel. Open the

'Configuration Manager' control panel applet. Select the actions tab and
initiate a machine policy refresh. Monitor until the the actions 'Software
Updates Deployment Evaluation Cycle' and 'Software Updates Scan Cycle'
appear on the Actions tab in the 'Configuration Manager' control panel
applet properties. Refreshes are done by closing and reopening the applet.
d. In the Config Mgr console, update and refresh the all systems collection to
ensure the client system shows up and lists S00 as it's site code.
1. Create a deployment
40 FINAL
a. In the Config Mgr console, navigate to Computer Management > Software

Updates > Update Repository > Security Updates > Microsoft > Windows
XP and click directly on the 'Windows XP' node. A list of available updates
in this category will be shown in the middle pane. Sort the 'Bulletin ID'
column so that it is sorted with the most recent updates on top.
b. Click on the MS06-034 update, right click on the highlighted update and
select 'deploy software updates'.
Note
This update has been pre-downloaded for use in the lab.
c. The 'Deploy Software Updates Wizard' opens. On the General page, type
'Lab deployment - MS06-034' as the name and click next.
d. On the 'Deployment Template' screen, select 'create a new deployment

definition' and click next.
Note
Templates are used to store common settings and can significantly reduce the amount of
administrative time to deploy new updates.
e. On the 'Collection' page, click browse and select the 'All Systems' collection
and then click next.
f. On the 'Display/Time Settings' screen, ensure 'Allow display notifications

on clients' is selected and ensure 'UTC' time is selected. Note the deadline
settings of 2 weeks. This default setting can delay updates from installing
as soon as might be expected. If immediate deployment is desired, this
should be set to 0 weeks. For our deployment, ensure this is set to 0 weeks
and click next.
g. On the 'Restart settings' pages, note the settings here and click next.
h. On the 'Event Generation' page, note the settings here and click next.
i. On the 'Update Binary Download - ConfigMgr Client Settings' ensure

'Download software updates from distribution point and install' is set and
click next.
FINAL 41
j. On the 'Create Template' screen ensure 'Save deployment properties as a

template' is set and enter 'Lab Template' as the template name and click
next.
Note
This step saves the settings just entered as a lab template. All of these settings can be
reused by choosing this template at the first of the deployment wizard.
k. On the 'Deployment Package' screen, select 'Create a new deployment

package' and enter the following information and then click next.
1.) Name: Lab deployment package
2.) Description: Lab Updates
3.) Package source: \\sccmsrv1\c$\LabUpdates
l. On the 'Distribution Points' page, browse and add the server DP to the
package and click next.
m. On the 'Download Location' page, select 'Download software updates from

a location on the local network' and browse to E:\Lab
Files\Updates\WU\Software\en\com_microsoft.windowsxp\x86\winxp\c
om_microsoft.windowsxp-kb917537-x86=181319 and click next.
n. On the 'Language selection' screen, ensure English is the only langauage

selected and click next.
o. On the 'Deployment Schedule' screen, review the settings. Ensure the

deadline for the deployment is the current data/time and click next.
Note
If you get an error about deadline time, set it a minute ahead of the current system clock
and the error should resolve.
p. On the 'Summary' page, review the information and click next. The
deployment will be created. Review the results and close the wizard.
q. In the Config Mgr console, review that we now have a deployment template
defined in the 'Deployment Templates' node. Review properties for this
template to see what all is stored on the template. Also note that we have a
new Deployment package and new Deployment under Deployment
42 FINAL
Management. Review the properties of the new 'Lab Deployment - MS06-

034' under the Deployment Management node.
r. In the database, expand the SMS_S00 database and expand tables. Locate
and open the CI_AssignmentTargetedCI's table. Write down the
AssignmentID and CI_ID. This table maps a unique assignment ID to the CI
that will be delivered with the assignment. Now open the
CI_CIAssignments table. Find the assignmentID you noted ealier and notice
the AssignmentName column - this is the Name of the deployment we
configured earlier. Also note the TargetCollection value. This value maps
to the collection that is targeted by the assignment in the Collections table.
Now open the CI_ConfigurationItems table. This table is the master table
for all CI's. Find the value CI_ID that matches what you noted earlier. Also
open the CI_UpdateCIs table and find the CI_ID value here. This table is the
detail table for CI's that are specifically for updates. Notice that the CI_ID
entry details information about the MS06-034 update.
s. On SCCMXP01 client, navigate to control panel and open the 'Configuration

Manager' control panel applet. Select the 'actions' tab and initiate a
machine policy refresh cycle. It may take several minutes for the policy to
refresh and you may need to update more than once.
t. Click on Start > Run and launch wbemtest.
u. In the WBEMTEST console click 'connect', in the namespace box enter

'root\ccm\policy\machine\actualconfig' and click connect. On the main
window click 'Enum Classes', select recursive and OK. From the Query
Result list, double-click CCM_UpdateCIAssignment. On the 'Object editor
for CCM_UpdateCIAssignment' window, select 'Instances'. On the query
result window we should have one listing. Double-click on it and then in
the object editor, click 'Show MOF'. This window will list the details about
the deployment. Note the AssignedCI's lists the UpdateID's of the patches
that are part of this assignment. Also notice the deadline settings here and
the other config info listed.
v. Back in the control panel applet, initiate a 'Software Updates Scan Cycle'.
Use the component flows located at \\lcmanage\sccm2007flows to trace
the software update through the logs.
1.) Did the update install?

_________________________________________________________________________________
_________________________________________________________________________________
FINAL 43
2.) How would you know if the update installed?

_________________________________________________________________________________
_________________________________________________________________________________
3.) Why did it install or not install?

_________________________________________________________________________________
_________________________________________________________________________________
Note
Config Mgr is significantly different from SMS 2003 and the patch management habits
learned there may not be the best practices to follow in Config Mgr. The idea of adding new
patches to an existing deployment is one such example. In Config Mgr there is no obvious way
to add new updates to an existing deployment. Instead, it is generally thought best to create
new deployments for new software updates. Config Mgr doesn't care what deployment or
deployment package the updates are in when deploying.
If you do want to add a new software update to an existing deployment, however, it is possible.
2. Adding an update to an existing deployment
a. In the Config Mgr console, navigate to the software update repository and
find MS05-047. Expand Deployment Management so that both the security
update and the existing deployment package, Lab Deployment - MS06-034,
are visible. Click on the MS05-047 patch and drag it to and drop it on the
Lab Deployment - MS06-034 node.
b. The 'deploy software updates wizard' will launch and display options for
appending the new software update to the existing deployment. Navigate
through the wizard to note any differences. When asked whether to
download or not, cancel the wizard.
Exercise 4. Software update reports

Scenario
Software updates reports have changed noticeably in Config Mgr. Now that we have
deployed an update, review the various report options and the information they
provide. Pay attention to the following groups of reports
■ Software Update - Infrastructure Health
44 FINAL
■ Software Updates - A. Compliance
■ Software Updates - B. Deployment Management
■ Software Updates - C. Deployment Status
■ Sofware Updates - E. Troubleshooting
The data for many of the new reports comes from state messages - a new type of
status message in Config Mgr. State messages aren't covered here but are small
condense messages indicating the state - either yes or no - of veraions new objects
in Config Mgr - software updates, desired configuration management, etc.
FINAL 45
Lab 5: Working with Operating System

Deployment
Before you Begin
■ Complete Module 6
What you will Learn

■ How to create a Task Sequence
■ How to add Device Drivers to the catalog
■ How to create a Driver package
Estimated time for the Lab: 2 hours
Exercise 1: Capturing an OSD reference image

Scenario
In this lab you will prepare the required task sequence to allow for image capture.
This requires selecting a boot image that will be used when generating the task
sequence media. We will then proceed to capture an image of a Windows XP SP2
system that will be used throughout the remaining lab exercises.
Tasks
1. Prepare capture task sequence
a. Launch the Config Manager administrator console.
b. Expand Computer Management > Operating System Deployment >

Boot Images > Boot Image (x86).
c. Right-click on the 'Boot Images (x86)' node and select properties.
1.) Click on the Windows PE tab and place a check mark in the 'Enable
command support (testing only)' box. This will enable command
prompt support in Windows PE.
d. Expand the 'Boot Image (x86)' package node.
e. Right click on the Distribution Points node and select 'New Distribution
Point'. Select the Distribution Point for the site and select OK.
46 FINAL
Lab Manual Lab 5: Working with Operating System Deployment
f. On the Operating System Deployment > Task Sequences node
1.) Right click 'Task Sequences' and select 'Create Task Sequence
Media'.
g. In the ‘Task Seqence Media Wizard' select ‘Capture Media' and select
Next.
h. On the 'Media Type' screen
1.) Select CD/DVD set and in the Media file box type
c:\capturemedia.iso.
2.) Click Next.
i. On the 'Boot Image' screen click browse for the boot image and select 'Boot
image (x86) and select OK. On the 'Distribution Point' windows ensure the
Distribution Point configured earlier is selected and click Next.
j. Review the information and click Next.
k. The capture media will be created.
1.) The resulting .iso will be used to capture the image in the Next step. A
copy of the capture ISO may be found on your host machine in the root
of the C:\ drive
2. Capture XP SP2 image
Note
A few configurations need to be in place when preparing a system to be imaged - the system
must be in a workgroup configuration, must have the Config Mgr client installed (doesn't have
to be assigned) and, if XP, must have the sysprep files copied to a folder called sysprep in the
root of the C drive. These configurations are already in place on our image.
a. On the SCCMSRV1 create a folder called xpsp2capture on the root of the C

drive and share it so that everyone has full control for both share and NTFS
permissions.
b. Turn on the XPFORCAPTURE VM and configure it's CD-ROM to mount the

capturemedia.iso created earlier.
1.) The 'Image Capture Wizard' should start up automatically. I
a.) f not, open 'My Computer' and double-click on the CD-ROM icon
which should start the wizard.
FINAL 47
c. Review the 'Welcome to the Image Capture Wizard' page and click Next.
d. On the 'Image Destination' page enter

\\sccmsrv1\xpsp2capture\xpsp2.wim for the destination.
1.) For the account name enter scsbeta\administrator and for the
password use !LS1setup.
e. On the 'Image Information' screen enter the following information and

click Next.
1.) Created by: TestOSDCapture
2.) Version: 1.0
3.) Description: XPSP2 image capture
f. Review the information on the Summary page and click Finish.
g. The task sequence engine will start and will verify/initialize the Config Mgr
client, run sysprep, reboot into PE and begin capturing the image. Once
booted into PE press the F8 button to launch a command window. This will
allow you to verify network settings, review logs, etc. Once image capture
begins use the command window to review the available drives and their
contents. Which drive(s) can you access? What do they contain? Review
the _SMSTaskSequence folder on the C drive. What does it contain? Open
the logs folder and open the SMSTS.LOG file with notepad. Review the
contents of this log. What does it show? Once complete you may abort the
capture. This XPSP2.WIM image has been previously captured for use in
remaining lab sections and is located on your Config Mgr server in the
E:\Lab Files directory.
Exercise 2: Configuring and deploying a captured image

Scenario
This lab will walk through the process of deploying a captured reference image -
including configuring and using a state migration point, configuring the image for
user state migration and configuring driver injection.
Tasks
1. Install and configure the state migration point
Note
The State Migration Point is used to store user state during migration. Data stored here is
48 FINAL
protected so that only the imaging system may have access to the user data.
a. In the Config Mgr console, navigate to Site Management > S00 - MS >
Site Systems.
1.) Right click on \\SCCMSRV1 and select 'New roles'.
2.) In the 'New Site Role Wizard' review the general information page
and click Next.
3.) On the 'System Role Selection' page, place a check mark on the State
Migration Point role and click Next.
4.) On the 'State Migration Point' page click the starburst to add a new
directory.
a.) On the 'Storage Folder' window that opens, enter c:\statemig for
the storage folder and then click OK.
b.) Review the remainder of the settings on this wizard screen and
click Next.
5.) Review the data on the summary page and click Next. Close the wizard
after it completes.
b. Open the Config Mgr logs folder and review the State Migration Point
installation logs - SMSSMPSetup.log and SMPMSI.log.
1.) Did the installation succeed?

_________________________________________________________________________________
2.) What command line was launched to initiate the install?

_________________________________________________________________________________
_________________________________________________________________________________
3.) Was the statemig folder created?

_________________________________________________________________________________
4.) What does it contain?

_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
FINAL 49
5.) What new SMS_Executive thread is now running to manage the SMP?
_________________________________________________________________________________
_________________________________________________________________________________
2. Configuring and deploying the captured reference image
a. Import the XPSP2 WIM
1.) In the Config Mgr console, navigate to Computer Management >

Operating System Deployment. Right-click on the Operating System
Images node and select 'Add Operating System Image'.
2.) On the 'Data Source' screen of the 'Add Operating System Image
Wizard' enter \\sccmsrv1\e$\lab files\xpsp2.wim for the path and
click Next.
3.) Verify the information on the 'General' page of the wizard and click
Next twice.
4.) Verify the import succeeded on the 'Wizard Completed' screen and
click close.
5.) To complete this section, add a Distribution Point to the image.
Note
Deploying an image requires creation of a custom task sequence.
3. Create package to install SMS client
Note
It is not required to create a program for the SMS client package - all that is needed is a
package that points to the client source files.
a. In the Admin Console, navigate to Computer Management > Software

Distribution > Packages.
1.) Right-click the Packages node and select New > Package. The 'New
Packages Wizard' will launch.
2.) On the 'General' page of the wizard enter 'Config Mgr client' for the
name of the package and click Next.
50 FINAL
3.) On the 'Data Source' page place a check by 'This package contains
source files' and then click 'set'. On the 'Set Source Directory'
screen select 'Local drive on site server' and enter e:\sms\client as
the source directory. Click OK and then click Next.
4.) On the 'Data Access', 'Distribution Settings', 'Reporting', 'Security'

and 'Summary' pages, review the settings and click Next through
them all. After the summary page the wizard will complete - click
close.
5.) Add a Distribution Point for the pack to complete this section.
4. Create package to for USMT 3.0
Note
It is not required to create a program for the USMT 3.0 package - all that is needed is a
package that points to the client source files.
a. Launch the InstallUSMT301_x86.msi file located in E:\Lab Files.
1.) Accept the defaults and complete the install.
b. Navigate to Computer Management > Software Distribution >

Packages.
c. Right-click the Packages node and select New > Package. The 'New
Packages Wizard' will launch.
d. On the 'General' page of the wizard enter 'USMT 3.0' for the name of the
package and click Next.
e. On the 'Data Source' page place a check by 'This package contains

source files' and then click 'set'.
f. On the 'Set Source Directory' screen select 'Local drive on site server'
and enter c:\program files\usmt301 as the source directory.
g. Click OK and then click Next.
h. On the 'Data Access', 'Distribution Settings', 'Reporting', 'Security' and

'Summary' pages, review the settings and click Next through them all.
i. After the summary page the wizard will complete - click close.
j. Add a Distribution Point for the pack to complete this section.
FINAL 51
Exercise 3: Import sample drivers

Scenario
Config Mgr has the ability to detect and inject drivers into the new OS during the
imaging process. Driver inject is also able to add drives to PE when it is created
through Config Mgr. We will import a test driver for inclusion with our image
deployment and PE. Note: The driver chosen is a random driver and will likely not
work with either the image or PE but is included for demonstration purposes.
Tasks
1. Mass storage driver import
a. We first need to create a source directory that will hold our driver package
that will be created during his exercise.
1.) Navigate to the root of the C drive and create a folder called DriverSrc.
Inside this folder create another folder called DriverTest
b. In the Config Mgr console navigate to Computer Managerment >

Operating System Deployment > Drivers.
c. Right click on the Drivers node and select Import.
1.) On the 'Locate Driver' page of the 'Import New Driver' wizard enter
\\sccmsrv1\e$\lab files\driver as the source folder and click Next.
d. On the 'Driver Details' page verify the driver shows up in the list and is
selected and click Next.
e. On the 'Add Driver to Package' screen, select 'New Package'.
f. Enter DriverTest for the name of the package and enter

\\sccmsrv1\c$\driverssrc\drivertest for the driver package source and
click OK.
g. Back on the 'Add Driver to Package' screen, click Next.
h. The wizard gives the option of also adding the driver to a boot image. If the
drive is a NIC or mass storage driver this option is particular helpful. On
the 'Add Driver to Boot Image' screen, select 'Boot Image (x86)' and
click Next twice to finish the wizard. The wizard will import and configure
the driver. Review the results and close the wizard.
52 FINAL
Exercise 4: Creating a deployment task sequence

Scenario
We will now create a task sequence for deploying our XPSP2 image that will pull all
of the configurations we have just made together.
Tasks
1. Create a new Task Sequence
a. In the Config Mgr console navigate to Computer Management >

Operating System Deployment > Task Sequences.
b. Right-click on Task Sequences and select 'New > Task Sequence'. This
will launch the 'New Task Sequence' wizard.
c. On the 'Create New Task Sequence' wizard, select 'Install an existing

image package' and click Next.
d. On the 'Task Sequence Information' page of the wizard, enter 'Test

deployment' as the Task Sequence name. For the boot image, select 'Boot
image (x86) and then click Next.
e. On the 'Install the Windows Operating System' screen, select the

Windows XP SP2 image we imported earlier for image package and click
Next.
f. On the 'Configure the network' screen, select 'Join a workgroup' and

enter 'Workgroup' for the name of the workgroup and click Next.
g. On the 'Install the ConfigMgr client' screen, select the 'Config Mgr Client'
package created earlier and click Next.
h. On the 'Configure State Migration' page, select the USMT 3.0 package
created earlier and click Next.
i. On the 'Include Updates in Image' page, ensure 'Don't install any

software updates' is selected and click Next.
j. On the 'Install Software Packages' page, note that we have now added the
ability to include updates as part of the image install. Make sure nothing is
included here and click Next.
k. On the summary page, click Next. Review the summary after the wizard
completes and click close.
FINAL 53
Note
We will be deploying this task sequence to bare metal. In order to do this we must
first import the new system into a collection.
2. Import the New System into a Collection
a. For this exercise, we need to be sure the XPFORIMAGING VM is set with a

static MAC address. Verify this in for the VM. We also need to precreate a
collection that will contain our XPFORIMAGING machine. Create this
collection and name it BAREMETALDEPLOY with no membership rules.
b. Navigate to Computer Management > Operating System Deployment >

Computer Associate. Right-click on the computer associate node and
select 'Import Computer Information Wizard'.
c. On the 'Select Source' page, select 'Import single computer' and click
Next.
d. On the 'Single Computer' page, enter XPFORIMAGING for the computer

name and enter the MAC address found in the network settings of the VM.
Examine the source computer option and how it is used. In this lab we will
not use the source computer.
e. Click Next.
f. On the 'Data Preview' page, review the information and select Next.
g. On the 'Choose Target Collection' page, click browse and select the
BareMetalDeploy collection created earlier. Once selected, click OK and
then Next.
h. On the 'Summary page' select Next. The wizard will import the new
computer and populate the collection. Review the results and close the
wizard.
3. Advertise the task sequence
a. In the Config Mgr console, navigate to Computer Management >

Operating System Deployment > Task Sequences. Select the task
sequences node which will show our 'Test Deployment' task sequence in
the middle window.
b. Right-click on the 'Test Deployment' task sequence and select 'advertise'
54 FINAL
c. In the 'New Advertisement Wizard' enter 'Test Deployment - bare

metal' for the name. Select the the BareMetalDeploy collection and also
ensure the 'Make this task sequence available to boot media and PXE'
IS checked. Without this check mark the task sequence would only be
available via advertisements.
d. On the 'Schedule' page, click Next.
e. On the 'Distribution Points' page, select 'Access content directly from a

Distribution Point' and click Next.
f. On the 'Interaction' page, ensure 'Show the task sequence progress' is

selected and click Next.
g. On the 'Security' and 'Summary' pages, click Next and when the wizard
finishes, close it.
4. Create deployment task sequence media
a. In the Config Mgr console, navigate to Computer Management >

Operating System Deployment > Task Sequences. Right-click on the
Task Sequences node and select 'Create Task Sequence Media'. The
'Task Sequence Media' wizard will launch.
b. On the 'Select Media Type' screen, select 'Bootable media' and click
Next.
c. On the 'Media Type' page, select 'CD/DVD set' and enter

c:\deploymedia.iso as the media file and click Next.
d. On the 'Security' page, remove the check beside 'Protect media with a
password' and click Next.
e. On the 'Boot image' page, select 'Boot Image (x86)' as the boot image.
Verify the Distribution Point is listed and click Next.
f. On the 'Summary' page, review the information and click Next. When the
wizard completes, review the summary and close the wizard. The
deploymedia.iso that was created is available on your host system in the
root of the C:\drive
5. Deploy image to VM
a. Before imaging the VM we need to configure the network access account

for use. Navigate to Site Management > S00 - MS > Site Settings > Client
Agents. Right-click on the computer client agent and select properties. On
the General tab, configure the network access account as follows:
FINAL 55
1.) Username: ScSBETA\administrator
2.) Password: !LS1setup
b. Configure the XPFORIMAGING VM to boot from the deploymedia.iso and

make sure the VM NIC is configured for the internal network. When
finished, power on the VM.
c. If prompted, select to boot from CD.
d. Windows PE should start up - when the initial splash screen is displayed

and the task sequence progress window shows up, press F8 to bring up a
command window. The 'Task Sequence Wizard' will display shortly
e. On the 'Welcome to the Task Sequence Wizard' page, select configure.

On this screen configure the following settings
1.) IP address - 192.168.250.101
2.) Subnet Mask - 255.255.255.0
3.) DNS Server - 192.168.250.1
f. You could also omit these settings provided a DHCP server is available for
addressing. Once complete, select OK and then click Next.
Note
If errors are noted retrieving policy, verify the IP address and that SCCMSRV1 can be pinged.
Also, use the command window to access the SMSTS.LOG to review the cause of the error. The
SMSTS.LOG at this stage will be on the X drive.
g. On the 'Select a Task Sequence' window, choose 'Test Deployment' and

click Next.
h. The wizard will review content and dependencies required by the task
sequence to make sure it is available.
Note
If errors are seen here it is usually due to content not being installed on a
Distribution Point. Review the error and, if needed, review the logs.
i. The task sequence will install the image. Using the command prompt,
review the logs. The SMSTS.log is the master log that will follow through
the deployment steps.
56 FINAL
Exercise 5: Install and configure the PXE service point

Scenario
The PXE service point is used to enable WDS deployments of OSD images. We will
install the PXE service point but will not use it for deployment in this lab.
Tasks
1. Verify that WDS is already installed on the machine by checking for the WDS
console under administrative tools - verify it will launch.
2. In the Config Mgr console, navigate to Site Management > S00 - MS > Site
Settings > Site Systems. Right-click on \\SCCMSRV1 and select 'new roles'.
3. On the 'General’ page' of the 'New Site Role Wizard', select Next.
4. On the 'System Role Selection' page, select 'PXE service point' and click Next.
5. Review the settings on the 'PXE - General' page. Remove the check mark for
requiring a password and click Next.
6. Review the settings on the 'PXE - Database' page and click Next.
7. Review the 'Summary' page and click Next. The wizard will complete, review
the results and close the wizard.
8. Review the PXESetup.log to verify installation was successful.
Note
In order for the PXE service point to work, at least one boot image must be available
to the PXE service point.
9. In the Config Mgr console, navigate to Computer Management > Operating

System Deployment > Operating System Images > Microsoft Windows XP
SP2. Expand this package and right-click on the Distribution Points node.
Select 'New Distribution Points'.
10. In the 'New Distribution Point Wizard', click Next.
11. On the 'Copy Package' screen, notice that a new PXE Distribution Point has
been added. Choose this Distribution Point and complete the wizard.
12. Where are the files and logs for supporting the PXE service point?
___________________________________________________________________________________________
FINAL 57
___________________________________________________________________________________________
___________________________________________________________________________________________
13. Navigate to C:\RemoteInstall. In this folder we see the three new folders for the
PXE service point.
14. What new thread of the executive has been added?

___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
15. Where is it's log?

___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
Exercise 6: Creating and distributing a non-OSD task

sequence
Tasks
1. To start this exercise, configure one package. In the source directory for this
package copy notepad.exe, wordpad.exe and calc.exe. Create the package and
then create three programs, one to run each executable. Stage the package onto
a Distribution Point.
Note
When creating the program MAKE SURE that the 'Allow this program to be installed
from the Install Software task sequence without being advertised' option is selected on
the advanced tab. Also MAKE SURE that the program is set to run 'whether or not a user
is logged on'. The task sequence editor will filter out any programs not configured in this
way.
2. In the Config Mgr console, navigate to Computer Management > Operating

System Deployment > Task Sequences. Right click on the Task Sequences
node and select New > Task Sequence.
3. In the 'New Task Sequence Wizard' select 'Create a new custom task
sequence' and click Next.
4. On the 'Task Sequence Information' page, enter non-OSD task sequence from
the task sequence name and click Next.
58 FINAL
5. On the 'Summary' page, click Next and when the wizard completes, close it.
6. The task sequence has been created - now it needs to be edited to provide
required execution steps.
Note
Any task sequence can be edited in this manner. The others created generally don't
need to be but can still be modified using the same editor.
7. In the 'Task Sequences' node, select the 'non-OSD task sequence'. Right-click
on it and select 'edit'.
8. In the task sequence editor, select 'add'. Review the various choices of actions
that can be taken in a task sequence. Once you are finished reviewing then,
choose the General > Install Software action.
9. On the properties page for this action, choose the package created in step 1 and
choose the notepad program. Add two more 'Install Software' options - the
second one for Wordpad and the third for Calculator. Once done, select OK on
the task sequence.
10. In the Task Sequences node of the console, right-click on the 'non-OSD task
sequence' and select 'advertise'.
11. In the 'New Advertisement Wizard' select 'all systems' for the collection and
click Next.
12. Review the settings in the 'Schedule' page and click Next.
13. On the 'Distribution Points' page, select 'Access content directly from a
Distribution Point when needed by the running task sequence' and click
Next.
14. On the 'Interaction' page, select 'Show the task sequence progress' option
and click Next.
15. On the 'Security' and 'Summary' pages, click Next and when the wizard
processing completes, close the wizard.
16. Review the All Systems collection and verify that SCCMXP01 is listed as a
installed and assigned tp the site. If not, ensure that it is.
17. On the SCCMXP01 Client, go to the control panel and open the Config Manager
applet and refresh machine policy.
FINAL 59
18. After several minutes, the 'run advertised program' control panel applet should
display the advertised task sequence. Continue to refresh until it arrives and, if
it doesn't show within 5 minutes, refresh the machine policy again. Once the
task sequence advertisement arrives, click on it and execute. You will notice the
three programs run in the order specified.
Important
The captured image we will use for the remaining sections is not activated - this is done on
purpose.
Exercise 7: Importing Windows Device Drivers into the

Driver Catalog
Scenario
Use the following procedure to import Windows device drivers into the driver
catalog. For the Import task use the INF file in the following directory on the host
machine:
E:\Lab Files\Dell Network Drivers\WinXP\i386
Tasks
1. Import Windows device drivers
a. In the Configuration Manager console, navigate to System Center

Configuration Manager / Site Database / Computer Management /
Operating System Deployment / Drivers.
b. To start the Import New Driver Wizard, do any of the following:
1.) Click Action on the Configuration Manager Console menu, and then
click Import.
2.) In the Actions pane, click Import.
3.) Right-click the Drivers node, and then click Import.
c. On the Locate Driver page, specify whether you want to import a specific
device driver or all device drivers contained in a specific directory.
d. To import a specific driver, select Import a specific driver and specify the
source file directory in UNC format and the Windows device driver.INF or
mass storage txtsetup.oem file to be imported.
60 FINAL
e. To import all of the device drivers in a specific directory, select Import all
drivers in the following network path (UNC) to its .inf or txtsetup.oem
file and specify the network path to the device driver directory.
f. On the Driver Details page, specify a descriptive name and optional

description for the driver.INF file or files that will be imported. To allow
computers to use the device drivers, the Enable these drivers and allow
computers to install them check box must be checked. This check box is
selected by default.
g. To assign the device drivers to a category for filtering purposes, such as

"Beta" or "Production," click the Categories button. The category
assignment is also used to configure the device drivers that will be
considered by the Auto Apply Driver task sequence step.
h. On the Platforms Applicability page, confirm the platforms where these

drivers will be installed.
i. To make the driver available to all platforms, select This driver can be
run on any platform.
j. To specify a particular client platform for the device driver to be installed,

select This driver can run only on the specified platforms, and then
select the applicable platforms.
k. On the Add Driver to Packages page, assign the device driver to an

existing package, or create a new package by clicking the New Package
button to open the New Driver Package dialog box.
l. Specify the Name, and Description that should be associated with the new
driver package and provide the source directory in UNC format, and then
select Update Distribution Points when finished to update the
Distribution Points immediately. Drivers must be part of a package and
deployed to Distribution Points before computers can install them. If you
do not update Distribution Points immediately, you must update the
Distribution Points later using the Update Distribution Point wizard.
m. On the Add Driver to Boot Images page, specify the boot image or
images,which should have the driver added.
n. Select Update Distribution Points when finished to update the

Distribution Points immediately with the updated boot images.
o. On the Summary page, review the action details, and then click Next to
complete the wizard.
FINAL 61
Lab Manual Lab 6: Implementing Service Windows
Lab 6: Implementing Service Windows

Objectives
■ Configure maintenance windows on collections.
■ Verify software distribution behavior to a client in a collection with a

maintenance window to allow distribution.
■ Verify software distribution behavior to a client in a collection that is configured

with a maintenance window to restrict distributions.
Exercise 1: Configuring Maintenance Windows on

Collections
Scenario
In this exercise, you will configure maintenance windows on collections. You will
configure a maintenance window to prevent software distribution to server
computers, and then configure a maintenance window to allow distribution to the
Windows XP client. Complete these tasks on the site server unless otherwise
specified.
Tasks
1. Configure a maintenance window to prevent software distribution
a. If not already running, on the Start menu, click Configuration Manager

Administrator Console. The Configuration Manager Administrator
Console window appears.
b. In the tree pane, expand SCCMSRV1, expand Computer Management,

expand Collections, and then click All Windows Server 2003
Systems.The list of members of the All Windows Server 2003 Systems
collection appears in the results pane. Notice that there are two
Configuration Manager clients in the collection (SCCMSRV1 and
SCCMSRV1) but that the Windows XP client (Configuration ManagerClient)
is not a member of the collection.
c. In the Actions pane, click Modify Collection Settings. The All Windows
Server 2003 Systems Settings dialog box appears displaying
FINAL 63
maintenance windows for the collection. Notice that by default, there are
no maintenance windows configured for the collection.
d. Click New (the icon resembles a starburst). The <new> Schedule dialog
box appears allows the configuration of a maintenance window for the
collection.
e. In the Name box, type Restricted window
f. In the Effective date box, set the date to tomorrow. Make sure you choose
tomorrow’s date, not today.
g. In the Start box, set the starting time to be the top of the current hour.
h. In the End, set the starting time to be the top of the next hour. You need at
least a 15 minute window for this exercise. Make sure your configuration
creates a maintenance window that will prevent the server computers
from running the advertised program today and has a duration of at least
15 minutes.
i. In the Recurrence pattern box, verify that None is selected and then click
OK. A Systems Management Server message box appears indicating that
the maintenance window is not configured for a recurring schedule and
that software updates will not install on the members of the collection.
j. Click Yes to create the non-recurring maintenance window. The All

Windows Server 2003 Systems Settings dialog box appears displaying
maintenance windows for the collection. Notice that the new maintenance
window is displayed for the collection.
k. Click OK. The list of members of the All Windows Server 2003 Systems
collection appears in the results pane.
2. Configure a maintenance window to allow software distribution
a. In the tree pane, expand SCCMSRV1, expand Computer Management,

expand Collections, and then click All Windows XP Systems. The list of
members of the All Windows XP Systems collection appears in the results
pane. Notice that there is only one Configuration Manager client in the
collection (Configuration ManagerClient) and that the two server
computers (SCCMSRV1 and SCCMSRV1) are not members of the collection.
b. In the Actions pane, click Modify Collection Settings. The All Windows
XP Systems Settings dialog box appears displaying maintenance windows
for the collection. Notice that by default, there are no maintenance
windows configured for the collection.
64 FINAL
c. Click New (the icon resembles a starburst). The <new> Schedule dialog
collection.
d. In the Name box, type Permitted window
e. In the Effective date box, verify that today’s date is displayed.
f. In the Start box, verify that the current time is displayed.
g. In the End, set the starting time to be two hours from the current time.
This configuration will create a maintenance window that will allow the
Windows XP client to run the advertised program in the next two hours as
the window is current. You should not need two hours, but to give yourself
plenty of time, you are configuring a two hour window.
h. In the Recurrence pattern box, verify that None is selected and then click
OK. A Systems Management Server message box appears indicating that
the maintenance window is not configured for a recurring schedule and
that software updates will not install on the members of the collection.
i. Click Yes to create the non-recurring maintenance window. The All

Windows XP Systems Settings dialog box appears displaying
maintenance windows for the collection. Notice that the new maintenance
window is displayed for the collection.
j. Click OK. The list of members of the All Windows XP Systems collection
appears in the results pane.
3. Identify collections with maintenance windows
a. In the tree pane, expand SCCMSRV1, expand Computer Management, and

then click Collections. The list of collections appears in the results pane.
b. In the results pane, if necessary, scroll to the right until you can view the
Maintenance Window column.
c. You may need to refresh the console to view the updated information. The
list of collections appears in the results pane including the listing of
whether or not each collection includes a maintenance window. Notice that
the two collections you configured earlier are identified as having
maintenance windows.
d. In the results pane, drag the Maintenance Window column to appear after
Name. The Maintenance Window column now appears right after Name.
FINAL 65
e. In the results pane, click the Maintenance Window column to sort by the
maintenance window attribute. The Maintenance Window column now
appears sorted by the appropriate value, with the collections containing
maintenance windows at the bottom of the display.
4. Identify maintenance windows available to a client

expand Reporting, and then click Reports. The list of reports appears in
the results pane.
b. 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 Report Options message box
appears prompting for the Reporting Point to use to run the report.
c. Click OK to use the only Reporting Point in our site. 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.
d. In the Client Name box, type Configuration ManagerClient, 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.
e. Close the Configuration Manager Report window. The Configuration

Manager Administrator Console window appears displaying the Service
Windows Available to a Particular Client Report Information report in
the results pane.
Exercise 2: Implementing the Maintenance Windows on the

SCCM Clients
Scenario
In this exercise, you will force the clients to retrieve policies, which will implement
the appropriate maintenance windows on the clients. Complete these tasks on the
SCCM clients unless otherwise specified.
66 FINAL
Tasks
1. Implement the maintenance windows
a. In Control Panel, start Systems Management. The Systems

Management Properties dialog box appears.
b. Click the Actions tab. The Systems Management Properties dialog box
displays the available actions for the Advanced Client. Notice the default
actions of Branch DP Maintenance Task, Discovery Data Collection Cycle,
File Collection Cycle, Hardware Inventory cycle, Machine Policy Retrieval &
Evaluation Cycle, Software Inventory Cycle, Software Metering Usage
Report Cycle, Software Updates Evaluation Cycle, User Policy Retrieval &
Evaluation Cycle and Windows Installer Source List Update Cycle.
c. Click Machine Policy Retrieval & Evaluation Cycle, and then click
Initiate Action. The SCCM client will request new policies, which will
include the policy related to the advertised program. A Machine Policy
Retrieval & Evaluation Cycle message box appears indicating the action
was initiated, and may take several minutes to complete.
d. Click OK. The Systems Management Properties dialog box appears.
e. Click OK. It will take a couple of minutes to evaluate and implement the
policy.
f. Open C:\Windows\System32\Ccm\Logs\ServiceWindowManager.log.
Notepad appears displaying the contents of the Service Window Manager
log file.
g. Search for New service window. Notepad displays the first occurrence of
“new service window”. Notice that the current line indicates that there
was a new service window policy implemented.
h. If you are looking at the Windows XP client, you will see lines referring to:
1.) Scheduling the StartTime for today
2.) The duration of two hours
3.) The Active Service Windows list has 1 window
4.) Programs can run
i. If you are looking at the server computer, you will see lines referring to:
1.) Scheduling the StartTime for tomorrow
FINAL 67
2.) The duration of an hour
3.) No windows in the Active Service Windows list
4.) “Scheduling the timer to fire in 0 days, 23 hours…”
j. Close Notepad.
Exercise 3: Distributing Software to the SCCM Clients

Scenario
In this exercise, you will distribute software to the SCCM clients. You will distribute
to the All Systems collection to include all three clients. Complete these tasks on the
site server unless otherwise specified.
Tasks
1. Distribute an application to a client

expand Collections, and then click All Systems. The list of members of the
All Systems collection appears in the results pane. Notice that all three
computers are installed as clients in the site.
b. In the Actions pane, click Distribute, and then click Software. The
Distribute Software to Collection Wizard dialog box appears.
c. Click Next. The Distribute Software to Collection Wizard Package

dialog box appears providing options for package creation or distribution.
d. Select Create a new package from a definition, and then click Next. The
Distribute Software to Collection Wizard Package Definition dialog box
appears allowing you to select the package definition file to use. Notice the
default package definitions built into SCCM 2007.
e. Click Browse. The Open dialog box appears.
f. Open C:\Configuration ManagerTools\SMS2003Toolkit2.msi. The

Distribute Software to Collection Wizard Package Definition dialog box
appears allowing you to select the package definition file to use. Notice that
Configuration Manager 2003 Toolkit 2 is displayed.
g. Under Package definition, verify that SMS 2003 Toolkit 2 is selected, and
then click Next.
68 FINAL
h. The Distribute Software to Collection Wizard Source Files dialog box

appears prompting for source file handling instructions.
i. Click Always obtain files from a source directory, and then click Next.
The Distribute Software to Collection Wizard Source Directory dialog
box appears allowing the designation of the source file directory.
j. Click Local drive on site server, and then click Browse. The Browse For
Folder dialog box appears.
k. Click C:\Configuration ManagerTools, and then click OK. The Distribute

Software to Collection Wizard Source Directory dialog box displays the
designated source directory.
l. Click Next. The Distribute Software to Collection Wizard Distribution

Points dialog box appears allowing the designation of Distribution Points
to store the package files. Notice that only the site server Distribution Point
(SCCMSRV1) is listed.
m. Under Distribution Points, select SCCMSRV1, and then click Next. The
Distribute Software to Collection Wizard Select Program dialog box
appears allowing the selection of the program to advertise.
n. Under Programs, click Per-system unattended, and then click Next. The
Distribute Software to Collection Wizard Advertisement Name dialog
box appears prompting for a name and comment for the advertisement.
o. Click Next to accept the default name. The Distribute Software to

Collection Wizard Advertisement Subcollection dialog box appears
prompting for advertising to subcollections.
p. Click Next to accept the default option of advertising to subcollections as

well (even though we do not have any subcollections). The Distribute
Software to Collection Wizard Advertisement Schedule dialog box
appears prompting for a start and expiration time for the advertisement.
q. After Advertise the program after, verify that the current date and time
is displayed.
r. Verify No. This advertisement never expires is selected, and then click
Next. The Distribute Software to Collection Wizard Assign Program
dialog box appears prompting for program assignments.
s. Click Yes. Assign the program.
FINAL 69
t. In the Assign after box, verify that the current time is listed. The time
configured should fit within the time frame of the maintenance window
configured for the All Windows XP Systems collection.
u. Click Next. The Distribute Software to Collection Wizard Summary

dialog box appears prompting to complete the wizard.
v. Click Next. The Distribute Software to Collection Wizard Confirmation

dialog box appears indicating the process was successful.
w. Click Close. The list of members of the All Systems collection in the results
pane.
2. Verify package configuration
a. In the tree pane, expand Computer Management, expand Software

Distribution, and then expand Packages. The new package appears in the
tree pane. You may need to refresh the display to see the new package.
b. In the tree pane, expand Microsoft Corporation Configuration Manager

2003 Toolkit 2 2.50.0 English. The Microsoft Corporation
Configuration Manager 2003 Toolkit 2 2.50.0 English package data
appears in the tree pane.
c. In the tree pane, click Programs. The configured programs for the package
appear in the results pane. Notice the Per-system unattended program
which you advertised to the client using the Distribute Software wizard.
d. In the results pane, click Per-system unattended, and then in the Actions
pane, click Properties. The Per-system unattended Properties dialog
box appears displaying general properties for the program. Notice the
command line used.
e. Click the Requirements tab. The Per-system unattended Properties

dialog box appears displaying requirements for the program. Notice that
the maximum run time is set to unknown. This is larger than our window,
and we need to set the max run time value to fit within our window.
f. In the Maximum allowed run time (minutes) box, type 5 and then click
OK. The configured programs for the package appear in the results pane.
Notice that the Per-system unattended program now displays a maximum
run time of 5 minutes.
g. In the tree pane, click Distribution Points. The Distribution Points for the
package appear in the results pane. Notice only the local site server is
listed.
70 FINAL
h. In the tree pane, click Advertisements. The advertisement for the

Configuration Manager 2003 Toolkit 2 program appears in the results
pane. Notice the Available After time is the date and time the
advertisement was created.
3. Search for available advertised programs
Note
In the following procedure, you will initiate the searching for advertised programs on your
SCCM client computer. Perform this task on the client computers.

policy. If you are looking at the Windows XP client computer, you will see
an Assigned Program About to Run icon appears in the system tray.
f. Double-click the Assigned Program About to Run icon. The Program

Countdown Status dialog box appears indicating an assigned program will
run within the next five minutes.
g. Click Run. The program will attempt to install. Since you advertised the
“Per-system unattended” program, this will be a silent installation, and you
will not see any user interface. The install will only take a minute to
complete. If you are looking at either of the two server computers, you will
not see anything occur, as the program will not run.
FINAL 71
4. Verify the program installation
Note
Complete this procedure on the Windows XP client.
a. On the Start menu, point to All Programs. The All Programs menu
appears. Notice that a new menu titled SMS 2003 Toolkit 2 appears.
b. Point to SMS Toolkit 2. The Configuration Manager 2003 Toolkit 2 menu

appears. This is a confirmation that the advertised program did install
successfully on the client in the configured service window.
c. Open C:\Windows\System32\Ccm\Logs\Execmgr.log. Notepad appears

displaying the contents of the Execution Manager’s log file.
d. Search for per-system. The first occurrence of “per-system” is highlighted.

Remember that the program you advertised was the per-system
unattended program. This line indicates a policy for the per-system
unattended program was received.
e. Search for service window. The first occurrence of “service window” is

highlighted. This line indicates that the service window does allow the
program to run.
f. Close Notepad.
5. Verify the program installation failure
Note
Complete this task on the site server.
appears. Notice that there is no new menu titled Configuration Manager
2003 Toolkit 2 as was displayed on the Windows XP client computer.
b. Open C:\Windows\System32\Ccm\Logs\Execmgr.log. Notepad appears

displaying the contents of the Execution Manager’s log file.
c. Search for per-system. The first occurrence of “per-system” is highlighted.

Remember that the program you advertised was the per-system
unattended program. This line indicates a policy for the per-system
unattended program was received.
72 FINAL
d. Search for service window. The first occurrence of “service window” is

highlighted. This line indicates that the program could not run due to a
service window restriction. Notice that the last line in the log indicates the
client is waiting for a service window.
e. Close Notepad.
6. Report the advertisement status

expand Reporting, and then click Reports. The list of reports appears in
the results pane.
b. In the results pane, click Status of a specific advertisement, and then in

the Actions pane, under Status of a specific advertisement, click Run.
c. The Status of a specific advertisement Report Information report

appears in the results pane. As this is a prompted report, you must supply
the ID of the advertisement you wish to view status for.
d. Click Values. The Values dialog box appears displaying the available
advertisements.
e. Under Advertisement ID, click the ID of the SMS 2003 Toolkit 2

advertisement.
f. The Status of a specific advertisement Report Information report

appears in the results pane displaying the ID of the advertisement for
which you wish to view status.
g. Click Display. An Internet Explorer window starts and display the Status
of a specific advertisement report. Notice that there were three clients
that received the advertisement, one was successful in running the
program, and two are listed as “waiting”.
h. Click the arrow to the left of “Succeeded”. The All system resources for a
specific advertisement in a specific state report appears. Notice that one
client listed is the Windows XP client (Configuration Manager Client) and
that the last status is “Program completed with success”.
i. Click Back, and then click the arrow to the left of “Waiting”. The All system
resources for a specific advertisement in a specific state report
appears. Notice that both clients listed are the Windows Server 2003
clients (SCCMSRV1 and SCCMSRV1) and that the last status is “Waiting for
a Service Window”.
FINAL 73
j. Close the Configuration Manager Report window. The Configuration

Manager Administrator Console window appears displaying the Status of
a specific advertisement Report Information report in the results pane.
7. Configure a maintenance window for All Systems

expand Collections, and then click All Systems. The list of members of the
All Systems collection appears in the results pane. Notice that all three
clients are members of this collection.
b. In the Actions pane, click Modify Collection Settings. The All Systems
Settings dialog box appears displaying maintenance windows for the
collection. Notice that by default, there are no maintenance windows
configured for the collection.
c. Click New (the icon resembles a starburst). The <new> Schedule dialog
collection.
d. In the Name box, type Daily window
e. In the Effective date box, verify that today’s date is displayed.
f. In the Start box, verify that the current time is displayed.
g. In the End, set the starting time to be two hours from the current time.
h. This configuration will create a maintenance window that will allow the
clients to run the advertised program as the window is current. Even
though the two server computers are members of another collection with a
restricted window, SCCM 2007 performs a union of all available windows
for the client to identify availability.
i. In the Recurrence pattern box, select Daily, and then click OK. The All
Systems Settings dialog box appears displaying maintenance windows for
the collection. Notice that the new maintenance window is displayed for
the collection.
j. Click OK. The list of members of the All Systems collection appears in the
results pane.
8. Implement the maintenance windows

74 FINAL
policy.
f. On the server computer, an Assigned Program About to Run icon

appears in the system tray.
g. Double-click the Assigned Program About to Run icon. The Program

Countdown Status dialog box appears indicating an assigned program will
run within the next five minutes.
h. Click Run.
i. The program will attempt to install. Since you advertised the “Per-system
unattended” program, this will be a silent installation, and you will not see
any user interface. The install will only take a minute to complete.
j. On the Windows XP client computer, you will see nothing new, as the
program has already run.
9. Verify the program installation
Note
Perform this task on all client computers.
appears. Notice that a new menu titled Configuration Manager 2003
Toolkit 2 appears.
FINAL 75
b. Point to SMS Toolkit 2. The SMS 2003 Toolkit 2 menu appears. This is a
confirmation that the advertised program did install successfully on the
client in the configured service window.
10. Report the advertisement status

expand Reporting, expand Reports, and then expand Visited Reports.
The list of reports that had previously been run appears in the results
pane. Notice that the “Status of a specific advertisement” report is listed.
b. In tree pane, click Status of a specific advertisement. The Status of a

specific advertisement Report Information report appears in the results
pane. As this is a prompted report, you must supply the ID of the
advertisement you wish to view status for.
c. In the Advertisement ID box, type S0020001, and then click Display. An

Internet Explorer window starts and display the Status of a specific
advertisement report. Notice that there were three clients that received
the advertisement, and all three clients were successful in running the
program.
d. Click the arrow to the left of “Succeeded”. The All system resources for a
specific advertisement in a specific state report appears. Notice that all
three clients are listed with a last status of “Program completed with
success”.
e. Close the Configuration Manager Report window. The Configuration

Manager Administrator Console window appears displaying the Status of
a specific advertisement Report Information report in the results pane.
f. You have now successfully implemented maintenance windows in SCCM

2007, and verified software distribution behavior using the maintenance
windows.
Exercise 4: Create two Maintenance Windows to control

software distribution
Scenario
In this exercise, you will create two maintenance windows that will be used to
control software distribution. Exercises 2 and 3 will demonstrate the behavior of
these maintenance windows.
76 FINAL
Tasks
1. Create a maintenance window for the all systems collection
a. Open the Configuration Manager Administrator console
b. Highlight the Collections node. Notice that the maintenance window

column shows 'no' for all collections at this time.
c. Highlight the "All Systems" collection. In the actions menu, select Modify
Collection Settings.
d. Click the yellow astrisk button to create a new maintenance Window.
e. Set the window to begin about 1 hour from the current time.
f. Set the duration of the window for 3 hours and do not select to use UTC
time.
2. Create a maintenance window for the all Windows XP systems collection
a. Highlight the All Windows XP Systems collection and choose modify

collection settings.
b. Create a maintenance window for this collection, but have the start time
begin at 1am and the end time at 4am.
c. After the second window has been created, highlight the Collections
container and verify that the two collections now show Yes under the
Maintenance window column.
Exercise 5: Create an advertisement to verify the first

Maintenance Window permits software distribution
Scenario
In this exercise, you will create two advertisements, one will begin before the
maintenance window starts, the other will begin after the maintenance window
starts.
Tasks
1. Advertise first.txt to run before the maintenance window.
a. Right click on the All Systems collection and select Distribute, then
Software.
FINAL 77
b. You will need to create a new package and program without a definition
file.
c. The source file will be the local drive E:\Labfiles\SWTest.
d. On the program identification page, set the command line to be

'Notepad.exe first.txt'. Any name or category can be given for this
program.
e. On the program properties tab, set the max run time to 10 minutes
f. Take the defaults on the next four pages.
g. On the Advertisement Schedule, set the advertisement time to begin 10

minutes before the maintenance window on the all systems collection is
set to begin.
h. Assign the program and take all the defaults on the Assign program page
for now. Click Finish.
i. Open the properties of the advertisement. On the schedule tab, under the
'Program rerun behavior' option, select 'Always rerun program' from the
drop-down box.
j. On the Interaction tab, give the user the option to run programs
independently of assignments
2. Advertise second.txt to run during the maintenance window.
a. Repeat the steps from task 1 with the following exceptions:
1.) On the program identification page, set the command line to be

'Notepad.exe second.txt'.
2.) On the Advertisement Schedule, set the advertisement time to

begin 5 minutes after the maintenance window on the all systems
collection is set to begin.
b. After the second advertisement has been created, open the Configuration
Manager Agent tool from Control panel.
c. Run a Machine Policy Retrieval & Evaluation Cycle from the Actions tab.
3. Review the Configuration Manager Client logs to determine why

advertisements ran or did not run
a. Run trace32 on the Site server.
78 FINAL
b. Open the execmgr.log from E:\SMS_CCM\Logs.
c. Highlight the string 'first' and review each attempt to run the program on
the site server.
d. Review the ServiceWindowManager.log to show existing service windows.
4. Review the maintenance window settings in WMI
a. Open WBEMTest on the site server and connect to the namespace

'root/ccm/policy/machine/actualconfig'
b. Enumerate all classes and open the properties for CCM_ServiceWindow
c. Click the instances button and see that one instance of

CCM_ServiceWindow appears.
d. Get the properties of this instance and then click the 'show MOF' button to
see the schedule and ID for this window.
e. To read the schedule token, use the SchedCnv.exe utility from E:\Labfiles.
This tool was first distributed in the BackOffice 4.5 Resource Kit.
5. Review the maintenance window settings in SQL
a. Open SQL Server Management Studio and navigate to the site database.
b. Under Views, select dbo.v_ServiceWindow.
c. Right click and choose 'Open Table'. You should be able to see all the
configured windows
6. Review the report 'Maintenance Windows Available to a Particular Client'
a. Open the Configuration Manager Administrator console
b. Navigate to Reports and find the report 'Maintenance Windows Available

to a Particular Client'
c. Run this report and select the site server as the client to view maintenance
windows for.
FINAL 79
Exercise 6: Create an advertisement that will run outside of

a Maintenance Window
Scenario
This advertisement shows how an advertisement can be configured to run outside
maintenance windows. One advertisement will be configured to ignore maintenance
windows and the other one will not.
Tasks
1. Create an advertisement that ignores maintenance windows
a. Right click on the All Windows XP collection and select Distribute, then
Software.
file.

'Notepad.exe Third.txt'.
e. On the program properties tab, set the max run time to 10 minutes
g. On the Advertisement Schedule, set the advertisement time to begin in 15

minutes from the current time.
h. Assign the program and accept the default assignment time on the Assign
program page.
i. Check the box for 'ignore maintenance windows when running programs'.
Click finish.
j. Open the properties of the advertisement. On the schedule tab, under the
drop-down box.
k. On the Interaction tab, give the user the option to run programs
2. Create an advertisement that respects maintenance windows
a. Repeat the steps from task 1 with the following exceptions:
80 FINAL
1.) On the program identification page, set the command line to be

'Notepad.exe Fourth.txt'.
2.) On the Advertisement Schedule, set the advertisement time to

begin 5 minutes after the advertisement for 'third.txt'.
3.) Don't check the box to 'ignore maintenance windows when running
programs'.
b. After the second advertisement has been created, open the Configuration
Manager Agent tool on the XP client's control panel.
c. Run a Machine Policy Retrieval & Evaluation Cycle from the Actions tab.
1. Troubleshoot advertisements that do not run at the appropriate times.
a. If either advertisement did not run when expected, or ran when it was not
expected, review the Execmgr.log for clues.
b. Review the Maintenance window settings for the XP Client using WMI, SQL
and Config Manager reporting for additional clues.
Exercise 7: Create an advertisement that runs past the

Maintenance window
Scenario
This exercise will show the behavior of an advertisement that runs past the end of a
maintenance window.
Tasks
1. Advertise fifth.txt to run before the maintenance window.
a. Right click on the All Systems collection and select Distribute, then
Software.
file.

'Notepad.exe fifth.txt'.
e. On the program properties tab, leave the max run time to the default value
of 120 minutes
FINAL 81
g. On the Advertisement Schedule, set the advertisement time to begin 10

minutes from the current time.
h. Assign the program and take all the defaults on the Assign program page
for now. Click Finish.
i. Open the properties of the advertisement. On the schedule tab, under the
drop-down box.
j. On the Interaction tab, give the user the option to run programs
2. Troubleshoot why advertisement did or did not run as expected.
a. If the advertisement did not run when expected, or ran when it was not
expected, review the Execmgr.log for clues.
b. Review the Maintenance window settings for the XP Client using WMI, SQL
and Config Manager reporting for additional clues.
c. Check for status messages related to this advertisement in the

Configuration Manager Administrator's console.
82 FINAL
Lab Manual Instructor Notes
Instructor Notes
This section provides additional information to assist instructors in course delivery.
Instructor notes are numbered consecutively throughout the document.
Answers to Lab Exercises

Lab 1: Upgrading Existing SMS 2003 Site
Exercise 1. Task 1. Step 4 - Yes
Exercise 1. Task 1. Step 5 - There were 4 classes and 14 attributes added to

Active Directory.
Exercise 3. Task 2. Step 10a - Yes, the local site server (SCCMSRV1), the domain
controller (SCCMSRV1) and the Windows XP Professional client (Configuration
ManagerClient) should have been discovered.
Exercise 3. Task 2. Step 10b - Yes, all are listed as being assigned to the site.
Exercise 3. Task 2. Step 13A - Configuration ManagerSite, which is the AD site

you added as a boundary for the site.
Lab 4: Deploying Software Updates

Exercise 1. Task 2. Step 2 - Update Services and WsusCertServer
FINAL 83

Supporting SCCM 2007 Lab Manual

Uploaded by

Copyright:

Available Formats

Supporting SCCM 2007 Lab Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Supporting SCCM 2007 Lab Manual

Uploaded by

Copyright:

Available Formats

Supporting System Center Configuration

Published: August 13, 2007

© 2007 Microsoft Corporation. All rights reserved.

Lab 1: Upgrade an Existing SMS 2003 site

Estimated time to complete this lab: 2 hours

Before You Begin

■ Complete Modules 1 and 2

■ Configure your computer(s) as described in Setting Up Your Lab

What You Will Learn

■ Extend the Active Directory schema for SCCM specific data.

■ Upgrade an Existing Configuration Manager 2003 server

■ View status message activity related to site server installation.

■ Configure basic SCCM options

■ Discover computer resources from Active Directory.

■ Install an SCCM 2007 Client on the Windows XP Professional client.

■ Install a Reporting Point

Setting Up Your Lab Environment

□ Server is configured as a Domain Controller and has the following software

● IIS with BITS and WebDAV enabled

● SQL 2005 SP2

● .NET Framework 2.0

● Working Configuration Manager 2003 Primary Server installed and

● Configuration Manager Toolkit 2

□ .NET Framework 2.0

□ Configuration Manager Toolkit 2

Note: These prerequisites are already installed in the VM

■ Administrative username and password for Server and client

□ ADRestore Password: !LS1setup

■ Site, Server and Client information

□ Server name: SCCMSRV1

□ Client name: SCCMXP01

■ Normal username and password

Additional Software located on the 2nd drive in a LABS folder:

■ SCCM 2007 RC1

Exercise 1: Installing Microsoft SCCM 2007

2. Under Prepare select Run the Prerequisite checker.

5. Double-click splash.hta and under Install click on Configuration Manager

6. At the Welcome screen click Next.

8. Accept the license terms and click Next.

10. On the Product Key screen click Next.

14. When setup completes click Finish.

View Status Messages

2. The Microsoft Management Console (MMC) starts, and then the

5. Verify that each site system has a status of OK.

7. In the Results pane, click Configuration

11. Click OK.

12. The Configuration Manager Status Message Viewer window appears.

13. On the File menu, click Exit.

15. Display the status messages for Configuration

18. Display the status messages for Configuration

20. Display the status messages for Configuration

Exercise 2: Preparing Active Directory for SCCM 2007

Steps to take before beginning this lab:

2. Open C:\Extadsch.log using Trace32. This file is created by the Extadsch.exe

3. Was the schema extension process successful?

Create an Active Directory site

2. The Active Directory Sites and Services window appears.

4. On the Action menu, click New Site.

5. The New Object – Site dialog box appears.

6. In the Name box, type Configuration ManagerSite