deploying sccm 2010

Deploying System Center Configuration Manager v.Next


Table of Contents

Deploying System Center Configuration Manager v.Next ....................................................... 1

Exercise 1 Preparing Active Directory for Configuration Manager Integration ............................................................. 2

Exercise 2 Installing Microsoft Configuration Manager v.Next ..................................................................................... 5

Exercise 3 Installing a Configuration Manager v.Next Client ....................................................................................... 10

Exercise 4 Reporting ConfigMgr v.Next Client Deployment Status ............................................................................. 16


Page 1 of 18


Objectives

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

Prepare Active Directory for Configuration Manager publishing and integration

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 client on a Windows 7 computer

Install a reporting point and generate client deployment reports

Scenario

In this lab you will learn how to prepare and deploy the newest version of System Center Configuration Manager within a simulated operational environment.

Estimated Time to Complete This Lab

75 Minutes

Computers used in this Lab Primary1

Client1

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


Page 2 of 18

Exercise 1 Preparing Active Directory for Configuration Manager Integration

Scenario In this exercise, you will prepare Active Directory for use with Configuration Manager. You will use a utility that is provided with Configuration Manager to extend the Active Directory schema for publishing data by Configuration Manager. You will also grant rights for the Configuration Manager site server to allow it to publish data to Active Directory. Finally, you will create an Active Directory site that will be added to the Configuration Manager boundaries for client management.

Tasks Detailed Steps

Complete the following task on:

Primary1

1. Extend the Active Directory schema for Configuration Manager

a. Start C:\ConfigMgrv.Next\SMSSetup\Bin\x64 \Extadsch.exe.

Note: A Command Prompt window appears as the Active Directory schema is extended for use by Configuration Manager. When the schema extension process has completed, the command prompt window closes.

b. Open C:\ExtADSch.log. Note: 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. Notice that the schema extension process was successful, and that 14 attributes and four classes were added to Active Directory.

c. Verify that there are no errors listed in the log, and then close Notepad. Note: The site server will attempt to publish data to Active Directory after it has been deployed, provided it has the rights to publish. You can then view the System\System Management container to see the objects the site server publishes to Active Directory when configured to do so. In the next task, you will grant rights to the site server to publish site data to Active Directory.


Primary1

2. Grant the Configuration Manager site server rights to Active Directory

a. Click Start | Administrative Tools, and then click Active Directory Users and Computers.

Note: The Active Directory Users and Computers window appears.

b. On the View menu, click Advanced Features.

Note: The Active Directory Users and Computers window displays additional Active Directory information, including displaying the System container. You will grant rights to the System container to allow the Configuration Manager site server to publish data to Active Directory.

c. In the console tree, expand ConfigMgrDom.local, and then click System.

d. On the Action menu, click Properties.

Note: The System Properties dialog box appears.

e. Click the Security tab.

Note: The System Properties dialog box displays the security permissions on the System container. Notice that the Configuration Manager site server computer (Primary1) is not listed.

f. Click Add.

Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears.


Page 3 of 18


Notice that in the "Select the object type" box, computers will not be searched nor validated.

g. Click Object Types.

Note: The Object Types dialog box appears. Notice that "Computers" is not selected.

h. Under Object types, click Computers, and then click OK.

Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears. Notice that in the "Select the object type" box, computers will be searched and validated.

i. In the Enter the object names to select box, type Primary1 and then click OK.

Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears. Notice that the Configuration Manager site server computer (PRIMARY1) is now listed with Read rights.

j. Under Permissions for PRIMARY1, click Full Control under Allow, and then click Advanced.

Note: The Advanced Security Settings for System dialog box appears displaying the rights for various accounts.

k. Under Name, click PRIMARY1, and then click Edit.

Note: The Permission Entry for System dialog box appears displaying the rights for CONFIGMGRDOM\PRIMARY1$. The site server requires full control rights to the container, as well as all descendant objects.

l. In the Apply to field, click This object and all descendant objects, and then click OK.

Note: The Advanced Security Settings for System dialog box appears.

m. Click OK.

Note: The System Properties dialog box appears.

n. Click OK.

Note: The Active Directory Users and Computers window appears. You can leave this window open if you want to view information that Configuration Manager publishes to Active Directory after installation.


Primary1

3. Create an Active Directory site

