Deploying SCCM

Microsoft Virtual Labs
Deploying System Center

Configuration Manager (SCCM)
2007
Deploying System Center Configuration Manager (SCCM) 2007
Table of Contents
Deploying System Center Configuration Manager (SCCM) 2007 ........................................... 3
Exercise 2 Installing Microsoft Configuration Manager 2007 ......................................................................................7
Exercise 3 Installing an SCCM 2007 Client ................................................................................................................ 12
Deploying System Center Configuration

Manager (SCCM) 2007
After completing this lab, you will be better able to:
Objectives Prepare Active Directory for Configuration Manager publishing and use
Install Configuration Manager 2007 using a custom setup
Install a required update to allow status messages to be processed
View status message activity related to site server installation
Discover computer resources from Active Directory
Install and configure a fallback status point
Install a Configuration Manager 2007 client on a Windows XP computer
Install a reporting point and generate client deployment reports
Scenario Description
Scenario
Before working on this lab, one virtual computer should be started as a Microsoft
Prerequisites Windows Server 2003® SP1 computer running as an Active Directory domain
controller (Deploy AD Server VPC). A second virtual computer is started as a
Microsoft Windows Server 2003® SP2 member server to install as an SCCM
primary site server (Deploy SCCM Server VPC). This computer has Microsoft
SQL Server 2005 installed. 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 (Deploy Client VPC).
The requirements for implementing SCCM 2007 (which have all been installed
in the lab VPC images), include:
Microsoft Windows Server 2003 SP1 or later in an Active Directory
domain
Internet Information Server (IIS) 6.0 or later, 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.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 75 Minutes

Complete This Lab
Computers used in this

Lab SCCM
Client
AD
Page 3 of 17
Exercise 1
Preparing Active Directory for SCCM 2007 Integration
Scenario
In this exercise, you will prepare Active Directory for use with SCCM 2007. You will use a utility that is provided
with Configuration Manager to extend the Active Directory schema for use by SCCM. You will also grant rights for
the SCCM site server to publish data to Active Directory. Finally, you will create an Active Directory site that will
be added to the SCCM boundaries for client management.
Note: Complete this exercise on the virtual computer running as a Windows Server 2003 Active Directory domain
controller only (AD VPC).
Tasks Detailed Steps

Complete the following a. Log on as administrator with a password of password.
task on: b. Run C:\ConfigMgr07_AD_Schema\Extadsch.exe.
A command prompt window appears as you extend the Active Directory schema
AD for use by Configuration Manager. When the schema extension process has
1. To extend the Active completed, the command prompt window closes.
Directory schema
c. Open C:\Extadsch.log.
Notepad displays the contents of the Extadsch.log file. This file is created by the
Extadsch.exe utility and reports on the Active Directory schema extension process.
Note: Was the schema extension process successful?
Yes
How many classes and attributes were added to Active Directory as a result of
extending the schema for Configuration Manager 2007?
There were 14 attributes and 4 classes added to Active Directory.
d. Verify that there are no errors listed in the log, and then close Notepad.
Complete the following a. On the Start menu, point to Administrative Tools, and then click Active
task on: Directory Users and Computers.
The Active Directory Computers and Users window appears.
AD
b. On the View menu, click Advanced Features.
2. To grant the SCCM
The Active Directory Computers and Users window displays additional Active
site server rights to
Directory information, including displaying the System container. You will grant
Active Directory
rights to the System container to allow the Configuration Manager site server to
publish data to Active Directory.
c. In the console tree, expand smsdomain.smsdemo.microsoft.com, and then click
System.
d. On the Action menu, click Properties.
The System Properties dialog box appears.
e. Click the Security tab.
The System Properties dialog box displays the security permissions on the
System container. Notice that the Configuration Manager site server computer
(SMSServer) is not listed.
Page 4 of 17
f. Click Add.
The Select Users, Computers, or Groups dialog box appears.
g. Click Object Types.
The Object Types dialog box appears.
h. Under Object types, click Computers, and then click OK.
The Select Users, Computers, or Groups dialog box appears.
i. In the Enter the object names to select field, type smsserver and then click OK.
The Select Users, Computers, or Groups dialog box appears. Notice that the
Configuration Manager site server computer (SMSSERVER) is now listed with
Read rights.
j. Under Permissions for SMSSERVER, click Full Control under Allow, and then
click Advanced.
The Advanced Security Settings for System dialog box appears displaying the
rights for various accounts.
k. Under Name, click SMSSERVER, and then click Edit.
The Permission Entry for System dialog box appears displaying the rights for
SMSServer$.
l. 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.
m. Click OK.
The System Properties dialog box appears.
n. 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.
Note: In the following procedure, you will create an Active Directory site to integrate
with Configuration Manager as part of its boundaries.
Complete the following a. On the Start menu, point to Administrative Tools, and then click Active
task on: Directory Sites and Services.
The Active Directory Sites and Services window appears.
AD
b. In the console tree, click Sites.
3. To create an Active
The list of AD sites appears in the results pane. Notice the default site name of
Directory site
Default-First-Site-Name.
c. On the Action menu, click New Site.

