System Center Configuration Manager 2007

Reviewers Guide
Microsoft Corporation Published: 10/2/2007 Updated: 11/2/2007

Executive Summary

The intent of this whitepaper is to provide a framework for the evaluation of System Center Configuration Manager 2007. System Center Configuration Manager—previously known as Systems Management Server— represents a tremendous advancement over its well-regarded predecessor, now providing the control necessary to more effectively manage change in today's dynamic IT infrastructures. Manage the full deployment and update lifecycle with streamlined, policy-based automation; with enhanced insight into, and control over, assets and systems compliance; and with optimization for Windows—particularly Windows Server 2008 and Windows Vista—and extensibility to customized administration experiences and third-party applications.

Microsoft System Center

1

© 2006 Microsoft Corporation. All rights reserved. This document is developed prior to the product‘s release to manufacturing, and as such, we cannot guarantee that all details included herein will be exactly as what is found in the shipping product. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. 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 information represents the product at the time this document was printed and should be used for planning purposes only. Information subject to change at any time without prior notice. wThis whitepaper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft, Active Directory, Windows, the Windows logo, and Windows Server System are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.

Microsoft System Center

2

Contents
Executive Summary ................................................................................................................................................................ 1 Navigation ................................................................................................................................................................................ 7 Windows Vista .........................................................................................................................................................................................7 Section 1: Exercise 5 – Upgrading Clients to Configuration Manager ........................................................................7 Section 2: Exercise 3 – Installing an SCCM Client .................................................................................................................7 Section 2: Exercise 3 – Reporting Configuration Manager 2007 Client Deployment Status ..............................7 Section 5: Exercise 2 - Creating a Capture Media Task Sequence ................................................................................7 Section 5: Exercise 3 - Creating an Image of the Windows Vista Reference Computer .......................................7 Section 5: Exercise 4 - Deploying an OS Image Using Configuration Manager 2007 ..........................................7 Section 5: Exercise 5 - Installing the Image at the Target Client Computer .............................................................7 Section 5: Exercise 6 - Viewing Status for the Image Deployment ...............................................................................7 Section 6: Exercise 4 - Distributing Software Updates Using Configuration Manager Software Update Management ......................................................................................................................................................................................7 Section 7: Exercise 5 - Software Update Deployment Options ......................................................................................7 The Datacenter ........................................................................................................................................................................................7 Section 4: Exercise 1 - Configuring Maintenance Windows on Collections ..............................................................8 Section 4: Exercise 2 - Implementing the Maintenance Windows on the Configuration Manager Clients 8 Section 4: Exercise 3 - Distributing Software to the Configuration Manager Clients............................................8 Section 6: Exercise 4 - Distributing Software Updates Using Configuration Manager Software Update Management ......................................................................................................................................................................................8 Section 7: Exercise 5 - Software Update Deployment Options ......................................................................................8 Security .......................................................................................................................................................................................................8 Section 2: Exercise 1 - Preparing Active Directory for SCCM 2007 Integration .......................................................8 Section 4: Exercise 1 - Configuring Maintenance Windows on Collections ..............................................................8 Section 6: Exercise 1 - Configuring Configuration Manager Integration with WSUS ...........................................8 Section 6: Exercise 2 - Generating Update Status on the Configuration Manager Client ...................................8 Section 6: Exercise 3 - Generating Software Update Compliance Reports ................................................................8 Section 6: Exercise 4 - Distributing Software Updates Using Configuration Manager Software Update Management ......................................................................................................................................................................................8 Section7: Exercise 1 - Installing the System Center Updates Publisher.......................................................................8 Section7: Exercise 2 - Synchronizing Custom Updates with Configuration Manager...........................................8 Section 7: Exercise 3 - Generating Status of Custom Updates on the Configuration Manager Client...........8 Section 7: Exercise 4 - Generating Software Update Compliance Reports for Custom Updates ......................8 Section 7: Exercise 5 - Software Update Deployment Options ......................................................................................8 Section 8: Exercise 1 - Creating and Importing Configuration Items ..........................................................................8 Section 8: Exercise 2 - Creating Configuration Baselines ..................................................................................................8 Section 8: Exercise 3 - Scanning Configuration Manager Clients for Compliance .................................................8 Asset Intelligence ....................................................................................................................................................................................8

Microsoft System Center

3

.................................................................................................................................................................................................................... 22 Microsoft System Center 4 ............9 Section 2: Exercise 4 ......................... 15 Configuring SQL Server Site Database Replication in Configuration Manager 2007 .......................................................................................................... 20 Objectives .............................................................. 18 Dual Boot Computers ............................................................................................................................................................................... 18 Virtual Machines ....................................... 16 Support for Windows Server Clustering .............................................................................................. 17 Remote Assistance Console Sessions..................................... 10 Configuration Manager Supported Configurations ........................................................ 20 Exercise 1 Identifying an SMS 2003 stallation ............................................................................................................. 17 Computers in Workgroups .......................................................................................... 17 Removable Disk Drive Support ............................................................................................................................................................................................................................................................... 13 Unsupported Client Platforms ............................................................................................. 16 Multi-Site Clients .......... 12 Configuration Manager 2007 Site Server System Requirements ................................................................................................................................................................................................................................................................................................................. 18 Section 1 : Upgrading SMS 2003 SP2 to System Center Configuration Manager 2007 .......................................................................................... 13 Site System Hardware Requirements ...................................................................... 18 Fast User Switching ....................................9 Section 2: Exercise 3 – Installing an SCCM 2007 Client .......................................................................................................................................................................................................... 16 Storage Area Network Support .................................................................................................................................................................................................................................................Configuring Maintenance Windows on Collections ................................................................... 10 The Microsoft Virtual Hard Disk Program .............................................................................................................................................................................................................................................................................................................................................................................................................................. 15 Unsupported Site Server Platforms ...............................................9 Section 5: Exercise 1 ...................................................................................................................................................................................................9 Section 4: Exercise 1 ....9 Section 4: Exercise 2 ..Configuring a Branch Distribution Point ...............................Section 9: Exercise 1 Editing the SMS_Def...............................................................................................................................................................mof ...................................................................... 16 Single Instance Storage Support ......................................................................................................................... 11 Supported Client Platforms .................................................. 16 Active Directory Schema Extensions ......................................................9 Section 9: Exercise 2 Viewing and Running Reports ............................... 18 Interoperability Between Configuration Manager and SMS 2003 Sites........................................Distributing Software to the Configuration Manager Client.............................................................................................................................................................9 Branch and Remote Management ..................................................................................................................................Reporting Configuration Manager 2007 Client Deployment Status ..........................................9 Introduction ................................... 12 SMS Client Embedded Operating System Support ............................................................................. 20 Prerequisites ................ 10 Evaluating Configuration Manager 2007 .... 16 Support for Specialized Storage Technology ................................................................... 11 Mobile Device Client ................................................................................................................................................................................................................................................. 10 Client Hardware Requirements ................................................................................................................................................. 13 Supported Site System Platforms............................................................................................................................................................................................................................................................................................................................................................................

.120 Exercise 3 Generating Software Update Compliance Reports .................................................................... 60 Section 4: Implementing Maintenance Windows for Software Distribution in System Center Configuration Manager 2007.................. 30 Exercise 5 Upgrading Clients to Configuration Manager ..................110 Section 6: Managing Microsoft Updates with System Center Configuration Manager 2007 .................................................................................................................................................................................. 54 Section 3: Implementing Branch Distribution Points in System Center Configuration Manager 2007............................................................................................................................................................................................100 Exercise 4 Deploying an OS Image Using Configuration Manager 2007..................................................................................................102 Exercise 5 Installing the Image at the Target Client Computer ..... 47 Exercise 4 Reporting Configuration Manager 2007 Client Deployment Status ................................... 38 Exercise 2 Installing Microsoft Configuration Manager 2007..................... 58 Exercise 2 Distributing Software to the Configuration Manager Client .................................................................................. 112 Objectives ...........................................................................................................122 Exercise 4 Distributing Software Updates Using Configuration Manager Software Update Management Microsoft System Center 5 ....... 77 Exercise 3 Distributing Software to the Configuration Manager Clients ..................................... 27 Exercise 4 Identifying a Configuration Manager Installation ................................................................................................................................................. 42 Exercise 3 Installing an SCCM 2007 Client ....................................................................................................................................................................................................................... 56 Exercise 1 Configuring a Branch Distribution Point .................................................................... 89 Exercise 1 Preparing the Environment for Configuration Manager OSD ...........................................................112 Exercise 1 Configuring Configuration Manager Integration with WSUS ................................................................................................................ 89 Objectives ................................................................................................... 31 Section 2: Deploying System Center Configuration Manager 2007 ..................................................................................................... 71 Exercise 1 Configuring Maintenance Windows on Collections ...... 56 Objectives ......................114 Exercise 2 Generating Update Status on the Configuration Manager Client .......................................................................................................................................................................... 73 Exercise 2 Implementing the Maintenance Windows on the Configuration Manager Clients .................................................................112 Before You Begin ................................... 38 Exercise 1 Preparing Active Directory for SCCM 2007 Integration ....... 79 Section 5: Deploying Operating System Images Using System Center Configuration Manager 2007 ......................................................................................................................................... 38 Prerequisites ................................................................................................................................................... 38 Objectives ...... 71 Prerequisites ...................................... 22 Exercise 3 Upgrading SMS 2003 SP2 to Configuration Manager.................. 71 Objectives .............................................................................................................................................................................................................................................................................................................................................................................................................................................................Exercise 2 Preparing to Upgrade SMS 2003 SP2 to Configuration Manager ............... 98 Exercise 3 Creating an Image of the Windows Vista Reference Computer ................................................................................................................................................................. 89 Before You Begin ......................................................................................................................108 Exercise 6 Viewing Status for the Image Deployment ......................................................................................................................................................................................................................... 91 Exercise 2 Creating a Capture Media Task Sequence........................................................ 56 Prerequisites .................................................................................................................................................................................................................................................................................................................................................................................................................................................

...............................................................................................................................................................................................................................................................................135 Exercise 2 Synchronizing Custom Updates with Configuration Manager ................................172 Enabling the Asset Intelligence Reporting Classes ...........................................................................................................................................................................136 Exercise 3 Generating Status of Custom Updates on the Configuration Manager Client .....................171 What‘s new ..............................................................130 Section 7: Managing Custom Application Updates using Systems Center Configuration Manager 2007 ...................................................................................................................................................................................................................171 Additional reports ....................................................................................................................................................................................................................................................................159 Exercise 2 Creating Configuration Baselines ..157 Prerequisites .................................................................. 171 Overview ........................... 133 Objectives .........................................................................................................................................................................................................................................................................................................................................mof ....................................................................................................133 Before You Begin .................................................133 Exercise 1 Installing the System Center Updates Publisher ..............................................167 Section 9: Implementing Asset Intelligence in System Center Configuration Manager 2007 ...........124 Exercise 5 Validating Current Software Update Compliance .....................................................................176 Exercise 2 Viewing and Running Reports ............157 Exercise 1 Creating and Importing Configuration Items ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................171 Performance enhancements .....................................................147 Exercise 5 Software Update Deployment Options ..........................................................172 Exercise 1 Editing the SMS_Def...............................................177 Microsoft System Center 6 ...........................................................176 Additional Resources ..........................................171 Data enhancements .............................................................................................................................145 Exercise 4 Generating Software Update Compliance Reports for Custom Updates ....................................................................................................................................................................................................................................................................................................................................................................................................................175 Asset Intelligence Reports ......................................................171 Setup experience ................................................................................................. 157 Objectives ..................................................154 Section 8: Implementing Desired Configuration Management in System Center Configuration Manager 2007 ...........................................................174 Estimating network Impact based on Reporting Classes ................................150 Exercise 6 Validating Current Software Update Compliance ........................................................................................................................................................................................................164 Exercise 3 Scanning Configuration Manager Clients for Compliance .............................................................................................................................................................................................................................172 A Description of the Different Classes ..................................................................

to deployment. Configuration Manager client deployment. workload requirements and geographic challenges from one console. Windows Operating System deployment. From planning and building servers.Navigation Within this evaluation kit you will find comprehensive evaluation guidance for System Center Configuration Manager 2007. In order to better suit your interests we have provided here for you a navigation checklist for some specific technology areas.Creating a Capture Media Task Sequence Section 5: Exercise 3 . build and provisioning.Creating an Image of the Windows Vista Reference Computer Section 5: Exercise 4 . collect and distribute the drivers your hardware needs to be running at peak performance. Configuration Manager drives more value to your datacenter with abilities to manage your desired configurations.Installing the Image at the Target Client Computer Section 5: Exercise 6 . System Center Configuration Manager 2007 in your Datacenter helps you gain automation. increasing the security of your business. as well as Desired Configuration Management.Distributing Software Updates Using Configuration Manager Software Update Management Section 7: Exercise 5 . to configuration management once in production. and SLA performance success by managing your business needs. tools to maximize your SLA agreements scheduling activities to minimize the business impact. There have been some significant features developed specifically with a Datacenter focus. Microsoft System Center 7 . We would like you to view the power of Configuration Manager for the desktop by evaluating a few capabilities. Configuration Manager drives return on your Windows desktop investment by enabling a secure. and the Driver Catalog brings together the right tools you need to import. Windows Vista System Center Configuration Manager 2007 brings incredible value to your desktop estate. We hope this assists you in your evaluation of Configuration Manager. Operating System Deployment is a major focus in datacenters today. software updates and when change is required.Software Update Deployment Options The Datacenter System Center Configuration Manager 2007 is not just for desktops. corporate and regulatory compliancy requirements. The below exercises will demonstrate for you the features specific to desktop management and security. Once in production. manage. Software distribution and Software Update Management are key areas to reducing the cost of your desktops.Viewing Status for the Image Deployment Section 6: Exercise 4 . configuration control.Deploying an OS Image Using Configuration Manager 2007 Section 5: Exercise 5 . Managing drivers is another challenge. and we would welcome your comments. to deployment Operating System including provisioning roles and specific capabilities. and supporting the demands for flexibility and mobility in an ever increasing wireless and mobile network. Section 1: Exercise 5 – Upgrading Clients to Configuration Manager Section 2: Exercise 3 – Installing an SCCM Client Section 2: Exercise 3 – Reporting Configuration Manager 2007 Client Deployment Status Section 5: Exercise 2 . We would like to highlight for you the abilities Configuration Manager has for your datacenter with some capability demonstrations highlighted below. For each of these modules please follow the guidance for more specific sections and exercises. significantly reduces the costs of server deployment. well managed infrastructure fabric to support your increasingly mobile client environment. From planning. and simplifying the management of the steps and tasks associated with server design. to managing your servers and workloads through security. Each of these modules is designed to assist you in your evaluation of a more specific feature that may cross multiple capabilities within the product. Hardware and Software Inventory.

Configuring Maintenance Windows on Collections Section 4: Exercise 2 .Software Update Deployment Options Section 8: Exercise 1 . Whether it be deploying updates with an operating system activity.Scanning Configuration Manager Clients for Compliance Asset Intelligence Information technology expenditures comprise an increasing portion of IT budgets—IT assets can often account for more than half of an enterprise‘s total asset base.Creating and Importing Configuration Items Section 8: Exercise 2 . Using certificate relationships. Configuration Manager provides you this capability. so for those critical updates you can limit network connectivity until Health Validation is successful. branches and remote or internet based connections. Security is also about how processes occur.Distributing Software to the Configuration Manager Clients Section 6: Exercise 4 .Generating Update Status on the Configuration Manager Clien Section 6: Exercise 3 . Configuration Manager weaves seamless security integration across every aspect of its capabilities. With the changing nature of today‘s technology Microsoft System Center 8 . Section 2: Exercise 1 .Software Update Deployment Options Security Security is a large focus for the business of any size.Preparing Active Directory for SCCM 2007 Integration Section 4: Exercise 1 . or delivering critical patches in an explicitly targeted.Configuring Configuration Manager Integration with WSUS Section 6: Exercise 2 .Distributing Software Updates Using Configuration Manager Software Update Management Section7: Exercise 1 .Configuring Maintenance Windows on Collections Section 6: Exercise 1 .Generating Status of Custom Updates on the Configuration Manager Client Section 7: Exercise 4 . encryption of data transfer and storage.Creating Configuration Baselines Section 8: Exercise 3 .Synchronizing Custom Updates with Configuration Manager Section 7: Exercise 3 . and System Center Configuration Manager 2007 brings security and control to all aspects of the modern organization.Implementing the Maintenance Windows on the Configuration Manager Clients Section 4: Exercise 3 .Generating Software Update Compliance Reports for Custom Updates Section 7: Exercise 5 .Section 4: Exercise 1 . scheduled fashion. From the desktop to the datacenter.Distributing Software Updates Using Configuration Manager Software Update Management Section 7: Exercise 5 . as well as supporting the broad scenarios your end users encounter such as internet connectivity or remote access points.Installing the System Center Updates Publisher Section7: Exercise 2 . across desktops. introducing network perimeter health validation. helping you define process automation. Configuration Manager gives you the ability to blanket your organization in a controlled manner with only the updates you require. But security is not just about delivering updates. Below we highlight for you some examples of how Configuration Manager improves security for your business. System Center Configuration Manager supports Network Access Protection in Windows Server 2008.Generating Software Update Compliance Reports Section 6: Exercise 4 . This release of Software Update Management supports all of the categories from Microsoft. laptops and devices are important to you. Through all of this your business must remain productive. flexible and efficient – while driving your security to new levels. as well as providing the tools to deliver updates of 3rd party and Line of Business applications to those in office locations. In the following exercises we will demonstrate these capabilities. configuration baselines and update strategies that meet your business needs. and show you how System Center Configuration Manager 2007 is the best choice for managing your business needs.

Reporting Configuration Manager 2007 Client Deployment Status Section 4: Exercise 1 . This drastically reduces the need for remote infrastructure to provide management services to clients. companies can make informed decisions about their IT assets. enabling the ability to extend the secure well managed environment of Configuration Manager to geographically distributed network locations.Configuring Maintenance Windows on Collections Microsoft System Center 9 . it is impossible for enterprises to determine if IT is providing value and to meet financial. and Configuration Manager answers this challenge by using readily available internet connectivity for management services. As you navigate through these exercises.Distributing Software to the Configuration Manager Client Section 5: Exercise 1 . With Configuration Manager 2007. you will be shown how to configure the Asset Intelligence infrastructure as well as learn how to access the wealth of reports available. regulatory and license compliance requirements. improve IT operations and mitigate compliance risks. Configuration Manager now delivers management services to the branch environment by enabling the ability to dedicate non server class systems in a branch as part of the distribution infrastructure (such as a desktop class PC). as well as mobile workforces. We would like to demonstrate for you the abilities of the Asset Intelligence feature in System Center Configuration Manager 2007 with some exercises on configuring and reporting. providing rich reports that IT administrators can use to optimize hardware and software usage.mof Section 9: Exercise 2 Viewing and Running Reports Branch and Remote Management System Center Configuration Manager 2007 has extended scenario support for today‘s modern business beyond the corporate network. and where they are. Section 9: Exercise 1 Editing the SMS_Def. Section 2: Exercise 3 – Installing an SCCM 2007 Client Section 2: Exercise 4 .Configuring a Branch Distribution Point Section 4: Exercise 2 . System Center Configuration Manager 2007 includes hardware and software inventory and software metering capabilities that help IT organizations understand exactly what hardware and software assets they have. Infrastructure improvements within Configuration Manager now provide depth and breadth support to both low bandwidth branch environments. The trend of laptop purchase and remote working increases the importance of being well managed.and the complexity of network environments. We would like to demonstrate this to you by walking through a collection of exercises that show these capabilities. Configuration Manager also has improved the support for the mobile workforce. enterprises find it difficult to track the IT assets they own. who is using them. by providing support for Internet Based Client Management services. Without an accurate record of their IT assets. Asset Intelligence translates the inventory data into information. This information is paramount to organizations planning their Windows Vista upgrade strategy.

or operating systems. please visit the new and improved Technet Technical library. To better assist your review the structure of this guide has been based on some assumptions for the evaluation environment.aspx Evaluating Configuration Manager 2007 The evaluation of a robust. simply reviewing an installation of the product may not satisfy your needs.microsoft. updates. comprehensive management toolset such as Configuration manager requires infrastructure to be managed. If you have an installed environment ready for evaluation.com/en-us/configmgr/default. in addition to reporting. and provides more seamless manageability.microsoft. this guide will still be of use. operating systems. The link for this resource is: http://technet. applications. System Center is represented in this program.com/en-us/configmgr/bb736730. Using the power of virtualization. This can be found at the following link: o http://technet. or policy. In order to provide a comprehensive review of Configuration Manager. For additional support and guidance on the deployment in production for your organization.Introduction Welcome to the System Center Configuration Manager 2007 Reviewer Guide. Due to the testing and potential broadcast or delivery of software updates. however exercises such as Configuration Manager Upgrade or Configuration Manager Install will not need to be done.aspx?familyid=469af3b8-849d-4400-bded9024c3db759f&displaylang=en Configuration Manager Supported Configurations Microsoft System Center 10 . and is not intended for production infrastructure. Your test environment has Active Directory installed You have appropriate credentials for your test environment. The Microsoft VHD format is a common virtualization file format that provides a uniform product support system. you can now quickly evaluate Microsoft and partner solutions through a series of pre-configured Virtual Hard Disks (VHDs). you may want to perform actual deployments of software.com/downloads/details. http://www. reliability and cost-efficiency for customers. The intent of this paper is to guide you through an evaluation of the product. the VHD program is an option where you can download a time-bomb version of installed and configured System Center Configuration Manager 2007.    The Microsoft Virtual Hard Disk Program As an alternative to preparing your own server installation.aspx You have a configured physical or virtual system that meets the minimum requirements of Configuration Manager. These are referred to as ‗Exercise 0‘ in each section. where all product documentation and guidance is located. security. discovery or broadcasting of network traffic. including:  Setup  Configuration  Feature evaluation The intent of this reviewer‘s guide is to preview the product in a non production environment. it is not recommended to utilize this guidance for any real world deployment. In other words. You can download the VHDs and evaluate them for free in your own environment without the need for dedicated servers or complex installations. and System Center Configuration Manager is available at the following link.  You have downloaded the evaluation version of System Center Configuration Manager 2007.microsoft.