Note: In the following procedure, you will create an Active Directory site to integrate with Configuration Manager as part of its boundaries. This process is not required, however it does provide a very common method to identify the clients to be managed by the local site.

a. Click Start | Administrative Tools, and then click Active Directory Sites and Services.

Note: The Active Directory Sites and Services window appears.

b. In the console tree, click Sites.

Note: The list of AD sites appears in the results pane. Notice the default site name of Default-First-Site-Name. You should never use the default site name (Default-First-Site-Name) as that site is created in all Active Directory implementations, and could lead to overlapping site boundaries when used. You should always create a custom, unique, AD site if you want to manage clients via AD site boundaries.

c. On the Action menu, click New Site.

Note: The New Object – Site dialog box appears.

d. In the Name box, type ConfigMgrSite

e. Under Link Name, click DEFAULTIPSITELINK, and then click OK.


Page 4 of 18


Note: An Active Directory Domain Services message box appears listing steps that may be required to complete the creation of the new site.

f. Click OK.

Note: The new site is now listed and selected in the tree view.

g. In the console tree, expand Sites, and then click Subnets.

Note: The list of IP subnets appears in the results pane. Notice that by default, no IP subnets are created.

h. On the Action menu, click New Subnet.

Note: The New Object – Subnet dialog box appears.

i. In the Prefix box, type 192.168.3.0/24 j. Under Select a site object for this prefix, click ConfigMgrSite, and then click OK. k. In the console tree, click Subnets.

Note: The list of subnets appears in the results pane. Notice the new subnet has been associated with the new AD site.

l. In the console tree, expand ConfigMgrSite, and then click Servers.

Note: The list of servers for this site appears in the result pane. Notice that there are no servers in this new site.

m. In the console tree, expand Default-First-Site-Name, expand Servers, and then click PRIMARY1.

Note: This is your domain controller. You will move this to your new site as its server.

n. On the Action menu, click Move.

Note: The Move Server dialog box appears displaying all sites available.

o. Under Site Name, click ConfigMgrSite, and then click OK.

The list of servers for the default site appears in the results pane. Notice that there are no servers in the default site.

p. In the console tree, expand Sites, expand ConfigMgrSite, and then click Servers.

Note: The list of servers for the new site appears in the results pane. Notice that your domain controller has been moved to the new site.

q. Close Active Directory Sites and Services.


Page 5 of 18

Exercise 2 Installing Microsoft Configuration Manager v.Next

Scenario In this exercise, you will install Configuration Manager using a custom installation. SQL Server 2008 SP1 is already installed on the computer Primary1. You will configure options in the Setup program to control the deployment of the standalone Configuration Manager site.



Primary1

1. Install a Configuration Manager v.Next standalone primary site

a. Start C:\ConfigMgrv.Next\Splash.hta.

Note: The Microsoft System Center Configuration Manager v.Next Beta 1 window appears. Notice the options available in the window include installing Configuration Manager v.Next, assessing server readiness, downloading the latest updates, installing the Configuration Manager console, and downloading System Center Updates Publisher. Also notice that you can access product documentation and help.

b. Click Install.

Note: The Welcome to the Microsoft System Center Configuration Manager v.Next - BETA 1Setup Wizard dialog box appears.

c. Click Next.

Note: The Microsoft System Center Configuration Manager v.Next Available Setup Options dialog box displays options for installation. Notice that you can either install a primary site or a central administration site.

4. Verify that Install a Configuration Manager Primary Site server is selected, and then click Next.

Note: The Microsoft System Center Configuration Manager v.Next Microsoft Software License Terms dialog box appears, prompting for a product key and displaying the license agreement. Read the licensing information.

d. In the Key box, enter your product key if it has not been pre-populated for you already.

e. Click I accept these license terms, and then click Next.

Note: The Microsoft System Center Configuration Manager v.Next Updated Prerequisite Components dialog box appears prompting for the location of the required prerequisite 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 virtual environment, the required files have already been downloaded and staged for the lab.

f. Click Browse.

Note: The Browse For Folder dialog box appears.

g. Point to C:\ConfigMgrv.Next\Redist, and then click OK.

h. Click The latest updates have already been downloaded to an alternate path, and then click Next.

Note: The Configuration Manager Product Updater dialog box appears for a few moments while verifying the prerequisite component files at the selected location. If successful, the dialog will close and then the Microsoft System Center Configuration Manager v.Next Site and Installation Settings dialog box appears.


Page 6 of 18