The New Object – Site dialog box appears.
d. In the Name box, type SCCMSite
e. 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.
f. Click OK.
The list of sites appears in the details pane. Notice the new site is listed.
g. In the console tree, expand Sites, click Subnets, and then on the Action menu,
Page 5 of 17
click New Subnet.
The New Object – Subnet dialog box appears.
h. In the Address box, type 192.168.1.0
i. In the Mask box, type 255.255.255.0
j. 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.
k. 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.
l. In the console tree, expand Default-First-Site-Name, expand Servers, and then
click ADServer.
This is your domain controller. You will move this to your new site as its server.
m. On the Action menu, click Move.
The Move Server dialog box appears displaying all sites available.
n. 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.
o. 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.
p. Close Active Directory Sites and Services.
Page 6 of 17
Exercise 2
Installing Microsoft Configuration Manager 2007
Scenario
In this exercise, you will install Configuration Manager 2007 using a custom installation. SQL Server 2005 is
already installed on the computer SMSServer. The installation will automatically use advanced security.
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 (SCCM VPC).

Complete the following a. Start C:\ConfigMgr07_RTM_ENU_5931_Eval\Splash.hta.
task on: The Microsoft System Center Configuration Manager 2007 Start window appears.
b. Under Install, click Configuration Manager 2007.
SCCM
The Welcome to System Center Configuration Manager 2007 Setup Wizard
1. To install
dialog box appears.
Configuration
Manager 2007 c. Click Next.
The Microsoft System Center Configuration Manager 2007 Available Setup
Options dialog box displays options for installation.
d. 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.
e. 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.
f. 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.
g. 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.
h. 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.
i. In the Key box, if not using the evaluation version of Configuration Manager, type
your product key, and then click Next.
The Microsoft System Center Configuration Manager 2007 Destination
Folder dialog box appears prompting for destination folder to install
Configuration Manager 2007 to.
j. Click Next to accept the default folder of
Page 7 of 17
C:\Program Files\Microsoft Configuration Manager.
The Microsoft System Center Configuration Manager 2007 Site Settings
dialog box appears prompting for site information.
k. In the Site Code box, type MCM.
l. In the Site Name box, type SCCM 2007 Primary Site, and then click Next.
The Microsoft System Center Configuration Manager 2007 Site Mode dialog
box appears displaying setup options for the SCCM security mode.
m. Click Configuration Manager Mixed Mode, and then click Next.
The Microsoft System Center Configuration Manager 2007 Client Agent
Selection dialog box appears displaying the available SCCM client agents, and
allowing you to enable or disable each as desired.
n. Click Next to enable and configure the selected agents (ensuring that Network
Access Protection is not enabled).
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.
o. Click Next to accept the default values of the SCCM site server’s installation of
SQL Server and SMS_MCM for the database name.
The Microsoft System Center Configuration Manager 2007 SMS Provider
Settings dialog box appears prompting for the computer to install the SMS
Provider on.
p. Click Next to use the SCCM site server for the SMS Provider.
The Microsoft System Center Configuration Manager 2007 Management
point dialog box appears prompting for the computer to use to install the
management point on. Since SCCM requires a management point, setup will
install one by default.
q. Click Next to install the management point on the SCCM site server.
The Microsoft System Center Configuration Manager 2007 Port Settings
dialog box appears prompting for the HTTP port to configure for use by SCCM.
r. Click Next to use the default HTTP port of 80.
The Microsoft System Center Configuration Manager 2007 Updated
Prerequisite Components dialog box appears prompting for the location of the
required client components. Notice that there are two options, one to download the
required updates from the Internet, and the other to use a local source of the
required files. As we’re in a VPC environment, the required files have already
been downloaded and staged for the lab.
s. Click The latest updates have already been downloaded to an alternate path,
and then click Next.
Prerequisite Component Path dialog box appears prompting for the location of
the required client components.
t. Click Browse.
The Browse For Folder dialog box appears.
u. Point to C:\SCCM Downloaded Client Files, and then click OK.
Prerequisite Component Path dialog box appears displaying the configured
Page 8 of 17
location of the required client components.
v. Click Next.
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.
w. Click Next.
The Configuration Manager Installation Prerequisite Check runs to validate that
the computers targeted for SCCM 2007 installation meet the requirements for
installation. When complete, the Microsoft System Center Configuration
Manager 2007 Installation Prerequisite Check dialog box appears indicating the
status of the validation process. Notice that there were no problems found with the
configuration that will prevent installation. There is a warning that no WSUS
installation was found (WSUS SDK). This is required to be able to deploy
software updates, but it is not required for the deployment lab, so you can
continue.
x. Click Begin Install.
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.
Note: The time to install a Configuration Manager site will be dependent on the
hardware available. It could take as few as 10 minutes to install, or over 30 minutes.
When complete, the Microsoft System Center Configuration Manager 2007
Setup Action Status Monitoring dialog box appears indicating that Setup
completed each action successfully.
y. Click Next.
The Completing the Microsoft System Center Configuration Manager
2007 Setup Wizard dialog box appears indicating the site is ready to use.
z. Click Finish.
Note: In the following procedure, you will install an update to the Configuration
Manager site server. This update is required to allow status messages to be processed
successfully and should be installed on every Configuration Manager site until it has
been incorporated into Configuration Manager 2007 Service Pack 1.
Complete the following a. Start
task on: C:\ConfigMgr_Hotfix\SCCM2007-RTM-KB945898-X86-ENU.EXE.
The Software Update Installation Wizard window appears.
SCCM
b. Click Next.
2. To install the
The Software Update Installation Wizard License Agreement dialog box
required update
appears.
c. Click I Agree, and then click Next.
A KB945898 Setup message box appears indicating that the SMS Executive
service must be stopped to install the update.
d. Click Continue.
The update is installed. The installation should only take a minute. When
complete, the Completing the Hotfix for Systems Center Configuration
Manager 2007 (KB945898) Installation Wizard dialog box appears.
e. Click Finish.
Complete the following Note: In the following procedure, you will use Configuration Manager status
Page 9 of 17
task on: messages generated by the site server installation to verify that the site server
installation was successful. You can use this same procedure to view status messages
SCCM generated by any Configuration Manager processes.
3. To view a. On the Start menu, point to All Programs, point to Microsoft System Center,
Configuration point to Configuration Manager 2007, and then click ConfigMgr Console.
Manager status The Microsoft Management Console (MMC) starts, and then the Configuration
messages Manager Console window appears.
b. In the tree pane, expand Site Database, expand System Status, expand Site
Status, expand MCM, and then click Site System Status.
The list of Configuration Manager site system roles appears in the results pane
with the current status of each site system. Verify that each site system has a status
of OK.
c. In the tree pane, click Component Status.
The list of SCCM components and their status appears in the results pane.
Note: As the update was applied to the site after installation, there may be warning
and error status in the site. However, if you are receiving status messages and can
display them, the hotfix was applied successfully and your site is processing status
messages. You should expect to have errors for SMS Offer Status Summarizer and
SMS Status Manager.
d. In the results pane, click SMS_SITE_COMPONENT_MANAGER, and then in