com/fwlink/?LinkId=31975.microsoft. or comparable processor recommended) 128 MB minimum (256 MB or more recommended. the temporary program download folder on clients is preconfigured at client installation to automatically increase to 5GB if necessary and if 5 GB or more is available. visit the Lifecycle Supported Service Packs Web site at http://go. visit the Microsoft Support Lifecycle Support Policy FAQ Web site at http://go. For information about device client requirements. 384 MB required when using operating system deployment) 350 MB minimum for a new installation. Hardware Component Processor RAM Free Disk Space Requirement 233 MHz minimum (300 MHz or faster Intel Pentium/Celeron family. Client Hardware Requirements The following table lists the minimum and recommended hardware requirements for Configuration Manager 2007 computer clients. The following table is a breakdown of the operating system support in System Center Configuration Manager 2007.).Configuration Manager 2007 introduces changes to supported Microsoft Windows client system requirements from previous versions of Systems Management Server. Service Pack 1 Windows Server 2003 Standard Edition Service Pack 1 Windows Server 2003 Enterprise Edition Service Pack 1 Windows Server 2003 Datacenter Edition1 Service Pack 1. To find the support timelines for your product. 265 MB minimum to upgrade an existing client (by default. Operating System Windows 2000 Professional Service Pack 4 Windows XP Professional Service Pack 2 Windows XP Professional for 64-bit Systems Windows Vista Business Edition Windows Vista Enterprise Edition Windows Vista Ultimate Edition Windows 2000 Server Service Pack 4 Windows 2000 Advanced Server Service Pack 4 Windows 2000 Datacenter1 Service Pack 4 Windows Server 2003 Web Edition. For additional information about Microsoft‘s support lifecycle policy. The following table lists the minimum Configuration Manager 2007 supported client operating systems. see Mobile Device Client later in this section. and in some cases the immediately preceding service pack.com/fwlink/?LinkId=31976. so not immediately needed.microsoft.   Note Microsoft provides support on the current service pack. 2 Windows Server 2003 R2 Standard Edition x86 Y Y N Y Y Y Y Y Y Y Y Y Y Y x64 N N Y Y Y Y N N N N Y Y Y Y IA64 N N N N N N N N N N Y Y Y Y Microsoft System Center 11 . This space is not used until required for a download. Supported Client Platforms Supported Configuration Manager 2007 client installation requires at least Windows 2000 Professional Service Pack 4.

com/en-us/library/bb632496. such as operating system deployment. Mobile Device Client The Mobile Device Client requires 0. For more information about managing devices with Configuration Manager. Note Configuration Manager 2007 support for x64 and IA64 systems is through 32-bit code running on 64-bit operating systems. Hotfix support is not offered for Windows Datacenter Server edition specific issues. In addition. for Configuration Manager 2007.0 and Windows Mobile 5. SMS Client Embedded Operating System Support Configuration Manager 2007 does not support a specific client for embedded platforms within a Configuration Manager 2007 hierarchy other than a Microsoft Systems Management Server (SMS) 2003 embedded client assigned to a child SMS 2003 primary site.0 Windows Mobile 5. mobile device management logging on the mobile device can require 256 KB of storage space.78 MB of storage space to install. The mobile device client is supported on the following platforms:  Windows Mobile for Pocket PC 2003  Windows Mobile for Pocket PC 2003 Second Edition  Windows Mobile for Pocket PC Phone Edition 2003  Windows Mobile for Pocket PC Phone Edition 2003 Second Edition  Windows Mobile Smartphone 2003 Note Password management is not supported for Windows Mobile Smartphone 2003.aspx).com/fwlink/?LinkId=80392).microsoft. but not certified.0 Smartphone Windows CE 4.microsoft. see Overview of Mobile Device Management (http://technet.Windows Server 2003 R2 Enterprise Edition Y Y Y Windows Embedded for Point of Service (WEPOS) Y N N Windows Fundamentals for Legacy PCs (WinFLP) Y N N Windows XP Embedded SP2 Y N N Windows XP Tablet PC SP2 Y N N 1Datacenter releases are supported. For more information. Microsoft System Center 12 .0 (ARM and x86 processors) Windows Mobile 6 Standard Windows Mobile 6 Professional Windows Mobile 6 Classic Password management on Windows Mobile for Pocket PC 5.0.0 Smartphone requires the Messaging and Security Feature Pack (MSPF). see the Windows Mobile Messaging and Security Feature Pack web page (http://go. are not supported for the mobile device client. Some Configuration Manager 2007 client features.2 (ARM processor only) Windows CE 5. Windows Mobile for Pocket PC Phone Edition 5.         Note Windows Mobile for Pocket PC 5.0 Windows Mobile for Pocket PC Phone Edition 5.

and in some cases the immediately preceding service pack. for roles other than the branch distribution point and Configuration Manager console. Hardware Component Processor RAM Free Disk Space Requirement 733 MHz Pentium III minimum (2.Configuration Manager 2007 introduces changes to supported site system requirements from previous versions. The following table lists the minimum operating systems required to support the various Configuration Manager 2007 site system roles. Supported Site System Platforms Microsoft System Center 13 .microsoft. require at least Windows Server 2003 Service Pack 1. Configuration Manager 2007 does not support site system role installation on servers running Windows 2000 Server or Windows 2003 Server with no service pack installed. visit the Lifecycle Supported Service Packs Web site at http://go. For additional information about Microsoft‘s support lifecycle policy.com/fwlink/?LinkId=31975. Note Microsoft provides support on the current service pack.microsoft.com/fwlink/?LinkId=31976. Site System Hardware Requirements The following table lists the minimum and recommended hardware requirements for Configuration Manager 2007 site systems. visit the Microsoft Support Lifecycle Support Policy FAQ Web site at http://go.0 GHz or faster recommended) 256 MB minimum (1024 MB or more recommended) 5 GB minimum (15 GB or more free recommended if using operating system deployment) Configuration Manager 2007 Site Server System Requirements Supported Configuration Manager 2007 site system role installation. To find the support timelines for your product.

Operating System Primary Site Server Secondary Site Server Management Point State Migration Point Distribution Point Reporting Point Server Locator Point Site Database Server Software Update Point Fallback status point PXE service point Configuration Manager console Windows XP Professional Service Pack 2 Windows XP Professional for 64-bit Systems Windows Vista Business Edition Windows Vista Enterprise Edition Windows Vista Ultimate Edition Windows Server 2003 Web Edition Service Pack 1 and 2 Windows Server 2003 Standard Edition Service Pack 1 and 2 Windows Server 2003 Enterprise Edition Service Pack 1 and 2 Windows Server 2003 Standard Edition Service Pack 1 and 2 64 bit N N N N Y1 N N N N N N Y N N N N Y1 N N N N N N Y N N N N Y1 N N N N N N Y N N N N Y1 N N N N N N Y N N N N Y1 N N N N N N Y N N N N Y N N N N N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Microsoft System Center 14 .

Unsupported Client Platforms The Configuration Manager client is not supported on any operating system prior to Windows 2000 Service Pack 4. Installing the Configuration Manager client is explicitly not supported on the following operating system versions:  Windows 95  Windows 98  Windows Millennium Edition  Windows XP Media Center Edition  Windows XP Starter Edition  Windows XP Home Edition  Windows XP Professional.0  Windows 2000 Server. Service Pack 3 and earlier  Windows 2003 Server.Windows Server 2003 Enterprise Edition Service Pack 1 and 2 64 bit Windows Server 2003 Datacenter Edition Service Pack 1 and 2 Windows Server 2003 Storage Server Edition Service Pack 1 and 2 Windows Server 2003 R2 Standard Edition Windows Server 2003 R2 Enterprise Edition Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N Y N N N N N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 1Only the branch distribution point role is supported for this operating system Note Configuration Manager 2007 support for IA64 systems is limited to the remote SQL server role. with less than Service Pack 2 applied  Windows Vista Starter Edition  Windows Vista Home Basic Edition  Windows Vista Home Premium Edition  Windows NT Workstation 4. with no service pack installed  Windows CE 3.0  Windows NT Server 4.0  Windows Mobile Pocket PC 2002  Windows Mobile SmartPhone 2002 Unsupported Site Server Platforms Microsoft System Center 15 .

but they are not required.com/fwlink/?LinkId=66170. Configuration Manager 2007 clients can only be assigned and report to one site. but they could each use their own logical partition on a physical partition of a shared storage device. Configuration Manager 2007 is designed to work with any hardware that is certified on the Windows Hardware Compatibility List (HCL) for the version of the operating system that the Configuration Manager component is installed on. see the following related Knowledge Base articles:  For information about System Area Networks. see Knowledge Base article 260176 at http://go.  For information about the differences between System Area Networks and Storage Area Networks.microsoft. For more information about the use of System Area Networks and Configuration Manager 2007.aspx).vbs script. Configuring SQL Server Site Database Replication in Configuration Manager 2007 Active Directory Schema Extensions Multi-Site Clients Support for Windows Server Clustering Storage Area Network Support Using a Storage Area Network (SAN) is supported as long as a supported Windows server is attached directly to the volume hosted by the SAN. It is not supported to install Configuration Manager 2007 site servers or any other site system server role on a Windows Server cluster instance. For more information about extending the Active Directory schema for Configuration Manager 2007.Configuration Manager 2007 site server roles are not supported on any operating system prior to Windows Server 2003 Service Pack 1. When auto assignment is used to assign clients to a site during client installation.com/en-us/library/bb693697. see How to Extend the Active Directory Schema for Configuration Manager (http://technet.microsoft. site systems running on separate computers can‘t share a logical partition on any storage technology. you should update your schema extensions for Configuration Manager 2007. the mppublish. Configuration Manager 2007 site server roles require NTFS file systems so that directory and file permissions can be set.0 Server  Windows 2000 Server  Windows 2003 Server. For information about how to configure replication to support management points and server locator points. If you have extended your Active Directory schema for SMS 2003. Because Configuration Manager 2007 introduces new site database views and functions that are not replicated by the mppublish. see Support for Specialized Storage Technology Microsoft System Center 16 . was used to configure Microsoft SQL Server site database replication between the site database server and SQL Server site database replicas used to support management points and server locator points.com/en-us/library/bb633121. with no service pack installed In SMS 2003. It is supported to install the site database server site system role on a Windows server failover cluster instance.. it is not supported for configuring SQL Server site database replication in Configuration Manager 2007 sites. and more than one site has the same boundary configured. If boundaries overlap across multiple Configuration Manager 2007 or SMS 2003 site hierarchies. Configuration Manager 2007 site roles are explicitly not supported on the following operating system versions:  Windows NT 4.vbs script. the actual site assignment of a client cannot be predicted. Because Configuration Manager 2007 assumes it has complete ownership of a logical drive when it uses naming conventions.microsoft. Configuration Manager 2007 Active Directory schema extensions provide many benefits for Configuration Manager 2007 sites. Note Physical node computers of a Windows server cluster instance can be managed as Configuration Manager 2007 clients. supplied with the SMS 2003 installation files. clients might not get assigned to the correct site hierarchy or may not even get assigned to a site at all.aspx). see How to Configure SQL Server Site Database Replication (http://technet.

To support workgroup clients.com/fwlink/?LinkId=66171. it will be unable to download machine policies containing the Network Access Account information. or it can be specified in the CCMSetup. the following requirements must be met:  During client installation. Computers in Workgroups Important Until a workgroup client has been approved in the Configuration Manager console. downloaded as part of their machine policy. For information about Systems Management Server and Storage Area Networks. see Knowledge Base article 307813 at http://go. it must be registered and accessible to workgroup clients in either WINS or DNS.microsoft. Although workgroup computers can be Configuration Manager 2007 clients.  The Configuration Manager client must be installed from a local source on each client machine.microsoft. Single Instance Storage Support Configuring distribution point package and signature folders to be configured on a Single Instance Storage (SIS) enabled volume is not supported. there are inherent limitations in supporting workgroup computers:  Workgroup clients cannot reference Configuration Manager 2007 objects published to Active Directory Domain Services.exe installation command-line parameters. It is also not supported for a Configuration Manager 2007 client's cache to be configured on a SIS enabled volume. It is also supported for a client to be moved from a workgroup to a domain or from a domain to a workgroup.  Workgroup clients must be able to locate a server locator point for site assignment because they cannot query Active Directory Domain Services. Note Single Instance Storage (SIS) is a feature of the Microsoft® Windows® Storage Server 2003 R2 operating system. This requirement ensures a local source for repair and client update application will be available for the client. Configuration Manager 2007 Microsoft System Center 17 . the logged-on user must possess local administrator rights on the workgroup system. to access package source files on distribution points.com/fwlink/?LinkId=66172.  Active Directory system. Note It is not supported to change the domain membership. or computer name. The server locator point can be manually published in WINS. Removable Disk Drive Support It is not supported to install Configuration Manager 2007 site system or client components on a removable disk drive.  Workgroup clients use the Network Access Account. of a Configuration Manager 2007 site system after it is installed. Configuration Manager 2007 provides support for clients in workgroups. or user group discovery is not possible. Knowledge Base article 264135 at http://go.  Using a workgroup client as a branch distribution point is not supported.  User targeted advertisements are not possible. All site servers must be members of a Windows 2000 or Windows 2003 Active Directory domain. For workgroup clients to locate their default management point computer. The only account that Configuration Manager 2007 can use to perform activities that require local administrator privileges is the account of the user that is logged on to the computer.  The client push installation method is not supported for workgroup client installation. user.

A static Virtual PC image cannot be updated. Dual Boot Computers Configuration Manager 2007 cannot manage more than one operating system on a single computer. see Planning for the Configuration Manager Console (http://technet. except for simultaneous use of Configuration Manager Remote Tools. which is available in Windows XP editions not joined to a domain and Windows Vista editions. The Configuration Manager console can manage an SMS 2003 secondary site connected to a Configuration Manager 2007 primary parent site. Note Configuration Manager 2007 does not support Virtual PC or Virtual Server guests running on Macintosh. Configuration Manager 2007 supports all site server roles running as virtual machines only on Microsoft Virtual Server 2005 R2. No special consideration is given to virtual machines.aspx). Configuration Manager 2007 cannot manage Virtual PC or Virtual Server guest operating systems unless they are running. Remote Assistance Console Sessions Console sessions controlled by Remote Assistance are supported. If there is more than one operating system on a computer that must be managed.requires that branch distribution point computers be members of a domain.microsoft. For example. Virtual Machines Configuration Manager 2007 support for virtual machine guest operating systems includes all supported client operating systems running on Microsoft Virtual PC or Virtual Server 2005 R2. nor can inventory be collected using the Configuration Manager client on the host computer. tailor the discovery and installation methods used to ensure that the Configuration Manager client is installed only on the operating system that needs to be managed.com/en-us/library/bb693800. with the following limitations:  You cannot change the accounts or passwords of SMS 2003 secondary sites in the Configuration Manager console. Configuration Manager 2007 might not determine that an update needs to be re-applied to a virtual machine image if it is stopped and restarted without saving the version of the image to which the update was applied. You can use an SMS 2003 Administrator console snap-in to manage SMS 2003 primary sites on a computer that does not have the Configuration Manager console installed or you can install the Configuration Manager console on a computer that already has the SMS 2003 Administrator console installed on it. Invoking Remote Assistance from the Configuration Manager console requires that the Configuration Manager console computer and the client computer are running one of the following operating systems:  Windows XP SP2  Windows Server 2003 SP1 or later  Windows Server 2003 R2  Windows Vista (supported editions) Fast User Switching Fast User Switching. Note Fast User Switching is not supported for any non-supported client platform capable of Fast User Switching. There are planning considerations when hosting both consoles on the same computer that should be considered before installing a Configuration Manager 2007 console on a computer that already has the SMS 2003 Administrator console installed on it. The Configuration Manager console cannot be used to fully manage an SMS 2003 primary site. Interoperability Between Configuration Manager and SMS 2003 Sites Microsoft System Center 18 . such as Windows XP Home and Windows Vista Home editions. For more information about planning for Configuration Manager 2007 console installations. is supported in Configuration Manager 2007.

SMS 2003 clients can be assigned to a Configuration Manager 2007 site.  The site database can be installed on the default or a named instance of SQL 2005 and it is supported to move the site database back to a local installation of SQL 2005 installed on the site server computer if it has been moved off of the site server computer previously. Assigning Configuration Manager clients to SMS 2003 sites is not possible. Windows Vista Enterprise. ensure that Configuration Manager clients are not within the boundaries of an SMS 2003 site. Ensure that the boundaries defined for your Configuration Manager site are set properly.0 and SQL Server 2000 are no longer supported to host the site database. Changes in Support from SMS 2003  SQL Server 2005 Service Pack 2 is now required to host the site database. You cannot configure Active Directory Security Group Discovery on an SMS 2003 secondary site.You cannot create or configure RAS sender addresses on SMS 2003 secondary sites. SQL Server 7. and they will be fully interoperable.   Microsoft System Center 19 . When installing Configuration Manager clients using auto assignment. and Windows Vista Ultimate editions are now fully supported client operating systems.  Windows Vista Business.

Upgrade SMS 2003 Advanced Clients to Configuration Manager clients. Use Configuration Manager Setup to test the SMS 2003 site database upgrade procedure. Use the Configuration Manager Prerequisite Check program to validate the site is ready to be upgraded. Estimated time to complete this section: 75 minutes Microsoft System Center 20 . you will be able to:   Identify an SMS 2003 site. Upgrade SMS 2003 to Configuration Manager. one virtual computer should be running as a Microsoft Windows Server 2003® SP1 computer installed as an SMS 2003 SP2 primary site server <your Configuration Manager Server>. Prepare the SMS 2003 site for an upgrade to Configuration Manager.      Prerequisites Before working on this lab.Section 1 : Upgrading SMS 2003 SP2 to System Center Configuration Manager 2007 Objectives After completing this section. A second virtual computer is booted as a Windows XP Professional client installed as an Advanced Client in the SMS 2003 site <your XP Client>. Identify a Configuration Manager site.

The members of the All Systems collection appear in the details pane. 3. 9. and the current membership of the All Systems collection is displayed. click Refresh. In the details pane. Notice also that one of the instances is listed as being Obsolete and inactive. On the Start menu. expand Collections. expand Site Database. 2. which should be listed as an Obsolete client (scroll to the right in the details pane) and then on the Action menu.Note Complete this procedure from the primary site server computer only. and then click All Systems. The SMS Administrator Console window appears. In the console tree. This is the old reference of the client. and then click Update Collection Membership. Click OK. 4.  To update the collection membership 1. 8. 5. The collection membership is updated. click SMS Administrator Console. 6. On the Action menu. click the topmost record for the <yourSMSClient> computer. A Confirm Delete message box appears prompting to delete the record. and the current membership of the All Systems collection is displayed. The All Systems message box appears prompting to update subcollection membership. Update the membership of the All Windows XP Systems collection. and then on the Action menu. Click Yes. Notice that the <yourSMSClient> computer is now displayed twice. Notice that the site server computer (<yourSMSServer>) and the Windows XP Professional client computer <yourSMSClient>appear as members. This collection will be used later in this lab to upgrade a client to Configuration Manager Microsoft System Center 21 . Delete any other obsolete records from the All Systems collection. click Delete. Log on as administrator with a password of password. 7. The collection membership is updated. point to All Tasks. Notice that the <yourSMSClient> computer is now displayed only once.

click About Systems Management Server. Note Complete this procedure from the primary site server computer only  To identify the SMS 2003 SP2 site 1. and then on the Action menu. on the Start menu. 3. and then click SMS Administrator Console. The About Systems Management Server dialog box appears displaying information about the local site. 6. Exercise 2 Preparing to Upgrade SMS 2003 SP2 to Configuration Manager In this exercise. 2. point to All Programs. The SMS Administrator Console window appears. Note Complete this exercise from the primary site server computer only  To verify the site’s readiness for upgrade to Configuration Manager Microsoft System Center 22 . Close the SMS Administrator Console window. you will verify the local site is running SMS 2003 SP2.Exercise 1 Identifying an SMS 2003 stallation In this exercise.50 SP2 (4253) which is SMS 2003 SP3 ________________________________________________________________________ 4. click Site Database.2000 which is SMS 2003 SMS 2. If not already running. Click OK. This is required for upgrade.50 SP2 (4160) which is SMS 2003 SP2 SMS 2. and then click Site Hierarchy. 5. This will include running the Configuration Manager prerequisite check program to verify the site can upgrade to Configuration Manager. What version of SMS is installed on the local site server? 2. What version of SMS is displayed? SMS 2. point to Systems Management Server. and will be done automatically as part of the setup. The local site information appears in the details pane.50 SP2 (4253) which is SMS 2003 SP3 ________________________________________________________________________ 7. you will prepare your SMS 2003 site for an upgrade to Configuration Manager. It can also be done manually to prepare the site prior to stating the upgrade process. In the console tree. This will be useful in determining that your site is running SMS 2003 SP2.4160. expand Site Database.50. In the console tree. and testing the SMS site database upgrade.

When complete. Notice that one of the options under Prepare is the prerequisite checker. When the schema extension process has completed. You will update the schema in the next step. Start <your SCCM eval download location> Splash. The Microsoft System Center Configuration Manager 2007 Start window appears displaying available options. Click OK. 5.1. Notice that it states that while this is not required. Microsoft System Center 23 . A command prompt window appears as you extend the Active Directory schema for use by Configuration Manager. Start <your SCCM eval download location> \SMSSetup\Bin\I386\Extadsch. This will take a few minutes to complete. the command prompt window closes. 2.exe. Notice that the default option for this site is for upgrade validation. the site will run with reduced functionality until the AD schema is updated for Configuration Manager. double-click Schema extensions. 3. Another warning is for the lack of secure key exchange configured for the current site. 4. Under Prerequisite.hta found in the <root> of the dir structure. The final warning is that the WSUS SDK is not installed on the site server. as the checker detected an SMS 2003 site installation. The Microsoft System Center Configuration Manager 2007 Installation Prerequisite Check Options dialog box appears. Click Run the prerequisite checker. The schema extension test information appears at the bottom of the dialog box. The Microsoft System Center Configuration Manager Installation Prerequisite Check dialog box appears displaying the status of the site prerequisite check. notice that there are six warnings displayed. Three warnings are for missing updates which are included in Windows Server 2003 SP2 (however the site server is only running Windows Server 2003 SP1). Another warning indicates that the Active Directory schema has not been extended for Configuration Manager. Also notice that this is not something that the Configuration Manager Setup program can resolve automatically.

Click Back Up. This will take a few minutes to complete. The New Database dialog box appears. Notice also that the warning for the Active Directory schema extensions is no longer listed. notice that there are now five warnings displayed. When complete. 7. As these are only warnings. There are three for missing updates. add SMSTest to the end of the supplied path. and then click Add. you will create a backup of the SMS 2003 SP2 site database and test the upgrade of the database. In the tree pane. and not failures. 3. 7. Microsoft System Center 24 . right-click Databases. and then click OK. <yourSMSServer>. On the Start menu. The Back Up Database – SMS_sitecode dialog box appears. The Select Backup Destination dialog box appears. A Connect to Server dialog box appears. In the Microsoft System Center Configuration Manager Installation Prerequisite Check dialog box. In the File name box. 2. and then point to Tasks. Note Complete this procedure from the primary site server computer only. A new menu appears. The Microsoft SQL Server Management Studio window appears. 6.6. click Run Check. The database is backed up. and then click New Database. 9. In the following procedure. Click OK. you can proceed with the upgrade.  To create a backup of the SMS site database 1. point to All Programs. The Microsoft System Center Configuration Manage Installation Prerequisite Check dialog box appears displaying the status of the site prerequisite check. In the Database box. and then click SQL Server Management Studio. 5. 8. point to Microsoft SQL Server 2005. When complete. a Microsoft SQL Server Management Studio message box appears indicating the backup completed successfully. Click Next to connect to the local SQL Server. and one for the WSUS SDK. The Back Up Database – SMS_sitecode dialog box appears displaying the new backup device. Click OK to close the Microsoft System Center Configuration Manager Installation Prerequisite Check dialog box. 4. one for secure key exchange. verify that SMS_sitecode is listed. right-click SMS_sitecode. The Microsoft SQL Server Management Studio window appears. In the tree pane. expand Databases. Click OK.

10. In the Database name box, type <sitecode>Backup and then click OK. The new database is created. When complete, the list of databases appears in the Microsoft SQL Server Management Studio window. 11. In the tree pane, right-click <sitecode>Backup, and then on point to Tasks. A new menu appears. 12. Point to Restore, and then click Database. The Restore Database - <sitecode>Backup dialog box appears. 13. In the From database box, click SMS_<sitecode>. Notice that the recent backup information appears in the list of backup sets for the <your_db_name> database. Restoring the <your_db_name> backup to the <your_db_name> Backup database will allow you to test the upgrade on the <your_db_name> database, but not upgrade the SMS site database (<your_db_name>). 14. In the To database box, click <sitecode>Backup. This sets the restore to go from the <your_db_name> database backup to the new <your_db_name> Backup database. 15. In the tree pane, click Options. The Restore Database - <sitecode>Backup dialog box appears displaying options for the restore process. 16. Under Restore options, click Overwrite the existing database. 17. Under Restore the database files as, click the ellipsis button (…) after SMS_< sitecode >_Data.MDF. The Locate Database Files dialog box appears. 18. In the File name box, type <your SCCM install path> \<sitecode>Backup.mdf and then click OK. The Restore Database - <sitecode>Backup dialog box appears. 19. Under Restore the database files as, click the ellipsis button (…) after SMS_<sitecode>__Log.LDF. The Locate Database Files dialog box appears. 20. In the File name box, type (this is an example location) <systempartition> \SMSData\<your_db_name> Backup.ldf and then click OK. The Restore Database - <sitecode>Backup dialog box appears. Notice that both the database and log files are now configured to restore to new files. 21. Click OK. The database is backed up. When complete, a Microsoft SQL Server Management Studio message box appears indicating the backup completed successfully. 22. Click OK. The Microsoft SQL Server Management Studio window appears. 23. Close the Microsoft SQL Server Management Studio window.

Microsoft System Center

25

In the following procedure, you will run Configuration Manager Setup with a special command line option to test the upgrade of the database.

Note Complete this procedure from the primary site server computer only. This process can take a number of minutes (potentially 15) depending on the hardware used. If you don‘t want to take the time to complete this test, you can skip this procedure in the lab. However, it is highly recommended that you do perform a database upgrade test in your environment prior to attempting an upgrade.

 To test an upgrade of the SMS site database
1. Start a command prompt, and then change to the <your SCCM eval download location> \SMSSetup\Bin\I386 folder. A command prompt window appears. 2. In the command prompt window, type Setup.exe /testdbupgrade <your_db_name>backup The Microsoft System Center Configuration Manager 2007 Installation Prerequisite Check dialog box appears. Notice that there is a new button available, Begin TestDBUpgrade. 3. Click Begin TestDBUpgrade. The testing of the database upgrade takes a few minutes to complete. When the database upgrade test completes, a Configuration Manager 2007 message box appears indicating the upgrade was successful. Note There is no user interface while the database upgrade test is running. However you can start Task Manager to monitor Setup.exe, as well as to wait for the Configuration Manager 2007 message box to appear when the test has completed. 4. Click OK, and then open C:\ConfigMgrSetup.log. Notepad appears and displays the contents of the ConfigMgrSetup.log file. 5. Search for <sitecode>backup. Notepad displays the first occurrence of <sitecode>backup. Notice that the reference is to the testdbupgrade command. A few lines later, notice a reference to ―Testing database upgrade on <sitecode>backup database, on the <yourSMSServer> server‖. These lines are the indication that Setup is being run to test the database upgrade process. 6. Scroll to the bottom of the log file.

Microsoft System Center

26

7. What is the last line logged in the file? TestDBUpgrade is done ________________________________________________________________________ If the ConfigMgrSetup.log file displays the success message, your database can be upgraded to Configuration Manager. 8. Close Notepad. Your site has passed the Configuration Manager Installation Prerequisite Check test, as well as the database upgrade test. Your site should be able to upgrade to Configuration Manager successfully.
Exercise 3 Upgrading SMS 2003 SP2 to Configuration Manager In this exercise, you will upgrade your SMS 2003 site to Configuration Manager.

Note Complete this exercise from the primary site server computer only

 To upgrade an SMS 2003 site to Configuration Manager
1. Start <your SCCM eval download location>\Splash.hta. The Microsoft System Center Configuration Manager 2007 Start window appears displaying available options. 2. Under Install, click Configuration Manager 2007. The Welcome to the System Center Configuration Manager 2007 Setup Wizard dialog box appears. 3. Click Next. The Microsoft System Center Configuration Manager 2007 Available Setup Options dialog box displays options for installation, which include an upgrade or uninstall. 4. Click Upgrade an existing Configuration Manager or SMS 2003 Installation, and then click Next. The Microsoft System Center Configuration Manager 2007 Microsoft Software License Terms dialog box appears displaying the license agreement. Read the licensing information. 5. Click I accept these license terms, and then click Next. The Microsoft System Center Configuration Manager 2007 Customer Experience Improvement Program Configuration dialog box appears prompting for participation in the customer experience improvement program. Notice that involvement in the program is not selected by default. 6. Click Next to not participate at this time. The Microsoft System Center Configuration Manager 2007 Product Key dialog box appears prompting for the product key for installation. 7. In the Key box, if not already supplied, type your product key, and then click Next. The Microsoft System Center Configuration Manager 2007 Updated Prerequisite

Microsoft System Center

27

As we‘re in a VPC environment. Notice that there are two options. and the other to use a local source of the required files.Components dialog box appears prompting for the location of the required client components. the required files have already been downloaded and staged for the lab. one to download the required updates from the Internet. Microsoft System Center 28 .

The Microsoft System Center Configuration Manager 2007 Updated Prerequisite Component Path dialog box appears displaying the configured location of the required client components. When complete. Point to <systempartition>\SCCM Downloaded Client Files. When complete. the Microsoft System Center Configuration Manager 2007 Installation Prerequisite Check dialog box appears indicating the status of the validation process.8. Click Begin Install. Notice that there were no problems found with the configuration that will prevent installation. 9. Microsoft System Center 29 . The Microsoft System Center Configuration Manager 2007 Settings Summary dialog box appears displaying various configuration values to be used during the installation of Configuration Manager. 15. 10. The Completing the System Center Configuration Manager 2007 Setup Wizard dialog box appears indicating the site is ready to use. Click Browse. Click Next. 14. Click Next. Click The latest updates have already been downloaded to an alternate path. Click Finish. The Browse For Folder dialog box appears. 12. The Microsoft System Center Configuration Manager 2007 Updated Prerequisite Component Path dialog box appears prompting for the location of the required client components. Click Next. 13. the Microsoft System Center Configuration Manager 2007 Setup Action Status Monitoring dialog box appears indicating that Setup completed each action successfully. This process will take several minutes to complete. and then click Next. 11. and then click OK. The Microsoft System Center Configuration Manager 2007 Setup Action Status Monitoring dialog box appears displaying the status of the individual tasks that must be completed as part of the Configuration Manager installation. The Configuration Manager Installation Prerequisite Check runs to validate that the computers targeted for Configuration Manager installation meet the requirements for installation.

and Software Updates Client Agent. The local site‘s home page appears in the results pane. Network Access Protection Client Agent.5931. point to Configuration Manager 2007. 7.00.Exercise 4 Identifying a Configuration Manager Installation In this exercise. you will verify that your site was successfully upgraded to Configuration Manager 2007. and then click Site Management. 4. point to Microsoft System Center. The list of client agents for the Configuration Manager appears in the results pane. In the tree pane. and then click ConfigMgr Console. expand Site Settings. Note Complete this exercise from the primary site server computer only  To identify an Configuration Manager site installation 1. Microsoft System Center 30 . click Site Database. Notepad appears and displays the contents of the ConfigMgrSetup. such as Computer Client Agent.log. expand Site Management. point to All Programs. expand Site Database.0000 which is Configuration Manager 2007 RTM. There are many other differences in the Configuration Manager Console from SMS 2003 to Configuration Manager. Notice that there are new client agents in Configuration Manager that were not available in SMS 2003. ________________________________________________________________________ 8. Notice that information is provided on completing the site configuration in order to support Configuration Manager client deployment. expand <sitecode> (like <your_db_name>) . 5. Desired Configuration Management Client Agent. You will explore those differences in this and other hands-on labs. In the tree pane.log file. and then click Client Agents.log file displays the success message. Open <systempartition>\ConfigMgrSetup. What version of SCM is installed on the local site server? 4. 6. What is the last line logged in the file? Moving to Finish page. Close Notepad. your site was upgraded to Configuration Manager. The Configuration Manager Console window appears displaying the Configuration Manager home page in the results pane. On the Start menu. 3. The local site information appears in the results pane. In the tree pane. 2. ________________________________________________________________________ If the ConfigMgrSetup. Installation and Configuration processes are done.

expand Computer Management. expand Reporting. The Computers with a specific SMS client version report appears in the results pane displays the names of SMS 2003 Advanced Clients in the SMS site database. Note Complete this procedure from the primary site server computer only  To upgrade an Advanced Client from SMS 2003 SP2 to Configuration Manager 2007 using the Client Push Installation Wizard 1. The members of the All Windows XP Systems collection appear in the results pane. and then in the Actions pane. 6.2000) ________________________________________________________________________ 5. click Run. you will upgrade your clients to Configuration Manager 2007. In the results pane. 4. and then click All Windows XP Systems. The list of reports appears in the results pane.50. as well as the client running on the Configuration Manager site server computer. What different versions of SMS clients are there. The Report Options message box appears prompting for the reporting point to use to run the report. 7. Notice that the <yourSMSClient> computer is listed as a member of the collection.4160. Click OK to use the only reporting point in our site. under Count SMS client versions. 3. expand Site Database. 2. and how many of each client type? There are two SMS 2003 SP2 Advanced Clients (2. You will upgrade the Advanced Client running on the Windows XP Professional computer.2000. Microsoft System Center 31 .50. Notice that there are many other reports included with Configuration Manager that were not available in SMS 2003. What computers are currently installed as SMS 2003 SP2 Advanced Clients? <yourSMSClient> and <yourSMSServer> ________________________________________________________________________ ________________________________________________________________________ The Configuration Manager Console window appears. expand Collections. click Count SMS client versions. The results of the Count SMS client versions report appear in the results pane. In the tree pane.Exercise 5 Upgrading Clients to Configuration Manager In this exercise. Click the arrow to the left of the 2. In the tree pane. and then click Reports.4160.

3. so you begin the process to upgrade the SMS 2003 Advanced Client on the site server and then return here to verify your Windows XP client did indeed upgrade. The Client Push Installation Wizard dialog box appears. When the Advanced Client has been upgraded to Configuration Manager. Click Always install (repair or upgrade the existing client). This is the installation program for the client. 10. Log on as administrator with a password of password. Your SMS 2003 SP2 Advanced Client computer has successfully upgraded to Configuration Manager.exe (SMS Agent Host) will appear.0001. and then click Next. In the Actions pane. Click Finish. Note You can move to the next procedure while the Windows XP client computer is upgrading from SMS 2003 SP2 to Configuration Manager.00. It should display 4. 2. Microsoft System Center 32 .exe will terminate. The Client Push Installation Wizard Installation options dialog box appears displaying options for the client installation. and then ccmsetup. The upgrade may take a number of minutes to complete. In the following procedure. The Task Manager window appears. start Configuration Manager.5931. 9. Close Task Manager. Notice the SMS Client Version listed. Notice that Ccmsetup. you will verify the Windows XP Professional client has upgraded to a Configuration Manager client. 11. Start Task Manager. and then in Control Panel. The Configuration Manager Properties dialog box appears. The Configuration Manager client is remotely installed on the Windows XP Professional client computer. Note Complete this procedure from the Windows XP Professional client computer only  To verify the Advanced Client upgrade 1. 4.exe is running. CcmExec.8. Click Next. Click Cancel. click Install Client. The Completing the Client Push Installation Wizard dialog box appears indicating it is ready to complete the installation. which is for Configuration Manager 2007. It will take a few minutes before the installation completes to upgrade the client from SMS 2003 SP2 to Configuration Manager.

The list of packages in the site appears in the results pane. In the tree pane. The Create Package from Definition Wizard Summary dialog box appears indicating that the wizard is complete. click New. this was from the SMS 2003 installation and migrated to Configuration Manager. and then click Next. and then click Browse. and then in the Actions pane. click Refresh. expand Site Database. Open <SMSinstallpath>\Client. and then click Packages. Notice that the Configuration Manager Client Upgrade package is listed. The Create Package from Definition Wizard dialog box appears. click Configuration Manager Client Upgrade. 5. The Create Package from Definition Wizard Source files dialog box appears. and then click OK. 10. The list of packages appears in the details pane. and then click Package From Definition. Under Package definition. The Create Package from Definition Wizard Source Directory dialog box appears. expand Computer Management. Click Always obtain files from a source directory. Notice that there is one package. The Browse For Folder dialog box appears. 6.In the following procedure. 2. 3. Notice that there is already a package definition included in Configuration Manager for the Configuration Manager Client Upgrade. Note Complete this procedure from the primary site server computer only  To prepare Configuration Manager for client upgrade using software distribution 1. 7. and then click Next. you will prepare the site to upgrade your the site server computer as a client to a Configuration Manager client. expand Software Distribution. click Packages. The Create Package from Definition Wizard Package Definition dialog box appears. Click Next. In the tree pane. Click Local drive on site server. 4. Microsoft System Center 33 . 9. Click Next. In the Actions pane. The Create Package from Definition Wizard Source Directory dialog box appears displaying the configured path. You will use software distribution to upgrade this client. The Configuration Manager Console window appears. Click Finish. though you could use the Client Push Installation Wizard as well. 8.

and then click Next. In the Actions pane. 16. 24. In the tree pane. The New Distribution Points Wizard Copy Package dialog box appears. 17. Click Close. and then click Advertisement. Under Distribution points. After Collection. click All Windows Server 2003 Systems. 18. 23. After Package. Click Next to not assign the program. The New Distribution Points Wizard Wizard Complete dialog box appears indicating that the wizard completed successfully. click Browse. and then click Distribution Points. and then click OK. expand Site Database. expand Computer Management. 14. Notice that there are no advertisements in the site. expand Packages.0 ALL. Click Microsoft Configuration Manager Client 4. The New Distribution Points Wizard dialog box appears. 15.11. type Configuration Manager Client Upgrade 19. click <yourSMSServer>. The Select a Package dialog box appears displaying the available packages. Notice that there are no distribution points for this package. 13. and then click OK. 21. 12. The New Advertisement Wizard Schedule dialog box appears allowing you to configure a schedule for this advertisement. click New. The Browse Collection dialog box appears. In the Actions pane. expand Microsoft Configuration Manager Client Upgrade 4. In the tree pane. Click Next. and then click Advertisements. click Browse. The New Advertisement Wizard General dialog box appears. click New Distribution Points. The list of advertisements appears in the results pane. The Configuration Manager Console window appears. Notice that the Advanced Client Silent Upgrade program is displayed as the program to advertise.0 ALL. The list of distribution points for the package appears in the details pane. The New Advertisement Wizard Distribution Points dialog box appears allowing you to configure whether or not the advertisement is run from the distribution point or downloaded before execution. Click Next. expand Software Distribution. The New Advertisement Wizard General dialog box appears. In the Name box. Under Collections. 22. 20. Microsoft System Center 34 . The New Advertisement Wizard General dialog box appears displaying the current properties for the advertisement.

and then click Next. and then click Initiate Action. 27. 29. The New Advertisement Wizard Wizard Completed dialog box appears indicating that the wizard has successfully created the advertisement. In Control Panel. Hardware Inventory Cycle. Click the Actions tab. The New Advertisement Wizard Interaction dialog box appears allowing you to configure whether or not the advertisement displays reminders to the logged on user. 3. 28. Software Metering Usage Report Cycle.25. which will include the policies related to the client upgrade advertisement. Note Verify that the All Windows Server 2003 Systems collection contains <yourSMSServer>. File Collection. Notice the default actions of Discovery Data Collection Cycle. and not require the use of protected distribution points. Click Next. Click Close. Click Next to use the default security rights. start Systems Management. 2. The Systems Management Properties dialog box displays the available actions for the Advanced Client. Click Next to run from local distribution points. The Advanced Client will request new policies. Click Display reminders according to the client agent reminder intervals. to not run from slow network boundaries. The Systems Management Properties dialog box appears. and may take several minutes to complete. Machine Policy Retrieval & Evaluation Cycle. In the following procedure. The Configuration Manager Console window appears displaying the new advertisement in the results pane. you will upgrade the Configuration Manager site server computer to a Configuration Manager client. Microsoft System Center 35 . Click Machine Policy Retrieval & Evaluation Cycle. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. 26. The New Advertisement Wizard Summary dialog box appears indicating that the wizard has been successfully completed. Software Inventory Cycle. The New Advertisement Wizard Security dialog box appears allowing you to configure security rights for this advertisement. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. Note Complete this procedure from the site server as a client computer only  To upgrade the Configuration Manager site server computer using software distribution 1.

This program will de-install the SMS 2003 client.4. 10. Note You can return to the previous procedure to verify that the Windows XP client computer did upgrade from SMS 2003 to Configuration Manager. Close Task Manager. This process will take a few minutes to complete.EXE will terminate. Click Cancel. and then the upgrade process starts. The Program Download Required dialog box appears. 8. This is the installation program for the Configuration Manager client. 6. and then click Download. Click OK. Click Close. Under Program Name. Notice that Ccmsetup. It should display 4. The Systems Management Properties dialog box appears. The Run Advertised Programs dialog box appears. and then install the Configuration Manager client. click Microsoft Configuration Manager Client Upgrade. Notice the SMS Client Version listed.5931.exe is running. start Configuration Manager.00. The upgrade to a Configuration Manager client will take a number of minutes to complete. 5. Click OK. which is for Configuration Manager 2007. The Configuration Manager Properties dialog box appears. 11. 9. so you can verify your Windows XP client did indeed upgrade. and then in Control Panel. double-click the New Program Available icon. The Run Advertised Programs dialog box appears.0001. You can use Task Manager to monitor the installation of the Configuration Manager client. 7. and then click Run.exe (SMS Agent Host) will appear. Your SMS 2003 Advanced Client computers have successfully upgraded to Configuration Manager clients. Click Run program automatically when download completes. When the Advanced Client has been upgraded. Microsoft System Center 36 . In two minutes. CcmExec. a New Program Available message box appears in the System Tray. In the System Tray. and then CCMSETUP. The program is downloaded.

Note Complete this procedure from the primary site server computer only. The results of the Count SMS client versions report appear in the results pane. Close the SMS Report window. and then expand Visited Reports. The list of reports previously run appears in the tree pane. What computers are currently installed as Configuration Manager clients? <yourSMSClient> and <yourSMSServer> ________________________________________________________________________ ________________________________________________________________________ 6. under Visited Reports. expand Reporting. The results of the drill down report action appears in the results pane. This process included running the Setup Prerequisite checker to validate the site was ready to be upgraded. 3. In the tree pane.00.In following procedure.00.5931.  To verify the Advanced Client upgrades 1. Click the arrow to the left of the clients (4. and two of your SMS 2003 clients to Configuration Manager 2007. 5.0001) ________________________________________________________________________ 4. you will verify that your clients have upgraded to Configuration Manager. expand Site Database. Notice that the results pane displays the Configuration Manager clients. click Count SMS client versions. expand Computer Management. Notice that there is one report you had run previously.5931. In the results pane. 2.0001). as well as performing a test database upgrade process to verify that the SMS site database could be upgraded to Configuration Manager. You have now successfully upgraded your SMS 2003 site server. the ―Count SMS client versions‖ report. What different versions of SMS clients are there. and how many of each client type? There are two Configuration Manager 2007 clients (4. Microsoft System Center 37 . The Configuration Manager Console window appears.

0 or later. Install and configure a fallback status point. You will use a utility to extend the Active Directory schema for use by SCCM. Install a reporting point Prerequisites This section is not dependant or connected to Section 1. The requirements for implementing SCCM 2007 (which have all been installed in the lab VPC images. View status message activity related to site server installation. Discover computer resources from Active Directory.0 or later Several KB updates The required client installation files already downloaded in the image if no Internet access is available Estimated time to complete this section: 75 minutes Exercise 1 Preparing Active Directory for SCCM 2007 Integration In this exercise. you will create an Active Directory site that will be added to the SCCM boundaries for client management.  To extend the Active Directory schema Microsoft System Center 38 . you will prepare Active Directory for use with SCCM 2007. The third virtual computer should be started as a Windows XP Professional SP2 client to be installed as a client in the Configuration Manager 2007 site <yourDeployClient>. Before working on this lab. This computer has Microsoft SQL Server 2005 installed. one virtual computer should be started as a Microsoft Windows Server 2003® SP1 computer running as an Active Directory domain controller <yourDeployADServer>.Section 2: Deploying System Center Configuration Manager 2007 Objectives After completing this section . where we focused on the SMS 2003 upgrade process. Install Configuration Manager 2007 using a custom setup. Install a Configuration Manager 2007 client on the Windows XP Professional client. include:  Microsoft Windows Server 2003 SP1 or later in an Active Directory domain      Internet Information Server (IIS) 6. Note Complete this exercise on the virtual computer running as a Windows Server 2003 Active Directory domain controller only. Finally. You will also grant rights for the SCCM site server to publish data to Active Directory. with BITS Server Extensions installed and WebDAV enabled (for management points and BITS-enabled distribution points) Microsoft SQL Server 2005 SP2 (Standard or Enterprise Edition) Microsoft Management Console 3. A second virtual computer is started as a Microsoft Windows Server 2003® SP2 member server to install as an SCCM primary site server <yourDeploySCCMserver>. you will be able to:        Prepare Active Directory for Configuration Manager publishing and use.

You will grant rights to the System container to allow the Configuration Manager site server to publish data to Active Directory. and then click System. 5. Computers. Computers. The Active Directory Computers and Users window displays additional Active Directory information. The Select Users.1. The Select Users. Run Extadsch. and then click Active Directory Users and Computers. Open C:\Extadsch. A command prompt window appears as you extend the Active Directory schema for use by Configuration Manager.exe http://technet.exe which is documented here. Click Add. expand <yourdomain> .log. Verify that there are no errors listed in the log. 3. click Properties. 5. the command prompt window closes. or Groups dialog box appears. On the Action menu. This file is created by the Extadsch. or Groups dialog box appears. Log on as administrator with your password. Click Object Types. 4. 4. 8. Notice that the Configuration Manager site server computer (<yourSMSServer>) is now listed with Read Microsoft System Center 39 . 6. The Select Users. Click the Security tab. point to Administrative Tools.com/en-us/library/bb680608.microsoft. When the schema extension process has completed. There were 14 attributes and 4 classes added to Active Directory. The Object Types dialog box appears. or Groups dialog box appears. The System Properties dialog box displays the security permissions on the System container. On the View menu. 2.aspx 3. Notepad displays the contents of the Extadsch. including displaying the System container.log file. In the Enter the object names to select field. Under Object types. How to Extend the Active Directory Schema Using ExtADSch. In the console tree. click Advanced Features. 9. Notice that the Configuration Manager site server computer (<yourSMSServer>) is not listed. On the Start menu. The System Properties dialog box appears. 2.exe utility and reports on the Active Directory schema extension process. and then close Notepad. Computers. The Active Directory Computers and Users window appears. click Computers. 7. and then click OK.  To grant the SCCM site server rights to Active Directory 1. type <yourSMSServer> and then click OK.

rights. 10. Under Permissions for <yourSMSServer>, click Full Control under Allow, and then click Advanced. The Advanced Security Settings for System dialog box appears displaying the rights for various accounts. 11. Under Name, click <yourSMSServer>, and then click Edit. The Permission Entry for System dialog box appears displaying the rights for <yourSMSServer>\$. 12. In the Apply onto field, click This object and all child objects, and then click OK. The Advanced Security Settings for System dialog box appears. 13. Click OK. The System Properties dialog box appears. 14. Click OK. The Active Directory Computers and Users window appears. You can leave this window open if you want to view information that Configuration Manager publishes to Active Directory after installation.
In the following procedure, you will create an Active Directory site to integrate with Configuration Manager as part of its boundaries.

 To create an Active Directory site
1. On the Start menu, point to Administrative Tools, and then click Active Directory Sites and Services. The Active Directory Sites and Services window appears. 2. In the console tree, click Sites. The list of AD sites appears in the results pane. Notice the default site name of DefaultFirst-Site-Name. 3. On the Action menu, click New Site. The New Object – Site dialog box appears. 4. In the Name box, type SCCMSite 5. 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. 6. Click OK. The list of sites appears in the details pane. Notice the new site is listed. 7. In the console tree, expand Sites, click Subnets, and then on the Action menu, click New Subnet. The New Object – Subnet dialog box appears. 8. In the Address box, type your range

Microsoft System Center

40

9. In the Mask box, type your subnet 10. Under Select a site object for this subnet, click SCCMSite, and then click OK. The list of subnets appears in the details pane. Notice the new subnet and its associated site. 11. In the console tree, expand SCCMSite, 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. 12. In the console tree, expand Default-First-Site-Name, expand Servers, and then click <yourADServer>. This is your domain controller. You will move this to your new site as its server. 13. On the Action menu, click Move. The Move Server dialog box appears displaying all sites available. 14. Under Site Name, click SCCMSite, 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. 15. In the console tree, expand Sites, expand SCCMSite, and then click Servers. The list of servers for the new site appears in the details pane. Notice that your PDC has been moved to the new site. 16. Close Active Directory Sites and Services.

Microsoft System Center

41

Exercise 2 Installing Microsoft Configuration Manager 2007 In this exercise, you will install Configuration Manager 2007 using a custom installation. SQL Server 2005 is already installed on the computer <yourSMSServer>. The installation will implement a mixed mode security environment.

Note Complete this exercise on the virtual computer running as a Windows Server 2003 SP2 member only. This is the computer that will be installed as the Configuration Manager site server

 To install Configuration Manager 2007
1. Start <your SCCM eval download location> \Splash.hta. The Microsoft System Center Configuration Manager 2007 Start window appears. 2. Under Install, click Configuration Manager 2007. The Welcome to System Center Configuration Manager 2007 Setup Wizard dialog box appears. 3. Click Next. The Microsoft System Center Configuration Manager 2007 Available Setup Options dialog box displays options for installation. 4. Click Install a Configuration Manager site server, and then click Next. The Microsoft System Center Configuration Manager 2007 Microsoft Software License Terms dialog box appears displaying the license agreement. Read the licensing information. 5. Click I accept these license terms, and then click Next. The Microsoft System Center Configuration Manager 2007 Installation Settings dialog box appears displaying options for installation. 6. Verify that Custom settings is selected, and then click Next. The Microsoft System Center Configuration Manager 2007 Site Type dialog box appears displaying options for the type of site to install. 7. Verify that Primary site is selected, and then click Next. The Microsoft System Center Configuration Manager 2007 Customer Experience Improvement Program Configuration dialog box appears prompting for participation in the customer experience improvement program. Notice that involvement in the program is configured to no participation. 8. As we are in a virtual environment, click Next to decline participation at this time. The Microsoft System Center Configuration Manager 2007 Product Key dialog box appears prompting for the product key for installation.

Microsoft System Center

42

The Microsoft System Center Configuration Manager 2007 Site Settings dialog box appears prompting for site information. type your product key. The Microsoft System Center Configuration Manager 2007 Destination Folder dialog box appears prompting for destination folder to install Configuration Manager 2007 to. if not using the evaluation version of Configuration Manager. The Microsoft System Center Configuration Manager 2007 SMS Provider Settings dialog box appears prompting for the computer to install the SMS Provider on. type an appropriate 3 character site code. 18. Click Next to accept the default values of the SCCM site server‘s installation of SQL Server and SMS_<your_db_name> for the database name. Click Next to use the default HTTP port of 80. The Microsoft System Center Configuration Manager 2007 Port Settings dialog box appears prompting for the HTTP port to configure for use by SCCM. Microsoft System Center 43 . Click Configuration Manager Mixed Mode. The Microsoft System Center Configuration Manager 2007 Updated Prerequisite Components dialog box appears prompting for the location of the required client components. 16. setup will install one by default. 14. In the Site Code box. The Microsoft System Center Configuration Manager 2007 Site Mode dialog box appears displaying setup options for the SCCM security mode. Click Next to enable and configure the selected agents (ensuring that Network Access Protection is not enabled). Notice that there are two options. 10. Click Next to accept the default folder of C:\Program Files\Microsoft Configuration Manager. and then click Next. 11. such as <your_db_name> (can be whatever you prefer). Since SCCM requires a management point. and then click Next. type SCCM 2007 Primary Site. As we‘re in a VPC environment. The Microsoft System Center Configuration Manager 2007 Client Agent Selection dialog box appears displaying the available SCCM client agents. and the other to use a local source of the required files. Click Next to use the SCCM site server for the SMS Provider. The Microsoft System Center Configuration Manager 2007 Database Server dialog box appears prompting for the SQL Server computer (and instance if required) to use as well as the name of the database for SMS. one to download the required updates from the Internet. 12. and allowing you to enable or disable each as desired. The Microsoft System Center Configuration Manager 2007 Management point dialog box appears prompting for the computer to use to install the management point on. 17. 15. and then click Next. the required files have already been downloaded and staged for the lab. 13. In the Key box. In the Site Name box. Click Next to install the management point on the SCCM site server.9.

Microsoft System Center 44 . 26. This is required to be able to deploy software updates. Click Next. The Microsoft System Center Configuration Manager 2007 Updated Prerequisite Component Path dialog box appears prompting for the location of the required client components. The Browse For Folder dialog box appears. When complete. When complete. The Microsoft System Center Configuration Manager 2007 Updated Prerequisite Component Path dialog box appears displaying the configured location of the required client components. There is a warning that no WSUS installation was found. The Microsoft System Center Configuration Manager 2007 Setup Action Status Monitoring dialog box appears displaying the status of the individual tasks that must be completed as part of the SCCM 2007 installation. but it is not required for the deployment lab. Click Begin Install. Click Next. 22.19. 25. Click The latest updates have already been downloaded to an alternate path. and then click OK. The Microsoft System Center Configuration Manager 2007 Settings Summary dialog box appears displaying various configuration values to be used during the installation of SCCM 2007. The Configuration Manager Installation Prerequisite Check runs to validate that the computers targeted for SCCM 2007 installation meet the requirements for installation. The Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard dialog box appears indicating the site is ready to use. 24. 20. 23. 21. so you can continue. Click Next. Click Browse. Notice that there were no problems found with the configuration that will prevent installation. the Microsoft System Center Configuration Manager 2007 Installation Prerequisite Check dialog box appears indicating the status of the validation process. Point to <systempartition>\SCCM Downloaded Client Files (or your location where these are located). the Microsoft System Center Configuration Manager 2007 Setup Action Status Monitoring dialog box appears indicating that Setup completed each action successfully. and then click Next. This process will take several minutes to complete. Click Finish.

as well as the text under Description. The Status Message Details dialog box appears. 2. This message indicates that SCCM retains the 100 most recent copies of the site control file. The Microsoft Management Console (MMC) starts. click Component Status. You might see messages with IDs of 2808. The list of Configuration Manager site system roles appears in the results pane with the current status of each site system. You can use this same procedure to view status messages generated by any Configuration Manager processes. On the Start menu. The ConfigMgr Status Message Viewer for <yoursitecode>. The list of SCCM components appear in the results pane. click Detail. In the results pane. Notice the message with an ID of 2866. and then click Site System Status. and then in the Actions pane.In the following procedure. window appears. On the File menu. 9. In the tree pane. The ConfigMgr Status Message Viewer for <yoursitecode>. You may notice the message with a message ID of 2819. 2814. 3. point to All Programs. The ConfigMgr Status Message Viewer for <yoursitecode>. click Exit. 8. Verify that each site system has a status of OK. You will view these messages in later sections of this review. expand <yoursitecode>. 6. and 2865 in each set of site control file modification requests. In the tree pane. you might notice many sets of site control file images being modified. Click All. Display the status messages for SMS_SITE_CONTROL_MANAGER. expand System Status.  To view Configuration Manager status messages 1. click SMS_SITE_COMPONENT_MANAGER. 5. Click OK. 2811. It mentions that the site server was configured to receive Configuration Manager server components. window appears. and then the Configuration Manager Console window appears. Click the message. From here. and then on the View menu. 2813. The list of SCCM components and their status appears in the results pane. point to Microsoft System Center. Microsoft System Center 45 . SCCM has just been installed. A new menu appears. Notice the header information for the message. click Show Messages. expand Site Database. you will use Configuration Manager status messages generated by the site server installation to verify that the site server installation was successful. 4. Notice the message with the ID of 1027. 7. point to Configuration Manager 2007. window appears. expand Site Status. This message indicates the actual site control file copy has been sent to the SMS Hierarchy Manager for addition to the SCCM site database. At this point. and then click ConfigMgr Console. however there will have already been some site control file modifications processed.

This occurred as a result of installing SCCM site components on the site server computer. The New Site Boundary dialog box appears allowing the creation of a new boundary.  To configure Configuration Manager to use the new AD site as a boundary 1. In the Description box. window appears. In the Actions pane. The New Site Boundary dialog box appears displaying the information specified for the new boundary. Microsoft System Center 46 . expand <sitecode>. 2. Under Site Name. and then click OK. and then click Boundaries. These messages indicate that Hierarchy Manager has successfully processed a site control file modification and updated the site database. 11. 5. The list of boundaries for the local site appears in the results pane. Under Network Connection. Notice that there no default boundaries added to the site. and then click Browse. click SCCMSite. In the tree. Notice that both the default AD site (Default-First-Site-Name) as well the AD site you created earlier (SCCMSite) are displayed. click New Boundary. 3. and then click OK. expand Site Database. verify that Fast (LAN) is selected. The Browse Active Directory sites dialog box appears displaying the available Active Directory sites. You might notice the message with a message ID of 4202. you will add the Active Directory site to the Configuration Manager 2007 Boundaries. Display the status messages for SMS_HIERARCHY_MANAGER. 6. expand Site Settings. Notice that the new AD site (SCCMSite) now appears as a boundary. type Active Directory site for SCCM 4. In the Type box. In the following procedure. This message indicates one server was discovered and discovery data was written for it.10. You might notice the messages with message IDs of 3306. click Active Directory site. Display the status messages for SMS_WINNT_SERVER_DISCOVERY_AGENT The ConfigMgr Status Message Viewer for <your_db_name> window appears. The ConfigMgr Status Message Viewer for <yoursitecode>. expand Site Management.

and then in the Actions pane. expand Site Management. Verify that Local domain is selected. Also notice that a recursive search will be performed on that container and that groups are excluded. 7. and then click Discovery Methods. Click the Polling Schedule tab. and then click OK. Select Enable Active Directory System Discovery. In the results pane. or custom query for the discovery. expand Site Settings. Notice the distinguished name for the container to search. Click Run discovery as soon as possible and then click OK. local forest. expand <yoursitecode>. The Select New Container dialog box appears allowing you to specify the container to use for discovery. and then click New (the icon resembles a starburst). You will begin by using Active Directory System Discovery to discover the computer from Active Directory. The Active Directory System Discovery Properties dialog box displays the default polling schedule for Active Directory System Discovery. 2. 4. The Active Directory System Discovery Properties dialog box appears. In the tree. and then click OK. expand Site Database. 5. you will install the Configuration Manager 2007 client on the Windows XP Professional client computer. this polling will occur daily. The Configuration Manager Console window appears. Select <yourdomainname>. The Active Directory System Discovery Properties dialog box appears. The list of discovery methods for the local site appears in the results pane. 6.Exercise 3 Installing an SCCM 2007 Client In this exercise. click Properties. Notice that by default.  To discover computers from Active Directory 1. Microsoft System Center 47 . Notice that there are four discovery methods related to Active Directory. 3. Note Complete this exercise on the virtual computer running as a Windows Server 2003 SP2 SCCM site server unless directed to use another VPC image. The New Active Directory Container dialog box appears allowing you to specify the use of a local domain. click Active Directory System Discovery.

5. expand Collections. and then click All Systems. In the results pane. click Properties. Are there any new members in the All Systems collection? Yes.  To verify Active Directory System Discovery 1. 8. click Update Collection Membership. the local site server (<yourSMSServer>). The list of collections appears in the results pane. all are listed as being assigned to the site. that being the Configuration Manager site server. 3. The collection is updated. In the Actions pane. The <yourSMSClient> Properties dialog box appears displaying discovery properties. It takes a moment before the database is updated with the new collection membership information. expand Computer Management. you will verify the results of the Active Directory System Discovery process. then verify that you have correctly listed SCCMSite as a boundary for the site. Are each of the systems assigned to the site? Yes. Note If the assigned status still remains listed as No. 7. The collection membership is updated. and then click Collections. Notice that there is one member in the All Systems collection currently. and the current membership of the All Systems collection is displayed. 6.In the following procedure. 4. click the Windows XP Professional client. expand Site Database. click Refresh. Note You will need to wait for a moment for the discovery process to complete. the domain controller (ADServer) (or DC) and the Windows XP Professional client <yourSMSClient>should have been discovered. and then in the Actions pane. Microsoft System Center 48 . An All Systems message box appears prompting to update subcollection membership. In the Actions pane. In the tree pane. 2. In the tree pane. Click OK. under <yourSMSClient>.

mspx 3. expand Site Settings. click Properties. 2. In the tree pane. please visit the Technet article on ‗Account Passwords and Policies‘ located at http://www. Click Close. Notice that the installation method is not enabled. you will configure the account in the Configuration Manager Console to allow installation of the Configuration Manager 2007 client. ‗complex passwords must be turned off. The Active Directory Users and Computers window appears. Add this user as a member of the Domain Admins group. Note Complete this procedure on the virtual computer running as a Windows Server 2003 Active Directory domain controller only  To create the account required to install the SCCM Client 1. Being a member of Domain Admins is not a requirement. From Administrative Tools. It does not need to be enabled for our admin controlled push installation. The Client Push Installation Properties dialog box displays accounts to be used to push out the Configuration Manager client software. In the following procedure. which is the AD site you added as a boundary for the site. 2. What is the discovered AD site name? SCCMSite. Create a new user with the name of ClientInstall. but simplifies the configuration in the lab environment. click Client Push Installation. It must be a local admin on the client computer. and then in the Actions pane.microsoft. assign it a password of password. The list of client installation methods appears in the results pane.9. Note Complete this procedure on the virtual computer running as a SCCM site server only  To configure the Configuration Manager 2007 client account 1. Notice that there are no accounts listed. ensure that the account is not disabled. expand Site Database. Microsoft System Center 49 . The Client Push Installation Properties dialog box appears. and that the password does not require changing at first logon.com/technet/prodtechnol/windowsserver2003/technologies/security/bpa ctlck. Note for a simple password to be accepted. This is the account that will be used to push the Configuration Manager 2007 client installation to your Windows XP Professional client. For information on how to do this. start Active Directory Users and Computers. and then click Client Installation Methods. Click the Accounts tab. expand Site Management. expand <yoursitecode>. In the results pane. 10. 3. In the following procedure. you will create the account necessary to remotely install the Configuration Manager 2007 client on your Windows XP Professional client computer.

4. expand <yoursitecode>. expand Site Management. Click OK. The list of configurable site settings appears in the results pane. Click New (the icon resembles a starburst). In the Password and Confirm password boxes. Note Complete this procedure on the virtual computer running as a SCCM site server only. The Configuration Manager Console window appears. and then expand Site Settings. In the Actions pane. and then click Next. Notice that the new account is listed. Verify that Specify a fully qualified domain name (FQDN) for this site system on the intranet is selected. and then in the Intranet FQDN box. The list of site system roles for the site server appears in the results pane. click New Roles. expand Site Database. 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. and is recommended to get client deployment status reporting.4. select Fallback status point. In the following procedure. The New Site Role Wizard General dialog box appears. The Windows User Account dialog box appears. In the tree pane. type password and then click OK. 6. The Client Push Installation Properties dialog box displays accounts to be used to push out the Configuration Manager client software. 7. and then click \\<yourSMSServer>. 3. Notice that there are six site system roles assigned to the computer.  To install a fallback status point 1. The New Site Role Wizard Fallback Status Point dialog box appears allowing you to configure the fallback status point message processing. 5.<yourdomain> 5. 2. In the tree pane. type <yoursmsdomain>\ClientInstall 6. you will use the Configuration Manager Console to install a fallback status point. Microsoft System Center 50 . type <yourSMSServer>. Click Next. In the User name box. expand Site Systems. This is a new site system to Configuration Manager 2007. Under Available roles.

Note You should not use a value of 360 in a production environment as it could cause performance issues when deploying large numbers of clients in a very short period of time. We are doing so in the lab to get our state messages processed more quickly to allow for client deployment reports to be generated in a timely manner. The Configuration Manager Console window appears displaying the site system roles for the computer <yourSMSServer>. The Configuration Manager Console window appears. Notice that the one default parameter is the SMSSITECODE set to the local site code. The New Site Role Wizard Summary dialog box appears indicating that you have successfully completed the wizard. you will configure clients to use the fallback status point during installation of the Configuration Manager 2007 client. Microsoft System Center 51 . In the following procedure. The Client Push Installation Properties dialog box appears. expand Site Settings. In the results pane. expand Site Database. Add the following to the existing command line: FSP=<yourSMSServer> and then click OK. 8. type 360. expand Site Management. Notice that the installation method is not enabled. 3. Click Close. It does not need to be enabled for our admin controlled push installation.  To configure the use of a fallback status point 1. Notice that the fallback status point role has been added to the list. The ‗New Site Role Wizard’ Wizard Completed dialog box appears indicating that SMS is now ready to begin installation of the reporting point. The Client Push Installation Properties dialog box displays the properties to use when performing a client push. In the tree pane. click Client Push Installation. 9. and then click Next. Click Next. Click the Client tab. and then in the Actions pane. 2. and then click Client Installation Methods.7. expand <yoursitecode>. click Properties. In the Throttle interval (in seconds) box. The list of client installation methods appears in the results pane. 4. Note Complete this procedure on the virtual computer running as a Configuration Manager site server only.

The Client Push Installation Wizard Installation options dialog box appears displaying options for the client installation. 9. <yourSMSClient>. expand Site Database. In the results pane. The collection membership is updated. 7. Click Next. In the Actions pane. click Update Collection Membership. 3. In the Actions pane. The collection is updated.In the following procedure. and then click All Windows XP Systems. and the current membership of the All Windows XP Systems collection is displayed. Microsoft System Center 52 . 5. The Client Push Installation Wizard dialog box appears. In the Actions pane. Click OK. The Actions pane updates to include actions for the selected resource.  To install the Configuration Manager client 1. under <yourSMSClient>. The members of the All Windows XP Systems collection appear in the results pane. The Configuration Manager 2007 client is remotely installed on the Windows XP Professional client computer. This should include the Windows XP Professional client computer. In the tree pane. Click Next to accept the default configuration to install the client to assigned resources. 8. 6. 2. you will use the Configuration Manager Console to push the installation of the Configuration Manager client to the Windows XP Professional client. expand Computer Management. Note Complete this procedure on the virtual computer running as a Configuration Manager site server only. The Completing the Client Push Installation Wizard dialog box appears indicating it is ready to complete the installation. click <yourSMSClient>. expand Collections. in this case. click Install Client. Notice that there are no members of the collection. It will take a few minutes before the installation completes. 4. The All Windows XP Systems message box appears prompting to update subcollection membership. Click Finish. <yourSMSClient>. click Refresh.

In the following procedure, you will verify that the Configuration Manager 2007 client has been installed on the Windows XP Professional client. Note Complete this procedure on your 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 Configuration Manager 2007 client has been successfully installed.

 To verify the Configuration Manager 2007 client installation
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 SMS Agent Host service has been started. 4. Close Services.
In the following procedure, you will verify that the Windows XP Professional client has reported to the Configuration Manager site that it is installed as a Configuration Manager 2007 client.

Note Complete this procedure on the virtual computer running as a Configuration Manager site server only

 To verify the reporting of the Configuration Manager 2007 client
1. In the tree pane, expand Site Database, expand Computer Management, 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 SMS client. 2. In the Actions pane, click Update Collection Membership. The All Windows XP Systems message box appears prompting to update subcollection 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 a Configuration Manager 2007 client.

Microsoft System Center

53

Exercise 4 Reporting Configuration Manager 2007 Client Deployment Status In this exercise, you will install a reporting point for your Configuration Manager site and then run reports to verify the client deployment success in the site.

Note Complete this exercise on the site server computer only.

 To install a reporting point
1. In the tree pane, expand Site Database, expand Site Management, expand <yoursitecode>, and then expand Site Settings. The list of configurable site settings appears in the results pane. 2. In the tree pane, expand Site Systems, and then click \\<yourSMSServer>. The list of site system roles for the site server appears in the results pane. Notice that there are seven 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 Next. 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. 5. 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. 6. Click Next to use the default values. The New Site Role Wizard Summary dialog box appears indicating that you have successfully completed the wizard. 7. Click Next. The New Site Role Wizard Wizard Completed dialog box appears indicating that SMS is now ready to begin installation of the reporting point. 8. Click Close. The Configuration Manager Console window appears displaying the site system roles for the computer <yourSMSServer>. Notice that the reporting point role has been added to the list. 9. From Administrative Tools, start Services. The Services window appears. Verify that the SMS Reporting Point service is installed and running. 10. Close Services.
In the following procedure, you will run a few built in reports to validate that the reporting point is running successfully and that the client was deployed successfully.

Note

Microsoft System Center

54

Complete this procedure on the virtual computer running as a Configuration Manager site server only.

 To report Configuration Manager data
1. In the tree pane, expand Site Database, expand Computer Management, expand Reporting, and then click Reports. The list of reports appears in the results pane. 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 <sitecode>, and then click Display. An Internet Explorer window starts and displays 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 (yourADServer) and the site server (<yourSMSServer>). In your evaluation these may be on the same computer. 5. Close the ConfigMgr Report window. The Configuration Manager Console window appears displaying the current report parameters. 6. In the tree pane, click Reports. The list of reports appears in the results pane. 7. In the results pane, click Client Deployment Status Details, and then in the Actions pane, under Client Deployment Status Details, click Run. The Client Deployment Status Details report appears in the results pane. Notice that this report shows the total number of clients with any deployment status (in our case one), the number of successfully deployed clients (in our case one), and the success and failure percentages (in our case 100% success). 8. In the results pane, click Client Deployment Success Report, and then in the Actions pane, under Client Deployment Success Report, click Run. The Client Deployment Success Report appears in the results pane. Notice that this report displays that status of each client that was installed. Notice that <yourSMSClient> is listed as a successfully deployed client. You have now successfully deployed Configuration Manager 2007 in your AD environment, including site systems required for client deployment and successfully installed a client computer.

Microsoft System Center

55

Section 3: Implementing Branch Distribution Points in System Center Configuration Manager 2007 Objectives After completing this section. Configure a branch distribution point. The second virtual computer could be booted as a Windows XP Professional SP2 client installed as a Configuration Manager client in the Configuration Manager site <yourSMSClient>. one virtual computer should be booted as a Microsoft Windows Server 2003 SP2 computer installed as a Configuration Manager primary site server <yourSMSServer>. you will be able to:     Configure a standard distribution point to support BITS downloads. Configure a protected site system. Estimated time to complete this section: 75 minutes Microsoft System Center 56 . Distribute software to a client to access a branch distribution point. Prerequisites Before working on this lab.

click Update Collection Membership. The collection membership is updated. Notice that the <yourSMSClient> computer is now displayed twice. expand Site Database. 10. expand Computer Management. 2. Click OK. 6. 5. An All Systems message box appears prompting to update subcollection membership. You have now prepared your images for the lab and may proceed to Exercise 1. In the tree pane. A Confirm Delete message box appears prompting to delete the record. The members of the All Systems collection appear in the details pane. click the obsolete record for the <yourSMSClient> computer. Delete any other Obsolete records from the All Systems collection. The Configuration Manager Console window appears. and then expand Collections.Note Complete this procedure from the primary site server computer only. Update the membership for the All Windows XP Systems collection. In the details pane. and the current membership of the All Systems collection is displayed. Notice also that one of the instances is listed as being Obsolete and inactive. and then in the Actions pane. On the Start menu. 4.  To update the collection membership 1. Log on as administrator with a password of password. Click Yes. 9. click Refresh. This is the old reference of the client. In the tree pane. click Delete. 3. click ConfigMgr Console. 8. In the Actions pane. and the current membership of the All Systems collection is displayed. Notice that the <yourSMSClient> computer is now displayed only once and it is an Active record (not Obsolete). 7. The list of collections appears in the results pane. The collection membership is updated. Notice that the site server computer (<yourSMSServer>) and the Windows XP Professional client computer <yourSMSClient>appear as members. Microsoft System Center 57 . and then in the Actions pane. click All Systems.

The list of site systems configured for the site displayed in the results pane. which includes branch distribution points. The Configuration Manager Console window appears. In the Actions pane. expand <yoursitecode>. expand Site Management. and then click Server. expand Site Systems. HTTP and HTTPS (required for device clients and Internet-based clients). click ConfigMgr Console. and then click Site Systems. 2. Click Allow clients to transfer content from this distribution point using BITS. In the tree pane. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. which is required to support a branch distribution point. expand <yoursitecode>. Microsoft System Center 58 . Notice that the role is not configured to support BITS.  To configure the distribution point to support BITS downloads 1. Notice that one of the site system roles configured for the site server is as a distribution point. The list of site system roles configured for the site server computer are displayed in the results pane. The ConfigMgr distribution point Properties dialog box appears displaying the current configuration of the distribution point role on the Configuration Manager site server.Exercise 1 Configuring a Branch Distribution Point In this exercise. You will begin by configuring the distribution point on the site server to support BITS downloads.  To create a branch distribution point 1. and then click \\<yourSMSServer>. Note Complete this procedure from the primary site server computer only. 4. expand Site Settings. you will configure a branch distribution point for the site. You will configure the Windows XP client to be the branch distribution point. Notice that there is currently only one site system in the site. and then click OK. This configures the distribution point to support BITS downloads to Configuration Manager clients. 2. expand Site Database. The New Site System Server Wizard General dialog box appears. expand Site Database. 3. In the following procedure. In the results pane. on the Start menu. click Properties. select ConfigMgr distribution point. and then in the Actions pane. expand Site Management. you will create a new site system as a branch distribution point. click New. that being the site server computer. If not already running. expand Site Settings. In the tree pane.

com 5. The New Site System Server Wizard General dialog box appears. The New Boundaries dialog box appears displaying the boundaries available for protecting the site system. The New Site System Server Wizard Wizard Completed dialog box appears indicating that you have now configured the branch distribution point.domain. The New Site System Server Wizard Summary dialog box appears indicating that you have successfully completed the wizard. Click Enable this site system as a protected site system. type <yourSMSClient>. 13. Click Enable as a branch distribution point. which is not supported on a Windows XP system. The Configuration Manager Console window appears displaying the site systems in the site. 11. Click New (the icon resembles a starburst). Click Next. 9. Under Boundaries. Notice that there are now two site systems in the site. Click Close.your.path. 8. 12. The New Site System Server Wizard System Role Selection dialog box appears displaying the list of site system roles that can be assigned to this computer. In the Name box. The Boundaries dialog box appears displaying the current configuration of protected boundaries for this site system. click SCCMSite and then click OK. Microsoft System Center 59 . and then click Select Boundaries. select Distribution point.3. and then click Next. Under Available roles. Notice that by default. the site server (<yourSMSServer>) and the Windows XP client (<yourSMSClient>). The Boundaries dialog box appears displaying the current configuration of protected boundaries for this site system. type <yourSMSClient> 4. Click Next. the site system would be a standard distribution point. Notice that the Active Directory site boundary is listed as an available boundary. The New Site System Server Wizard Distribution Point dialog box appears allowing you to configure the distribution point.here. 6. Notice that the site system is now configured to be protected for only the one Active Directory site that is added as a boundary in the site. Under Intranet FQDN. Notice that there are currently no protected boundaries configured for this site system. 7. and then click Next. Notice also that the boundaries are only applicable to the distribution point and state migration point site system roles. Click OK. 10.

Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. and then in the Actions pane. expand Site Database. and then click \\<yourSMSClient>. The Distribute Software to Collection Wizard Package dialog box appears providing Microsoft System Center 60 . click Distribute. 4. you will distribute software to the Configuration Manager client. In the tree pane. Notice that both computers are installed as clients in the site. and then click Client Agents. and then click OK. BITS throttling is configured by default and could affect the download of content to the branch distribution point. and then click All Systems.  To distribute an application to a client 1. click Properties. expand Computer Management. The Distribute Software to Collection Wizard dialog box appears.14. expand Site Settings. The list of site system roles configured for the site system are displayed in the results pane. expand Site Management. The Computer Client Agent Properties dialog box appears displaying general properties. you will configure the branch distribution point to not perform BITS throttling. and then click Software. expand <yoursitecode>. Click the BITS tab. Click Not configured. The list of members of the All Systems collection appears in the results pane. This could cause delays in the download of the content to the branch distribution point. In the tree pane. Exercise 2 Distributing Software to the Configuration Manager Client In this exercise. 3.  To remove BITS throttling 1. Initially this will fail as the branch distribution point will not be configured for the package. In the results pane. The list of available client agents appears in the results pane. 2. In the tree pane. expand Site Systems. In the following procedure. Click Next. click Computer Client Agent. Notice that the Windows XP client is configured as a ConfigMgr distribution point and a ConfigMgr site system. 2. In the Actions pane. Notice that the default configuration is to perform BITS download throttling from 9 am to 5 pm daily. The list of available client agents appears in the results pane. expand Site Database. The Computer Client Agent Properties dialog box appears displaying the BITS configuration. 3. expand Collections. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console.

7. The Distribute Software to Collection Wizard Package Definition dialog box appears allowing you to select the package definition file to use. The Distribute Software to Collection Wizard Source Directory dialog box displays the designated source directory. The Browse For Folder dialog box appears. and then click Next.microsoft. The Distribute Software to Collection Wizard Source Directory dialog box appears allowing the designation of the source file directory. Under Package definition. Select Create a new package from a definition. 9. The Open dialog box appears.options for package creation or distribution.aspx?FamilyID=61E4E21F-2652-42DD-A04DB67F0573751D&displaylang=en 6. Click <yourdownloadlocation>. 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. Microsoft System Center 61 . 11. and then click OK. verify that SMS 2003 Toolkit 2 is highlighted. Click Always obtain files from a source directory. Notice the default package definitions built into Configuration Manager. Click Local drive on site server. Notice that SMS 2003 Toolkit 2 is displayed. The Distribute Software to Collection Wizard Source Files dialog box appears prompting for source file handling instructions. Click Browse.msi. 8. If you do not already have the SMS2003 Toolkit. Download and expand this.com/downloads/details. and then click Browse. and then click Next. this can be obtained from here. 5. 12. Open <yourdownloadlocation> \SMS2003Toolkit2. 4. 10. Systems Management Server 2003 Toolkit http://www.

select only the site server (<yourSMSServer>) as a distribution point. The Distribute Software to Collection Wizard Advertisement Name dialog box appears prompting for a name and comment for the advertisement. select <yourSMSServer>. Verify No. 14. 19. and then click Next. 16. Verify that No. and then click Next. 20. The Distribute Software to Collection Wizard Summary dialog box appears prompting to complete the wizard.13. 21. Click Next. 22. Under Programs. The Distribute Software to Collection Wizard Wizard Completed dialog box appears indicating the process was successful. The Distribute Software to Collection Wizard Select Program dialog box appears allowing the selection of the program to advertise. Click Next to accept the default option of advertising to subcollections as well (even though we do not have any subcollections). After Advertise the program after. Do not select the branch distribution point (<yourSMSClient>). The Distribute Software to Collection Wizard Distribution Points dialog box appears allowing the designation of distribution points to store the package files. and then click Next. Notice that both the standard (<yourSMSServer>) and branch distribution points <yourSMSClient>are listed. The Distribute Software to Collection Wizard Advertisement Subcollection dialog box appears prompting for advertising to subcollections. 17. Under Distribution points. Click Close. and then click Next. do not assign the program is selected. verify that the current date and time is displayed. The Distribute Software to Collection Wizard Assign Program dialog box appears prompting for program assignments. 15. Click Next. click Per-system unattended. Note For the purposes of this exercise. Click Next to accept the default name. The Distribute Software to Collection Wizard Advertisement Schedule dialog box appears prompting for a start and expiration time for the advertisement. Microsoft System Center 62 . this advertisement never expires is selected. 18. The list of members of the All Systems collection in the results pane.

5.In the following procedure. 3. The SMS 2003 Toolkit 2 Properties dialog box appears displaying properties for distribution point access. Also notice that the default configuration is to not require download from a protected distribution point. click SMS 2003 Toolkit 2. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. Notice only the local site server is listed. Notice that the default values are to download from fast network boundaries. 4. click Programs. In the tree pane. In the tree pane. and then expand Packages. Notice the Persystem unattended program which you advertised to the client using the Distribute Software wizard. click Advertisements. Notice the Available After time is the date and time the advertisement was created. In the tree pane. Microsoft System Center 63 . and then click OK. click Properties. click Distribution Points. You will also configure the advertisement to only allow content access from the protected distribution point. program. expand Microsoft Corporation SMS 2003 Toolkit 2 2.50. you will verify the configuration of the package. The distribution points for the package appear in the results pane. 7. Click to clear Allow clients to fallback to unprotected distribution points when the content is not available on the protected distribution point. In the results pane. The advertisement for the SMS 2003 Toolkit 2 program appears in the results pane. and then in the Actions pane under SMS 2003 Toolkit 2.  To verify package configuration 1.50. Click the Distribution Points tab.0 English. expand Computer Management. The new package appears in the tree pane. Note You may need to refresh the display to see the new advertisement. 8.0 English package data appears in the tree pane. In the tree pane. expand Software Distribution. and not run from slow network boundaries. The SMS 2003 Toolkit 2 Properties dialog box appears displaying general properties for the advertisement. 6. In the tree pane. and advertisement that were created by the Distribute Software to Collection Wizard. The Microsoft Corporation SMS 2003 Toolkit 2 2. The configured programs for the package appear in the results pane. 2. Note You may need to refresh the display to see the new package.

For this procedure. 4. Click Machine Policy Retrieval & Evaluation Cycle. Notice that the SMS 2003 Toolkit advertised program is listed with a status of Failed. 6. you will use the client running on the site server computer. Under Program Name. 7. which will include the policy related to the advertised program. refresh the display (use F5). start Configuration Manager. Note Complete this procedure from the Configuration Manager client computer on the Configuration Manager site server (<yourSMSServer>) only. The Run Advertised Programs window appears displaying new programs that are available to be installed. Software Inventory Cycle. The Configuration Manager Properties dialog box appears. The Configuration Manager Properties dialog box appears. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. and then click Run.  To search for available advertised programs 1. Notice the default actions of Branch Distribution Point Maintenance Task. Machine Policy Retrieval & Evaluation Cycle. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. Software Updates Deployment Evaluation Cycle. In Control Panel. The Run Advertised Programs window appears displaying new programs that are available to be installed. 2. Software Metering Usage Report Cycle. File Collection Cycle. Click the Actions tab. 9. Discovery Data Collection Cycle. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. Notice that the SMS 2003 Toolkit 2 program is available. and may take several minutes to complete. and then click Initiate Action. The Run Advertised Programs window appears. you will initiate the searching for advertised programs on your Configuration Manager client computer. Notice that the SMS 2003 Toolkit 2 program is available. A Cannot Run Program message box appears indicating the program can‘t run as the package source files are not available. Hardware Inventory cycle. It will take a couple of minutes. click Microsoft Corporation SMS 2003 Toolkit 2. 5. and then the New Program Available icon appears on the system tray. Click OK. Click OK. Click OK. The Configuration Manager client will request new policies.In the following procedure. In the Run Advertised Programs window. 8. Double-click the New Program Available icon. Microsoft System Center 64 . 3.

11. In the following procedure. you will view the advertisement status of the advertised program using the Software Distribution home page to verify the program installation or failure on the clients. Notice that the SMS 2003 Toolkit 2 advertisement is displayed. expand Computer Management. Status has to be summarized before it appears in the home page. the client can only access the content from the branch distribution point. Search for matching.  To report the advertisement status 1. Notice also that both the statistics and graph indicate that one client has not started the advertisement and another client failed. Click Close. Notepad displays the first occurrence of ―matching‖. Notice that the current line indicates that there was no matching distribution point found for the content location request. click Run Home Page Summarization. The Software Distribution home page appears in the results pane displaying the current advertisements.10. It will take a moment for the summarization process to complete. Notepad appears displaying the contents of the Content Access Service log file. The Software Distribution home page appears in the results pane. 3. and then click Software Distribution. In the Actions pane. And the branch distribution point does not contain the requested content. as the branch distribution point was protected for the Active Directory site that the client is a member of. and so there is no matching distribution point available for this client. 2. In the tree pane. and then open <systempartition>\Program Files\SMS_Ccm\Logs\Cas. However.log. In the Actions pane. We know that the content was distributed to the standard distribution point on the site server. Microsoft System Center 65 . click Refresh. Close Notepad. Note Complete this procedure from the primary site server computer only in the Configuration Management Console. Notice that there are no results to display. expand Site Database. 12.

 To add the package to the branch distribution point 1. expand Packages. expand Microsoft Corporation SMS 2003 Toolkit 2 2. Click Next. The Configuration Manager Properties dialog box appears. In the Actions pane. and then add the branch distribution point. Note Complete this procedure from the branch distribution point computer only (<yourSMSClient>). expand Computer Management.50. click <yourSMSClient>. expand Software Distribution. and then click Distribution Points. you will force the distribution of the content the branch distribution point. You are going to complete this procedure simply to speed up the process for the lab. click New Distribution Points. The distribution points for the package appear in the results pane. Notice that now both distribution points are listed for this package.0 English. you will verify the current distribution points for the package do not include the branch distribution point. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. the client is unable to run the program as the protected distribution point (branch distribution point) does not contain the content requested.In the following procedure. 5. 2. 3. The distribution points for the package appear in the results pane. Microsoft System Center 66 . Notice only the local site server is listed. as the content will be distributed to the branch distribution point automatically. and then click Next. The New Distribution Points Wizard Copy Package dialog box appears displaying the distribution points available for this package. Click Close.  To distribute the package to the branch distribution point 1. In the following procedure. start Configuration Manager. In Control Panel. 4. Since the advertisement is configured to only use protected distribution points. and the client is within the boundaries of the protected distribution point. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard was completed successfully. The New Distribution Points Wizard window appears. Under Distribution points. In the tree pane. You do not need to complete this procedure in a production environment. Notice that the Windows XP branch distribution point <yourSMSClient>is listed.

Click Machine Policy Retrieval & Evaluation Cycle. expand <systempartition>\SMSPKGC$. SMSPKGC$. Notice a new folder has been created. In the following procedure. This is the folder that the branch distribution point uses to store locally distributed package content. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. Discovery Data Collection Cycle. Click OK. Note Complete this procedure from the branch distribution point computer only (<yourSMSClient>). The contents of the C drive appears. 4. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. 3. Click the Actions tab. and then the content will begin being downloaded to the branch distribution point. Machine Policy Retrieval & Evaluation Cycle. and may take several minutes to complete. 5. Software Updates Deployment Evaluation Cycle. Software Metering Usage Report Cycle. and then click Initiate Action. In the console tree. Click OK. The contents of the package folder appear in the details pane.  To verify the package is distributed to the branch distribution point 1. Software Inventory Cycle. Notice that the distributed source files are now available on the branch distribution point. and then click the package folder (<yoursitecode>packagenumber. Start Windows Explorer and then view the contents of drive C.). you will verify that the content the branch distribution point has requested has been distributed locally. Hardware Inventory cycle. Notice the default actions of Branch Distribution Point Maintenance Task. The Configuration Manager Properties dialog box appears. File Collection Cycle.2. The Configuration Manager client will request new policies. It will take a couple of minutes. which will include the policy related to the branch distribution point package location. Microsoft System Center 67 . 2. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client.

and then click Run. These were installed through the SMS 2003 Toolkit 2 advertisement. In the Run Advertised Programs window. 4. Open <systempartition>\Program Files\SMS_Ccm\Logs\Cas. Notepad appears displaying the contents of the Content Access Service log file. Click Close. 2. Notice that a new program group item for the SMS 2003 Toolkit 2 appears. This is an unattended installation. start Run Advertised Programs. The list of program is displayed. Notice that the SMS 2003 Toolkit advertised program is listed with a status of Failed. 3. In Control Panel. and then on the Start menu. Wait a moment before proceeding. The Run Advertised Programs window appears. Notice that the SMS 2003 Toolkit advertised program is listed with a status of Successful. The program is installed. 6.  To run the advertised program 1.log. Click Run program automatically when download completes. so you won‘t see any installation occur. point to All Programs. in Configuration Manager. refresh the display (use F5). The list of programs in the SMS 2003 Toolkit 2 program group appears. A Program Download Required message box appears. The Run Advertised Programs window appears. Point to SMS 2003 Toolkit 2. you will run the advertised program now that the content is available on the branch distribution point. Microsoft System Center 68 . Note Complete this procedure from the Configuration Manager client computer on the Configuration Manager site server (<yourSMSServer>) only. advertised programs will be downloaded from the distribution point prior to installation. click Microsoft Corporation SMS 2003 Toolkit 2. 5. By default. Note It will take a moment to install the program. 7. Under Program Name.In the following procedure. and then click Download.

8. click Refresh. 2. The Software Distribution home page appears in the results pane displaying the current advertisements. Also notice that this is the Windows XP branch distribution point. Notice also that both the statistics and the graph indicate that one client still has not started the advertisement and the other client was successful. Search for dptype. in which case the package would have been distributed to the branch distribution point automatically after the client requested it. It will take a moment for the summarization process to complete. as indicated by the name <yourSMSClient>and the DPType (branch).  To report the advertisement status 1. In the following procedure. 11. click Run Home Page Summarization. To see what type of distribution point was used. In the Actions pane. Close CAS.com. Notice that the SMS 2003 Toolkit 2 advertisement is displayed. 9. No administrator action would be required to complete the assignment of the branch Microsoft System Center 69 . 10. In this section. in this case <yourSMSClient>. Close Notepad. You could have configured the package for distribute on demand. Notice that the highlighted line indicates the name and path of the distribution point used.log and then open LocationServices. In the tree pane. and then click Software Distribution.yourdomain. expand Site Database. Notice also that both the statistics and the graph indicate that one client has not started the advertisement and another client failed. 3. In the Actions pane. you will view the advertisement status of the advertised program using the Software Distribution home page to verify the program installation on the clients. You have now successfully implemented a branch distribution point solution in your Configuration Manager environment and verified the ability to retrieve content from the branch distribution point.log file. The Software Distribution home page appears in the results pane displaying the current advertisements. Search for download location found. Notepad displays the first occurrence of ―dptype‖. you deployed the package to the branch distribution point via an administrator action (adding the branch distribution point to the package). You also used the Software Distribution home page to validate advertisement status. you need to look in the LocationServices. Notice that the current line indicates that there was one matching distribution point found for the content location request. Notice that the SMS 2003 Toolkit 2 advertisement is displayed. Notepad displays the first occurrence of ―download location found‖.yourdomain. Note Complete this procedure from the primary site server computer only in the Configuration Management Console. Also notice that is lists the FQDN of the distribution point used. expand Computer Management.log. Notepad appears displaying the contents of the Location Service log file.

distribution point to the package in that scenario. Microsoft System Center 70 .

 Prerequisites Before working on this section. So. Verify software distribution behavior to a client in a collection with a maintenance window to allow distribution. one virtual computer should be booted as a Microsoft Windows Server 2003 SP2 computer installed as a Configuration Manager primary site server (<yourSMSServer>. It will reside on the branch DP as well as the standard DP. The package you may have deployed in the previous section will already have been created and distributed. Verify software distribution behavior to a client in a collection that is configured with a maintenance window to restrict distributions.Section 4: Implementing Maintenance Windows for Software Distribution in System Center Configuration Manager 2007 Objectives After completing this section. remove the package from all locations. you will be able to:   Configure maintenance windows on collections. Make a note of your site code for the installed site. consider a 2 nd package for distribution here. Estimated time to complete this section: 75 minutes Microsoft System Center 71 . or advertise your package as an uninstall to complete this section. The second virtual computer is booted as a Windows XP Professional SP2 client installed as a Configuration Manager client in the Configuration Manager site (<yourSMSClient>).

The list of collections appears in the results pane. and then expand Collections. In the Actions pane. click All Systems.Note Complete this procedure from the primary site server computer only. In the details pane. Delete any other Obsolete records from the All Systems collection. On the Start menu. You have now prepared your images for the lab and may proceed to Exercise 1. The members of the All Systems collection appear in the details pane. 10. and then in the Actions pane. Click OK. Update the membership for the All Windows XP Systems and All Windows Server 2003 Systems collections. In the tree pane. click Update Collection Membership. click the obsolete record for the <yourSMSClient> computer. Microsoft System Center 72 . 3. 4. Click Yes. 9. Notice that the site server computer (<yourSMSServer>) and the Windows XP Professional client computer <yourSMSClient>appear as members. The Configuration Manager Console window appears. Log on as administrator with a password of password. 2. and the current membership of the All Systems collection is displayed. click Refresh. The collection membership is updated. An All Systems message box appears prompting to update subcollection membership. The collection membership is updated. This is the old reference of the client. expand Site Database. click Delete. expand Computer Management.  To update the collection membership 1. Notice also that one of the instances is listed as being Obsolete and inactive. click ConfigMgr Console. Notice that the <yourSMSClient> computer is now displayed only once and it is an Active record (not Obsolete). 7. and then in the Actions pane. Notice that the <yourSMSClient> computer is now displayed twice. 6. A Confirm Delete message box appears prompting to delete the record. and the current membership of the All Systems collection is displayed. 5. 8. In the tree pane.

click ConfigMgr Console. In the Actions pane. update the collection membership and then refresh until it does display the site server (<yourSMSServer>). Notice that there is one Configuration Manager client in the collection (<yourSMSServer>) but that the Windows XP client <yourSMSClient>is not a member of the collection. click Modify Collection Settings. In the Start box. In the tree pane. there are no maintenance windows configured for the collection. You will configure a maintenance window to prevent software distribution to server computers. 7. on the Start menu. The All Windows Server 2003 Systems Settings dialog box appears displaying maintenance windows for the collection. The All Windows Server 2003 Systems Settings dialog box appears displaying maintenance windows for the collection. expand Collections. type Future window 6. 3. not today. you will configure maintenance windows on collections. 4.Exercise 1 Configuring Maintenance Windows on Collections In this exercise. Click New (the icon resembles a starburst). and then configure a maintenance window to allow distribution to Windows XP clients. You need at least a 15 minute window for this exercise.  To configure a maintenance window to prevent software distribution 1. expand Computer Management. Click OK. set the date to tomorrow. set the starting time to be the top of the next hour. 5. If not already running. expand Site Database. 9. 2. The <new> Schedule dialog box appears allows the configuration of a maintenance window for the collection. In the End. Notice that the new maintenance window is displayed for the collection. 8. Notice that by default. Note Complete this procedure from the primary site server computer only. The list of members of the All Windows Server 2003 Systems collection appears in the results pane. In the Effective date box. Make sure your configuration creates a maintenance window that will prevent the server computer from running the advertised program today and has a duration of at least 15 minutes. Microsoft System Center 73 . Make sure you choose tomorrow‘s date. and then click All Windows Server 2003 Systems. set the starting time to be the top of the current hour. The Configuration Manager Console window appears. In the Name box. Note If your collection does not display the site server computer as a member.

3. expand Collections. set the starting time to be two hours from the current time. In the End. The list of members of the All Windows Server 2003 Systems collection appears in the results pane. click Modify Collection Settings. you will create a maintenance window that will allow the Windows XP SCCM client to run an advertised program. Notice that by default. Click OK. Notice that the new maintenance window is displayed for the collection. The list of members of the All Windows XP Systems collection appears in the results pane. 7. expand Site Database. 8. 9. 6. In the following procedure. and then click All Windows XP Systems. Click OK. In the tree pane. but to give yourself plenty of time. Click OK. In the Actions pane. set the time to the top of the current hour. there are no maintenance windows configured for the collection. expand Computer Management. The All Windows XP Systems Settings dialog box appears displaying maintenance windows for the collection. The <new> Schedule dialog box appears allows the configuration of a maintenance window for the collection. Notice that there is only one Configuration Manager client in the collection <yourSMSClient>and that the server computer (<yourSMSServer>) is not a member of the collection. 4. type Weekly window 5. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. Click New (the icon resembles a starburst). verify that today‘s date is displayed. 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. The list of members of the All Windows XP Systems collection appears in the results pane.  To configure a maintenance window to allow software distribution 1. Microsoft System Center 74 . You should not need two hours. In the Start box. 2.10. In the Effective date box. The All Windows XP Systems Settings dialog box appears displaying maintenance windows for the collection. you are configuring a two hour window. In the Name box.

In the results pane. scroll to the right until you can view the Maintenance Windows column. click Run. In the tree pane. and then in the Actions pane. Notice that the two collections you configured earlier are identified as having maintenance windows. In the tree pane.In the following procedure. Note Complete this procedure from the primary site server computer only in the Configuration Management Console. expand Site Database. In the results pane. Microsoft System Center 75 . expand Site Database. 5. The Maintenance Windows column now appears sorted by the appropriate value. 2. under Maintenance Windows Available to a Particular Client. In the Actions pane. In the results pane. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. In the following procedure. expand Computer Management. In the results pane. The list of collections appears in the results pane. you will view the collections with maintenance windows. The list of collections appears in the results pane including the listing of whether or not each collection includes a maintenance window. click the Maintenance Windows column to sort by the maintenance window attribute.  To identify collections with maintenance windows 1. The list of reports appears in the results pane. 4. drag the Maintenance Windows column to appear after Name. click Refresh. 2. expand Computer Management. and then click Collections. The Maintenance Windows Available to a Particular Client Report Information report appears in the results pane. expand Reporting. you will view the maintenance windows available to the Configuration Manager clients using Configuration Manager reporting. The Maintenance Windows column now appears right after Name.  To identify maintenance windows available to a client 1. with the collections containing maintenance windows at the bottom of the display. 3. click Maintenance Windows Available to a Particular Client. As this is a prompted report. and then click Reports. if necessary. you must supply the computer name of the client you wish to view the maintenance windows for.

In the Client Name box. and then click Display. Close the ConfigMgr Report window. type <yourSMSClient>. Notice that there is one maintenance window available to the client. duration. Microsoft System Center 76 . and other values for the maintenance window. An Internet Explorer window starts and displays the Maintenance Windows Available to a Particular Client report. The Configuration Manager Console window appears displaying the Maintenance Windows Available to a Particular Client Report Information report in the results pane. Notice also that this report shows the start time. 4.3.

The Configuration Manager Properties dialog box appears. 3. Note Complete this procedure from each of the SCCM clients. It will take a couple of minutes to evaluate and implement the policy. Click the Actions tab. Click Machine Policy Retrieval & Evaluation Cycle. File Collection Cycle. you will force the clients to retrieve policies. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. Click OK.Exercise 2 Implementing the Maintenance Windows on the Configuration Manager Clients In this exercise. Open C:\Program Files\SMS_CCM\Logs Notepad appears displaying the contents of the Service Window Manager log file. Software Metering Usage Report Cycle. 6. Software Updates Deployment Evaluation Cycle.  To implement the maintenance windows 1. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. Software Inventory Cycle. and then click Initiate Action. and may take several minutes to complete. start Configuration Manager. Hardware Inventory cycle. Click OK. 2. 4. 5. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. Notice the default actions of Branch Distribution Point Maintenance Task. The Configuration Manager client will request new policies. Microsoft System Center 77 . Discovery Data Collection Cycle. In Control Panel. The Configuration Manager Properties dialog box appears. Machine Policy Retrieval & Evaluation Cycle. which will include the policy related to the maintenance window. which will implement the appropriate maintenance windows on the clients.

Microsoft System Center 78 . Search for New service window. you will see lines referring to: 8. Close Notepad. 23 hours…‖. If you are looking at the Windows XP client. Notice that the current line indicates that there was a new service window policy implemented. you will see lines referring to:         Scheduling the StartTime for today The duration of two hours The Active Service Windows list has 1 window Programs can run Scheduling the StartTime for a week from today The duration of an hour No windows in the Active Service Windows list ―Scheduling the timer to fire in 0 days. Notepad displays the first occurrence of ―new service window‖. If you are looking at the site server computer.7.

and then click All Systems. Notice the default package definitions built into SCCM 2007. 7. The Distribute Software to Collection Wizard Package dialog box appears providing options for package creation or distribution. Click Next. click Distribute. and then click Software. Under Package definition. Click Always obtain files from a source directory. The Distribute Software to Collection Wizard Package Definition dialog box appears allowing you to select the package definition file to use. The Browse For Folder dialog box appears. The Distribute Software to Collection Wizard dialog box appears. and then click Next. Open <download location>\SMS Toolkit\SMS2003Toolkit2. In the Actions pane. 9. Click <download location>\SMS Toolkit. Notice that SMS 2003 Toolkit 2 is displayed. Click Browse. In the tree pane. and then click Browse. The Distribute Software to Collection Wizard Source Directory dialog box displays the designated source directory. The Distribute Software to Collection Wizard Package Definition dialog box appears allowing you to select the package definition file to use. The Distribute Software to Collection Wizard Source Directory dialog box appears allowing the designation of the source file directory. expand Computer Management.msi. 5. 10. 2. Notice that both computers are installed as clients in the site. The Distribute Software to Collection Wizard Source Files dialog box appears prompting for source file handling instructions. Click Local drive on site server. 3.  To distribute an application to the clients 1. 6.Exercise 3 Distributing Software to the Configuration Manager Clients In this exercise. expand Site Database. The list of members of the All Systems collection appears in the results pane. and then click OK. you will distribute software to the Configuration Manager clients. You will distribute to the All Systems collection to include both clients. expand Collections. 8. and then click Next. Note Complete this procedure from the primary site server computer only in the Configuration Management Console. The Open dialog box appears. and then click Next. 4. verify that SMS 2003 Toolkit 2 is highlighted. Microsoft System Center 79 . Select Create a new package from a definition.

The Distribute Software to Collection Wizard Summary dialog box appears prompting to complete the wizard. assign the program. 21. 22. Click Next. Click Next. and then click Next. this advertisement never expires is selected. The Distribute Software to Collection Wizard Wizard Completed dialog box appears indicating the process was successful. 17. The time configured should fit within the time frame of the maintenance window configured for the All Windows XP Systems collection. The Distribute Software to Collection Wizard Advertisement Schedule dialog box appears prompting for a start and expiration time for the advertisement. The Distribute Software to Collection Wizard Advertisement Name dialog box appears prompting for a name and comment for the advertisement. Under Distribution points. Click Close. Click Next to accept the default name. verify that the current date and time is displayed. 12. The Distribute Software to Collection Wizard Distribution Points dialog box appears allowing the designation of distribution points to store the package files. 16. The Distribute Software to Collection Wizard Select Program dialog box appears allowing the selection of the program to advertise. select <yourSMSServer>. and then click Next. 13. Notice that only the site server distribution point (<yourSMSServer>) is listed. Click Next. The Distribute Software to Collection Wizard Assign Program dialog box appears prompting for program assignments. 15. verify that the current time is listed. Verify No. The Distribute Software to Collection Wizard Advertisement Subcollection dialog box appears prompting for advertising to subcollections. 18. In the Assign after box.11. The list of members of the All Systems collection in the results pane. Click Next to accept the default option of advertising to subcollections as well (even though we do not have any subcollections). Microsoft System Center 80 . Under Programs. 19. 14. After Advertise the program after. and then click Next. 20. click Per-system unattended. Click Yes.

Notice that the maximum run time is set to unknown. 7. The Per-system unattended Properties dialog box appears displaying general properties for the program. The distribution points for the package appear in the results pane.50. The new package appears in the tree pane. Notice only the local site server is listed. When the program is processed on the client.0 English package data appears in the tree pane. Note You may need to refresh the display to see the new advertisement.  To verify package configuration 1. 5. Note Complete this procedure from the primary site server computer only in the Configuration Management Console. Notice the command line used. The Per-system unattended Properties dialog box appears displaying requirements for the program. program. The Microsoft Corporation SMS 2003 Toolkit 2 2. Click the Requirements tab. The configured programs for the package appear in the results pane. click Distribution Points. and then in the Actions pane. 3. expand Microsoft Corporation SMS 2003 Toolkit 2 2.50. expand Computer Management. Notice that the Persystem unattended program now displays a maximum run time of 5 minutes. expand Software Distribution. and ―Unknown‖ value is assumed to be larger than our window.0 English.In the following procedure. In the tree pane. and then expand Packages. click Per-system unattended. Microsoft System Center 81 . In the tree pane. and advertisement that were created by the Distribute Software to Collection Wizard. 6. you will verify the configuration of the package. 4. Notice the Persystem unattended program which you advertised to the client using the Distribute Software wizard. click Programs. 2. In the tree pane. The advertisement for the SMS 2003 Toolkit 2 program appears in the results pane. type 5 and then click OK. In the tree pane. In the results pane. In the tree pane. Note You may need to refresh the display to see the new package. The configured programs for the package appear in the results pane. so you need to set the max run time value to fit within our window. click Properties. Notice the Available After time is the date and time the advertisement was created. In the Maximum allowed run time (minutes) box. click Advertisements. 8.

4. File Collection Cycle. and you will not see any user interface. you will initiate the searching for advertised programs on your Configuration Manager client computer. this will be a silent installation. If you are looking at the site server computer. start Configuration Manager. you will see an Assigned Program About to Run icon appears in the system tray. Click Run. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. 7. 6. Software Inventory Cycle. If you are looking at the Windows XP client computer.In the following procedure. The Program Countdown Status dialog box appears indicating an assigned program will run within the next five minutes. For this procedure. The Configuration Manager client will request new policies. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. The Configuration Manager Properties dialog box appears.  To search for available advertised programs 1. It will take a couple of minutes to evaluate and implement the policy. Hardware Inventory cycle. as the program will not run. Click OK. Software Metering Usage Report Cycle. The install will only take a minute to complete. The Configuration Manager Properties dialog box appears. Software Updates Deployment Evaluation Cycle. The program will attempt to install. 3. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. Click the Actions tab. Click Machine Policy Retrieval & Evaluation Cycle. Microsoft System Center 82 . Double-click the Assigned Program About to Run icon. Note Complete this procedure from each of the SCCM client computers in the site. In Control Panel. which will include the policy related to the advertised program. Since you advertised the ―Per-system unattended‖ program. 2. Notice the default actions of Branch Distribution Point Maintenance Task. Machine Policy Retrieval & Evaluation Cycle. Click OK. 5. Discovery Data Collection Cycle. and may take several minutes to complete. you will use the client running on the Configuration Manager site server computer. you will not see anything occur. and then click Initiate Action.

Notepad appears displaying the contents of the Execution Manager‘s log file. 2. you will verify that the advertised program did indeed run on the Windows XP client computer.In the following procedure.  To verify that the program did not install 1. The All Programs menu appears. In the following procedure. Search for service window. Notice that there is no new menu titled SMS 2003 Toolkit 2 as was displayed on the Windows XP client computer. On the Start menu. The first occurrence of ―per-system‖ is highlighted. 4. Notepad appears displaying the contents of the Execution Manager‘s log file. The first occurrence of ―per-system‖ is highlighted.log. Notice that a new menu titled SMS 2003 Toolkit 2 appears. 6. Close Notepad. This is a confirmation that the advertised program did install successfully on the client in the configured service window. you will verify that the advertised program did not run on the Windows Server 2003 client computer. Search for per-system. Microsoft System Center 83 . Point to SMS 2003 Toolkit 2. 3. Open %Windows%\System32\Ccm\Logs\Execmgr. On the Start menu.log. 5. This line indicates a policy for the per-system unattended program was received. The SMS 2003 Toolkit 2 menu appears. Note Complete this procedure from the Windows Server 2003 client computer (<yourSMSServer>) only. 3. This line indicates a policy for the per-system unattended program was received. The first occurrence of ―service window‖ is highlighted. Search for per-system. point to All Programs. Open <systempartition>\Program Files\SMS_Ccm\Logs\Execmgr. Note Complete this procedure from the Windows XP client computer <yourSMSClient>only. point to All Programs. 2. Remember that the program you advertised was the per-system unattended program.  To verify the program installation 1. Remember that the program you advertised was the per-system unattended program. The All Programs menu appears. This line indicates that the service window does allow the program to run.

The Status of a specific advertisement report appears in the results pane. In the Actions pane. 4. click Refresh. under Advertisement. In the following procedure. The Software Distribution home page appears in the results pane displaying the current advertisements. The All system resources for a specific advertisement in a specific state report appears. one was successful in running the program. In the Actions pane. and one that is listed as ―waiting‖. 5. Status has to be summarized before it appears in the home page. and then click the arrow to the left of ―Waiting‖.4. and then click Software Distribution. Search for service window. Close Notepad. Notice that the last line in the log indicates the client is waiting for a service window. Click Back. 5. The Software Distribution home page appears in the results pane. 3. The All system resources for a specific advertisement in a specific state report appears. In the tree pane. In the results pane.  To report the advertisement status 1. Microsoft System Center 84 . 2. The first occurrence of ―service window‖ is highlighted. This line indicates that the program could not run due to a service window restriction. expand Site Database. click SMS 2003 Toolkit 2. Notice that there were two clients that received the advertisement. It will take a moment for the summarization process to complete. 6. you will view the advertisement status of the advertised program using the Software Distribution home page to verify the program installation or failure on the clients. Notice that the SMS 2003 Toolkit 2 advertisement is displayed. Notice also that the graph shows one client successfully ran the advertisement and another client is in a waiting state. Notice that the client listed is the Windows Server 2003 client (<yourSMSServer>) and that the last status is ―Waiting for a Service Window‖. Note Complete this procedure from the primary site server computer only in the Configuration Management Console. expand Computer Management. Notice that one client listed is the Windows XP client <yourSMSClient>and that the last status is ―Program completed with success‖. Notice that there are no results to display. click Run Home Page Summarization. Click the arrow to the left of ―Succeeded‖.

In the following procedure, you will create a maintenance window that will allow all members of the All Systems collection to run an advertised program.

Note Complete this procedure from the primary site server computer only in the Configuration Manager Console.

 To configure a maintenance window for All Systems
1. In the tree pane, expand Site Database, expand Computer Management, expand Collections, and then click All Systems. The list of members of the All Systems collection appears in the results pane. Notice that both clients are members of this collection. 2. 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. 3. Click New (the icon resembles a starburst). The <new> Schedule dialog box appears allows the configuration of a maintenance window for the collection. 4. In the Name box, type Daily window 5. In the Effective date box, verify that today‘s date is displayed. 6. In the Start box, set the time to the top of the current hour. 7. 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 clients to run the advertised program as the window is current. Even though the server computer is a member of another collection with a restricted window, Configuration Manager performs a union of all available windows for the client to identify availability. 8. Under Recurrence pattern, 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. 9. Click OK. The list of members of the All Systems collection appears in the results pane.

Microsoft System Center

85

In the following exercise, you will force the clients to retrieve policies, which will implement the appropriate maintenance windows on the clients.

Note Complete this procedure from each of the Configuration Manager clients.

 To implement the maintenance windows
1. In Control Panel, start Configuration Manager. The Configuration Manager Properties dialog box appears. 2. Click the Actions tab. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. Notice the default actions of Branch Distribution Point 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 Deployment Evaluation Cycle, User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. 3. Click Machine Policy Retrieval & Evaluation Cycle, and then click Initiate Action. The Configuration Manager client will request new policies, which will include the policy related to the maintenance window. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated, and may take several minutes to complete. 4. Click OK. The Configuration Manager Properties dialog box appears. 5. Click OK. It will take a couple of minutes to evaluate and implement the policy. On the server computer, an Assigned Program About to Run icon appears in the system tray. 6. 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. 7. 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. On the Windows XP client computer, you will see nothing new, as the program has already run.

Microsoft System Center

86

In the following procedure, you will verify that the advertised program did indeed run on the Windows Server 2003 client computer that failed to run the program earlier.

Note Complete this procedure from the Windows Server 2003 client computer (<yourSMSServer>) only.

 To verify the program installation
1. On the Start menu, point to All Programs. The All Programs menu appears. Notice that a new menu titled SMS 2003 Toolkit 2 appears. 2. Point to SMS 2003 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.
In the following procedure, you will view the advertisement status of the advertised program using the Software Distribution home page to verify the program installation.

Note Complete this procedure from the primary site server computer only in the Configuration Management Console.

 To report the advertisement status
1. In the tree pane, expand Site Database, expand Computer Management, and then click Software Distribution. The Software Distribution home page appears in the results pane displaying the current advertisements. Notice that the SMS 2003 Toolkit 2 advertisement is displayed. Notice also that the graph shows one client successfully ran the advertisement and another client is in a waiting state. 2. In the Actions pane, click Run Home Page Summarization. It will take a moment for the summarization process to complete. 3. In the Actions pane, click Refresh. The Software Distribution home page appears in the results pane displaying the current advertisements. Notice that the SMS 2003 Toolkit 2 advertisement is displayed. Notice also that the graph shows both clients successfully ran the advertisement. 4. In the results pane, under Advertisement, click SMS 2003 Toolkit 2. The Status of a specific advertisement report appears in the results pane. Notice that there were two clients that received the advertisement and both were successful in running the program.

Microsoft System Center

87

and verified software distribution behavior using the maintenance windows. You have also used the Software Distribution home page and reports to validate deployment success. Microsoft System Center 88 . Notice that both clients are listed with a last status of ―Program completed with success‖. Click the arrow to the left of ―Succeeded‖.5. You have now successfully implemented maintenance windows in Configuration Manager 2007. The All system resources for a specific advertisement in a specific state report appears in the results pane.

Before You Begin In this lab. you must configure Virtual PC networking configuration to ―Local only‖. Deploy the Windows Vista image to a Windows XP client computer. one virtual computer should be started as a primary site server running Configuration Manager. Install a Configuration Manager State Migration Point to store user state information. Image a Windows Vista client computer. The site code for the installed site is <yoursitecode>. Import the Windows Vista image into Configuration Manager as an OS image package.0 to capture and restore user state information. Create an Operating System Capture Disk. There are no requirements for any connections outside the VPC image. A second virtual computer should be running as a Windows Vista Configuration Manager client computer to be imaged . and as OSD requires DHCP. you will be able to:       Install USMT 3. The final virtual computer is a Windows XP Professional Configuration Manager client to be upgraded to Windows Vista using the OS deployment feature of Configuration Manager 2007. Estimated time to complete this section: 75 minutes Microsoft System Center 89 .Section 5: Deploying Operating System Images Using System Center Configuration Manager 2007 Objectives After completing this lab.

This collection will be targeted for deployment later in this lab. A Confirm Delete message box appears prompting to delete the record. Notice that there are four members in the collection. 2. 5. Delete any other Obsolete records from the All Systems collection. and the current membership of the All Systems collection is displayed. 3.Note Complete this procedure from the primary site server computer only.  To update the collection membership 1. 4. 7. click ConfigMgr Console. 8. and then in the Actions pane. click Update Collection Membership. click All Systems. 9. In the tree pane. Notice that the <yourSMSClient> computer is now displayed twice. expand Site Database. In the tree pane. Update the collection membership for the All Windows XP Professional Systems collection. Notice also that one of the instances is listed as being Obsolete and inactive. Log on as administrator with a password of password. In the Actions pane. In the details pane. This is the old reference of the client. and then expand Collections. The list of collections appears in the results pane. click the obsolete record for the<yourSMSClient> computer. Notice that the <yourSMSClient> computer is now displayed only once and it is an Active record (not Obsolete). and the current membership of the All Systems collection is displayed. An All Systems message box appears prompting to update subcollection membership. The Configuration Manager Console window appears. and then in the Actions pane. The collection membership is updated. click Refresh. 10. expand Computer Management. The members of the All Systems collection appear in the details pane. You have now prepared your images for the lab and may proceed to Exercise 1. The collection membership is updated. Click OK. Click Yes. On the Start menu. 6. Microsoft System Center 90 . click Delete.

com/WindowsVista/en/library/91f62fc4-621f-4537-b3111307df0105611033.microsoft. and then grant administrators full control to the USMT share. 3. and then click Next. point to Administrative Tools. USMT 3. The Software Update Installation Wizard dialog box appears. Create a new user named NetworkAccess with a password of password and ensuring that the password does not have to be changed at next logon. Click I Agree.0 1. Download User State Migration Tool 3. 6. Start <download location>\USMT30\InstallUsmt30_x86_2000andXP.  To install USMT 3. 3. Close Active Directory Users and Computers.0 – located at the following link.exe. In the following procedure. the Software Update Installation Wizard dialog box appears indicating the installation was successful. Note Complete this exercise from the primary site server only. You will begin by installing the User State Migration Tool version 3. Microsoft System Center 91 . which is used by Configuration Manager 2007 to back up and restore user state information.Exercise 1 Preparing the Environment for Configuration Manager OSD In this exercise. The Software Update Installation Wizard License Agreement dialog box appears. you will prepare the Configuration Manager environment for deploying operating system images using OSD. Share the <systempartition>\Program Files\USMT30 folder as USMT. 2. Click Finish. 5. you will create an account that will be used as the Network Access Account. 4.mspx?mfr=true 2.0. The Active Directory Users and Computers window appears. Note Complete this exercise from the site server computer  To create a user account to be assigned as the Network Access Account 1. Click Next. and then click Active Directory Users and Computers.0 is installed. On the Start menu. http://technet2. When complete.

In the tree pane. The Windows User Account dialog box appears prompting for the account and password to configure as the Advanced Client Network Access Account. The Configuration Manager Console window appears. expand Software Distribution. click Computer Client Agent. This account is used by the client to access the Configuration Manager distribution point when booted under WinPE. you will create the Configuration Manager package that OSD will use to install the Configuration Manager client after distributing the new operating system image. 2. The list of client agents appears in the results pane.In the following procedure. click Set. expand <yoursitecode>. Microsoft System Center 92 .  To create a Network Access Account 1. The Configuration Manager Console window appears. click Properties. expand Site Database. 5. expand Site Database. In the Password and Confirm password boxes. on the Start menu. expand Site Management. If not already running. and then click Client Agents. Click OK. In the following procedure. In the result pane. 4. Notice that there are no packages created at this point.  To create a Configuration Manager Client installation package 1. you will configure the required Network Access Account in the Configuration Manager Console. and then click Packages. click ConfigMgr Console. 7. type password and then click OK. The list of packages for the site appears in the results pane. In the Name box. Note Complete this exercise from the primary site server with the Configuration Manager Console running and active. expand Site Settings. and then in the Actions pane. 3. The Computer Client Agent Properties dialog box appears displaying properties for the Computer Client Agent. After Network Access Account. The Computer Client Agent Properties dialog box appears displaying general properties. In the tree pane. Note Complete this exercise from the primary site server with the Configuration Manager Console running and active. type <domainname>\NetworkAccess 6. expand Computer Management.

Click <systempartition>\Program Files\Microsoft Configuration Manager\Client. The distribution points for this package appear in the results pane. The Create Package from Definition Wizard Source Directory dialog box displays the configured source directory. The Create Package from Definition Wizard Summary dialog box appears indicating the wizard is ready to create the package. 4. and then click Microsoft Configuration Manager Advanced Client Upgrade. The Create Package from Definition Wizard Package Definition dialog box appears allowing you to select the package definition file to use. Notice that there is only one program for this package. The Create Package from Definition Wizard Source Files dialog box appears prompting for source file handling instructions. Click Always obtain files from a source directory. and then click Package From Definition. 14. The Create Package from Definition Wizard Source Directory dialog box appears allowing the designation of the source file directory. Notice the default package definitions built into Configuration Manager 2007 include the Configuration Manager Client Upgrade package definition. click New Distribution Points. Click Finish. Click Next. click Configuration Manager Client Upgrade. Click Next. and then click Next. 13. and then click OK. and then click Browse. click Distribution Points. In the tree pane. In the tree pane. The New Distribution Points Wizard window appears. 3. Notice that there are no distribution points assigned to this package yet. The programs for the package appear in the results pane. The wizard completes the package creation and then the Configuration Manager Console appears displaying the packages in the site. that being a silent upgrade. 7. 10. The Browse For Folder dialog box appears. 12. Notice that the Configuration Manager Client Upgrade package is displayed. In the tree pane. click Programs. 8. 5. 6. In the Actions pane. In the Actions pane. Under Package definition. 9. and then click Next. click New. The package objects appear in the tree pane. The Create Package from Definition Wizard dialog box appears. expand Packages. Click Local drive on site server. Microsoft System Center 93 . Click Next. expand Microsoft Configuration Manager Client Upgrade. 11.2.

15. The New Package Wizard General dialog box appears prompting for the package name. In the Name box. click New. and then click Package. Click <systempartition>\Program Files\Usmt30. 5. The list of packages in the site appears in the results pane. and then click Packages. 9. 16. Under Distribution points. and then click Set. The New Package Wizard Distribution Settings dialog box appears allowing configuration of the download of package source files to branch distribution points. Note Complete this exercise from the primary site server with the Configuration Manager Console running and active. Notice that there is no package created for USMT. expand Site Database. Click This package contains source files. The package is copied to the designated distribution point. The New Package Wizard Data Source dialog box appears displaying the current configuration for the source files for the package.The New Distribution Points Wizard Copy Package dialog box appears displaying the list of distribution points for the package. In the Actions pane. The Set Source Directory dialog box appears displaying the source file location. The New Package Wizard Data Access dialog box appears allowing configuration of the access to the package source files. In the following procedure. Click Close. The New Package Wizard Data Source dialog box appears allowing you to configure source files for the package. you will create the Configuration Manager package that OSD will use to migrate user state while distributing the new operating system image. The Set Source Directory dialog box appears prompting for source file location. Click Local drive on site server. Microsoft System Center 94 . 2. The Browse For Folder dialog box appears. 3. 4. and then click Browse. type USMT and then click Next.  To create a USMT package 1. and then click Next. Click Next to accept the default of the standard ConfigMgr package share. 8. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard was successfully completed. and then click OK. click <yourSMSServer>. In the tree pane. 7. Click OK. Click Next. expand Software Distribution. expand Computer Management. 6.

You do not need to configure a program for the USMT package. click New Distribution Points. Notice that the USMT package is displayed in the list of packages. 11. The Configuration Manager Console appears displaying the packages in the site. click Distribution Points. In the Actions pane. The package is copied to the designated distribution point. 18. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard has completed successfully. Click Next to use the default security rights. The New Distribution Points Wizard window appears. The New Package Wizard Reporting dialog box appears prompting for the values to use when matching status mif values. expand Packages. click Programs. Click Next to use the default package properties as the mif matching values. 20. Notice that there are no distribution points assigned to this package yet. Click Close. In the tree pane. 13. 19. click <yourSMSServer>. Click Next. 15. Click Next. The programs for the package appear in the results pane. 17. 16. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of distribution points for the package. and then click USMT. The New Package Wizard Security dialog box appears prompting for security rights to be created for this package. 21. Microsoft System Center 95 . 14. The distribution points for this package appear in the results pane. Under Distribution points.10. Click Next to accept the default to automatically download to branch distribution points and complete the wizard. Notice that there are no programs created for the package. 12. The wizard completes the package creation and then the New Package Wizard Confirmation dialog box appears indicating the package creation was successful. Click Close. In the tree pane. The package options appear in the tree pane. expand USMT. In the tree pane. The wizard completes the package creation and then the New Package Wizard Summary dialog box appears indicating the wizard completed the package creation. and then click Next.

expand Site Database. Note Complete this exercise from the primary site server with the Configuration Manager Console running and active. Under Distribution points. In the Actions pane. Microsoft System Center 96 . and then in the Actions pane. expand Boot Images. expand Site Systems. click New Distribution Points. expand <yoursitecode>. Notice that there are no distribution points assigned to this boot image yet. The boot image is used to start the computer with WinPE for capturing the operating system image as well as prior to deploying the operating system image to a system. 3. 2. 6. 2. and then click Boot Images. expand Operating System Deployment. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of available distribution points for the boot image. and then click Next. expand Site Database. it may take a couple minutes to completely distribute to the distribution point. The list of boot images in the site appears in the results pane. 5. click <yourSMSServer>. Click Next. The boot image is copied to the designated distribution point. In the tree pane.  To distribute the boot package 1. expand Site Settings. As boot images are larger in size. and then click Site Systems.  To create a state migration point 1. In the tree pane. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard has completed successfully. you will create a State Migration Point for the site. expand Computer Management. In the tree pane. In the tree pane. 4. The New Site Role Wizard General dialog box appears. expand Site Management. you will distribute the boot image package to a distribution point. The New Distribution Points Wizard window appears. Notice that there are two boot images for various platforms. Click Close. Note Complete this exercise from the primary site server with the Configuration Manager Console running and active. click New Roles. The state migration point is used by USMT to store the state information during operating system image deployment. click <yourSMSServer>.In the following procedure. The list of site systems configured for the site displayed in the results pane. In the following procedure. expand Boot image (x86) (assuming x86 systems are used) . The distribution points for this package appear in the results pane. and then click Distribution Points.

9. 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. Click Next. and the required minimum free disk space of 100 MB. 8. The New Site Role Wizard Wizard Completed dialog box appears indicating that you have now configured the state migration point and it is currently being installed. 6. state information is removed one day after successful restore. The Storage Folder dialog box appears allowing you to configure the drive to use to maintain the user state information. select State migration point. Notice that the default values of a maximum of 100 clients storing state on the state migration point. 7. Notice that the state migration point role is now listed for the site system. Click Close. It will take a minute to install the state migration point. Click Next. 4. The New Site Role Wizard General dialog box appears displaying the current configuration of the state migration point. 5. and then click Next. Notice also that by default. The Configuration Manager Console window appears displaying the site systems for the computer. In the Storage folder box.3. The New Site Role Wizard State Migration Point dialog box appears allowing you to configure the state migration point. Microsoft System Center 97 . type C:\Userstate and then click OK. Under Available roles. The New Site Role Wizard Summary dialog box appears indicating that you have successfully completed the wizard. Click New (the icon resembles a starburst). Click Next to accept the current configuration to remove the state after 1 day.

Exercise 2 Creating a Capture Media Task Sequence In this exercise.  To create the Capture Media task sequence 1. expand Computer Management. In the tree pane. 3. When complete. Click Next. type C:\Capture. In the tree pane. Note Complete this exercise from the site server computer only in the Configuration Manager Console. The operating system deployment items appear in the tree pane. The Task Sequence Media Wizard Boot Image dialog box appears displaying the selected boot image and distribution point to use. expand Site Database. In the Actions pane. 8. Verify that CD/DVD set is selected. The Task Sequence Media Wizard Summary dialog box appears indicating the wizard is complete and is ready to create the media. bootable. 6. Click Capture media. 10. 7. 9. The task sequences for the site appear in the results pane. and then click Next. and then expand Operating System Deployment. The task sequence media is created. The Task Sequence Media Wizard Select Media Type window appears prompting for the type of task sequence media to create: either a standalone. Notice that there are no task sequences yet. The Task Sequence Media Wizard Media Type dialog box appears prompting for the type of media to create: either a USB flash drive or a CD/DVD. The Select a Boot Image dialog box appears displaying the boot images available. 5. 2. click Create Task Sequence Media. In the Media file box. Click Next. Click Boot image (x86)(assuing x86 systems are used) and then click OK. The Task Sequence Media Wizard Boot Image dialog box appears prompting for the boot image to use. You need to create a task sequence that will allow you to capture an operating system image. you will create a task sequence that will be used to capture the Windows Vista client computer image. 4. or capture media type.iso and then click Next. click Task Sequences. Microsoft System Center 98 . This process will take a couple of minutes to complete. a ―Task Sequence Media Wizard” Wizard Completed dialog box appears indicating the media was successfully created. Click Browse.

Under the Start menu. The Browse for Folder dialog box appears. It may take a couple of moments to copy the Capture. Under the Start menu. we will just use the . click Local Disk (C:) and then click OK. This would only be done if you are using VPC images. 5. and then click Remove Z:. Verify the file was copied to Z:. The list of task sequence items appear in the tree pane. Copy C:\Capture. The local host‘s drive C: is connected as drive Z: on the virtual computer.iso to Z:\.iso file without creating an actual CD.iso file. Notice that the process of creating a task sequence capture media does not create a task sequence in the Configuration Manager Console.11. and then click Share Folder. burn a CD from the Capture.iso file just created.  To copy the ISO file to the host computer 1. In the lab. The contents of the folder appear. Click Close. Start Windows Explorer.iso file. In the following procedure. 12. Microsoft System Center 99 . right-click the icon that resembles a folder. you will copy the OS Capture Media disk to your host computer so it can be accessed by the reference virtual computer. right-click the icon that resembles a folder. but rather the . 3. and then display the contents of C:\. which can now be burned to a CD for booting on computers to be imaged. 2. Under My Computer. Notice the Capture. 4.iso file to the host computer. If using physical systems.

8. Close the System window. 2. The Image Capture Wizard Image information dialog box appears prompting for additional information regarding the image.Exercise 3 Creating an Image of the Windows Vista Reference Computer In this exercise. Click Next. Click C:\Capture. 2. Log on as administrator with a password of password. type \\<yourSMSServer>\<share_you_create_to_store_images>\MyVista. The System window appears displaying basic information about the computer. In the Account Name box. right-click Computer. In the Password box.iso from the host computer. 3. 4. you will create an image of the Windows Vista reference computer. Note Complete this exercise from the Windows Vista client only. In the Version box. 3. In the Destination box. Notice that the computer is a member of a workgroup. type <yourdomain>\Administrator. Reference systems must be workgroup clients. The Select CD Image to Capture dialog box appears. you will create an image of the reference computer running as a Configuration Manager 2007 client. type <yourpassword> and then click Next.0 10.exe. and not domain members. and then click Open. and then click Properties. 5. The Image Capture Wizard Summary dialog box appears indicating the image creation Microsoft System Center 100 . insert the CD into the drive. This step is only done if using VPC images. 9. 7. type Windows Vista master image and then click Next. Click Run TSMBAutorun. In the Created by box. If using physical systems.  To prepare the client for imaging 1. or some other account that has rights to save to your share in step 5. An AutoPlay dialog box appears prompting to run Run TSMBAutorun. In the following procedure.wim 6. click Capture ISO Image. If your reference system is still a domain member you are required to remove the computer from the domain to create an OS image of the computer. In the Description box.exe. The Image Capture Wizard Image destination dialog box appears prompting for information regarding the image creation process. type your name. On the Windows Vista Virtual PC CD menu. type 1. The Image Capture Wizard window appears. On the Start menu. This lab will use a Windows Vista Business edition client as the reference computer.  To create a Windows Vista image 1.

When the client has restarted and begun the capture process. Windows Vista is then shut down and the computer is restarted. When prompted to save changes. After restarting. click Turn off and delete changes. Microsoft System Center 101 . It will likely take anywhere from 30 to 60 minutes to complete. an Installation Progress dialog box appears displaying the progress of the image capture process. 11. When ready. you can close the Windows Vista client Virtual PC as it is no longer needed.process is ready to begin. and then click OK. 12. Shut down the Windows virtual PC. Note Capturing an image of an operating system is a lengthy process. 13. This process includes automatically running sysprep. and may take an hour depending on your hardware. Windows PE initializes. a System Restart message box appears indicating that the system is going to be restarted. Click Finish. When complete. An Installation Progress dialog box appears as the computer is prepared for imaging.

In the Actions pane. click Add Operating System Image. 4. In the Version box.Exercise 4 Deploying an OS Image Using Configuration Manager 2007 In this exercise. In the tree pane. The Add Operating System Image Wizard Summary dialog box appears indicating that the operating system image is ready to be created. 5. The Add Operating System Image Wizard Data Source dialog box appears allowing you to specify the image file to use. Click Next. 9. version and comment for the operating system image to be created. Notice that the Windows Vista image appears. Microsoft System Center 102 . 2. The operating system deployment items appear in the tree pane. Note Complete this exercise from the primary site server only. In the Comment box. you will create a new package and advertisement to deploy the Windows Vista image to the Windows XP client. The Add Operating System Image Wizard General dialog box appears allowing you to specify the name. In the tree pane. type \\<yourSMSServer>\<share_you_create_to_store_images>\Vista. Click Close. type Windows Vista 6. You need to create an operating system image from the Vista. type Windows Vista image and then click Next. 8. The operating system images for the site appear in the results pane.  To create the image package 1.wim and then click Next. The list of image packages appears in the results pane. click Operating System Images. and then expand Operating System Deployment. Notice that there are no images yet.wim file previously created. Note The process of creating the package in the Configuration Manager Console can take a number of minutes to complete (approximately three minutes) in a Virtual PC. The Add Operating System Image Wizard Wizard Completed dialog box appears indicating that the wizard completed successfully. Remain at this point until the image has been successfully created and the disk activity has stopped. In the Path box.0 7. expand Site Database. expand Computer Management. In the Name box. type 1. 3.

2. The OS image is copied to the designated distribution point. Microsoft System Center 103 . In the following procedure. expand Site Database. and then click Task Sequence. In the tree pane. The operating system deployment items appear in the tree pane. expand Computer Management. click <yourSMSServer>. In the tree pane. However. click New. expand Computer Management. Notice that there are no task sequences yet. 3. and then expand Operating System Deployment. Click Next. In the Actions pane. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of available distribution points for the OS image. Click Close.In the following procedure. and then click Next. The Windows Vista image items appear in the tree pane. build a reference system or a custom task sequence. In the tree pane. 5.  To add the image to a distribution point 1. click Distribution Points. expand Site Database. In the tree pane. you will assign the image to a distribution point to make the image available for access by Configuration Manager clients. and then in the Actions pane. 4. The task sequences for the site appear in the results pane. the image must be distributed to the distribution point before the client attempts to run the advertisement. click Task Sequences. It will take several minutes to completely distribute to the distribution point. This will take several minutes due to the size of the image. click New Distribution Points. you will create a task sequence to deploy the Windows Vista OS image. You do not have to wait for it to complete distribution before you move onto the next procedure. As the OS image is very large in size. 2. Note You can use the Package Status node under the image to identify when the image package has been distributed to the distribution point. You need to create a task sequence that will allow you to deploy an operating system image. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard has completed successfully. 3. and then expand Windows Vista. The New Task Sequence Wizard Create a New Task Sequence window appears prompting for the type of task sequence to create: to deploy an image package.  To create an image deployment task sequence 1. The New Distribution Points Wizard window appears. Operating System Deployment. expand Operating System Images. Under Distribution points.

Click Next. 9. The Select a Package dialog box appears displaying the image packages available. Also notice that the default configuration is to partition and format the target computer‘s hard disk. If you are deploying to an existing client this is not needed. and administrator password to use. licensing. Click Join a domain. type Installs Windows Vista image and then click Browse. which we are not performing. Click Boot image (x86) (if using x86 systems) and then click OK. as well as which boot image to use. click your. 7. and to disable the local administrator account on the target system. type Install Vista Image 6. Notice that the default action is to install all images in the package. If you are doing a bare metal installation. Click Browse. In the Comment box. In the Task sequence name box. The New Task Sequence Wizard Install the Windows Operating System dialog box appears displaying the image package to use.here. The New Task Sequence Wizard Install the Windows Operating System dialog box appears prompting for the image package. The New Task Sequence Wizard Configure the Network dialog box appears prompting whether the target system will join a workgroup or domain. Notice that you can also configure a specific OU for the client to join. 12. The Select a Domain dialog box appears displaying the available domains. 11. Clearing this option will make the image deployment process faster. and then after Domain. Under Domains. 10. as well as the boot image to use. not specify a licensing mode. click Browse.com and then click OK. Click Windows Vista 1. The New Task Sequence Wizard Task Sequence Information dialog box appears prompting for the name and description for the task sequence. Microsoft System Center 104 .domain.4. Click Next to create a task sequence that will install an existing image package. The Select a Boot Image dialog box appears displaying the boot images available.0 and then click OK. 13. Partitioning and formatting the target computer‘s hard disk is only required in a bare metal scenario. 5. 14. 8.path. The New Task Sequence Wizard Configure the Network dialog box appears displaying the domain the target client should join after installation of the Vista image. not a quick format. Click Next to not designate a product key. The New Task Sequence Wizard Task Sequence Information dialog box appears displaying the name and description of the task sequence. especially as the default format is a full format. That is only required in a bare metal scenario. click to clear the Partition and format the target computer before installing the operating system.

Click USMT and then click OK. 20. The New Task Sequence Wizard Install the SMS client dialog box appears displaying the package and program to use for the Configuration Manager client installation. Click Set. which occurs after the OS image has been deployed. Click Next. The New Task Sequence Wizard Configure the Network dialog box appears displaying the domain the target client should join after installation of the Vista image as well as the account that will be used to add the client to the domain. Click Microsoft Configuration Manager Client Upgrade and then click OK. 22. Microsoft System Center 105 .15. The New Task Sequence Wizard Include Updates in Image dialog box appears prompting for deployment of software updates. Click Next. Notice that the installation properties includes the FSP parameter to allow the new client deployment to report deployment state messages. The New Task Sequence Wizard Configure State Migration dialog box appears displaying the configuration of the user state capture process. The Select a Package dialog box appears displaying the packages available. The New Task Sequence Wizard Install Software Packages dialog box appears prompting for deployment of software packages after the image has been installed. This is where you‘d configure to add in additional SMS packages. 19. The Select a Package dialog box appears displaying the packages available. Click Next. 25. 18. type password and then click OK. such as Microsoft Office 2007. Click Next to not deploy any software updates in our lab. Notice that the defaults are to capture user state. type <yourdomain>\administrator 17. Notice that the default configuration is to not deploy software updates with the image. capture network settings. 21. The Windows User Account dialog box appears prompting for the account and password to configure as the Advanced Client Network Access Account. 23. In the Name box. Click Browse. 24. In the Password and Confirm password boxes. Click Browse. and capture Microsoft Windows settings. The New Task Sequence Wizard Configure State Migration dialog box appears prompting for configuration of the user state capture process. The New Task Sequence Wizard Install the ConfigMgr client dialog box appears prompting for the package to use for the Configuration Manager client installation. 16. save it to the state migration point.

27. 2. In the Actions pane. In the results pane. Notice that the name defaults to the task sequence name. Start Windows Explorer and verify that each of the four packages are available on the distribution point. Click the References tab. click Advertise. 7. 28. 9. The task sequence properties appear at the bottom of the results pane. you will advertise the task sequence to deploy the Windows Vista image to the Windows XP computer. Note Do not proceed until the four packages are available on the distribution point. Notice that there is now one task sequence in the site. The New Advertisement Wizard General dialog box appears prompting for general properties of the advertisement. The New Task Sequence Wizard Summary dialog box appears indicating the wizard has been completed and is ready to create the task sequence. Notice that there are four packages used by this task sequence. and then the New Task Sequence Wizard Wizard Completed dialog box appears indicating that the task sequence was successfully created. The New Advertisement Wizard General dialog box appears prompting for general properties of the advertisement. 4. Click All Windows XP Systems. The task sequences for the site appear in the results pane. click Install Vista Image. The task sequence is created. 8. The New Advertisement Wizard Schedule dialog box appears prompting for the advertisement schedule. Click Next. The Browse Collection dialog box appears. In the following procedure.  To advertise the task sequence 1. The list of packages used by this task sequence appears in the results pane. After Collection. Click Next. 6. The Assignment Schedule dialog box appears. The New Advertisement Wizard Schedule dialog box appears displaying the advertisement schedule. Click New (the toolbar icon resembles a star burst). and then click OK. Click Next to not deploy any software packages in the lab environment. Click Close.26. Microsoft System Center 106 . 3. click Browse. Click OK to create a schedule for the current date and time. 5.

Microsoft System Center 107 . Click Next. 12. to not allow access to remote distribution points. The advertisement is created. Click Next to not allow the user to run the program as an optional program prior to the mandatory schedule and to display progress of the task sequence. The New Advertisement Wizard Interaction dialog box appears prompting for how the user will interact with the task sequence. and require the use of protected distribution points if available. Notice that there is now one task sequence in the site. Verify that all processes were completed successfully. and then click Close. 14. 11. 15. The New Advertisement Wizard Security dialog box appears prompting for security rights for the task sequence. 13. The task sequences for the site appear in the results pane. Click Next to allow content to be downloaded when needed by the task sequence.10. Click Next to use the default security rights. Click Next. and then the New Advertisement Wizard Wizard Completed dialog box appears indicating the advertisement was successfully created. The New Advertisement Wizard Distribution Points dialog box appears prompting for how the task sequence will access any content that is required. The New Advertisement Wizard Summary dialog box appears indicating the wizard has been completed successfully and is ready to create the advertisement.

In the following procedure. Click Machine Policy Retrieval & Evaluation Cycle. right-click My Computer.  To verify the current configuration 16. 3. The Configuration Manager Properties dialog box displays the available actions for the client. What operating system is listed for the client computer? Microsoft Windows XP Professional Service Pack 2. The Configuration Manager Properties dialog box appears. The client will request new policies. Click OK. The System Properties dialog box appears. 6. The Configuration Manager Properties dialog box appears. 2. On the Start menu. you will install the Windows Vista image on the Windows XP client computer. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. 18. Click OK. Log on as administrator with a password of password. Note Complete this exercise from the Windows XP client only. Double-click the Assigned Program About to Run icon on the system tray. 4.Exercise 5 Installing the Image at the Target Client Computer In this exercise. and then click Properties. In Control Panel. Microsoft System Center 108 . Note It will take two minutes for the policy to be evaluated and the Assigned Program About to Run notification to be displayed. You will begin by verifying the current client configuration. and may take several minutes to complete. 5. and then click Initiate Action. you will install the Windows Vista image. Remain at this point until the Assigned Program About to Run notification appears.  To install the operating system image 1. which will include the policy related to the advertised task sequence. The Program Countdown Status dialog box appears indicating a program is about to run. start Configuration Manager. Click Cancel. Click the Actions tab. ________________________________________________________________________ 19. 17.

________________________________________________________________________ ________________________________________________________________________ 7. you will verify that the Windows Vista image was installed successfully. The System Properties dialog box appears. the Installation Properties message box appears displaying the progress bar for installing the image. 2. start System. you can still complete the next exercise to report on the operating system deployment progress. What operating system is listed for the client computer? Microsoft Windows Vista. 3. Microsoft System Center 109 . After the system reboots into Window PE. ________________________________________________________________________ 4. Close the Services and Administrative Tools windows. Notice that Windows PE is started and initialized to install the image.7. An Installation Progress message box appears as the Windows Vista operating system image is installed on the Windows XP client computer. Click Run. you can shut down the Windows XP virtual PC image and not wait for the image installation process to occur. What SMS services are installed on the client computer? The SMS Agent Host and SMS Task Sequence Agent services. automatically run through Windows setup to apply configuration settings. and not Windows XP. In Control Panel. and then finally reboot again into Windows Vista. The Services window appears. It will automatically restart in the middle of this process. Note It will take a number of minutes for the Windows Vista image to be deployed to the computer (approximately 60 minutes).  To verify the operating system image installation 1. The Administrative Tools window appears. In the following procedure. If you do cancel the deployment. Log on to <yourdomain> as administrator. 6. These services indicate a Configuration Manager client installation. Close the System Properties dialog box and then start Administrative Tools. Double-click Services. If you do let the image continue the installation process. the computer will restart. Also notice that the Welcome Center window appears. 5. Notice that the wallpaper on the desktop is for Windows Vista.

click Run Home Page Summarization. running. etc. The All system resources for a specific task sequence advertisement in a specific state report appears in the results pane. Notice that there is now one task sequence that has been advertised. In the Actions pane.Exercise 6 Viewing Status for the Image Deployment In this exercise. In the Actions pane. Click the arrow to the left of the one execution state listed. expand Site Database. This report displays the status for each task sequence step executed on the client computer. failed. and then click Operating System Deployment. Click the arrow to the left of <yourSMSClient>. 4.Specific task sequence advertisements run on a specific computer report appears in the results pane. 3. You will also notice that a chart has been created to the right of the list of task sequence advertisements. This report displays the status for this task sequence advertisement. succeeded. The Operating System Deployment home page appears in the results pane. The status of the task sequence advertisement depends on the state of the image deployment: canceled. or completed. in progress. Microsoft System Center 110 . so the chart shows the state of that one computer – running. The History . 2. 6. expand Computer Management. In our case. 10005 and 11140. Notice that there are no results to display unless the scheduled summarization process of hourly has already occurred. depending on how far you allowed the process to complete. 5. You should at least see messages with IDs of 10035. This will take a moment to complete. we only have one computer targeted. The Operating System Deployment home page appears in the results pane. In the results pane. you will view status messages for the image installation. The Status summary of a specific task sequence advertisement report appears in the results pane. The home page for operating system deployment is summarized.  To verify the image deployment 1. The task sequence steps displayed depends on the state of the image deployment: canceled. under Advertisement. The chart will indicate the state of the advertised task sequence. Many others could be available after this one. In the tree pane. This report displays the clients who are reporting the specific execution state you drilled into. Note Complete this exercise from the Configuration Manager primary site server only. or completed. 10002. click Refresh. Notice that the report displays the last status message ID as well as the description of the last status message. click Install Vista Image.

You have now successfully configured your Configuration Manager site for an OS image deployment. and upgraded your Windows XP client to Windows Vista. Microsoft System Center 111 . prepared and captured your Windows Vista reference system. created the appropriate task sequence to deploy the image.

You can have additional Configuration Manager clients if you want to scan for and deploy updates to multiple client platforms. Before You Begin In this lab. you will be able to:     Configure integration between WSUS 3. These could be the same computer. you need a Configuration Manager primary site server and a Configuration Manager client. Distribute an update using Configuration Manager. Estimated time to complete this section: 75 minutes Microsoft System Center 112 . Use Configuration Manager Reporting to report update status. Analyze required updates.0 and Configuration Manager.0 server (<yourSMSServer>) and a Windows XP SP2 Professional client. The systems needed for this section include a Windows Server 2003 SP2 site server configured as a WSUS 3.Section 6: Managing Microsoft Updates with System Center Configuration Manager 2007 Objectives After completing this section.

In the tree pane. 5. and then in the Actions pane. and then in the Actions pane.  To update the collection membership 1. click Refresh. You have now prepared your images for the lab and may proceed to Exercise 1. An All Systems message box appears prompting to update subcollection membership. The members of the All Systems collection appear in the details pane. expand Site Database. click ConfigMgr Console.Note Complete this procedure from the primary site server computer only. click Delete. The collection membership is updated. Notice that the <yourSMSClient> computer is now displayed only once and it is an Active record (not Obsolete). 9. Click OK. In the Actions pane. Click Yes. The list of collections appears in the results pane. click All Systems. The collection membership is updated. 4. expand Computer Management. Delete any other Obsolete records from the All Systems collection. Log on as administrator . Notice that the site server computer (<yourSMSServer>) and the Windows XP Professional client computer <yourSMSClient>appear as members. 7. 8. Notice that the <yourSMSClient> computer is now displayed twice. click the obsolete record for the <yourSMSClient> computer. and the current membership of the All Systems collection is displayed. 3. click Update Collection Membership. 6. In the details pane. The Configuration Manager Console window appears. In the tree pane. Microsoft System Center 113 . 2. A Confirm Delete message box appears prompting to delete the record. This is the old reference of the client. and then expand Collections. Notice also that one of the instances is listed as being Obsolete and inactive. On the Start menu. and the current membership of the All Systems collection is displayed.

 To verify the installation of WSUS 3.Exercise 1 Configuring Configuration Manager Integration with WSUS In this exercise. expand Site Database.0 1. you will configure Configuration Manager to integrate with WSUS 3. The Configuration Manager Console window appears. that being the site server (<yourSMSServer>). The list of site system roles for the Configuration Manager site server appears in the tree pane. In the Actions pane. Microsoft System Center 114 . This server is the WSUS server. click <yourSMSServer>. In the tree pane. Note Complete this procedure from primary site server computer only. and then expand Site Systems. so you will need to add the site system role to perform the role of the software update point. start Services. none having to do with software updates. expand <yoursitecode>. 4. In the following procedure. Note Complete this procedure from the primary site server only.0 server as a software update point for Configuration Manager.0 in order to scan for. 2. Close Services. If not already running. The New Site Role Wizard General dialog box appears. Notice that there is only one site system. You will begin by configuring the WSUS 3.  To configure a software update point 1. you will configure the WSUS 3. click New Roles. Notice that there are eight roles implemented. 3. updates to the Configuration Manager clients. 2. expand Site Settings. What services are installed that indicate that Windows Server Update Services is installed locally? Update Services and WsusCertServer ________________________________________________________________________ ________________________________________________________________________ 3. expand Site Management. The list of site systems appears in the tree pane. and deploy. In the tree pane. From Administrative Tools.0 computer as a Configuration Manager software update point. The Services window appears displaying the services installed locally. start the Configuration Manager Console.

service packs. Notice also that there is a message at the bottom of the dialog box indicating that you can‘t modify the update classifications when you are not configured to sync from a source. select Software update point. Notice that by default. and then click Next. The New Site Role Wizard Active software update point settings dialog box appears allowing you to configure the software update point as the active software update management point for the Configuration Manager site. The New Site Role Wizard Products dialog box appears allowing you to configure the various Microsoft software products that can be updated by Configuration Manager. Notice that the default configuration is to synchronize with Microsoft Updates. you will change the configuration. the software update point does not synchronize with the WSUS server automatically. Notice that by default. security updates. 10. Click Use this server as the active software update point. Click Next. The New Site Role Wizard Synchronization source dialog box appears displaying settings for synchronization with the software update point. 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. 7. Under Available roles. Select this option only if the export/import function is used to obtain software update definitions and then click Next. and then click Next. and to configure the port to use when interacting with WSUS. Click Next to not configure the use of a proxy server. Notice that there is a message at the bottom of the dialog box indicating that you can‘t modify the products when you are not configured to sync from a source. You may want to sync additional classifications such as critical updates. and update rollups are to be managed by Configuration Manager. You may want to choose to synchronize from Microsoft Update or an upstream update server. The New Site Role Wizard Update classifications dialog box appears displaying the various product categories of updates that are available in Configuration Manager for reporting and deployment. The New Site Role Wizard Synchronization schedule dialog box appears allowing you to configure the schedule to synchronize updates from WSUS with Configuration Manager. Microsoft System Center 115 .5. Click Next. 11. 6. The New Site Role Wizard Software Update Point dialog box appears allowing you to configure the proxy server to use for access to the update content if needed. Since you are in a virtual environment without Internet access and will perform manual synchronization. 8. 9. Click Next to not schedule synchronization.

log. and then open <systempartition>\Program Files\Microsoft Configuration Manager\Logs\ WSUSCtrl. Note Complete this procedure from the primary site server only. 13.0 server. The New Site Role Wizard Summary dialog box appears indicating that you have successfully completed the wizard. Notice that multiple languages are enabled by default. Notice that the log indicates that the required WSUS version was detected. and that the installation was successful. Under Update File. Click Next. Click Close. Click Next.12. You have now successfully installed an Configuration Manager software update point on the WSUS 3. a ConfigMgr site system. a ConfigMgr reporting point. 15. The Configuration Manager Console window appears displaying the site systems in the site in the results pane. you will verify the configuration of the ConfigMgr software update point was successful. The New Site Role Wizard Languages dialog box appears displaying the languages that content will be managed for through Configuration Manager. a ConfigMgr management point. To make the synchronization and management process of updates quicker. Notepad appears displaying the contents of the Configuration Manager software update point installation log. and that the local database connection was successful. Notice that the computer is configured as a ConfigMgr component server. Notepad appears displaying the contents of the Configuration Manager WSUS Control Manager‘s log.  To verify the software update point role 1. 14.log.log. 2. a ConfigMgr distribution point. Notice that the log indicates there was a successful connection to the WSUS server. a ConfigMgr site server. you will clear all languages except the local language. clear each language as appropriate. Microsoft System Center 116 . a ConfigMgr fallback status point. a ConfigMgr software update point and a ConfigMgr site database server. and then click Next. leaving only the local language (such as English). In the following procedure. Close the SUPSetup. Open <systempartition>\Program Files\Microsoft Configuration Manager\Logs\ SUPSetup. The New Site Role Wizard Wizard Completed dialog box appears indicating that you have now configured the software update point.

Notice the most recent messages with IDs of 6701.In the following procedure. 6705 and 6702. 6. In the tree pane. Note Complete this procedure from the primary site server only. This process may take some time to complete. On the File menu. the home page displays current compliance for security updates for the current month. The synchronization process is initiated. The ConfigMgr Status Message Viewer for <your_db_name> window appears displaying the status messages for the WSUS Sync Manager. This is due to the fact that synchronization has not yet occurred. There is no visual indication that the process has completed. 7. expand Computer Management. expand Site Database. The updates synchronized with Configuration Manager are displayed in the results pane. expand Site Database. Click Yes. expand Site Status. no updates are listed. and then click Component Status. In the tree pane. click WSUS_Sync_Manager. click Exit. Microsoft System Center 117 . expand <sitecode>. and then in the Actions pane. The Configuration Manager Console window appears.  To force catalog synchronization 1. and then click Update Repository. 5. 2. click Run Synchronization. A Run Update Synchronization message box appears prompting to run the synchronization process on the site. A new menu appears. Click All. Notice that by default. respectively. so you‘ll need to view status messages or Configuration Manager log files to verify that the process has completed successfully. as no synchronization has occurred yet. 8. is in progress. and completed. These messages indicate the sync process has started. and then click Software Updates. you will force synchronization of the Configuration Manager site database with updates from the software update point. 3. expand Software Updates. and then in the Actions pane. click Show Messages. In the results pane. expand System Status. In the tree pane. The home page for software updates appears in the results pane. The list of Configuration Manager server components and their current status appears in the results pane. Notice that by default. Also notice that there are no results to display. In the tree pane. click Update Repository. 4.

expand Computer Management. which is a requirement for display in the console. 13. There should be some updates in the Configuration Manager database. This forces the software updates data in the results pane to be summarized. Note Wait a moment here to allow the summarization process to complete before refreshing. Search for synchronizing. 10. Open <systempartition>\Program Files\Microsoft Configuration Manager\Logs\ Wsyncmgr.log. In the Actions pane. In the tree pane. Notepad appears displaying the contents of the WSUS Sync Manager‘s log file. Notice that there currently is not information to display. expand Site Database. notice the following processes occurring:       Successful connection to the local WSUS server Requested localization languages – one for each language configured in WSUS (likely only English in the lab) Requested update classification – one for each type of update to be managed (multiple different classifications in the lab) Synchronizing updates – this begins the process of synchronization of individual updates (numerous pages of updates being synchronized in the lab) Done synchronizing SMS with WSUS Server <yourSMSServer> – signals the end of the synchronization process Updated x items in SMS database – the number depends on the specific lab configuration. wait another moment and then proceed. 12. etc. On later lines of the log. Close Notepad. The Configuration Manager Console appears. Microsoft System Center 118 .9. Notepad displays the first occurrence of the text ―synchronizing‖. 11. Notice that the line indicates that the synchronization process is happening with Configuration Manager and the WSUS server <yourSMSServer>. The summarization process will take a moment to complete. If you refresh and the data is not update. and then click Software Updates. The home page for software updates appears in the results pane. catalog. click Run Home Page Summarization.

Notice that there are now may be some service packs that have been synchronized with Configuration Manager from WSUS.14. Microsoft System Center 119 . expand Software Updates. The service packs synchronized with Configuration Manager are displayed in the results pane. In the tree pane. Notice that there are now may be some critical updates that have been synchronized with Configuration Manager from WSUS. This will update the Update Repository node to include Critical Updates and Service Packs. and then in the Actions pane. click Update Repository. This will refresh the data in the software updates home page. expand Service Packs. In the tree pane. expand Update Repository. click Refresh. In the Actions pane. and then click All Updates. 17. 16. expand Software Updates. 15. expand Critical Updates. The critical updates synchronized with Configuration Manager are displayed in the results pane. expand Update Repository. click Refresh. In the tree pane. and then click All Updates. expand Software Updates.

Machine Policy Retrieval & Evaluation Cycle. This will cause the client to scan for updates through WSUS. Configuration Manager will then automatically send the data to the Configuration Manager site through state messages. 2. Software Inventory Cycle. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. and may take several minutes to complete. Software Updates Scan Cycle. and then check again. you can force a policy retrieval cycle ―Machine Policy Retrieval & Evaluation Cycle‖. Software Metering Usage Report Cycle. The client will force a scan for software updates. Notice the default actions of Branch Distribution Point Maintenance Task. Note If the ―Software Updates Scan Cycle‖ task does not appear. Click Software Updates Scan Cycle. It will take at least 15 minutes (the default for state message forward interval) for the client to be scanned. and then store the information in WMI. 5. Click OK. you will force the client to run a software updates scan cycle. Software Updates Deployment Evaluation Cycle. and then click Initiate Action. File Collection Cycle. Click the Actions tab. Discovery Data Collection Cycle. The Configuration Manager Properties dialog box appears. If you have multiple computers in the site. A Software Updates Scan Cycle message box appears indicating the action was initiated. Microsoft System Center 120 . The Configuration Manager Properties dialog box displays the available actions for the client. start Configuration Manager. you can complete this procedure on all clients. wait two minutes.Exercise 2 Generating Update Status on the Configuration Manager Client In this exercise. and the results to be returned to the Configuration Manager site through state messages. Click OK. The Configuration Manager Properties dialog box appears. In Control Panel. Hardware Inventory Cycle. 4.  To force the software updates scan cycle on the client 1. Note Complete this procedure from the Configuration Manager client computer. 3.

Notice that there now may be some service packs that have been synchronized with Configuration Manager from WSUS and all are listed as required updates for both clients. By default. expand Software Updates. 4. Do not begin this procedure for a few minutes to allow time for the client to complete the scan process. click Run Home Page Summarization. Microsoft System Center 121 . and then click All Updates. expand Update Repository. The critical updates synchronized with Configuration Manager are displayed in the results pane. Notice that there are now may be some critical updates that have been synchronized with Configuration Manager from WSUS. In the Actions pane. 5. If you refresh and the data is not update. configure the Month and year to August. you will verify that the Configuration Manager client computer has successfully reported software update compliance data. and then click All Updates. The home page for software updates appears in the results pane. you will get up to date information more quickly. In the Actions pane. and then click Go.In the following procedure.  To view results of the software updates scan cycle 1. Configuration Manager only summarizes the software updates information every four hours. Note Complete this procedure from the primary site server with the Configuration Manager Console running. configure the Vendor to <your_variable_here>. 2. expand Critical Updates. Note Wait a moment here to allow the summarization process to complete before refreshing. In the tree pane. expand Computer Management. By forcing the summarization process. expand Service Packs. 6. wait another moment and then proceed. 2007. configure the Update classification to Critical Updates. and then click Software Updates. expand Software Updates. 3. In the results pane. Notice that the home page displays current compliance for security updates for the current month. Also notice the status of each update with the number of systems requiring this update (should be two clients) and the number of not compliant (zero) systems. The Software Update Compliance Status Summary information appears in the details pane. expand Update Repository. In the tree pane. In the tree pane. The service packs synchronized with Configuration Manager are displayed in the results pane. expand Site Database. click Refresh.

with vendor and update class as optional attributes. In the tree pane. and requires the computer name. Notice that there are 353 reports available. 2.Specific computer Report Information appears in the results pane. The list of available reports appears in the results pane.Updates required but not deployed Report Information appears in the results pane. click Compliance 6 . After Collection ID. expand Computer Management. 6. Notice this is a prompted report. In the tree pane. article ID. The Select Value dialog box appears displaying the list of available collections. Note Complete this exercise from the Configuration Manager site server. Notice the list of updates available for the Configuration Manager client computer. the update ID. update class. title. 9. you will use generate reports for analysis and reporting of software update status. 4. In the tree pane. type the name of the Configuration Manager client you want to report on (it can be either of the clients). click Reports. Close the ConfigMgr Report window. Notice the information in the report includes the vendor. 7. A ConfigMgr Report window appears.Exercise 3 Generating Software Update Compliance Reports In this exercise. In the results pane. 8. whether the computer is compliant with the update. vendor and update class.  To generate an update status report for software updates 1. and an information URL. and requires the collection to report on and the vendor and update class. click Run. Click Display. expand Site Database. and then in the Actions pane. The Compliance 6 . 5. The Compliance 6 . click Management 1 . click Reports. click Run. 3.Updates required but not deployed. In the results pane. The list of available reports appears in the results pane.Specific computer. bulletin ID.Specific computer Report Information appears in the results pane displaying the designated computer name. and then in the Actions pane. Notice this is a prompted report. click Values. and then expand Reporting. In the Computer Name box. Microsoft System Center 122 . The Management 1 . The available Configuration Manager Reporting tool functions appear in the tree pane.

Click Display. and information URLs for the collection members. Notice that the classes are the same as configured in SCCM for synchronization with WSUS. Notice the report displays information for the appropriate update.Updates required but not deployed Report Information appears in the results pane displaying the configured prompted values.Updates required but not deployed Report Information appears in the results pane allowing configuration of the prompted values. 16. the options are <your_variable_here> . Microsoft System Center 123 . The Management 1 . Click All Systems. The Management 1 . After Update Class.Updates required but not deployed Report Information appears in the results pane allowing configuration of the prompted values. The Management 1 . A Select Value dialog box appears displaying the available vendors. After Vendor. 13. Click Lab. Click Critical Updates. A Select Value dialog box appears displaying the available update classes. title. Notice also that some updates are listed as being required but not yet deployed. including the article ID. 11. Local Publisher and Microsoft. In our case. 14.Updates required but not deployed Report Information appears in the results pane. A ConfigMgr Report window appears.10. 12. Close the ConfigMgr Report window. bulletin ID. click Values. click Values. The Management 1 . the number of client‘s requiring the update. 15.

The lab procedures will use a synthetic update. 5. Configuration Manager supports multi-selection of items in most nodes. Notice that in the lower portion of the Actions pane. expand Critical Updates. and then click All Updates. In the Name box. 2. expand Software Updates. is displayed a message that three items are selected. notice you can also multi-select here to view greater details or pursue specific actions. expand Update Repository. under Description. In the tree pane. In the Description box. The ―Update List Wizard” Wizard Completed dialog box appears indicating the wizard successfully completed. filtered from the original updates. The Update List Wizard Update List dialog box appears allowing you to select an existing update list or create a new one. Click Next. In the Look for box. Notice that there are now leses updates displayed in the results pane. 9. The Update List Wizard Security dialog box appears allowing you to configure security on the update list. Click Next. 10. type English update and then click Find Now. The Update List Wizard Summary dialog box appears indicating the wizard has all the information it needs to successfully complete. 6. Click Create a new update list. you will distribute a specific update using Configuration Manager and the software updates management feature. Under Title. 4. type <an_update_name> 7. Microsoft System Center 124 . click Update List. Click Next. Note Complete this procedure from the Configuration Manager site server with the Configuration Manager Console running.  To distribute the update to the Configuration Manager client 1. 3. Notice that there may be some updates available. The information for all critical updates appears in the results pane. In the Actions pane. The results for the search for English updates appear in the results pane.Exercise 4 Distributing Software Updates Using Configuration Manager Software Update Management In this exercise. type <an_update_name> 8.

click All Systems. type <your_update_name>and then click Next. 18. expand Software Updates. Click Browse. whether displayed time is the client time or UTC. type <your_update_name> 15. 16. Under Collections. The Configuration Manager Console appears. Notice that the default is not to suppress restarts and that restarts can not occur outside maintenance windows. and how of a time period do users have to deploy mandatory updates before forced on the computer. In the Actions pane. The Deploy Software Updates Wizard Collection dialog box appears prompting for the collection to be targeted with the update. The Deploy Software Updates Wizard Collection dialog box appears displaying the designated collection to be targeted with the updates. and then click <your_update_name> The list of software updates in the update list appears in the results pane. and then click OK. and then click Next. Click Next. 20. The Deploy Software Updates Wizard Deployment Template dialog box appears prompting to create a deployment template for distributing software updates. The Deploy Software Updates Wizard Restart Settings dialog box appears allowing you to configure the reboot behavior when updates require a system restart. In the Name box. 14. click Servers. Microsoft System Center 125 . 13. Click Next to accept the default values to display user notifications. Click Next to not generate a Windows event in the case of a failure. The Browse Collection dialog box appears displaying the collections in the site. 17. Click Next to create a new deployment definition. expand Update Lists. 21.11. use UTC. The Deploy Software Updates Wizard General dialog box appears. including whether or not reboots should occur outside any configured maintenance windows. and allow two weeks before updates become mandatory. The Deploy Software Updates Wizard Update Binary Download – ConfigMgr Client Settings dialog box appears allowing you to configure whether or not clients can install updates when in slow network boundaries. Under Suppress the system restart on. In the Description box. In the tree pane. 12. 19. The Deploy Software Updates Wizard Display/Time Settings dialog box appears allowing you to configure whether notifications will be displayed to the user. Click Close. The Deploy Software Updates Wizard Event Generation dialog box appears allowing you to configure whether or not any failure in the update deployment will generate a Windows event. click Deploy Software Updates. 22. or when the client‘s protected distribution point does not contain the update content.

type Critical updates for all clients 30. type Standard update deployment template 25. In the Description box. Doing so will make deployment of future updates much quicker.23. 24. Click Next. and then click Browse. 36. as you can use the template and not have to respond to configure all the settings you have done so on the last set of wizard pages. The Browse For Folder dialog box appears allowing you to select the source of they updates. type Normal software update deployments with suppression for servers 26. Notice that the default is to use an existing deployment package. Click Download software updates from a location on the local network (or your internet connection). expand <sitecode>. The Deploy Software Updates Wizard Download Location dialog box appears allowing you to configure whether or not to download updates automatically from the Internet or to retrieve them from a network location. The Add Distribution Points dialog box appears displaying the site(s) that can be targeted. The Deploy Software Updates Wizard Distribution Points dialog box appears displaying the distribution points to distribute the package to. In the Package source box. 32. type Critical Updates 29. In the Template description box. Click Next. Under Distribution points. 27. you do not have one yet. The Deploy Software Updates Wizard Deployment Package dialog box appears prompting to name the new deployment package to add the updates to. In the Name box. type \\<yourSMSServer>\<systempartition>\Critical 31. 35. click <sitecode> to select all distribution points in the site. Notice that the local site server (as a distribution point) is listed. Click Next. 33. Click Next to not support slow network boundaries and to allow fallback to unprotected distribution points. so will need to create a deployment package. Notice in our implementation. The Deploy Software Updates Wizard Create Template dialog box appears allowing you to save the configuration as a deployment template. The list of distribution points for the local site appears. 34. Click Create a new deployment package. Click Browse. and then click OK. Microsoft System Center 126 . The Deploy Software Updates Wizard Distribution Points dialog box appears allowing you to designate the distribution points to distribute the package to. only one site is listed. As this is your first deployment. In the Template name box. 28. Under Distribution points.

Notice that the default is the same as you configured during the configuration of the software update point. click Deployment Management. The Deploy Software Updates Wizard Language Selection dialog box appears allowing you to configure which languages updates should be downloaded for. expand Deployment Management. In the following procedure. Note Complete this procedure on the Configuration Manager primary site server only. and then click Close. Notice the list of updates includes the <updates you selected> prior to starting the DSUW. Click Next. which includes the downloading of each update to be deployed. 38. 39. The Deployment Management information appears in the results pane. 2. the Deploy Software Updates Wizard Wizard Completed dialog box appears displaying the status on each phase of the deployment. and then click Software Updates. The Deploy Software Updates Wizard Summary dialog box appears indicating you have successfully completed the wizard. The Configuration Manager Console appears displaying the list of critical updates in the results pane.37. 40. you will verify the software update deployment objects created. and updates can only be deployed within any configured maintenance windows for the targeted collection. and creating the deployment template and deployment package. and become mandatory in two weeks time. Notice that the default values are to become available now. In the tree pane. Notice the deployment name and values listed from the DSUW. and when the deployment becomes mandatory. The list of software updates in this deployment appears in the results pane. Click Next. The Deploy Software Updates Wizard Download Location dialog box appears displaying the configured source folder. expand <your_update_name>. 42. Verify that each phase of the process was successful. 41. The Deploy Software Updates Wizard Progress dialog box appears displaying the progress of the deployment. Click <systempartition>\WSUS Synthetic. The Deploy Software Updates Wizard Deployment Schedule dialog box appears allowing you to configure when the update deployment will be made available to clients.  To view the software update distribution objects 1. Click Next to accept the default values. When complete. In the tree pane. and then click OK. Microsoft System Center 127 . Also notice that Wake on LAN is not enabled for this deployment. Click Next to accept the configured languages.

In the following procedure. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. and then click Standard update deployment template. you will install the update on the client computer. The Configuration Manager Properties dialog box appears. The Standard update deployment template information appears in the results pane. Click Machine Policy Retrieval & Evaluation Cycle. Notice that this matches the distribution points you selected in the DSUW. You can use this template for future deployments and not have to complete all the pages of the DSUW. expand Deployment Templates. 6. expand Deployment Packages. The deployment status of the deployment package to the assigned distribution points appears in the results pane. In the tree pane. and then click Initiate Action. Microsoft System Center 128 . start Configuration Manager. For the lab. Click OK. The Software Updates information appears in the results pane. The distribution points assigned to this deployment package appears in the results pane. The Configuration Manager Properties dialog box appears. expand Critical Updates. and then click Software Updates. 4.  To install the update on the Configuration Manager client 1. 4. expand Critical Updates. In the tree pane. 2. Notice that the list of updates available in this deployment package is those you selected prior to launching the DSUW. and then click Distribution Points. 5. expand Deployment Packages. and then click Package Status. expand Critical Updates. In the tree pane. expand Deployment Packages. Click the Actions tab. Notice the template name and description. you will force the client to check for new advertisements instead of waiting for the automated detection to occur. In Control Panel. expand Package Status. In the tree pane. Notice that deployment package has been successfully deployed (listed as Installed) to the only distribution point in our site. Note Complete this procedure on each client computer that is to receive the update (which may include the site server computer). The Configuration Manager client will request new policies.3. 3. and may take several minutes to complete. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. which will include the policy related to the advertised program.

These are configurable in the Software Updates Client Agent. A Software Updates Installation icon appears in the System Tray indicating that new software updates are available. that they will be installed automatically after the configured optional period (two weeks in our case) and that a system restart may be required to complete the installation. and the status to be reported through state messages. Wait a few minutes here before proceeding to exercise 5. 6.5. Microsoft System Center 129 . This is an attended update. double-click the Software Updates Installation icon. This causes the Configuration Manager client to check for new policies. Notice also that ConfigMgr detected multiple update for the client. 7. Note It will take a few minutes for the new state messages to be sent to the site. When it has finished the check. The ConfigMgr .Software Update Management dialog box appears. It will take some time for the updates to be applied. and that you can perform an express or custom installation. Notice the default values of ―IT Organization‖ and ―Protecting your PC‖. In the System Tray. Click OK. Click Install to perform an express installation of the updates. Your updates may require a system restart. The updates are applied to the system. Note It will take a few minutes for the policy to be downloaded and evaluated before the software update will be available. so you will see the new Configuration Manager user interface. the update will be available for installation.

Note Complete this exercise from the Configuration Manager site server. The Compliance 6 . and then will validate using the Software Updates node. expand Computer Management. You will begin by generating reports for analysis and reporting of Microsoft update status. click Values. 3. under Visited Reports.Specific computer. the update ID. In the tree pane. The Compliance 6 . 8. with vendor and update class as optional attributes. 4. The Management 1 . Microsoft System Center 130 . click Compliance 6 . Notice that you ran two reports earlier. expand Reports.Updates required but not deployed. Close the ConfigMgr Report window. A ConfigMgr Report window appears. In the tree pane. The Select Value dialog box appears displaying the list of available collections. bulletin ID. and requires the computer name. Notice this is a prompted report. expand Site Database. and an information URL. and then expand Visited Reports.Specific computer Report Information appears in the results pane displaying the designated computer name. title. In the Computer Name box. article ID. In the tree pane. 7. The list of reports that have already been run appears in the results pane.Exercise 5 Validating Current Software Update Compliance In this exercise. type the name of the Configuration Manager client you want to report on (use one that you successfully ran the update deployment on earlier in this lab). 2. whether the computer is compliant with the update.  To generate an update status report for Microsoft updates 1. Notice the list of updates available for the Configuration Manager client computer. Notice the information in the report includes the vendor. After Collection ID. vendor and update class. 6. 5.Specific computer Report Information appears in the results pane. update class. Notice also that <the_updates_you_deployed> listed as being compliant (approved and installed). click Management 1 . Click Display. and requires the collection to report on and the vendor and update class. The available Configuration Manager Reporting tool functions appear in the tree pane. Notice this is a prompted report. In the tree pane. and then expand Reporting.Updates required but not deployed Report Information appears in the results pane. you will validate that the update has been deployed successfully.

14. but not yet deployed Report Information appears in the results pane. Note Complete this step from the primary site server with the Configuration Manager Console running. the number of client‘s requiring the update. In the following procedure. 12. 11. 15. 13.Updates required but not deployed Report Information appears in the results pane displaying the configured prompted values.Updates required but not deployed Report Information appears in the results pane allowing configuration of the prompted values. Notice also that there are some updates listed as being required but not yet deployed. the options are <your_variable_here>. expand Computer Management. click Values. The Management 1 . In our case. expand Site Database. The home page for software updates appears in the results pane. 10. The Software updates that are required. and information URLs for the collection members. title. A Select Value dialog box appears displaying the available vendors. The Management 1 . After Update Class. After Vendor.9. Notice the report displays information for the appropriate update. A ConfigMgr Report window appears. The Management 1 .  To view the update status data 1. Click Display. A Select Value dialog box appears displaying the available update classes. click Values. Local Publisher and Microsoft.Updates required but not deployed Report Information appears in the results pane allowing configuration of the prompted values. Notice that the classes are the same as configured in Configuration Manager for synchronization with WSUS. In the tree pane. bulletin ID. you will view the updated status data for the Microsoft update directly from the Configuration Manager Console. Close the ConfigMgr Report window. Click Critical Updates. Click <your_variable_here>.. including the article ID. and then click Software Updates. Microsoft System Center 131 . Click All Systems.

configure the Vendor to <your_variable_here> (perhaps choose Microsoft) . Notice that the updates are now compliant. In the tree pane. name. 8. Microsoft System Center 132 . click Refresh. click Run Home Page Summarization. There are many other aspects in the software updates role for Configuration Manager that you‘ll experience outside this simple scenario. which is a requirement for display in the console. In the Actions pane. Notice that the update status now reflects that the three updates were successfully installed to the Configuration Manager client. expand Software Updates. The results for the search for English updates appear in the results pane. In the Actions pane. The Software Update Compliance Status Summary information appears in the details pane. The Critical Updates (or your choice you made above) information appears in the results pane. expand Update Repository. configure the Update classification to <your_preference>. severity. and then click All Updates. You now will set the values to identify current status of the deployed updates. Notice that only the specific updates are displayed. 4. The summarization process will take a moment to complete. In the Look for box. The Software Updates information appears in the results pane. status of compliance. and are now compliant. and then click Software Updates. configure the Month and year to <a_specific_date>. expand Deployment Packages. 3. In the tree pane. and then expand Critical Updates (or some other preference). In the results pane. size and other information. 6. Notice that the list of updates available in this deployment package is displayed along with the status of the updates. click Refresh. Wait for a moment before refreshing the home page. including bulletin ID. This forces the software updates data in the results pane to be summarized.2. The home page is refreshed. article ID. You have now explored a simple scenario for deploying Microsoft updates in Configuration Manager. In the Actions pane. expand Critical Updates. 5. Note It will take a moment for the summarization process to complete. and then click Go. You should see some changes in the compliance as a result of the distribution. This displays the current status for the updates for the current month. 7. type English Updates and then click Find Now. Notice that updates are displayed for the selected month.

0 server and Configuration Manager software update point (<yourSMSServer>) and a Windows XP SP2 Professional client Estimated time to complete this section: 75 minutes Microsoft System Center 133 . Publish custom catalog information to Configuration Manager for scanning. Analyze required updates. Import a catalog for a synthetic application (if available – download required). Before You Begin In this lab. you need a Configuration Manager 2007 primary site server and a Configuration Manager client. You can have additional Configuration Manager clients if you want to scan for and deploy updates to multiple client platforms. Perform a scan for custom updates. The machines for this section include a Windows Server 2003 SP2 site server configured as a WSUS 3.Section 7: Managing Custom Application Updates using Systems Center Configuration Manager 2007 Objectives After completing this section. Use Configuration Manager Reporting to report update status. Distribute an update using Configuration Manager. These could be the same computer. you will be able to:         Install the System Center Updates Publisher. Create a catalog for a custom update.

Notice also that one of the instances is listed as being Obsolete and inactive. The Configuration Manager Console window appears. The members of the All Systems collection appear in the details pane. Microsoft System Center 134 . Delete any other Obsolete records from the All Systems collection. The All Systems message box appears prompting to update subcollection membership. Log on as administrator with a password of password. click ConfigMgr Console. On the Start menu. Click OK. click the obsolete record for the <yourSMSClient> computer. Notice that the <yourSMSClient> computer is now displayed twice.Note Complete this procedure from the primary site server computer only. 7. On the Action menu.  To update the collection membership 1. and the current membership of the All Systems collection is displayed. Notice that there are multiple members. The collection membership is updated. You have now prepared your images for the lab and may proceed to Exercise 1. In the details pane. 2. This is the old reference of the client. click Refresh. expand Collections. and the current membership of the All Systems collection is displayed. including the site server computer (<yourSMSServer>) and the Windows XP Professional client computer. and then click All Systems. 6. and then on the Action menu. In the console tree. and then click Update Collection Membership. Click Yes. click Delete. 3. A Confirm Delete message box appears prompting to delete the record. The collection membership is updated. Notice that the <yourSMSClient> computer is now displayed only once and it is an Active record (not Obsolete). 5. expand Site Database. 8. and then on the Action menu. point to All Tasks. 4.

Start <your SCCM eval download location> \Splash. 7. Click Next. click I accept the license agreement. Notice that the default value is MSSQLSERVER. 2. Click System Center Updates Publisher. When complete. The Setup Wizard for System Center Updates Publisher License agreement dialog box appears displaying the end user license agreement. 9. This process will take a few minutes to complete. Click Next to accept the default location of C:\Program Files\System Center Updates Publisher. Click Finish. you will install the System Center Updates Publisher. This is one of the tools in the Configuration Manager source. 4. 3. Note Complete this exercise from the primary site server computer. including the System Center Updates Publisher. The System Center Updates Publisher is installed.hta. 5.  To install the System Center Updates Publisher 1. The Setup Wizard for System Center Updates Publisher Installation dialog box appears indicating the installation is ready to complete. The Setup Wizard for System Center Updates Publisher Destination Folder dialog box appears prompting for the location to install the System Center Updates Publisher. Click Next to use the SQL Server installation. Click Next to use the default instance on the local server.Exercise 1 Installing the System Center Updates Publisher In this exercise. The Setup Wizard for System Center Updates Publisher window appears. The Setup Wizard for System Center Updates Publisher Select Database Server and Instance Name dialog box appears prompting for the local or remote database server to use. and then click Next. The Microsoft System Center Configuration Manager 2007 Start window appears displaying various installation options. 6. Microsoft System Center 135 . Click Next. The Setup Wizard for System Center Updates Publisher Select instance name dialog box appears prompting for the instance of SQL Server to use. 8. Read the end user license agreement. a Setup Wizard for System Center Updates Publisher Setup Complete dialog box appears indicating the installation was successfully completed.

available from the System Center website on Microsoft. In the Vendor box. and then click System Center Updates Publisher.com/systemcenter) Note Complete this procedure from the Configuration Manager site server. type http://<yourSMSServer> 10. 11. Click Create Basic rule.com/downloads/details. Click Add Rule (button with a ―+‖). The Create Update Wizard Update Information dialog box appears prompting for update information. We will create rules to apply this update to only Windows XP SP1 and SP2 systems that are running English for their language. On the Configuration Manager server Start menu. type Synthetic Software and then click Next. click Create Update. type Test update 5. The System Center Updates Publisher window appears. In the Update Title box. In the Description box. 9. you can create a custom catalog that will be imported into Configuration Manager for scanning with the standard Configuration Manager software updates scan process.  To create a custom catalog 1. click Moderate. type Evaluation. click Windows Version. In the More Info URL box. In the Product box. In the Actions pane. The Create Update Wizard Define Prerequisite Rules dialog box appears prompting for information on how to identify systems the update is applicable for. this can be found here. 7. You can also import 3rd party catalogs that contain updates. In the Classification box. and then in the Rule Type box.Exercise 2 Synchronizing Custom Updates with Configuration Manager In this exercise. If you do not have the Updates Publisher installed.microsoft. http://www. type <a_name_for_an_update> 4. 6.aspx?FamilyID=DC2329DD-304B-47259D4C-9C3F339F9D85&displaylang=en 2. The Create Update Wizard Extended Properties dialog box appears prompting for additional update information. In the Reboot Behavior box.com (http://www. The Add Rule dialog box appears expands to allow for configuration of a ―Windows Version‖ rule. In the Severity box. Microsoft System Center 136 . and then click Next. click Never reboots. point to All Programs. 8. 3. The Add Rule dialog box appears prompting for the type of rule to create. point to System Center Updates Publisher. click Security Updates.microsoft. 12.

type 2 26. This creates a rule to identify Windows XP SP2 and earlier systems. type 0 27. type 5 24. 14. click English. 23. click Windows Version. We want this to be an ―And‖ operator. type 1 25. In the SP Minor Version box. This creates a rule to identify Windows XP SP1 and later systems. The Create Update Wizard Define Prerequisite Rules dialog box appears displaying the rule created. with an ―Or‖ operator for the two rules. In the SP Major Version box. 30. In the Comparison box. 31. Under Operation. In the Minor Version box. and then in the Rule Type box. type 2600 28. Microsoft System Center 137 . 22. In the Major Version box. This will allow the rule to filter out all operating systems that are not Window XP SP1 or Windows XP SP2. 20. type 5 15. and then click Add Rule (button with a ―+‖). click Workstation. The Add Rule dialog box appears expands to allow for configuration of a ―Windows Version‖ rule. and then in the Rule Type box. click Windows Language. click Workstation. and then click Next. Click Create Basic rule. In the Build Number box. In the Language box. Click Create Basic rule. Click Add Rule (button with a ―+‖). Make sure both operators are set to And. In the Product Type box. In the Product Type box. type 1 16. 21. type 1 17. In the SP Major Version box. The Create Update Wizard Define Prerequisite Rules dialog box appears displaying the rule created. click Greater Than or Equal To. The Add Rule dialog box appears expands to allow for configuration of a ―Windows Language‖ rule. In the Minor Version box. In the Major Version box. In the Comparison box. The Add Rule dialog box appears prompting for the type of rule to create. and then click OK. and then click OK. click Less Than or Equal To. The Create Update Wizard Define Prerequisite Rules dialog box appears displaying the rule created. In the SP Minor Version box. Notice that you now have two rules. type 2600 19. In the Build Number box. type 0 18. The Add Rule dialog box appears prompting for the type of rule to create. 32. select And from the drop down list. 29. and then click OK.13.

In the Installer Type box.exe). click Command Line Installation (. Microsoft System Center 138 .The Create Update Wizard Select Package dialog box appears prompting the location and type of update to be deployed. 33.

In the Registry value box. Click Add Rule (button with a ―+‖). The Create Update Wizard Define Applicability Rules dialog box appears prompting for information on how to identify the file to be updated.In the Download URL (or UNC) box. 39. 46. The Select File dialog box appears prompting the location of update to be deployed. making a copy of any install such as a Windows update you have will be fine. type –I and then click Next. The Create Update Wizard Select Package dialog box appears prompting the location and type of update to be deployed. Click Create Basic rule. After Rule Type.exe 43. The Create Update Wizard Define Installed Rules dialog box appears prompting for information on how to identify whether or not the file is already installed. Notice that there are no default rules. The Add Rule dialog box appears expands to allow for configuration of a ―Registry Value Exists‖ rule. 35. If the value is not present. 36. type \\<yourSMSServer>\<SCUP install location> \yourfile. that indicates the update is required. 37. The Create Update Wizard Define Applicability Rules dialog box appears prompting for information on how to identify the file to be updated. click Not rule. Click Save your rule as. Click Next. 45. Click Browse. type 0 38. click Registry Value Exists. The Add Rule dialog box appears prompting for the type of rule to create. You will a create rule to apply this update to only clients without a specific registry value configured. 41. type Update Test Registry Check and then click OK. open the path to that file. and then in the Save your rule as box. click REG_SZ. Microsoft System Center 139 . Once completed. Notice that your one rule is now displayed. type HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ yourfile.34. In the Command line (quiet) box. In the Success Return Codes box. and then in the Rule Type box. type Installed 44. 40. 42. At this point you can choose anything you would like to test this available feature. In the Registry value type box. In the Registry Path box. For example. This creates a rule to identify systems that do not have the specific registry value configured.exe Notice the default values for success and pending reboot return codes as well as default command line switch for unattended installation are not provided for command line installations as they are for Windows Installer updates.

This will happen when synchronization is forced between SCUP and WSUS. click to clear Not rule. Note Complete this procedure from the primary site server only with the System Center Updates Publisher window active. 2. The Add Rule dialog box appears prompting for the type of rule to create. The System Center Updates Publisher window appears. 50. The update is created. When complete. the Create Update Wizard Confirmation dialog box appears indicating the update was created successfully. The Create Update Wizard Define Installed Rules dialog box appears displaying your configured rule. Click Use existing rule. under Update Test Software Update. The rule you just created is imported and is now used to validate whether or not the update has already been deployed. In the Actions pane. you need to clear the ―Not rule‖ configuration. click Update Test Registry Check.  To configure the custom update to be published to Configuration Manager 1. click Set Publish Flag. and then in the Rule Type box. expand your node. and then click Synthetic Software.47. Click Next. In the tree pane. Microsoft System Center 140 . 52. Notice also that it is not flagged to be published to Configuration Manager. you will configure the custom update to be published to Configuration Manager. The list of updates for the SCCM Lab vendor appears in the results pane. Click Next. 51. and then Configuration Manager synchronizes from WSUS. The Create Update Wizard Summary dialog box appears indicating the wizard is ready to create the update. so that it evaluates correctly for the query. The list of updates for the SCCM Lab vendor appears in the results pane. 49. Click Close. In the following procedure. However. Notice also that your synthetic update is now flagged to be published to Configuration Manager. Notice that the SCCM Lab vendor appears in the tree pane. 48. After Rule Type. and then click OK. Click Add Rule (button with a ―+‖). Notice that your custom update for the Synthetic Software Update is listed.

Note Complete this procedure from the primary site server only with the System Center Updates Publisher window active. Browse to the catalog.In the following procedure. The Import Software Updates Catalog Wizard Summary dialog box appears displaying the catalog to be imported. you have to download the content for the updates. Click Next. 7. 3. 5. Click Next to import a single catalog. You will not actually publish the 3rd party updates to WSUS (to be synchronized with Configuration Manager). The Select Catalog to Import dialog box appears. which you will not do in the VPC environment.  To import a custom catalog 1. and then in the Actions pane. 2. Click Next. click Import Updates. Notice that both the catalogs are listed. Click Accept. 6. 8. When complete. A Catalog Validation – Security Warning message box appears prompting to import the catalog. The System Center Updates Publisher window appears displaying the two catalogs. The Import Software Updates Catalog Wizard Select Import Method dialog box appears. 4. The file is imported. Click Close. In the tree pane. Microsoft System Center 141 . you will import two 3rd party catalogs to be published to Configuration Manager. the Import Software Updates Catalog Wizard Confirmation dialog box appears. In order to publish custom and 3rd party updates to WSUS. The Import Software Updates Catalog Wizard Select File dialog box appears prompting for the file to import. The Import Software Updates Catalog Wizard Select File dialog box appears displaying the file to be imported. Click Browse. click System Center Updates Publisher.

click Settings. The Settings dialog box appears displaying synchronization settings. the Publish Wizard Confirmation dialog box appears indicating the synchronization was successful. click Publish Updates. Click Accept. 3. 9. Notice that the tool is currently not configured to publish to an update server (WSUS 3. The Publish Wizard Summary dialog box appears indicating it is ready to publish one update.aspx 1. and then a Test Connection message box appears indicating that the connection was validated. Microsoft System Center 142 . 2. This process can take a few minutes depending on how many updates you are publishing to WSUS. 5. The Settings dialog box appears. 10. Verify that Connect to a local update server is selected.microsoft. The System Center Updates Publisher window appears. The System Center Updates Publisher window appears. http://technet. 4.In the following procedure. If not set. Click Close. click System Center Updates Publisher. there is a policy that must be set to allow 3rd party content to be installed from WSUS. which is not set by default. Click the Update Server tab. and then in the Actions pane. In the tree pane. A Content Validation – Security Warning message box appears validating that you want to publish the Synthetic Software Update. Click OK. The update is published to WSUS. 6.0).  To configure SCUP and WSUS for publishing In order to follow this section. and then click Test Connection. In the Actions pane. then no updates can be deployed. Click OK. Click Next. This is documented here. you will configure the System Center Updates Publisher to synchronize updates with WSUS so that Configuration Manager can synchronize the updates as with Microsoft Updates. The connection is validated. 7. Notice that the bottom portion of the property page displays the WSUS signing certificate information. The Settings dialog box appears displaying synchronization settings. When complete.com/enus/library/bb633114. Note Complete this procedure from the primary site server only with the System Center Updates Publisher window active. you must create and deploy a certificate. 8. as the publisher is not known. As well. Click Enable publishing to an update server.

There is no visual indication that the process has completed. Notice that there are folders for Critical Updates and Service Packs. click Run Synchronization. In the tree pane. click WSUS_Sync_Manager. Click All. This process may take a few minutes to complete. 4. and then click Component Status. expand Site Status. 5. so you‘ll need to view status messages or Configuration Manager log files to verify that the process has completed successfully. expand Software Updates.In the following step. On the File menu. 3. you will force the custom update to be published to Configuration Manager. In the results pane. Notice that by default. This will sync Configuration Manager with WSUS and will add the synthetic software update we created in the Synthetic Updates Publishing Tool into the Configuration Manager database. The ConfigMgr Status Message Viewer for <your_db_name> window appears displaying the status messages for the WSUS Sync Manager. The list of Configuration Manager server components and their current status appears in the results pane.  To force catalog synchronization 1. the home page displays current compliance for Microsoft security updates for the current month. These messages indicate the sync process has started. The Configuration Manager Console window appears. click Update Repository. Click OK. In the tree pane. Notice the most recent messages with IDs of 6701. 8. In the tree pane. and then in the Actions pane. Microsoft System Center 143 . expand <your_db_name>. 6. In the tree pane. The synchronization process is initiated. A Run Update Synchronization message box appears prompting to run the synchronization process on the site. A new menu appears. expand Computer Management. expand Site Database. click Show Messages. 7. expand System Status. and completed. and then click Update Repository. The update categories synchronized with Configuration Manager are displayed in the results pane. click Exit. 2. 6705 and 6702. and then click Software Updates. as these have been synchronized with WSUS previously. Note Complete this step from the primary site server only with the Configuration Manager Console window active. and then in the Actions pane. is in progress. expand Site Database. respectively. The home page for software updates appears in the results pane.

expand Software Updates.9. Note It will take a minute for the summarization process to complete. 10. click Refresh. The home page for software updates appears in the results pane. In the tree pane. expand Computer Management. in addition to the Critical Updates and Service Packs that had already been synchronized. In the tree pane. which is a requirement for display in the console. Microsoft System Center 144 . In the Actions pane. Remember that you had configured the Synthetic Software Update to be a Security Update. click Refresh. This will update the Update Repository node to include Security Updates. The security updates synchronized with Configuration Manager are displayed in the results pane. expand Site Database. and then click Software Updates. 11. expand Update Repository. Wait a moment before refreshing the console. and then in the Actions pane. In the tree pane. 12. click Update Repository. In the Actions pane. 13. The summarization process will take a minute to complete. This will refresh the data in the software updates home page. expand <your chosen update>. expand Software Updates. This forces the software updates data in the results pane to be summarized. click Run Home Page Summarization. and then click All Updates.

Click OK. Software Updates Scan Cycle. Software Updates Deployment Evaluation Cycle. Click Software Updates Scan Cycle. and the results to be returned to the Configuration Manager site through state messages.  To force the software updates scan cycle on the client 1. start Configuration Manager. and then click Initiate Action. Click the Actions tab. Notice the default actions of Branch Distribution Point Maintenance Task. File Collection Cycle. 4. A Software Updates Scan Cycle message box appears indicating the action was initiated. Discovery Data Collection Cycle. The Configuration Manager Properties dialog box appears. The client will force a scan for software updates. Software Inventory Cycle. and may take several minutes to complete. In Control Panel. both Microsoft Updates as well as custom updates. Click OK. The Configuration Manager Properties dialog box appears. Microsoft System Center 145 . you will force the client to run a scan cycle to identify applicable and installed updates. If you have multiple computers in the site. 3. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. Machine Policy Retrieval & Evaluation Cycle. you can complete this procedure on all collection members but must complete this on at least one client. Note Complete this procedure from each of the Configuration Manager client computers. 5. 2. It will take a few minutes for the client to be scanned. Software Metering Usage Report Cycle. The Configuration Manager Properties dialog box displays the available actions for the client.Exercise 3 Generating Status of Custom Updates on the Configuration Manager Client In this exercise. Hardware Inventory Cycle.

Microsoft System Center 146 . Note Complete this procedure from the primary site server with the Configuration Manager Console running. expand Software Updates. Configuration Manager only summarizes the software updates information every four hours. Do not begin this procedure for a few minutes to allow time for the client to complete the scan process. The updates synchronized with Configuration Manager are displayed in the results pane. 2. 4. In the Actions pane. and then click All Updates. expand Computer Management. The home page for software updates appears in the results pane. you will get up to date information more quickly. Note It will take a minute for the summarization process to complete.In the following procedure. By forcing the summarization process. By default. In the tree pane. click Run Home Page Summarization. expand <your chosen update>. expand Update Repository. click Refresh. 3. you will verify that the Configuration Manager client computer has successfully reported software update compliance data. and then click Software Updates. Wait a moment before refreshing the console. expand Site Database. In the Actions pane.  To view results of the software updates scan cycle 1. In the tree pane.

The Compliance 6 . and then expand Reporting.Specific computer. Notice that the classes are the same as configured in Configuration Manager for synchronization with WSUS. Notice that there are 353 reports available. The available Configuration Manager Reporting tool functions appear in the tree pane. click Values. click Run. Click Security Updates.Specific computer Report Information appears in the results pane. 2.Specific computer Report Information appears in the results pane displaying the designated computer name. type the name of the Configuration Manager client you want to report on (it can be either of the clients though <yourSMSClient> is the only one the update is applicable for according to our rules). After Vendor. vendor and update class. 7. Notice this is a prompted report. Local Publisher. and Microsoft. In the Computer Name box.Exercise 4 Generating Software Update Compliance Reports for Custom Updates In this exercise. After Update Class. click Compliance 6 .Specific computer Report Information appears in the results pane allowing configuration of the prompted values. 3. 8. Click the <vendor_name_you_created>. click Reports. vendor and update class. In the tree pane. In the results pane. the options are <your_variable_here>. Note Complete this exercise from the site server. you will use generate reports for analysis and reporting of the custom software update status. In the tree pane. In our case. The Compliance 6 . A Select Value dialog box appears displaying the available update classes. 5. 4.  To generate an update status report for software updates 1. A Select Value dialog box appears displaying the available vendors. click Values. expand Site Database. and then in the Actions pane. and requires the computer name. 6. expand Computer Management. The Compliance 6 .Specific computer. under Compliance 6 . The list of available reports appears in the results pane. Microsoft System Center 147 .

The Compliance 6 . Title. and one client that does not require it. In the results pane. 10. 18. Notice the report displays information for the synthetic update. A ConfigMgr Report window appears. The Select Value dialog box appears displaying the list of available collections. In the tree pane. the update ID.Specific software update states report appears displaying the number of clients in various states for this update. Click All Systems. Click Display.Specific software update. title. bulletin ID. After Update. and an information URL. 13. Notice the information in the report includes the vendor.Specific software update Report Information appears in the results pane. 16. Notice this is a prompted report. title. 15.9. click Run. and information URLs for the collection members. click Reports. vendor and update class.Specific computer Report Information appears in the results pane displaying the designated computer name. As the only security update synchronized is the custom update <your_update_you_created> there is only data available for one update. A Select Value dialog box appears displaying the available updates. 11. Microsoft System Center 148 . click Values. article ID. Click the left arrow next to the <vendor_name_you_created> The Compliance 7 . The Compliance 2 . bulletin ID. whether the computer is compliant with the update. including the article ID. Notice that the list includes all updates synchronized with WSUS. Notice that you have one client that requires the update. the number of client‘s requiring the update. 14. The Compliance 2 . The list of available reports appears in the results pane. Click Display. click Values.Specific software update Report Information appears in the results pane displaying the configured prompted values. including the Synthetic Software Update. 12. Notice that you have one client with a state of ―Update is required‖ and one client with a state of ―Update is not required‖. and then in the Actions pane. click Compliance 2 . under Compliance 2 . After Collection ID.Specific software update Report Information appears in the results pane allowing configuration of the prompted values. 17. and requires the collection to report on and update.Specific software update. Notice the list of security updates available for the Configuration Manager client computer. A ConfigMgr Report window appears. Click <your_update_you_created> The Compliance 2 . update class. Bulletin ID or Article ID. Close the ConfigMgr Report window.

The Compliance 9 .Specific software update Report Information appears in the results pane. <yourSMSClient>. is the only one that is listed. Close the ConfigMgr Report window. Microsoft System Center 149 . Notice that the Windows XP client.19.Computers in a specific compliance state for an update report appears displaying the number of clients that require this software update. 20. The Compliance 2 . Click the left arrow next to Update is required.

11.Exercise 5 Software Update Deployment Options In this exercise. 6. type Test of a custom update and then click Next. type \\<yourSMSServer>\<path to your software update> 10. 5. Click Create a new deployment package. 7. expand Software Updates.  To distribute the update to the Configuration Manager client 1. Click Next to use the existing deployment template. Click Next. Click Browse. The Deploy Software Updates Wizard Deployment Package dialog box appears prompting to name the new deployment package to add the updates to. The Deploy Software Updates Wizard General dialog box appears. In the Name box. Notice that the default is to use an existing deployment package. type Synthetic Custom Update 8. In the Name box. The Deploy Software Updates Wizard Deployment Template dialog box appears prompting to use an existing deployment template for distributing software updates. The Deploy Software Updates Wizard Distribution Points dialog box appears allowing you to designate the distribution points to distribute the package to. In the Description box. click Deploy Software Updates. type Synthetic Custom Update 4. you will distribute a specific update using Configuration Manager and the software updates management feature. 3. Microsoft System Center 150 . Notice in our implementation. In the Description box. The information for all security updates appears in the results pane. only one site is listed. In the tree pane. In the Package source box. You will create a new deployment package. and then click All Updates. type Custom update test for all Windows XP clients 9. The lab procedures will use a synthetic update. click <your software update>. expand Update Repository. 2. expand Security Updates. Note Complete this procedure from the Configuration Manager site server with the Configuration Manager Console running. Notice that there is only one update available. Notice that there is an existing template titled ―Standard update deployment template‖. and then in the Actions pane. The Add Distribution Points dialog box appears displaying the site(s) that can be targeted. Under Title.

which only includes the one synthetic update. Notice that the local site server (as a distribution point) is listed. Click Next to accept the default values. 13. 16. The Deploy Software Updates Wizard Summary dialog box appears indicating you have successfully completed the wizard. Notice that the default values are to become available now. The Deploy Software Updates Wizard Progress dialog box appears displaying the progress of creating the deployment. Click Next. Microsoft System Center 151 . Notice that the default is the same as you configured during the configuration of the software update point. click <site code> to select all distribution points in the site. The Deploy Software Updates Wizard Download Location dialog box appears allowing you to configure whether or not to download updates automatically from the Internet or to retrieve them from a network location. The Configuration Manager Console appears displaying the list of security updates in the results pane. and then click OK. 14. and become mandatory in two weeks time. 17. When complete. and then click Close. Click Next. and when the deployment becomes mandatory. Click Next to accept the configured languages. the Deploy Software Updates Wizard Wizard Completed dialog box appears displaying the status on each phase of the deployment. and then click Next.12. Also notice that Wake on LAN is not enabled for this deployment. The Deploy Software Updates Wizard Set Deployment Schedule dialog box appears allowing you to configure when the update deployment will be made available to clients. Verify that each phase of the process was successful. The Deploy Software Updates Wizard Distribution Points dialog box appears displaying the distribution points to distribute the package to. and updates can only be deployed within any configured maintenance windows for the targeted collection. Under Distribution points. Click Download software updates from the Internet to pull the updates from the published location (which was configured to a UNC path on the site server in the custom catalog). including the download of the update file. The Deploy Software Updates Wizard Language Selection dialog box appears allowing you to configure which languages updates should be downloaded for. 15.

expand Package Status. In the tree pane. In the tree pane. Click the Actions tab. click Deployment Management. and may take several minutes to complete. 4. The Software Updates information appears in the results pane. Notice that only one distribution point was targeted. Notice the deployment name and values listed from the DSUW. 3. In the following procedure. For the lab. expand Deployment Packages (if you named it this way). The list of software updates in this deployment appears in the results pane. start Configuration Manager. Note Complete this procedure on each client computer that is to receive the update (the update is only applicable to the Windows XP client computer however you can retrieve policies on both of your systems). if you created a site hierarchy expand <your site hierarchy>. The Configuration Manager Properties dialog box appears. and then click Package Status.  To install the update on the Configuration Manager client 1. Note Complete this procedure on the primary site server only. and then click Initiate Action. 2. you will force the client to check for new advertisements instead of waiting for the automated detection to occur. expand Deployment Packages. which only included your update (unless you added others). and it received the package successfully (Installed = 1). The Deployment Management information appears in the results pane. In the tree pane. In Control Panel. 2. The status of the distribution of the deployment package to the distribution point appears in the results pane. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated.  To view the software update distribution objects 1. you will verify the software update deployment objects created. expand <your update>. which will include the policy related to the software update deployment. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. expand Deployment Management. expand <your update>. Notice that the list of updates available in this deployment package is those you selected prior to launching the DSUW. you will install the update on the client computer. Microsoft System Center 152 . The Configuration Manager client will request new policies. 3.In the following procedure. In the tree pane. Click Machine Policy Retrieval & Evaluation Cycle.

the update will be available for installation. Your update may require a reboot – this will vary by package.Software Update Management dialog box appears. When it has finished the check. and that you can perform an express or custom installation.4. The update is applied to the system. The ConfigMgr . Click OK. Click Install to perform an express installation of the updates. so you will see the new Configuration Manager user interface. This is an attended update. Wait a few minutes before moving onto the next exercise. A Software Updates Installation icon appears in the System Tray of the Windows XP client computer indicating that new software updates are available. Note It will take a minute for the update to be deployed and updated state messages to be sent. The Configuration Manager Properties dialog box appears. It will take a few minutes for the update to be applied. These are configurable in the Software Updates Client Agent. 6. Microsoft System Center 153 . 7. 5. Note It will take a few minutes for the policy to be downloaded and evaluated before the software update will be available. In the System Tray. Notice also that Configuration Manager detected a single update for the client. and the status to be reported through state messages. Notice the default values of ―IT Organization‖ and ―Protecting your PC‖. double-click the Software Updates Installation icon. Click OK. that they will be installed automatically after the configured optional period (two weeks in our case) and that a system restart may be required to complete the installation. This causes the Configuration Manager client to check for new policies.

After Collection ID. The list of reports that have already been run appears in the results pane. 3. and requires the collection to report on and update. Title.Specific software update. and one client that does not require it. 10. In the tree pane. and then will validate using the Software Updates node. The Compliance 9 . and information URLs for the collection members. The Compliance 7 . A Select Value dialog box appears displaying the available updates.Specific software update Report Information appears in the results pane allowing configuration of the prompted values. click Values. In the results pane. 8.Specific software update states report appears displaying the number of clients in various states for this update. bulletin ID.Specific software update Report Information appears in the results pane displaying the configured prompted values. expand Site Database. The available Configuration Manager Reporting tool functions appear in the tree pane. The Select Value dialog box appears displaying the list of available collections. Notice that you have one client with a state of ―Update is installed‖ and one client with a state of ―Update is not required‖. Click All Systems. You will begin by generating reports for analysis and reporting of Microsoft update status. you will validate that the update has been deployed successfully. Click Display. title. 6.  To generate an update status report for custom updates 1. Click < Name/title/update that is appropriate> The Compliance 2 . After Update. Click the left arrow next to SCCM Lab. In the tree pane. 5. expand Computer Management. Notice that you have one client that installed the update. 7. A ConfigMgr Report window appears. Bulletin ID or Article ID.Specific software update Report Information appears in the results pane. including the article ID. The Compliance 2 . click Compliance 2 . Notice this is a prompted report. Notice the report displays information for the synthetic update. click Run. 4. Notice that you ran two reports earlier. Click the left arrow next to Update is installed. and then expand Reporting.Exercise 6 Validating Current Software Update Compliance In this exercise.Computers in a specific compliance state for a software update Microsoft System Center 154 . and then expand Visited Reports. under Compliance 2 . click Values. Note Complete this exercise from the site server. The Compliance 2 . 2. and then in the Actions pane. the number of client‘s requiring the update. expand Reports.Specific software update. Notice that the list includes all updates synchronized with WSUS. 9.

 To view the update status data 1. is the only one that is listed. severity. This forces the software updates data in the results pane to be summarized. Microsoft System Center 155 . expand Computer Management. Validate that the ―Last Updated‖ time is the current date and time. status of compliance. configure the Month and year to the current month and year. expand Site Database. article ID. 4. and then click All Updates. and is now compliant for one client and not required for the second client. which is a requirement for display in the console. 5. The home page for software updates appears in the results pane. Note Complete this step from the primary site server with the Configuration Manager Console running. and then expand Security Updates. click Run Home Page Summarization. Close the ConfigMgr Report window. The Security Updates information appears in the results pane. <yourSMSClient>. In the following procedure. Notice that the Windows XP client. you will view the updated status data for the custom update directly from the Configuration Manager Console. 3. and then click Go. expand Software Updates. and then click Software Updates.report appears displaying the number of clients that have installed this software update. click Refresh. This displays the current status for the updates for the current month. name. The home page for software updates appears in the results pane.Specific software update Report Information appears in the results pane. In the Actions pane. 11. In the tree pane. In the tree pane. size and other information. expand Update Repository. 2. including bulletin ID. The summarization process will take a minute to complete. Notice that updates are displayed. Notice that the update status now reflects that the update was successfully installed on the client. In the results pane. The Compliance 2 . In the Actions pane. configure the Update classification to Security Updates. you can configure the Vendor to <SCCM as a vendor name>. The Software Update Compliance Status Summary information appears in the details pane.

The Software Updates information appears in the results pane.6. You should see some changes in the compliance as a result of the distribution. In the Actions pane. Notice that the update is now compliant. expand Deployment Packages. 7. Notice that the list of updates available in this deployment package is displayed along with the status of the updates. Microsoft System Center 156 . expand <your update> and then click Software Updates. You have now explored another scenario in System Center Configuration Manager software updates management that being the ability to distribute updates for 3rd party and custom applications just as easily as you can do so for Microsoft updates. In the tree pane. click Refresh.

Estimated time to complete this section: 75 minutes Microsoft System Center 157 . http://www. you will be able to:      Create a configuration item for compliance. Verify compliance for the assigned baselines.microsoft. Prerequisites Before working on this lab. Create baselines for assignment. Configuration Packs are available for download from the System Center web site. Assign baselines to collections. located here. Import pre-created configuration items from the System Center Pack website.com/systemcenter .Section 8: Implementing Desired Configuration Management in System Center Configuration Manager 2007 Objectives After completing this section. The second virtual computer is booted as a Windows XP Professional SP2 client installed as a Configuration Manager client in the Configuration Manager site <yourSMSClient> . one virtual computer should be booted as a Microsoft Windows Server 2003 SP1 computer installed as a Configuration Manager primary site server <yourSMSServer>.

Click OK. 5. You have now prepared your images for the lab and may proceed to Exercise 1. The Configuration Manager Console window appears. and then in the Actions pane. and the current membership of the All Systems collection is displayed. expand Computer Management. and then expand Collections. Delete any other Obsolete records from the All Systems collection. Notice that the <yourSMSClient> computer is now displayed only once and it is an Active record (not Obsolete). click All Systems. 10. On the Start menu. Log on as administrator. and then in the Actions pane. In the Actions pane.  To update the collection membership 1. An All Systems message box appears prompting to update subcollection membership. The collection membership is updated. Click Yes. Notice that the <yourSMSClient> computer is now displayed twice. 7. 2. 9. 3. click Update Collection Membership. 8. Notice that the site server computer (<yourSMSServer>) and the Windows XP Professional client computer <yourSMSClient>appear as members. Notice also that one of the instances is listed as being Obsolete and inactive. click ConfigMgr Console. click the obsolete record for the <yourSMSClient> computer. 4. Microsoft System Center 158 . The members of the All Systems collection appear in the details pane. expand Site Database. 6. click Refresh. Update the membership for the All Windows XP Systems and All Windows Server 2003 Systems collections. This is the old reference of the client. The list of collections appears in the results pane. and the current membership of the All Systems collection is displayed. click Delete. In the tree pane.Note Complete this procedure from the primary site server computer only. The collection membership is updated. In the details pane. A Confirm Delete message box appears prompting to delete the record. In the tree pane.

and server. expand Site Database. business or operating system. and automatically selected for this application configuration item. Notice that you can create three types of configuration items – application. and then click Desired Configuration Management. The Create Application Configuration Item Wizard Identification dialog box appears allowing the configuration of the CI. type SCCM Client and then click Add. Microsoft System Center 159 . In the tree pane. as no configuration baselines have been deployed. appears in the results pane. Notice that by default there are no configuration items created. or create your own. Notice that the SCCM Client category has been added. and then click Configuration Items. If not already running. expand Desired Configuration Management. 3. 6. The Configuration Manager Console window appears. IT infrastructure. In the Name box. click New. expand Computer Management. type Looks for SCCM clients not using the standard Windows\System32\Ccm folder and then click the Categories button. The Categories dialog box appears allowing you to select an existing category. In the Description box. you will configure configuration items. The Categories dialog box appears displaying the available categories. 4. Note Complete this procedure from the primary site server computer only. type SCCM Client 7. line of business. Notice that by default. The list of configuration items. Notice also that there are no items to display. which are used to identify specific configurations for determining compliance.Exercise 1 Creating and Importing Configuration Items In this exercise. 2. In the Actions pane. You will begin by manually creating a configuration item. The Desired Configuration Management home page appears in the results pane. A new menu appears. 8.  To create a configuration item 1. In the Add a new category box. click ConfigMgr Console. 5. Click Application Configuration Item. on the Start menu. the home page displays configuration baselines that are reported as being out of compliance with at least one violation of the severity of ―Error‖. Notice the default categories for client. In the tree pane. which are used to create configuration baselines.

type SCCM Install Directory 16. The Create Application Configuration Item Wizard Objects dialog box appears allowing you to configure the configuration item you want to monitor compliance with. The New Registry Setting Properties dialog box appears allows the configuration of the registry value to query. Verify that Always assume application is installed is selected.9. verify that Equals is displayed. The Create Application Configuration Item Wizard Identification dialog box appears allowing the configuration of the CI. 15. 19. 11. 17. type Install folder 21. type SOFTWARE\Microsoft\SMS\Client\Configuration\Client Properties 18. 10. Microsoft System Center 160 . 22. In the Display name box. verify that HKEY_LOCAL_MACHINE is displayed. as that is how it is stored in the Registry. verify that String is displayed. type <systempartition>\Windows\System32\Ccm\ Note Be sure to include the trailing backslash. Click New. The Create Application Configuration Item Wizard Detection Method dialog box appears allowing you to configure the method of detection for this configuration item. 14. The Configure Validation dialog box appears allows the configuration of the registry value for validation. This configuration is if you wish to check security (Access Control Lists) on objects instead of the object settings themselves. Click Next. and then click New. The New Registry Setting Properties dialog box appears allows the configuration of the registry value for validation. Click OK. Click Next to not define objects for security checks. In the Operator box. however you can also do detection via Microsoft Installer or a VB script. 12. 13. In the Value box. In the Value name box. In the Key box. 20. A new menu appears with various options for configuring the object. Notice that the information you supplied is displayed. In the Name box. type Local SMS Path and then click the Validation tab. Notice that the default option is to assume the application is always installed. In the Hive box. The Create Application Configuration Item Wizard Settings dialog box appears allowing you to configure the settings for the configuration item you want to monitor compliance with. In the Data Type box. Click Registry. and then click Next.

In the Severity box. Click Next. Click Close. In the following procedure. which are used to create configuration baselines. 24. The list of configuration items appears in the results pane. In the tree pane. 2.23. The New Registry Setting Properties dialog box appears displaying the rule for validation. The configuration item is created. and then click Configuration Items. appears in the results pane. and then the ―Create Application Configuration Item Wizard” Wizard Completed dialog box appears indicating that the configuration item was successfully created. Notice that your configuration item is listed. The Create Application Configuration Item Wizard Settings dialog box appears displaying the settings you are using for this application rule. Notice that by default no files are listed to be imported. Click Next. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. Click Next to use all Windows platforms. The Create Application Configuration Item Wizard Applicability dialog box appears allowing you to configure the client operating systems that this rule is appropriate for. click Warning. Notice that your configuration item is now listed. expand Desired Configuration Management. 27. and then click OK. Microsoft System Center 161 . you will import pre-created configuration items that will be used to create a configuration baseline. expand Computer Management. In the Actions pane.  To import or create configuration items 1. 25. the rule is applicable for all Windows operating systems. 28. The Create Application Configuration Item Wizard Summary dialog box appears indicating it is ready to create the configuration item. Notice that by default. Click OK. 26. click Import Configuration Data. The Import Configuration Data Wizard Choose Files dialog box appears displaying the files to import. The list of configuration items. expand Site Database.

3. type in the name of the Operating System Configuration Item you intend to create. The Import Configuration Data Wizard Summary dialog box appears indicating that there are two configuration items ready to be imported. Build numbers. select New.com/systemcenter Download these to be used in this section. Operating System Configuration Item. If you have downloaded any Configuration Packs. 14. you begin to have some choices. Notice that there are now three configuration items listed. This particular customization can be very useful for organizations that may have their own build revisions that they monitor and Microsoft System Center 162 . You are also able to select existing or create new Categories in the same window. Click Run. 13. Notice that the two selected files are listed to be imported. 6. The list of configuration items appears in the results pane. Select Configuration Items.cab could not be validated and prompting to run the cab file anyway. 12. such as Major/Minor versions. place the name a short description of the Operating System Configuration Item you are creating. you may Specify a particular Windows Operating System by description in the drop down menu. path to your downloaded CPs and then click Open. 7. For example.microsoft. 11. Select the Desired Configuration Management section within your Configuration Manager console. and expand to show the two subsections. In the Dialog box that appears. Click Finish. A Microsoft Management Console – Security Warning message box may appear for some Configuration Packs. Click Add. 9. To create an Operating System Configuration Item. 4. The Import Configuration Data Wizard Choose Files dialog box appears displaying the files to import. or specify more granular details of an Operating System. Select Next when complete. The Create Operating System Configuration Item Wizard launches. Service Pack version (major or minor). In the next step. 10. indicating the publisher of the file Windows Server 2003 SP1. and in the Actions pane.cab file could not be validated and prompting to run the cab file anyway. Click Next. The Configuration Pack downloads are located here: http://www. The Open dialog box appears allowing you to select the file to import. Click Run. 5. A Microsoft Management Console – Security Warning message box may appear indicating the publisher of the Windows XP SP2. In the Description dialog box. To create an Operating System Configuration Item for the next section follow the next set of steps. 8.

In the next step. You have now created an Operating System Configuration Item that you may reference later in your evaluation. Some customers or partners for example use elements such as Registry key values. 16. This is an optional step. you also have the option of adding additional objects you may want to use to verify an Operating System version. This section is optional. In the next step. 15. Select Next when complete. you will be given a Details page. and also you have the option of going to Previous steps if modifications are needed. Select Next when complete. Select Next when complete. you have the option of querying additional resources from places such as Active Directory. Select Next when complete. Here you can review your choices. 18.administrate outside of Microsoft official releases. The final step in the wizard is a summary Detail list. Once the Wizard finished the Configuration Item creation. Microsoft System Center 163 . 17. registry and others. Select Close when complete.

6. and then click Configuration Baselines. 3. In the Actions pane. click operating system. The list of configuration baselines appears in the results pane. If you do not see these options. Under Available categories. 8. Notice that <your OS choice> configuration items are now listed under operating systems. expand Computer Management. click New Configuration Baseline. select the Operating System you would like to include in your baseline. type Client Operating Systems 4. Under Name. The Categories dialog box appears allowing you to select the category of items to display. Click Next. In the Name box. Notice the default rule configuration options. 7. Under Rules. 5. In the Description box. 9. 2. The Choose Configuration Items dialog box appears allowing you to select the operating system configuration items you created earlier.  To create a configuration baseline for operating systems 1. In the tree pane.Exercise 2 Creating Configuration Baselines In this exercise. Notice that there are no configuration baselines displayed. type Verifies all clients are running <your Operating system Configuration Item you created> and then click the Categories button. Click Next. and then click OK. expand Site Database. you will create configuration baselines that will be used to determine compliance of your Configuration Manager clients. The Create Configuration Baseline Wizard Identification dialog box appears allowing the configuration of the baseline. The Create Configuration Baseline Wizard Summary dialog box appears indicating it is ready to create the configuration baseline. click both Client and Server. The Create Configuration Baseline Wizard Set Configuration Baseline Rules dialog box appears allowing the configuration of the rules that are used to validate the baseline. they are easily added at the top under the section called ‗Add a new category‘ The Create Configuration Baseline Wizard Identification dialog box appears displaying the configuration of the baseline. expand Desired Configuration Management. Microsoft System Center 164 . What you see here is dependent on what OS packages you have created in your Configuration Manager – Desired Configuration Manager environment in the previous excercise. The Create Configuration Baseline Wizard Set Configuration Baseline Rules dialog box appears allowing the configuration of the rules that are used to validate the baseline. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console.

expand Desired Configuration Management. 3. The Choose Configuration Items dialog box appears allowing you to select the application or general rule configuration items created. In the Description box. When complete. Under Rules. The list of configuration baselines appears in the results pane. type SCCM Client 4. 11. Under Available categories. In the Actions pane. type Uses all SCCM client configuration items and then click the Categories button. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. The Create Configuration Baseline Wizard Set Configuration Baseline Rules dialog box appears allowing the configuration of the rules that are used to validate the baseline. the Create Configuration Baseline Wizard Wizard Completed dialog box appears indicating the configuration baseline was successfully created. The Create Configuration Baseline Wizard Identification dialog box appears displaying the configuration of the baseline. Also notice that the category is ―SCCM Client‖. click SCCM Client. Microsoft System Center 165 . and then click OK. click applications and general. The Categories dialog box appears allowing you to select an existing category. Click Close. In the following procedure.  To create a configuration baseline for SCCM client installation 1. and server as well as the SCCM Client category you created earlier. You can also add the an Operating Systems baseline to the new baseline. The list of configuration baselines appears in the results pane. and then click Configuration Baselines. 2. Notice that there is only one configuration item listed. Notice that the Client Operating Systems configuration baseline is displayed. which you had configured as the filter earlier in this procedure. or create your own.10. which is the SCCM Client configuration item you created. 6. Notice the default rule configuration options. 7. In the Name box. Click Next. expand Site Database. expand Computer Management. In the tree pane. Click Next. 5. Notice the default categories for client. IT infrastructure. line of business. Notice that the operating system configuration baseline is displayed. The Create Configuration Baseline Wizard Identification dialog box appears allowing the configuration of the baseline. you will create a configuration baseline to check for the Configuration Manager client configuration. click New Configuration Baseline. The configuration baseline is created.

Notice that the SCCM Client configuration item is now listed under ―application and general‖. allowing the nesting of Parent and Child relationships to exist. 10. and then click OK. The configuration baseline is created. the Create Configuration Baseline Wizard Wizard Completed dialog box appears indicating the configuration baseline was successfully created. click Client Operating Systems. The Create Configuration Baseline Wizard Summary dialog box appears indicating it is ready to create the configuration baseline. Notice that both the Operating System and SCCM Client configuration baselines are displayed. This is a very powerful feature of Desired Configuration Management. 13. 12. and for Configuration Items and Baselines to have relationships. click configuration baselines. Click Next. click SCCM Client. The Create Configuration Baseline Wizard Set Configuration Baseline Rules dialog box appears allowing the configuration of the rules that are used to validate the baseline. 11. Microsoft System Center 166 . The Choose Configuration Baselines dialog box appears allowing you to select the configuration baselines potentially already created. which is the Operating Systems configuration baseline you created earlier. 9.8. When complete. The list of configuration baselines appears in the results pane. and then click OK. Under Name. The Create Configuration Baseline Wizard Set Configuration Baseline Rules dialog box appears displaying the rules for the new configuration baseline. You may only see one configuration baseline listed. Click Next. Under Rules. You can add one baseline as a requirement of another one. Notice that both the SCCM Client configuration item and the Client Operating Systems baseline are added as rules. Click Close. Under Name.

Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. 2. 5. 4.Exercise 3 Scanning Configuration Manager Clients for Compliance In this exercise. The Browse Collection dialog box appears prompting for the collection to target with the configuration baselines. Click Next to use the default schedule of weekly scans. expand Desired Configuration Management. Click Next. 6.  To assign the baselines to collections 1. 7. The Assign Configuration Baseline Wizard Choose Collection dialog box appears allowing you to configure the collection the baselines are to be assigned to. Notice that the default schedule is weekly. Notice that both baselines are already listed. click All Systems. Microsoft System Center 167 . In the results pane. Under Collections. Click Next. The Assign Configuration Baseline Wizard Summary dialog box appears indicating it is ready to create the assignment. and then in the Actions pane. The Assign Configuration Baseline Wizard Set Schedule dialog box appears allowing the configuration of the schedule clients in the assigned collection should use for compliance scanning. and then click Configuration Baselines. 3. expand Computer Management. expand Site Database. The Assign Configuration Baseline Wizard Choose Collection dialog box appears displaying the All Systems collection as the collection the baselines are to be assigned to. Click Browse. The Assign Configuration Baseline Wizard Choose Configuration Baselines dialog box appears allowing you to configure the baselines to assign. and then click OK. as you had selected both when you launched the wizard. Notice that both the Operating Systems (you created earlier) and SCCM Client configuration baselines are displayed. click both configuration baselines (if you created both). The list of configuration baselines appears in the results pane. you will generate compliance data for your Configuration Manager clients. You will begin by assigning the configuration baselines to the appropriate collections. In the tree pane. click Assign to a Collection.

Hardware Inventory cycle. Click OK. Notice also that there are no items to display. start Configuration Manager. 2. Notice that the home page displays configuration baselines that have no compliance data reported. User Policy Retrieval & Evaluation Cycle and Windows Installer Source List Update Cycle. Click Next. which includes your configuration baselines. Notice that by default there are no configuration baselines assigned. Click Close. Click Machine Policy Retrieval & Evaluation Cycle.8. Click the Actions tab. Note Complete this procedure from each of the Configuration Manager client computers in the site. Microsoft System Center 168 . The Configuration Manager Properties dialog box displays the configuration baselines assigned to the client. In the tree pane. after Minimum severity. you will initiate the retrieval of policies on your SCCM client computers. data will appear in the home page. as no configuration baselines have been deployed. Notice the default actions of Branch Distribution Point Maintenance Task. Software Inventory Cycle. expand Computer Management. The Desired Configuration Management home page appears in the results pane. The list of configuration baselines appears in the results pane. 4. and then click Initiate Action. 5. 11. and may take several minutes to complete. 3. The Configuration Manager Properties dialog box appears. and receive compliance data from them. Discovery Data Collection Cycle. 9. In the following procedure. As you scan your clients. Software Metering Usage Report Cycle. Software Updates Deployment Evaluation Cycle.  To search for new policies 1. The Configuration Manager client will request new policies. Desired configuration management baselines are delivered to clients through policies. The Desired Configuration Management home page appears in the results pane. expand Site Database. A Machine Policy Retrieval & Evaluation Cycle message box appears indicating the action was initiated. In the results pane. which will include the policies related to configuration baselines. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client. The assignment process completes. In Control Panel. and then the Assign Configuration Baseline Wizard Wizard Completed dialog box appears indicating the process was successful. the home page displays configuration baselines that are reported as being out of compliance with at least a Severity of ―Error‖. and then click Desired Configuration Management. 10. Machine Policy Retrieval & Evaluation Cycle. Notice that by default. click None. The Configuration Manager Properties dialog box appears. Click the Configurations tab. File Collection Cycle.

and then click Desired Configuration Management. Notice that in our case. Notice that by default there are now two configuration baselines assigned to the client. 2. In Control Panel. This baseline should have one non-compliant system and one compliant system. Wait at least two minutes before moving onto the next step. which is the SCCM Client baseline. click Run Home Page Summarization. The Configuration Manager Properties dialog box displays the configuration baselines assigned to the client. expand Site Database. The Desired Configuration Management home page displays the current status in the results pane. both with a severity of None. In the following procedure.6. Click OK. 3. In the tree pane. we have two baselines. Click the Configurations tab. Notice that statistics on each baseline and a a pie chart for the selected baseline are displayed in the results pane. The Configuration Manager Properties dialog box appears. Microsoft System Center 169 . Depending on which client you are looking at. start Configuration Manager. Click OK.  To view the compliance status 1. Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. 9. 7. click Refresh. It will take a moment for the summarization process to complete. The pie chart is for the highlighted baseline. 8. The Desired Configuration Management home page appears in the results pane. you will view the compliance status of each Configuration Manager client for the two configuration baselines. Notice that the home page displays configuration baselines that are configured. the SCCM Client configuration baseline may be listed as not being compliant (the site server computer‘s Configuration Manager client is installed in C:\Program Files\SMS_CCM\ instead of C:\Windows\System32\Ccm\). It will take a couple of minutes for the client to download the policies and then implement them. In the Actions pane. expand Computer Management. In the Actions pane.

in the list of baselines. 6. created configuration baselines.4. for the Computer Name of <yourSMSServer>. version. Microsoft System Center 170 . click None. Click the arrow to the left of SCCM Client. scanned clients for compliance. click SCCM Client. Notice that this report displays each configuration item and the state of each configuration item at each client. under Name. If you scroll to the right. You have now used Configuration Manager 2007 to monitor compliance of systems using the desired configuration management feature of Configuration Manager. In the results pane. compliance state. The Non-compliance details for a configuration item on a computer report appears in the results pane. This is expected. which is why the item is listed as non-compliant. This will select the Operating System baseline but not launch a report that would happen if you clicked the Operating Systems baseline name under Name. desired state. 8. Notice that it reports that you have one compliant and one non-compliant system reporting for this baseline. Click the arrow to the left of SCCM Client. Notice that it displays the baseline name. configuration item. expand Computer Management. and reported system compliance through the DCM home page and reports. The Summary compliance by configuration baseline report appears in the results pane. 9. and then click Desired Configuration Management. configuration type. not the normal client folder. 5. Notice that it displays an entry for each SCCM client reporting status for this baseline. Notice that it displays the results of this configuration item on this specific client. and applicability and detected states for each client. The Desired Configuration Management home page displays the results of the Operating Systems baseline in the pie chart. assigned the baselines to collections. In the tree pane. expand Site Database. under Severity. The Configuration Manager Console window appears. you‘ll see the current value of the key. The Compliance details for a configuration baseline by configuration item report appears in the results pane. You created and imported configuration items. as the SCCM client was installed into the management point folder. In the results pane. and the Actual Compliance State of Non-Compliant. The Summary compliance for a configuration item by computer report appears in the results pane. Click the arrow to the left of the SCCM Client configuration item. Notice that all clients have reported that they are compliant with this baseline. 7.

Asset Intelligence is fully integrated into the setup experience. we ship the Asset Intelligence reporting classes in a disabled state. Client Access Licenses usage tracking for Microsoft Windows and Exchange: o Both User and Device CALs usage is tracked. Asset Change Summarization: o A summary of changes to computer assets is stored in a central table. Note: If you do not enable the Asset Intelligence reporting classes. To avoid unintentional or unnecessary data collection. examine some of the enhancements made to performance and briefly talk about the updated knowledge base catalog. Performance enhancements Several performance enhancements were included in this release of Asset Intelligence with special optimization for large environments. Asset Intelligence enhances the inventory capabilities of SCCM 2007 by extending hardware and software inventory and adding license management functionality. Many inventory classes improve the breadth of information gathered about hardware and software assets. In the following sections we will cover the ‗what‘s new in this release‘. In addition. and it is up to you to decide which reporting classes to enable. we will provide some hands-on exercises that will help you get acquainted with this feature set. o Data returned through hardware inventory. ―when did they do that‖ questions. o Additional reports help you answer the ―What has changed recently in my environment?‖ question. we will cover the reporting classes and their correlation to the Asset Intelligence reports and finally. Auto-created Metering Rules: o Last Usage Inventory can be used to auto-create full metering rules which you can decide to enable. o Simplifies the process of creating metering rules. Additional reports We have added additional reports and functionality that can be broken into the following high level buckets:     Recent Usage Inventory: o SCCM metering agent will inventory the last time any executable was running in the user context. o Based on Security audit logs. reports will contain no data and will instead display a message stating:"No matching records could be found".Section 9: Implementing Asset Intelligence in System Center Configuration Manager 2007 Overview Microsoft System Center Configuration Manager 2007 contains the second release of Asset Intelligence which continues and enhances the focus on improving asset & license visibility in the enterprise. These include a wide range of changes from more efficient data Microsoft System Center 171 . o Additional reports will help you answer the ―When was the last time this was used?‖ question. What’s new Setup experience In Configuration Manager 2007. This means that the knowledge base catalog as well as all reports are installed during SCCM 2007 setup and are no longer treated as optional components. o Managing deltas help reduce the complexity of asset management. o Additional reports answer the ―who used up the CALs‖ .

Likewise.com/fwlink/?LinkId=87301). which resulted in higher quality data to work with. Several fixes we introduced to address issues we discovered in SMS 2003 SP3. For more information. then Asset Intelligence data collection will remain enabled. we invested effort in adding additional titles.Uncategorized Software Software 6A . you must enable the WMI class on which it depends. Note: Enabling classes increases the bandwidth consumed by the inventory process. The following classes are available and are listed with the reports that depend on them. If you want to utilize a given report. The following reports are dependent on this class: Hardware 1A .Software by Category and Family Software 2D . disabling classes will decrease the bandwidth consumed by the inventory process but.Installed Software on a Specific Computer Software 3A .Summary of Computers in a Specific Collection Microsoft System Center 172 . A Description of the Different Classes The classes that support Asset Intelligence functionality are listed below with the reports that depend on them for data.Summary of Installed Software in a Specific Collection Software 2A .microsoft.Computers with a specific Microsoft License Ledger Item and Sales Channel Software 1A . The end result is a faster.Computers with a Specific Software Product Software 2E . and Asset Intelligence is already installed and enabled. The following reports are dependent on this class: License 1C . By default. SMS_InstalledSoftware This class tracks information about installed software.MOF and each classes correlates to specific report(s). more robust product.Computers with a specific Microsoft License Ledger Item and Sales Channel License 1D .Search for Installed Software SMS_InstalledSoftwareMS This class tracks information specifically about installed Microsoft software.Microsoft License Ledger for Microsoft License Statements License 1B . these classes are disabled and you will need to enable the ones that control report you wish to utilize. Data enhancements As the heart of Asset intelligence is the knowledge base catalog.Microsoft License Ledger products on a specific computer SMS_SystemConsoleUsage This class polls the System Security Event Log for information about all console usage. cleaning up older ones as well work around title schema rationalization. These classes are contained in the SMS_DEF. see the Microsoft TechNet article Customizing with MOF Files (http://go.Software Families Software 2B .Software Categories with a Family Software 2C .Microsoft License Ledger Item by Sales Channel License 1C . will adversely affect the reports that depend upon that class for data.collection to fewer reporting ‗Joins‘. The following reports are dependent on this class: License 1A . Enabling the Asset Intelligence Reporting Classes Asset Intelligence data collection is controlled via SCCM WMI classes. Note: If you are upgrading from Systems Management Server 2003 Service Pack 3.

To enable the auditing of Logon/Logoff policy you will need to go to the Local Security Settings->Local Policies -> Audit Policy -> Audit logon events and allow ―Success‖ auditing. If the log has less than 90 days of data. regardless of the length of the log. most software considered "malware" is in the form of browser helper objects.Computers with a Specific Browser Helper Object Software 5C .Hardware 2B .Auto-Start Software on a Specific Computer SMS_BrowserHelperObject This class tracks browser helper objects.Computers for a Specific Primary Console User Hardware 4A .Computers with a Specific Software Product Software 4B .Computers within an age range with a collection Hardware 3A .Primary computer users Hardware 3B .Computers with a Specific USB Device Hardware 8A . you will also need to enable audits on these servers.Shared (multi-user) Computers Hardware 5A .Computers with a Specific License Status License 4B .Console Users on a Specific Computer Hardware 6A .Browser Helper Objects Software 5B . The following reports are dependent on this class: Software 4A . The following reports are dependent on this class: Hardware 3A . SMS_AutoStartSoftware This class tracks information about software that starts automatically with the operating system.Computers with a Specific Product Managed by Software Licensing Service Software 2D .Console Users on a Specific Computer All CAL Reports Note: This class only reads the last 90 days of the event log.Computers with a Specific Auto-Start Software Software 4C .Computers with a Specific Browser Helper Object SMS_SystemConsoleUser This class polls the System Security Event Log for information about specific console users.Computers with Licenses Nearing Expiration License 3B . the entire log is read.Computers with a Specific Auto-Start Software Software 5B .Hardware that is Not Ready for a Software Upgrade Hardware 9A .Auto-Start Software Software 4B .Computers for a Specific Primary Console User Hardware 4A .Primary computer users Hardware 3B . The following reports are dependent upon this class: Software 5A . In addition to enabling this class.Computers for Which Console Users Could not be Determined Hardware 7C .Search for computers License 1C .Computers with a specific Microsoft License Ledger Item and Sales Channel License 2B . While some browser helper objects are beneficial.Browser Helper Objects on a Specific Computer Microsoft System Center 173 .Shared (multi-user) Computers Hardware 5A .

The following reports are dependent upon this class: License 2A .USB Devices by Manufacturer and Description Hardware 7C . Exercise 1 Editing the SMS_Def.Count of Licenses by License Status License 3B . The following reports are dependent upon this class: Hardware 1A .Hardware that is Not Ready for a Software Upgrade Hardware 9A .mof First we will need to enable the Asset Intelligence reporting classes. SMS_SoftwareShortcut This class is not currently used to support existing Asset Intelligence reports.com/fwlink/?LinkId=87205). However.Summary of Computers in a Specific Collection Hardware 2A . it can be enabled to support custom reports.Computers with a Specific USB Device Hardware 7D . it can be enabled to support custom reports.Count of Licenses Nearing Expiration by Time Ranges License 2B . we will provide more in-depth cover to rach of the classes in the SCCM 2007 SDK documentation.Computers with a Specific License Status License 4A . The SMS_def. The following reports are dependent upon this class: License 2C . SoftwareLicensingService This class is specific to Windows Vista.License Information on a Specific Computer License 5A .0 Technical Attributes (http://go. see the Microsoft TechNet article Windows Vista Volume Activation 2.Search for computers SMS_InstalledExecutable This class is not currently used to support existing Asset Intelligence reports.Estimated Computer Age by Ranges within a Collection Hardware 2B .Computers with Licenses Nearing Expiration License 2C . For more information.microsoft.Win32_USBDevice This class tracks devices connected to USB ports.com/fwlink/?LinkId=87205).Computers within an age range with a collection Hardware 8A .License Information on a Specific Computer License 3A .mof file consists of a list of Microsoft System Center 174 .USB Devices on a Specific Computer SMS_Processor This is an existing SMS class to which new properties have been added to provide more complete data about processors. However. For more information. The following reports are dependent upon this class: Hardware 7A . see the Microsoft TechNet article Windows Vista Volume Activation 2.0 Technical Attributes (http://go.microsoft.Count of Products Managed by Software Licensing License 4B .Computers Acting as a Key Management Service SoftwareLicensingProduct This class is specific to Windows Vista.USB Devices by Manufacturer Hardware 7B .Computers with a Specific Product Managed by Software Licensing Service Note: In addition to this.

it is sent to each client in your site. for CAL usage). After you have complied and tested the file. When you open the file. set them to FALSE. indicating whether or not the class is to be reported in SMS inventory. [SMS_Report (TRUE)] string ChannelCode. From there. While this is taking place. If there are attributes and classes that you no longer want to collect. the path is C:\Program Files\Microsoft Configuration Manager\.src\Hinv folder. Note: Hardware inventory will require time to start.e. in the \SMS\Inboxes\Clifiles. However. Classes that are set to TRUE are collected and those set to FALSE are not. Note: The highlighted line (i. }.mof file by replacing the file in the \SMS\Inboxes\Clifiles. SMS_Report(TRUE).classes and attributes. you can replace the default SMS_def. For Configuration Manager.g. there is an exception: if a class is set to TRUE (as it is in the example above). you can explore the new Asset Intelligence reports or enable the logon audit to allow for additional data collection (e. the path is C:\Program Files\Microsoft Configuration Manager\.src\Hinv folder on the site server. If you want to add attributes.mof file. //* //************************************************************************** [ dynamic. SMS_Report) acts as the ‗on/off‘ switch. [SMS_Report (TRUE)] string ChannelID. SMS_Class_ID ("MICROSOFT|INSTALLED_SOFTWARE_MS|1. [SMS_Report (TRUE)] string ProductCode. You can find the file on the SCCM site server. For Configuration Manager.0") ] class SMS_InstalledSoftwareMS : SMS_Class_Template { [SMS_Report (TRUE). collect and send data to the site server. Estimating network Impact based on Reporting Classes A key question you will need to answer before enabling these classes in Production will be network Microsoft System Center 175 . then any attributes with the key property are collected. SMS_Namespace (TRUE). [SMS_Report (TRUE)] string MPC. key] string SoftwareCode. You can use Notepad to modify the SMS_def. SMS_Group_Name ("Installed Software MS"). provider("AAInstProv"). you will see the following format: //************************************************************************** //* Class: SMS_InstalledSoftwareMS //* Derived from: (nothing) //* //* Key = SoftwareCode //* //* This Asset Intelligence class provides specific to Installed Microsoft Software information. even if the individual attribute is set to FALSE. set them to TRUE.

using a production image of a client) will yield the best approximation for production time rollout. Asset Intelligence Reports In this section. It is important to note that true to life testing (e. you can use these numbers guidelines to start the evaluation. which users ran them. see the SCCM help file under License Management Reports. For more information. Example of # Installed item 60 14 1 2 11 2 0 1 0 0 0 0 Class SMS_InstalledSoftware SMS_InstalledSoftwareMS SMS_SystemConsoleUsage SMS_SystemConsoleUser SMS_AutoStartSoftware SMS_BrowserHelperObject Win32_USBDevice SMS_Processor SMS_InstalledExecutable SMS_SoftwareShortcut SoftwareLicensingService SoftwareLicensingProduct Payload Size (Bytes) 1047 290 330 294 681 589 606 496 739 775 813 401 File Size (Bytes) 62791 4065 330 589 7495 1178 0 496 0 0 0 0 76944 When testing Asset Intelligence. One of these new reports identifies the number of processors in computers running software that can be licensed using the per-processor licensing model. These new reports identify recently used executables. see the SCCM help file under Hardware Reports. Based on testing we did. 11 auto-start items etc (see breakdown in table)).g. and the devices on which the executables were run.bandwidth. we encourage you to explore the new Asset Intelligence reports. see the SCCM help file under Hardware Reports. Exercise 2 Viewing and Running Reports  To view the Asset Intelligence Reports Microsoft System Center 176 . providing the means to track Client Access Licenses (CAL) in addition to the existing volume license reports. The changes identified in these reports include both hardware and software changes. Software Reports Six new software reports extend previous inventory capabilities by adding software metering. Hardware Reports Three new hardware reports help identify computers that have changed since the last inventory cycle. For more information. The remaining 8 new reports identify User CAL usage and Device CAL usage summaries. Examine the hardware inventory files as they come from the client to perform this analysis. and history. the anticipated range for a client is about 54KB-75KB (that‘s for a machine that has 60 installed applications. For more information. License Management Reports Nine new license management reports have been added. details.

To see the possible options. 2. 3. If you repackage applications and in the process modify the MSI data. 2. information will become available for you to generate the different reports. Software 02A – Software Families) In the Actions pane click Run In the Collection box. 4. File Server.g. expand Reporting. Exchange Server) since e the auditing data collected is per machine and not per role. You can see the SKU of an installed SQL Server but not the licensing mode in which it runs. In order to have data available to report on. where report 1A provides a high level view and then allows drill-down. Click on a report (e. Exchange 2007 does not appear in the License Leger report because it does not have a ProductID. type Asset Intelligence and hit Enter.microsoft.microsoft. 4. type OS (if desired) To generate the report. and then click Reports. 5. expand Site Database. Additional Resources    The Asset Intelligence Forum: http://forums. During testing it is important that you cover key scenarios and examine the results carefully. The reporting structure is similar in most cases. click ConfigMgr Console.g. click on Display Note: Each batch of reports may require different variables.aspx Microsoft System Center 177 . Asset Intelligence offers a powerful set of tools and you need to see what can and can‘t be done in this release. you need to retrieve polices. In the console tree. Note: After Hardware Inventory runs and sends data to the SCCM site database. Log on as administrator with a password of password.1. you can click on the Values box to see a menu that you can select from. On the Start menu. and then force a Hardware Inventory Cycle.com/enus/configmgr/default.com/TechNet/ShowForum. On the ‗Look For’ filter. 3. The Configuration Manager Console window appears.aspx?ForumID=1816&SiteID=17 System Center Configuration Manager in-the-box help file System Center Configuration Manager On-line: http://technet. Know Issues and Limitations     CAL Reports will only provide accurate data on single purpose servers (e. You now see all 57 Asset Intelligence reports. it is very likely that the application will appear as ‗uncategorized‘. type SMS00001 (All Systems) In the Family box. expand Computer Management. Running Reports  To run Asset Intelligence Reports 1.

Sign up to vote on this title
UsefulNot useful