i. Open C:\ConfigMgrSetup.log.

Note: Notepad displays the contents of the ConfigMgrSetup.log file. Setup writes progress of the setup process to this log, including the results of the prerequisite component verification. Notice that the verification process was successful, and that 13 files were validated in seven different groups.

j. Verify that there are no errors listed in the log, and then close Notepad.

Note: The Microsoft System Center Configuration Manager v.Next Site and Installation Settings dialog box appears prompting for information about the site to be installed.

k. In the Site name box, type Configuration Manager Primary Site

l. In the Site code box, type MCM

m. Verify that the Installation folder box contains the default setting of C:\Program Files\Microsoft Configuration Manager.

n. Verify that Install Administrative console is selected, and then click Next.

Note: The Microsoft System Center Configuration Manager v.Next Primary Site Installation dialog box appears allowing you to configure whether this site will be joined with other servers in a hierarchy or if it will be a standalone site. As we do not need more than one primary site in our environment, we'll configure to be a standalone primary site.

o. Click Primary site will be installed as a standalone site, and then click Next.

Note: The Microsoft System Center Configuration Manager v.Next Site Mode dialog box appears displaying setup options for the Configuration Manager security mode. Notice that native mode configuration is the default selection, as it is more secure than mixed mode. However, native mode requires a public key infrastructure environment, with specific certificates installed, which most environments don't have in place.

p. Click Configuration Manager Mixed Mode, and then click Next.

Note: The Microsoft System Center Configuration Manager v.Next 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 Configuration Manager and the folder to be used when creating SQL replication snapshots.

q. Click Next to accept the default values of the Configuration Manager site server’s installation of SQL Server, SMS_MCM for the database name, and C:\ConfigMgrReplication for the snapshot folder.

Note: The Microsoft System Center Configuration Manager v.Next SMS Provider Settings dialog box appears prompting for the computer on which to install the SMS Provider. The SMS Provider is a security layer between the administrator and the information in the Configuration Manager site database. Usually this is recommended to be installed on the SQL Server computer, unless using a clustered SQL Server environment.

r. Click Next to use the Configuration Manager site server for the SMS Provider.

Note: The Microsoft System Center Configuration Manager v.Next Site System Roles dialog box appears prompting for which additional site system roles should be installed by Setup and the computer name(s) on which each role should be installed. Since Configuration Manager requires a management point and a distribution point, Setup will install them by default. The other options (Server Locator Point, Reporting Services Point, and Fallback Status Point) have not been implemented yet, so they are disabled in the current version of the product.

s. Click Next to install the management point and distribution point on the


Page 7 of 18


Configuration Manager site server.

Note: The Microsoft System Center Configuration Manager v.Next Client Agent Selection dialog box appears displaying the available Configuration Manager client agents, and allowing you to enable or disable each as desired.

t. Click Next to enable and configure the selected agents (ensuring that Network Access Protection is not enabled).

Note: The Microsoft System Center Configuration Manager v.Next Customer Experience Improvement Program Configuration dialog box appears prompting for participation in the customer experience improvement program. Notice that involvement in the program is mandatory for pre-release versions of the product.

u. Click Next to accept participation in the program.

Note: The Microsoft System Center Configuration Manager v.Next Settings Summary dialog box appears displaying various configuration values to be used during the installation of Configuration Manager v.Next.

v. Click Next.

Note: The Configuration Manager Installation Prerequisite Check runs to validate that the computers targeted for Configuration Manager v.Next installation meet the requirements for installation.

w. When complete, the Microsoft System Center Configuration Manager v.Next 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.

x. Open the file %TEMP%\ConfigMgrAutoSave.ini.

Note: The ConfigMgrAutoSave.ini file is created by Setup automatically when starting the prerequisite check. This file is useful if you would like to perform an unattended installation of a site server using the /SCRIPT [script file] command line option of Setup. For example, you may want to configure a Windows scheduled task to silently install the site server after business hours. The settings within the script file can also be modified and used to install other site servers, as well. Another use for this file is if any prerequisites are missing and the installation of the prerequisite requires a reboot. You can use the script file to perform an unattended installation instead of having to run through the Setup wizard and select all the same options again.

y. Close Notepad.

Note: The Microsoft System Center Configuration Manager v.Next Installation Prerequisite Check dialog box appears. As there are no errors in the prerequisite check, you can proceed with the installation of the site.