the Actions pane, click Show Messages.
A new menu appears.
e. Click All.
The ConfigMgr Status Message Viewer for <MCM> window appears. Notice the
message with the ID of 1027. It mentions that the site server was configured to
receive Configuration Manager server components.
f. Click the message, and then on the View menu, click Detail.
The Status Message Details dialog box appears. Notice the header information for
the message, as well as the text under Description.
g. Click OK.
The ConfigMgr Status Message Viewer for <MCM> window appears.
h. On the File menu, click Exit.
The list of SCCM components appear in the results pane.
i. Display the status messages for SMS_SITE_CONTROL_MANAGER.
message with a message ID of 2819. This message indicates that SCCM retains the
100 most recent copies of the site control file. At this point, SCCM has just been
installed, however there will have already been some site control file modifications
processed.
Notice the message with an ID of 2866. This message indicates the actual site
control file copy has been sent to the SMS Hierarchy Manager for addition to the
SCCM site database.
From here, you should notice many sets of site control file images being modified.
You should see messages with IDs of 2808, 2814, 2813, 2811, and 2865 in each
set of site control file modification requests. You will view these messages in later
labs.
Page 10 of 17
j. Display the status messages for SMS_HIERARCHY_MANAGER.
messages with message IDs of 3306. These messages indicate that Hierarchy
Manager has successfully processed a site control file modification and updated
the site database.
k. Display the status messages for
SMS_WINNT_SERVER_DISCOVERY_AGENT.
message with a message ID of 4202. This message indicates one server was
discovered and discovery data was written for it. This occurred as a result of
installing SCCM site components on the site server computer.
Note: In the following procedure, you will add the Active Directory site to the
Configuration Manager 2007 Boundaries.
Complete the following a. In the tree, expand Site Database, expand Site Management, expand MCM,
task on: expand Site Settings, and then click Boundaries.
The list of boundaries for the local site appears in the results pane. Notice that
SCCM there no default boundaries added to the site.
4. To configure b. In the Actions pane, click New Boundary.
Configuration
The New Site Boundary dialog box appears allowing the creation of a new
Manager to use the
boundary.
new AD site as a
boundary c. In the Description box, type Active Directory site for SCCM
d. In the Type box, click Active Directory site, and then click Browse.
The Browse Active Directory sites dialog box appears displaying the available
Active Directory sites. Notice that both the default AD site (Default-First-Site-
Name) as well the AD site you created earlier (SCCMSite) are displayed.
e. Under Site Name, click SCCMSite, and then click OK.
The New Site Boundary dialog box appears displaying the information specified
for the new boundary.
f. Under Network Connection, verify that Fast (LAN) is selected, and then click
OK.
Notice that the new AD site (SCCMSite) now appears as a boundary.
Page 11 of 17
Exercise 3
Installing an SCCM 2007 Client
Scenario
In this exercise, you will install the Configuration Manager 2007 client on the Windows XP Professional client
computer. You will begin by using Active Directory System Discovery to discover the computer from Active
Directory.
Note: Complete this exercise on the virtual computer running as a Windows Server 2003 SP2 SCCM site server
(SCCM VPC) unless directed to use another VPC image.

Complete the following a. In the tree, expand Site Database, expand Site Management, expand MCM,
task on: expand Site Settings, and then click Discovery Methods.
The list of discovery methods for the local site appears in the results pane. Notice
SCCM that there are four discovery methods related to Active Directory.
1. To discover b. In the results pane, click Active Directory System Discovery, and then in the
computers from Actions pane, click Properties.
Active Directory
The Active Directory System Discovery Properties dialog box appears.
c. Select Enable Active Directory System Discovery, and then click New (the icon
resembles a starburst).
The New Active Directory Container dialog box appears allowing you to specify
the use of a local domain, local forest, or custom query for the discovery.
d. Verify that Local domain is selected, and then click OK.
The Select New Container dialog box appears allowing you to specify the
container to use for discovery.
e. Select smsdomain, and then click OK.
The Active Directory System Discovery Properties dialog box appears. Notice
the distinguished name for the container to search. Also notice that a recursive
search will be performed on that container and that groups are excluded.
f. Click the Polling Schedule tab.
The Active Directory System Discovery Properties dialog box displays the
default polling schedule for Active Directory System Discovery. Notice that by
default, this polling will occur daily.
g. Click Run discovery as soon as possible and then click OK.
The Configuration Manager Console window appears.
Note: In the following procedure, you will verify the results of the Active Directory
System Discovery process.
Complete the following Note: You will need to wait for a moment for the discovery process to complete.
task on:
a. In the tree pane, expand Site Database, expand Computer Management, and
then click Collections.
SCCM
The list of collections appears in the results pane.
2. To verify Active
Directory System b. In the tree pane, expand Collections, and then click All Systems.
Discovery Notice that there is one member in the All Systems collection currently, that being
Page 12 of 17
the Configuration Manager site server.
c. In the Actions pane, click Update Collection Membership.
An All Systems message box appears prompting to update subcollection
membership.
d. Click OK.
The collection is updated. It takes a moment before the database is updated with
the new collection membership information.
e. In the Actions pane, click Refresh.
The collection membership is updated, and the current membership of the All
Systems collection is displayed.
Note: Are there any new members in the All Systems collection?
Yes, the local site server (SMSServer), the domain controller (ADServer) and the
Windows XP Professional client (SMSClient) should have been discovered.
Are each of the systems assigned to the site?