z. Click Begin Install.

Note: The Microsoft System Center Configuration Manager v.Next Setup Action Status Monitoring dialog box appears displaying the status of the individual tasks that must be completed as part of the Configuration Manager v.Next installation. 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.

aa. When complete, the Microsoft System Center Configuration Manager v.Next Setup Action Status Monitoring dialog box appears indicating that Setup completed each action successfully.

bb. Click Next.

Note: The Completing the Microsoft System Center Configuration Manager v.Next Setup Wizard dialog box appears indicating the site is ready to use.


Page 8 of 18


cc. Click Finish.


Primary1

2. Start the Configuration Manager Console

Note: In the following procedure, you will use Configuration Manager status messages generated by the site server installation to verify that the site server installation was successful.

a. Click Start | All Programs | Microsoft System Center | Configuration Manager v.Next, and then click ConfigMgr Console

Note: The System Center Configuration Manager console window appears displaying the Administration Overview page. Notice that the title of the window includes the site code and site name that the console is connected to.

b. In the wunderbar, click Monitoring. c. In the navigation pane, expand System Status, and then click Component Status. Note: The Monitoring Overview page appears.

The list of Configuration Manager components and their status appears in the results pane.

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

Note: A new menu appears.

e. Click All.

Note: The Status Messages: Set Viewing Period dialog box appears allowing you to configure the age of status messages to be displayed. Notice that the default value is to display status messages for the past one day.

f. Click OK.

Note: The ConfigMgr Status Message Viewer for <MCM> <Configuration Manager v.Next Primary Site> window appears. Notice the message with the ID of 1027. It indicates that the site server was configured to receive Configuration Manager server components.

g. Click the message, and then on the View menu, click Detail.

Note: The Status Message Details dialog box appears. Notice the header information for the message, as well as the text under Description.

h. Click OK.

Note: The ConfigMgr Status Message Viewer for <MCM> <Configuration Manager v.Next Primary Site> window appears.

i. On the File menu, click Exit.

Note: The list of Configuration Manager components appears in the results pane.

j. Follow previous steps 3-8 to display the status messages for SMS_HIERARCHY_MANAGER.

Note: The ConfigMgr Status Message Viewer for <MCM> <Configuration Manager v.Next Primary Site> window appears. Notice the messages with message IDs of 3306. These messages indicate that Hierarchy Manager has successfully processed a site control file modification and updated the site database.

k. Follow previous steps 3-8 to display the status messages for SMS_WINNT_SERVER_DISCOVERY_AGENT.

Note: The ConfigMgr Status Message Viewer for <MCM> <Configuration Manager v.Next Primary Site> window appears. Notice the message with a message ID of 4202. This message indicates one server was discovered and discovery data was written for it. This occurred as a result of installing Configuration Manager site components on the site server computer.


Page 9 of 18


l. In the wunderbar, click Administration. Note: The Administration Overview page appears.

m. In the navigation pane, expand Site Operations, and then click Sites. Note: The list of Configuration Manager sites appears in the list view. Notice that there is only one site in this hierarchy, that being MCM. Notice that the details pane displays summary information for the site selected in the list view.

n. In the navigation pane, click Site System Servers. Note: The list of Configuration Manager site systems for the site appears in the results pane. Notice that the site server is the only site system in this site.

o. In the navigation pane, click Site Roles. Note: The list of Configuration Manager site system roles for the site appears in the results pane. Notice that the site server, site database, management point, and distribution point roles have all been installed on the site server computer (as well as site system and component server).

You have now validated that the site has installed successfully, and will now complete some basic configuration of the site before installing a client.


Primary1

3. Configure Configuration Manager to use the new AD site as a boundary

Note: In the following procedure, you will add the Active Directory site to the Configuration Manager v.Next Boundaries. This will designate which clients are to be managed by this specific Configuration Manager site – those that are members of the specific Active Directory site. You are not required to use Active Directory sites as Configuration Manager boundaries, though it is a very common practice to do so.

a. In the wunderbar, click Administration. Note: The Administration page appears.

b. In the navigation pane, expand Site Hierarchy, and then click Boundaries.

Note: The list of boundaries for the local site appears in the results pane. Notice that there are no default boundaries added to the site.

c. In the Tasks pane, click Create Boundary.

Note: The Properties dialog box appears allowing the creation of a new boundary.

d. In the Description box, type Active Directory site for Configuration Manager