Yes, all are listed as being assigned to the site.
Note: If the assigned status still remains listed as No, then verify that you have
correctly listed SCCMSite as a boundary for the site.
f. In the results pane, click the Windows XP Professional client, and then in the
Actions pane, under SMSClient, click Properties.
The SMSClient Properties dialog box appears displaying discovery properties.
Note: What is the discovered AD site name?

SCCMSite, which is the AD site you added as a boundary for the site.
g. Click Close.
Note: 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.
Complete the following Note: Complete this procedure on the virtual computer running as a Windows Server
task on: 2003 Active Directory domain controller only (AD VPC).
a. From Administrative Tools, start Active Directory Users and Computers.
AD The Active Directory Users and Computers window appears.
3. To create the account
b. Create a new user with the name of ClientInstall, assign it a password of
required to install the
password, ensure that the account is not disabled, and that the password does not
SCCM Client
require changing at first logon.
c. Add this user as a member of the Domain Admins group.
This is the account that will be used to push the Configuration Manager 2007
client installation to the Windows XP Professional client. It must be a local admin
on the client computer. Being a member of Domain Admins is not a requirement,
but simplifies the configuration in the lab environment.
Note: In the following procedure, you will configure the account in the Configuration
Manager Console to allow installation of the Configuration Manager 2007 client.
Complete the following Note: Complete this procedure on the virtual computer running as a SCCM site server
Page 13 of 17
task on: only (SCCM VPC).
a. In the tree pane, expand Site Database, expand Site Management, expand MCM,
SCCM expand Site Settings, and then click Client Installation Methods.
4. To configure the The list of client installation methods appears in the results pane.
Configuration
b. In the results pane, click Client Push Installation, and then in the Actions pane,
Manager 2007 client
click Properties.
account
The Client Push Installation Properties dialog box appears. Notice that the
installation method is not enabled. It does not need to be enabled for our admin
controlled push installation.
c. Click the Accounts tab.
The Client Push Installation Properties dialog box displays accounts to be used
to push out the Configuration Manager client software. Notice that there are no
accounts listed.
d. Click New (the icon resembles a starburst).