e. In the Type box, click Active Directory site, and then click Browse.

Note: 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 (ConfigMgrSite) are displayed. (You may notice a delay while the list of sites is being retrieved from Active Directory.) It is never recommended to use the default AD site (Default-First-Site-Name) as a boundary as it is a common name in all Active Directory environments.

f. Under Site Name, click ConfigMgrSite, and then click OK.

Note: The Properties dialog box appears displaying the information specified for the new boundary.

g. Under Network Connection, verify that Fast (LAN) is selected, and then click OK.

Note: The list of boundaries for the local site appears in the results pane. Notice that the new AD site (ConfigMgrSite) now appears as a boundary in the list view.


Page 10 of 18

Exercise 3 Installing a Configuration Manager v.Next Client

Scenario In this exercise, you will install the Configuration Manager v.Next client on the Windows 7 client computer. You will begin by using Active Directory System Discovery to discover the computer from Active Directory.



Primary1

1. Discover computers from Active Directory


b. In the navigation pane, expand Site Operations, and then click Sites.

Note: The list of Configuration Manager sites appears in the list view. Notice that there is only one site in this hierarchy, that being MCM.

c. In the details pane, click the Discovery Methods tab.

Note: The list of discovery methods for the local site appears in the details pane. Notice that there are four discovery methods related to Active Directory, and one each for Network Discovery and Heartbeat Discovery.

d. In the details pane, click Active Directory System Discovery, and then in the Tasks pane, under Active Directory System Discovery, click Properties.

Note: The Active Directory System Discovery Properties dialog box appears.

e. Select Enable Active Directory System Discovery, and then click New (the icon resembles a starburst).

Note: The New Active Directory Container dialog box appears allowing you to specify the path for the discovery.

f. Click Browse.

Note: The Select New Container dialog box appears allowing you to specify the container to use for discovery. In our lab, we’ll discover all systems starting at the root of the domain. However in a production environment, you may very well only want to discover systems from a specific organizational unit or container to control the systems that are discovered for a specific site.

g. Click ConfigMgrDom, and then click OK. Note: The New Active Directory Container dialog box appears. Notice that the distinguished name for the container to search. Also notice that a recursive search will be performed on that container, that groups are excluded from the search, and that the site server computer account will be used.

h. Verify that Recursively search Active Directory child containers is selected, and then click OK.

Note: The Active Directory System Discovery Properties dialog box appears. Notice that a recursive search will now beperformed on that container.

i. Click the Polling Schedule tab.

Note: 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 weekly. Also notice that by default, delta discovery is enabled and will run at five minute intervals (although it can be disabled or set to a different interval as desired).


Page 11 of 18


j. Click OK.

Note: The Configuration Manager Console window appears displaying the discovery methods in the details pane.

k. In the Tasks pane, under Active Directory System Discovery, click Run Now.

Note: A Discovery message box appears confirming the discovery is to be run now.

l. Click Yes.

Note: You will need to wait for a moment for the discovery process to complete.


Primary1

2. Verify Active Directory System Discovery

Note: In the following procedure, you will verify the results of the Active Directory System Discovery process. You will verify the results by updating the membership of the All Systems collection.

a. In the wunderbar, click Assets and Compliance.

Note: The Assets and Compliance Overview page appears.

b. In the navigation pane, click Device Collections.

Note: The list of collections for devices are displayed in the results pane. Notice that there are only four device collections included with the product.

c. In the results pane, click All Systems, and then in the Tasks pane, click Show Members.

Note: The "All Systems" collection is added as a sticky node in the navigation pane under "Collection Members", and then the members of the All Systems collection appear in the list view. Notice that there is one member in the All Systems collection currently that being the Configuration Manager site server (Primary1). If Primary1 does not appear yet, that is OK, as the collection membership will be updated and it will appear then.

d. In the Tasks pane, under All Systems, click Update Collection Membership.

Note: An All Systems message box appears prompting to update the collection membership.

e. Click OK.

Note: The collection is updated. It takes a moment before the database is updated with the new collection membership information.

f. In the navigation pane, click All Systems, and then refresh the All Systems collection membership.

Note: The collection membership is updated, and the current membership of the All Systems collection is displayed. Notice that there are now eight systems displayed as members of the All Systems collection, and that all eight are assigned to the local site MCM.

g. In the list view, click Client1, and then in the Tasks pane, under Client1, click Properties.