The Windows User Account dialog box appears.
e. In the User name box, type smsdomain\ClientInstall
f. In the Password and Confirm password boxes, type password and then click
OK.
The Client Push Installation Properties dialog box displays accounts to be used
to push out the Configuration Manager client software. Notice that the new
account is listed.
g. Click OK.
Note: In the following procedure, you will use the Configuration Manager Console to
install a fallback status point. This is a new site system to Configuration Manager
2007, and is recommended to get client deployment status reporting.
Complete the following Note: Complete this procedure on the virtual computer running as a SCCM site server
task on: only (SCCM VPC).
SCCM and then expand Site Settings.
5. To install a fallback The list of configurable site settings appears in the results pane.
status point
b. In the tree pane, expand Site Systems, and then click \\SMSSERVER.
The list of site system roles for the site server appears in the results pane. Notice
that there are six site system roles assigned to the computer.
c. In the Actions pane, click New Roles.
The New Site Role Wizard General dialog box appears.
d. 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, type
smsserver.smsdomain.smsdemo.microsoft.com
e. 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.
f. Under Available roles, select Fallback status point, and then click Next.
The New Site Role Wizard Fallback Status Point dialog box appears allowing
you to configure the fallback status point message processing.
Page 14 of 17
g. In the Throttle interval (in seconds) box, type 360, and then click Next.
Note: You should not use a value of 360 in a production environment as it could cause
performance issues. 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 New Site Role Wizard Summary dialog box appears indicating that you
have successfully completed the wizard.
h. 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.
i. Click Close.
The Configuration Manager Console window appears displaying the site system
roles for the computer SMSServer. Notice that the fallback status point role has
been added to the list.
Note: In the following procedure, you will configure clients to use the fallback status
point during installation of the Configuration Manager 2007 client.
Complete the following Note: Complete this procedure on the virtual computer running as a Configuration
task on: Manager site server only (SCCM VPC).
SCCM expand Site Settings, and then click Client Installation Methods.
6. To configure the use The list of client installation methods appears in the results pane.
of a fallback status
b. In the results pane, click Client Push Installation, and then in the Actions pane,
point
click Properties.
The Client Push Installation Properties dialog box appears. Notice that the
installation method is not enabled. It does not need to be enabled for our admin
controlled push installation.
c. Click the Client tab.
The Client Push Installation Properties dialog box displays the properties to use
when performing a client push. Notice that the one default parameter is the
SMSSITECODE set to the local site code MCM.
d. Add the following to the existing command line: FSP=SMSServer and then click
OK.
Note: In the following procedure, you will use the Configuration Manager Console to
push the installation of the Configuration Manager client to the Windows XP
Professional client.
a. In the tree pane, expand Site Database, expand Computer Management, expand
SCCM Collections, and then click All Windows XP Systems.
7. To install the The members of the All Windows XP Systems collection appear in the results
Configuration pane. Notice that there are no members of the collection.
Manager client
b. In the Actions pane, click Update Collection Membership.
The All Windows XP Systems message box appears prompting to update
subcollection membership.
Page 15 of 17
c. Click OK.
The collection is updated.
d. In the Actions pane, click Refresh.
Windows XP Systems collection is displayed. This should include the Windows
XP Professional client computer, SMSClient.
e. In the results pane, click SMSClient.
The Actions pane updates to include actions for the selected resource, in this case,
SMSClient.
f. In the Actions pane, under SMSClient, click Install Client.
The Client Push Installation Wizard dialog box appears.
g. Click Next.
The Client Push Installation Wizard Installation options dialog box appears
displaying options for the client installation.
h. Click Next to accept the default configuration to install the client to assigned
resources.
The Completing the Client Push Installation Wizard dialog box appears
indicating it is ready to complete the installation.
i. Click Finish.
The Configuration Manager 2007 client is remotely installed on the Windows XP
Professional client computer. It will take a few minutes before the installation
completes.
Note: In the following procedure, you will verify that the Configuration Manager 2007
client has been installed on the Windows XP Professional client.
Complete the following Note: Complete this procedure on the Windows XP Professional client computer only
task on: (Client VPC). 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
Client is running, the client is being installed. When ccmsetup.exe terminates and
Ccmexec.exe starts, the Configuration Manager 2007 client has been successfully
8. To verify the
installed.
Configuration
Manager 2007 client a. Log on as administrator with a password of password.
installation b. In Control Panel, double-click Administrative Tools, and then start Services.
The Services window appears.
c. Verify that the SMS Agent Host service has been started.
d. Close Services.
Note: 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.
SCCM Collections, and then click All Windows XP Systems.
9. To verify the The members of the All Windows XP Systems collection appear in the results
reporting of the pane. Notice that the Windows XP Professional computer appears. Also notice that
Configuration the computer is not listed as being an SMS client.
Manager 2007 client
b. In the Actions pane, click Update Collection Membership.
Page 16 of 17
The All Windows XP Systems message box appears prompting to update
subcollection membership.
c. Click OK.
The collection is updated.
d. In the Actions pane, click Refresh.
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.
Page 17 of 17
Exercise 4
Reporting Configuration Manager 2007 Client Deployment
Status
Scenario
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.