Note: The Client1 Properties dialog box appears displaying discovery properties. Notice that the data collected and displayed includes the AD Site Name, which is the same as the boundary configured for this Configuration Manager site, ConfigMgrSite.

h. Click OK.


Primary1

3. Create the account

Note: In the following procedure, you will create the account necessary to remotely install the ConfigMgr v.Next client on your Windows 7 client computer. In order to install the Configuration Manager client on a system from the site server, the site server requires administrative rights to the target client. This can be using the site server computer account, or a defined user account.

a. Click Start | All Programs | Administrative Tools | Active Directory Users and


Page 12 of 18


required to install the Configuration Manager client via a client push process

Computers.

Note: The Active Directory Users and Computers window appears.

b. Create a new user with the name of ClientInstall, assign it a password of password, ensure that the account is not disabled, and that the password does not require changing at first logon.

c. Add this user as a member of the Domain Admins group.

Note: This is the account that will be used to push the ConfigMgr v.Next client installation to the Windows 7 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.


Primary1

4. Configure the Configuration Manager v.Next client push account

Note: In the following procedure, you will configure the account in the Configuration Manager Console to allow installation of the ConfigMgr v.Next client. Configuration Manager must be configured to use the accounts that you want a client push process to use.


b. In the navigation pane, expand Site Operations, and then click Sites.


c. In the details pane, click the Client Installation Settings tab.

Note: The list of client installation methods appears in the details pane. Notice that there are two different client installation methods, client push and software update point client installation.

d. In the details pane, click Client Push Installation, and then in the Tasks pane, under Client Push Installation, click Properties.

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

e. Click the Accounts tab.

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

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

Note: The Windows User Account dialog box appears.

g. In the User name box, type ConfigMgrDom\ClientInstall

h. In the Password and Confirm password boxes, type password and then click OK.

Note: 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. You can list multiple accounts here that the site server can try to use as the client push installation account to different clients. Configuration Manager does not validate the account credentials, so it is important to type the credentials correctly.

i. Click OK.

Note: The Configuration Manager Console window appears.


Note: In the following procedure, you will use the Configuration Manager Console to install a fallback status point. This is recommended to get client deployment status reporting to provide easier validation that clients have been successfully installed, as well as to provide details as to why a client failed to install successfully (if a client


Page 13 of 18


Primary1

5. Install a fallback status point

does fail installation).

a. From the Administration root node, expand Site Operations, and then click Sites.


b. In the navigation pane, click Site Roles.

Note: The list of site system roles deployed in the site appears in the results pane. Notice that there is no fallback status point deployed in the site.

c. In the navigation pane, click Site System Servers.

Note: The list of site systems in the site appears in the results pane. Notice that there is only one site system in the site, that being the site server. It is recommended in a production environment that the fallback status point be installed on its own site system, however in our lab we'll install this role on the site server computer.

d. In the Tasks pane, click Create Roles.

Note: The New Site Role Wizard General dialog box appears. Notice that the site is publishing the intranet FQDN of the site server. This information was collected during Configuration Manger Setup.

e. Click Next.

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

Note: The New Site Role Wizard Fallback Status Point dialog box appears allowing you to configure the fallback status point message processing.

g. In the Throttle interval (in seconds) box, type 300, and then click Next.

Note: You should not use a value of 300 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.

Note: The New Site Role Wizard Wizard Completed dialog box appears indicating that the new role creation has succeeded. It will take a minute for the fallback status point installation to complete.

i. Click Close.

Note: The Configuration Manager Console window appears displaying the site systems for the site.

j. In the navigation pane, click Site Roles.

Note: The list of site system roles deployed in the site appears in the results pane. Notice that there is now a fallback status point deployed in the site on the site server - Primary1. you may need to refresh the site system roles to view the fallback status point.


Primary1

6. Configure the use of the fallback status

Note: In the following procedure, you will configure clients to use the fallback status point during installation of the ConfigMgr v.Next client. This provides data for a number of client deployment reports, two of which you’ll run at the end of the lab.

a. In the Administration navigation pane, expand Site Operations, and then click Sites.



Page 14 of 18


point b. In the details pane, click the Client Installation Settings tab.

Note: The list of client installation methods appears in the details pane.

c. In the details pane, click Client Push Installation, and then in the Task pane, under Client Push Installation, click Properties.

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