Complete the following Note: Complete this exercise on the site server computer only.
task on: a. In the tree pane, expand Site Database, expand Site Management, expand MCM,
and then expand Site Settings.
SCCM
The list of configurable site settings appears in the results pane.
1. To install a reporting
b. In the tree pane, expand Site Systems, and then click \\SMSSERVER.
point
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.
c. In the Actions pane, click New Roles.
The New Site Role Wizard General dialog box appears.
d. 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.
e. 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.
f. Click Next to use the default values.
The New Site Role Wizard Summary dialog box appears indicating that you
have successfully completed the wizard.
g. 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.
h. Click Close.
The Configuration Manager Console window appears displaying the site system
roles for the computer SMSServer. Notice that the reporting point role has been
added to the list.
i. From Administrative Tools, start Services.
The Services window appears. Verify that the SMS Reporting Point service is
installed and running.
j. Close Services.
Note: 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.
Page 18 of 17
SCCM Reporting, and then click Reports.
2. To report The list of reports appears in the results pane.
Configuration
b. In the results pane, click Computers assigned but not installed for a particular
Manager data
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.
c. 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.
d. In the Site Code box, type MCM, 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 (ADServer) and the site server (SMSServer).
e. Close the ConfigMgr Report window.
The Configuration Manager Console window appears displaying the current report
parameters.
f. In the tree pane, click Reports.
The list of reports appears in the results pane.
g. 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).
h. 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 SMSClient
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.
Page 19 of 17

Deploying SCCM

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Deploying SCCM

Încărcat de

Drepturi de autor:

Formate disponibile

Microsoft Virtual Labs

Deploying System Center

Deploying System Center Configuration

Estimated Time to 75 Minutes

Computers used in this

Tasks Detailed Steps

c. On the Action menu, click New Site.

Tasks Detailed Steps

d. In the results pane, click SMS_SITE_COMPONENT_MANAGER, and then in

Tasks Detailed Steps

Are each of the systems assigned to the site?

Note: What is the discovered AD site name?

d. Click New (the icon resembles a starburst).

Tasks Detailed Steps

S-ar putea să vă placă și