d. Click the Client tab.

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

e. Add the following to the existing command line (use a space as the delimiter between the two command line parameters): FSP=PRIMARY1 and then click OK.

Note: The Configuration Manager Console window appears.


Primary1

7. Install the Configuration Manager client on the Client1 computer using client push

Note: In the following procedure, you will use the Configuration Manager Console to push the installation of the Configuration Manager client to the Windows 7 client.

a. In the wunderbar, click Assets and Compliance.

Note: The Assets and Compliance page appears.

b. In the navigation pane, expand Collection Members, and then click All Systems.

Note: The members of the All Systems collection appear in the list view. Notice that there are eight members of the collection, including Client1.

c. In the list view, click Client1.

Note: The Tasks pane updates to include actions for the selected resource, in this case, Client1.

d. In the Tasks pane, under Client1, click Install Client. Note: The Client Push Installation Wizard dialog box appears.

e. Click Next.

Note: The Client Push Installation Wizard Installation options dialog box appears displaying options for the client installation. As Client1 is not a domain controller, and is not already installed with an existing Configuration Manager client, and there is only one site in our environment, we do not need to make any configuration on this wizard page.

f. Click Next to accept the default configuration to install the client to assigned resources.

Note: The Completing the Client Push Installation Wizard dialog box appears indicating it is ready to complete the installation. Notice that under Details, it displays the "Object name", which is listed as "Client1". You can use this information to verify the target of the push process before proceeding.

g. Click Next.

Note: The Client Push Installation Wizard Completion dialog box appears indicating that the wizard has successfully completed.

h. Click Close.

Note: The ConfigMgr v.Next client is remotely installed on the Windows 7 client computer. It will take a few minutes before the installation completes.


Note: In the following procedure, you will verify that the ConfigMgr v.Next client has been installed on the Windows 7 client.


Page 15 of 18


Client1

8. Verify the Configuration Manager v.Next client installation

a. In Control Panel, click System and Security, click Administrative Tools, and then start Services.

Note: The Services window appears.

b. Verify that the SMS Agent Host service has been installed and started.

Note: It may take a while for the installation to complete. If SMS Agent Host is not displayed, wait a few minutes and continue to refresh until it displays. The SMS Agent Host service is the primary service for Configuration Manager clients.

c. Close Services, close Administrative Tools, and then close Control Panel.

Note: You have now validated that Client1 has successfully installed the Configuration Manager client locally. You will verify that the client has reported into the Configuration Manager site as a client in the next task.


Primary1

9. Verify the reporting of the ConfigMgr v.Next client

Note: In the following procedure, you will verify that the Windows 7 client has reported to the Configuration Manager site that it is installed as a ConfigMgr v.Next client. You will view collection information at this point, then reports in the next exercise.

a. From the Assets and Compliance root node , expand Collection Members, and then click All Systems.

Note: The members of the All Systems collection appear in the results pane. Notice that the Windows 7 computer does not appear.

b. In the Tasks pane, click Update Collection Membership.

Note: The All Systems message box appears prompting to update the collection membership.

c. Click OK.

Note: The collection is updated.

d. In the navigation pane, click All Systems, and then refresh the list of collection members.

Note: The collection membership is updated, and the current membership of the All Systems collection is displayed. Notice that the list view includes the "Client Type" and "Client" attributes. Also notice that Client1 displays "Advanced" under "Client Type" and "Yes" under "Client".

e. In the list view, click Client1, and then in the Tasks pane, under Client1, click Properties.

Note: The Client1 Properties dialog box appears displaying discovery properties. Notice that you now see "Agent Name" values of "MP_Client Registration" and "Heartbeat Discovery". These values, along with the "Client" attribute displaying a value of "1" indicate that the computer is a Configuration Manager client.

f. Click Cancel.

Note: The list of members of the All Systems collection appears in the list view.

You have now validated that the computer Client1 is installed as a Configuration Manager client and has sent client data to the site.


Page 16 of 18

Exercise 4 Reporting ConfigMgr v.Next Client Deployment Status

Scenario In this exercise, you will install a Reporting Services point for your Configuration Manager site and then run reports to verify the client deployment success in the site.



Primary1

1. Install a Reporting Services point


b. In the navigation pane, expand Site Operations, and then click Sites. Note: The list of Configuration Manager sites appears in the list view. Notice that there is only one site in this hierarchy, that being MCM.

c. In the navigation pane, click Site Roles. Note: The list of site system roles deployed in the site appears in the results pane. Notice that there is no reporting services point deployed in the site.

d. In the navigation pane, click Site System Servers. Note: The list of site systems in the site appears in the results pane. Notice that there is only one site system in the site, that being the site server. In a production environment you may want the reporting point to be installed on its own site system, however in our lab we'll install this role on the site server computer.

e. In the Tasks pane, click Create Roles. Note: The New Site Role Wizard General dialog box appears. Notice that the site is publishing the intranet FQDN of the site server. This information was collected from Configuration Manager Setup.

f. Click Next. Note: 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.

g. Under Available roles, select Reporting Services point, and then click Next. Note: The New Site Role Wizard Reporting Services point dialog box appears allowing you to configure the settings for this Reporting Services point.

h. Verify that the server (Primary1) and database (SMS_MCM) are correct, and then click Verify.

Note: This process is required (as indicated by the red circle and white exclamation point) and is used to verify that the Reporting Services point can access the site database. When verified, the red circle and white exclamation point are removed and a message appears indicating that the verification was successful.

i. In the Credentials box, click Credentials stored securely in the report server. Note: This is the recommended setting from the SQL Server product group.

j. In the User name box, type ConfigMgrDom\administrator k. In the Password and Confirm password boxes, type password l. Select Use as Windows credentials when connecting to the data source, and

then click Next. Note: In a production environment, you likely would use a different account as the


Page 17 of 18


reporting account. However for simplicity in the lab environment, you are configuring the Reporting Services point to use the domain admin account.

m. The New Site Role Wizard Summary dialog box appears indicating that you have successfully completed the wizard.

n. Click Next. Note: The New Site Role Wizard Confirmation dialog box appears indicating that Configuration Manager is now ready to begin installation of the Reporting Services point.

o. Click Close. Note: The Configuration Manager Console window appears displaying the site systems for the site. It will take a minute to install the Reporting Services point site system role.

p. In the navigation page, click Site Roles. Note: The list of site system roles deployed in the site appears in the results pane. Notice that there is now a reporting services point deployed in the site on the site system Primary1. If it does not appear yet, you will need to wait another moment, and then refresh the list of site system roles.


Primary1

2. Report Configuration Manager data

Note: In the following procedure, you will run a few built in reports to validate that the Reporting Services point is running successfully and that the client was deployed successfully.

a. In the wunderbar, click Monitoring.

Note: The Monitoring Overview page appears.

b. In the navigation pane, expand Reporting, and then click Reports.

Note: The list of reports appears in the results pane. Notice that there are 397 reports available. If the list of reports does not appear, wait a moment, and then refresh the Reports node. The

reports are installed after the role has been installed, and takes a few minutes to complete the installation of the reports.

c. In the results pane, click Computers assigned but not installed for a particular site, and then in the Tasks pane, under Computers assigned but not installed for a particular site, click Run.

Note: The Computers assigned but not installed for a particular site report appears in a new window. 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 View Report.

Note: The Computers assigned but not installed for a particular site report appears. Notice that there are multiple computers discovered and assigned to the site that are not yet installed as clients, one being the site server (Primary1).

e. Close the Computers assigned but not installed for a particular site window.

Note: The Configuration Manager Console window appears displaying the list of reports appears in the results pane.

f. In the results pane, click Client Deployment Status Details, and then in the Tasks pane, under Client Deployment Status Details, click Run.

Note: The Client Deployment Status Details report appears in a new window. 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).


Page 18 of 18


g. Close the Client Deployment Status Details window.

Note: The Configuration Manager Console window appears displaying the list of reports appears in the results pane.

h. In the results pane, click Client Deployment Success Report, and then in the Tasks pane, under Client Deployment Success Report, click Run.

Note: The Client Deployment Success Report appears in a new window. Notice that this report displays that status of each client that was installed. Notice that Client1 is listed as a successfully deployed client.

These last two reports use data that is generated via a fallback status point, so you can only use these reports if you have installed a fallback status point in your site, and clients have been configured to use the fallback status point for client deployment state reporting.

You have now successfully deployed Configuration Manager v.Next in your AD environment, including site systems required for client deployment, and have successfully installed a client computer using the client push installation process.

deploying sccm 2010

Documents

white exclamation

fallback status

schema extension

active directory

active directory

reporting

expand site

confirm password