3.exercise - SCCM Microsoft

Lab Answer Key: Module 1: Managing computers and mobile devices in the enterprise
Lab: Exploring the Configuration Manager tools

Exercise 1: Searching in the Configuration Manager console
Task 1: Using console filters
1. Sign in to LON-CFG as Adatum\Administrator with the password Pa55w.rd.
2. On the taskbar, click the Configuration Manager console icon.
3. In the Configuration Manager console, in the Assets and Compliance workspace, click the Users node.
Note: At the top of the results pane, the Users indicator shows that there are 32 items in the results pane.
4. In the search bar, type ch, and then click Search.
5. The Users indicator shows that there are 2 items.
Task 2: Using search criteria

1. Click the Devices node.
Note: At the top of the results pane, the Devices indicator shows that 8 items are in the results pane.
2. Click the Add Criteria link. Note the available criteria for devices.
3. Click Name, and click Add.
4. In the AND Name row, in the Enter valid characters text box, type LON, and then click Search.
5. Verify that the Devices indicator now shows that there are 6 items.
6. Click the Add Criteria link.
7. Scroll down, click Operating System, and then click Add.
8. In the AND Operating System row, in the Enter valid characters text box, type Server, and then
click Search.
Note: Note that the results contain three servers LON-SVR2, LON-SVR1, and LON-CFG.
9. In the AND Operating System row, delete Server, and in the Enter valid characters text box,
type Windows, and then click Search.
Note: The results show that all the LON computers run a Windows operating system.
Task 3: Create and save a local node search

1. In the Configuration Manager console, click the Assets and Compliance workspace.
2. Click User Collections.
3. Double-click All Users. This runs a local node search automatically, and displays all the
members of the collection.
4. Next to the Search button, click Add Criteria, select the Name check box, and then

click Add.
5. In the AND Name row, click contains, and then note the options available for refining the
search.
6. Click starts with, type Adatum\T in the Enter valid characters text box, and then
click Search. The results are now limited to the Adatum users whose names begin with T.
7. On the ribbon, in the Save group, click Save Current Search.
8. In the Configuration Manager dialog box, type T users, and then click OK.
Task 4: Create and save a global search

1. Select the Overview node, and on the ribbon, click All Objects.
2. In the Search text box, type Configuration Manager, and then click Search.
Note: Notice the different Object Types and Workspaces that the search returns.
3. On the ribbon, in the Save group, click Save Current Search.
4. In the Configuration Manager dialog box, in the Search name field, type Configuration

Manager Objects, and then click OK.
5. Close the Configuration Manager console.
Task 5: Use saved searches

1. On the taskbar, click the Configuration Manager console icon.
Note: You should notice that the sticky nodes from your previous searches were closed when the
console was closed.
2. On the ribbon, click Saved Searches. This displays a drop-down list of the saved searches
categories.
Note: The only available option is global searches: Manage Searches for All Objects.
4. Click the User Collections node.
5. Click Saved Searches, and click Manage Searches for Current Node. Note that no searches are
available, and click Cancel.
6. Double-click the All Users collection.
7. On the ribbon, click the Home tab.
8. Click Saved Searches, and click Manage Searches for Current Node. Note that the T users search is
available, and click Cancel.
9. Click the Device Collections node.
10. On the ribbon, click Saved Searches, and then click Manage Searches for All Objects.
11. Click the Configuration Manager Objects search, and click OK.
Note: This displays the same results as before.
Result: At the end of this exercise, you should have performed both local node and global searches. You also should have refined the local node
search and saved the custom local node search for future use. Finally, you should have observed the differences between saving a global search and
saving a local node search. You can view the expected results in the lab answer key.
Exercise 2: Using Windows PowerShell with Configuration Manager

Task 1: View all commands related to Configuration Manager
1. In the Configuration Manager console, in the upper- left corner, click the Down Arrow, and then
click Connect via Windows PowerShell.
2. When prompted in the Windows PowerShell window, on the keyboard, press A, and then press
Enter.
3. To view all of the cmdlets in the Configuration Manager module for Windows PowerShell, at the
Windows PowerShell command prompt, type the following command, and then press Enter:
Get-Command –Module ConfigurationManager | Out-Gridview
4. Review the commands, and close the Get-Command –Module ConfigurationManager | Out-

Gridview dialog box.
Task 2: View Configuration Manager information
1. To view a list of devices, in the Windows PowerShell window, type the following
command, and then press Enter:
Get-CMDevice | ft Name, ADSiteName, SiteCode, DeviceOS
2. To view a list of distribution points, in the Windows PowerShell window, type the
following command, and then press Enter:
Get-CMDistributionpoint
3. To view a list of management points, in the Windows PowerShell window, type the
Get-CMManagementPoint | ft NetworkOSPath, RoleName, SiteCode, RoleCount
4. To view a list of packages, in the Windows PowerShell window, type the following
Get-CMPackage | ft Name, Description, PkgSourcePath
5. To view a list of applications, in the Windows PowerShell window, type the following
Get-CMApplication | ft LocalizedDisplayName, SourceSite
6. To view a list of sites, in the Windows PowerShell window, type the following
Get-CMSite | ft SiteName, SiteCode, ServerName
7. To view a list of users, in the Windows PowerShell window, type the following
Get-CMUser | ft Name, Domain
8. To view a list of user collections, in the Windows PowerShell window, type the
Get-CMUserCollection | ft Name, Comment, MemberCount
9. To view a list of device collections, in the Windows PowerShell window, type the
Get-CMDeviceCollection | ft Name, Comment, MemberCount
10. Close the Administrator: Windows PowerShell window.
Result: At the end of this exercise, you will have used Windows PowerShell to determine information about Configuration Manager devices,
distribution and management points, packages, applications, sites, users, and user and device collections.
Exercise 3: Using Configuration Manager Service Manager to manage components
Task 1: Configure the log file size for a single component
1. Click the Monitoring workspace, and expand the System Status folder.
2. Click the Component Status node.
3. On the ribbon, click the Home tab, click the Start drop-down list box, and then
click Configuration Manager Service Manager.
4. Click to expand S01, and click Components.
5. In the right pane, scroll down, right-click SMS_POLICY_PROVIDER, and then click Logging.
6. In the Configuration Manager Component Logging – Single Component dialog box, set the Log

Size (MB): scroll box to 5.
7. From the Log filename field, write down the name of the log file that displays.
8. To close the Configuration Manager Component Logging – Single Component dialog box,

click OK.
Task 2: Manage Configuration Manager components

1. Right-click SMS_POLICY_PROVIDER, and click Select All.
2. Right-click one of the selected components, and click Query.
3. To dismiss the Configuration Manager Service Manager dialog box, click OK. You can dismiss the
messages about error communicating with components. This message indicates that some
components are not configured, which is expected.
4. Scroll through the list of services, and note that some services are not running. To remove the
highlighting, click SMS_POLICY_PROVIDER.
5. Right-click SMS_POLICY_PROVIDER, and click Stop. Note that the status display does not change.
6. Right-click SMS_POLICY_PROVIDER, and click Query.
7. Right-click SMS_POLICY_PROVIDER, and click Start.
8. Right-click SMS_POLICY_PROVIDER, and click Query.
9. Close the Configuration Manager Service Manager.
Result: At the end of this exercise, you should have used Configuration Manager Service Manager to manage Configuration Manager components by
adjusting the log file sizes, and stopping and starting components.
Exercise 4: Monitoring Site and Component Status

Task 1: Examine the Site Status node
1. Click the Site Status node.
2. Examine the Site Status node.
Note: All of the icons should have a green circle with a white check mark to indicate that they are okay. If there are any red circles with a white X
(Critical), notify your instructor.
Task 2: View Site Status messages

1. Under Site System Role, right-click the Site server role, click Show Messages, and then click All.
2. In the Status Messages: Set Viewing Period dialog box, retain the default settings, and then
click OK.
3. In Configuration Manager Status Message Viewer for <S01> <Adatum Site>, click View, and
then click Filter.
4. In the Message ID: text box, type 5104, and then click OK.
5. Double-click the status message for the latest milestone from SMS_POLICY_PROVIDER.
6. Examine the status message, and write down the Process ID information.
7. To close the Status Message Details dialog box, click OK, and then close the Configuration
Manager Status Message Viewer for <S01> <Adatum Site>.
Task 3: View Component Status messages

1. Click the Component Status node, and examine the status of the components.
Note: If any of the components display a red circle with a white X, notify your instructor.
2. Right-click SMS_POLICY_PROVIDER, click Show Messages, and then click All.
3. In the Status Messages: Set Viewing Period dialog box, retain the default settings, and
then click OK.
4. Note the number of entries between the latest 5104 milestone and the previous 5104
milestone.
5. Double-click the latest 5104 status message, and examine the status message.
Note: This is the same status that you reviewed in the previous task.
6. To close the Status Message Details dialog box, click OK.
7. Close Configuration Manager Status Message Viewer for <S01> <Adatum Site>, and close
the Configuration Manager console.
Result: At the end of this exercise, you should have examined the status messages for a site system and a component.
Exercise 5: Reviewing log files by using the Configuration Manager Trace tool
Task 1: Use the Configuration Manager Trace Log tool
1. On the taskbar, click the File Explorer icon.
2. Navigate to the C:\Program Files\Microsoft Configuration Manager\tools folder.
3. Right-click cmtrace.exe, and click Pin to Taskbar.
4. On the taskbar, click the Configuration Manager Trace Log Tool icon.
5. In the Configuration Manager Trace Log Tool, click File, and then click Open.
6. Scroll down, click the Policypv.log file, and then click Open.
7. Click Tools, and click Highlight. In the Highlight text box, type 5104, and then click OK.
8. Click Tools, and click Find. In the Find text box, type the Process ID that you recorded earlier, and then
click Find.
9. To find the next entry, press the F3 key, and repeat until there are no more new responses.
10. Scroll up until you see the previous highlighted entry. Note the number of entries between the two
milestones.
Question: How does the number of events between milestones compare to the number of events shown in
the status message viewer?
Answer: Typically there are more entries in the log file than in the status message viewer.
11. Click Tools, and click Filter.
12. In the Filter Settings dialog box, select the Filter when the Entry Text check box.
13. In the Filter when the Entry Text drop-down list box, click contains.
14. In the text box next to the Filter when the Entry Text drop-down list box, type the Process ID that you
recorded earlier, and then click OK.
15. Close the Configuration Manager Trace Log tool.

Lab Answer Key: Module 2: Analyzing data using queries, reports, and CMPivot
Lab A: Creating and running queries
Exercise 1: Creating data queries
Task 1: Create a query for Marketing users
1. On LON-CFG, if the Configuration Manager console is not open already, on the taskbar, click

the Configuration Manager Console icon.
2. Click the Monitoring workspace, and then click Queries.
3. Right-click the Queries node, and then click Create Query.
4. In the Create Query Wizard, on the General page, in the Name box, type Marketing Users, and then

click Import Query Statement.
5. In the Browse Query dialog box, in the Queries box, click All Users, and then click OK.
6. In the Create Query Wizard, on the General page, click Edit Query Statement, and then click
the Criteria tab.
7. In the Marketing Users Query Statement Properties dialog box, click New ( ).
8. In the Criterion Properties dialog box, click Select.
9. In the Select Attribute dialog box, in the Attribute class drop-down list, click User Resource.
10. In the Attribute drop-down list, click User Group Name, and then click OK.
11. In the Criterion Properties dialog box, verify that in the Operator box, the is equal to option is
selected.
12. In the Value box, use the Value button to browse to ADATUM\Marketing, and then click OK twice.
13. In the Marketing Users Query Statement Properties dialog box, click OK.
14. In the Create Query Wizard, on the General page, click Next.
15. On the Summary page, click Next, and then on the Completion page, click Close.
Task 2: Create a query for Sales or Research users
2. In the Create Query Wizard, on the General page, in the Name box, type Sales or Research Users, and

then click Import Query Statement.
the Criteria tab.
5. In the Sales or Research Users Query Statement Properties dialog box, click New ( ).
6. In the Criterion Properties dialog box, click the Criterion Type drop-down list, and then select List of
values.
7. Click Select.
8. In the Select Attribute dialog box, in the Attribute class list, click User Resource.
9. In the Attribute list, click User Group Name, and then click OK.
10. In the Criterion Properties dialog box, verify that in the Operator box, the is in option is selected.
11. In the Value to add box, type ADATUM\Sales, and then click Add.
12. In the Value to add box, type ADATUM\Research, click Add, and then click OK.
13. In the Sales or Research Users Query Statement Properties dialog box, click OK.
15. On the Summary page, click Next.
16. On the Completion page, click Close.
Task 3: Run the user data queries
1. Right-click the Marketing Users query, and then click Run.

2. Review the results, which should include 52 users.
3. Click the Queries node, right-click the Sales or Research Users query, and then click Run.
Result: After this exercise, you should have created and tested data queries in Configuration Manager.
Exercise 2: Creating subselect queries
Task 1: Create a query for users who are in the Marketing department
2. In the Create Query Wizard, on the General page, in the Name box, type All Marketing Users.
3. In the Object Type drop-down list, click User Resource, and then click Edit Query Statement.
4. In the All Marketing Users Query Statement Properties dialog box, on the General tab, click New ( ).
5. In the Result Properties dialog box, click Select.
6. In the Select Attribute dialog box, in the Attribute drop-down list, click Unique User Name, and then
click OK.
7. In the Result Properties dialog box, click OK.
8. In the All Marketing Users Query Statement Properties dialog box, click the Criteria tab, and then
click New ( ).
10. In the Select Attribute dialog box, in the Attribute Class list, click User Resource.
11. In the Attribute list, click User Group Name, and then click OK.
12. In the Criterion Properties dialog box, verify that in the Operator box, the is equal to option is selected.
13. In the Value box, type ADATUM\Marketing, and then click OK.
14. In the All Marketing Users Query Statement Properties dialog box, click OK.
Task 2: Create a query for users who are not in the Marketing department
2. In the Create Query Wizard, on the General page, in the Name box, type Users Not in the

Marketing Group, and then click Import Query Statement.
the Criteria tab.
5. In the Users Not in the Marketing Group Query Statement Properties dialog box, click New
( ).
6. In the Criterion Properties dialog box, in the Criterion Type drop-down list, click SubSelected

values, and then click Select.
8. In the Attribute list, click Unique User Name, and then click OK.
9. In the Criterion Properties dialog box, in the Operator list, select is not in.
10. Click Browse, browse to and select the All Marketing Users query, and then click OK.
11. In the Criterion Properties dialog box, click OK.
12. In the Users Not in the Marketing Group Query Statement Properties dialog box, click OK.
16. Right-click the Users Not in the Marketing Group query, and then click Run.
18. Minimize the Configuration Manager console.

Task 3: Prepare for the next lab
• When you finish the lab, keep the virtual machines running because you will need them for the next
lab in this module.
Result: After this exercise, you should have created and tested a subselected data query in Configuration Manager.
Lab B: Configuring SSRS

Exercise 1: Configuring a reporting services point
Task 1: Configure SSRS
1. On LON-CFG, click Start, expand Microsoft SQL Server 2016, and then click Reporting Services
Configuration Manager.
2. In the Reporting Services Configuration Connection dialog box, click Connect.
3. In Reporting Services Configuration Manager:LON-CFG\MSSQLSERVER, click the Service Account node.
4. Under Report Server Service Account, in the Network Service drop-down list, verify that the Network
Service account is being used.
5. Click the Web Service URL node, and review the default settings. Click Apply.
6. On the Database page, click Change Database.
7. In the Report Server Database Configuration Wizard, on the Action page, ensure that Create a new

report server database is selected, and then click Next.
8. On the Database Server page, click Test Connection. If it is successful, click OK, and then click Next. If it

is not successful, contact your instructor.
9. On the Database page, click Next.
10. On the Credentials page, click Next.
12. On the Progress and Finish page, click Finish.
13. In Reporting Services Configuration Manager:LON-CFG\MSSQLSERVER, click the Web Portal URL node.

Verify the URL, and then click Apply.
14. Click the URL, and then verify that the SQL Server Reporting Services Home page appears.
15. Close Internet Explorer.
16. In Reporting Services Configuration Manager:LON-CFG\MSSQLSERVER, click Exit.
Task 2: Install and configure the reporting services point role

1. Restore the Configuration Manager console.
2. Click the Administration workspace, and then expand Site Configuration.
3. Click Servers and Site Systems Roles.
4. Right-click \\LON-CFG.Adatum.com, and then click Add Site System Roles.
5. In the Add Site System Roles Wizard, on the General page, click Next.
6. On the Proxy page, click Next.
7. On the System Role Selection page, select the Reporting services point check box, and then click Next.
8. On the Reporting Services Point page, click Verify.
9. On the Reporting Services Point page, click Set, and then click New Account.
10. In the Windows User Account box, click Browse, type Adatum\Administrator, and then click OK.
11. In the Password and Confirm password boxes, type Pa55w.rd, and then click OK.
12. On the Reporting services point page, click Next.
13. Review the Summary page, and then click Next.
15. Open File Explorer, and then navigate to and open the C:\Program Files\Microsoft Configuration
Manager\Logs\srsrpsetup.log file.
16. Monitor the reporting services point installation by using the srsrpsetup.log file.
Task 3: Test the reporting services point in the Configuration Manager console
1. In the Monitoring workspace, expand Reporting, and then click Reports.
Note: You might have to refresh the console until all reports display. You can
also monitor the C:\Program Files\Microsoft Configuration
Manager\Logs\srsrp.log file for status on the deployed reports. It will take
several minutes for the reports to be deployed.
2. Expand Reports, and then click Users.
3. Right-click the Users in a specific domain report, and then click Run.
4. In the Users in a specific domain window, click Values.
5. In the Parameter Value dialog box, click ADATUM, and then click OK.
6. In the Users in a specific domain window, click View Report.
7. Close the Users in a specific domain window, and then minimize

the Configuration Manager console.
Task 4: Test the reporting services point in the SQL Server Reporting Services website
1. Open Internet Explorer. In the address bar, type http://LON-CFG/Reports, and then press Enter.
2. Click the ConfigMgr_S01 link, and click the Users folder.
3. Click the Count users by domain report.
4. View the results, and then close Internet Explorer.
• When you finish the lab, keep the virtual machines running because you will need them for the next lab in
this module.
Result: After this exercise, you should have installed and configured a reporting services point and tested it by opening reports in both
the Configuration Manager console and the SQL Server Reporting Services (SSRS) website.
Lab C: Analyzing the real-time state of a device by using CMPivot

Exercise 1: Using CMPivot to Analyze the current state of devices
Task 1: Create a CMPivot query to analyze local administrative users
1. On LON-CFG, if the Configuration Manager console is not already open, on the taskbar, click
2. Click the Asset and Compliance workspace, and then click Device Collections.
3. In the center panel, right-click All Desktop and Server Clients, and then click Start CMPivot.
4. In the CMPivot (All Desktop and Server Clients) window, click the Query tab.
5. On the Query tab, in the text box, type Administrators.
6. Click the Run Query button.
7. Review the results.
Task 2: Create a collection based on the CMPivot query results

1. In CMPivot, select the Query Summary tab.
2. Next to the Failed row, click 1.
3. In the Failed Devices window, make a note of the reason for the failure.
4. Click Create Collection.
5. In the Create Device Collection Wizard, on the General page, in the Name box,

type Computers without PowerShell 5.
6. Click Next.
7. On the Membership Rules page, clear the Schedule a full update on this collection check

box.
8. Click Summary.
10. On the Completed page, click Close.

11. Close the Failed Devices Window.
12. Close the CMPivot (All Desktop and Server Clients) window.
Task 3: Create a user on LON-CL1

1. On LON-CL1, click Start and then type Computer Management.
2. Click Computer Management.
3. In the Computer Management window, expand Local Users and Groups.
4. Right-click Users, and then select New User.
5. In the New User window, in the User name text box, type Bill.
6. In the Password text box, type Pa55w.rd.
7. In the Confirm Password text box, type Pa55w.rd.
8. Click Create.
9. Click Close.
10. Select Users, and then verify that the user account Bill is listed under it.
11. Right-click Bill, and then select Properties.
12. Click the Member Of tab.
13. Click Add… .
14. In the Select Groups window, in the Enter the object names to select text box, type Administrators.
15. Click OK twice.
Task 4: Rerun the CMPivot query to analyze local administrative users

1. On LON-CFG, if the Configuration Manager console is not already open, on the taskbar, click
2. Click the Asset and Compliance workspace, and then click Device Collections.
3. In the center panel, right-click All Desktop and Server Clients, and then click Start CMPivot.
4. In the CMPivot (All Desktop and Server Clients) window, click the Query tab.
5. On the Query tab, in the text box, type Administrators.
8. Notice that the user Bill is listed on LON-CL1.
Task 5: Export the CMPivot query results to a CSV file

1. In the CMPivot (All Desktop and Server Clients) window, on the Query tab, click Export, and then
click To File.
2. In the Export to File window, under Quick access links, click Desktop.
3. In the File name text box, type List of who is in the local Administrator group, and then click Save.
4. On the computer’s desktop, double-click the List of who is in the local Administrator group.csv file.
5. In the How do you want to open this file? Window, select Notepad, and then click OK.
6. Notice these results are the same as the results listed in the CMPivot results pane.
7. Close Notepad.
Task 6: Run a CMPivot query to identify stopped services

1. In the CMPivot (All Desktop and Server Clients) window, on the Query tab, replace the existing
text with Services | where State == 'Stopped'.
Note: Make sure that “where” is in lowercase.
4. In the CMPivot (All Desktop and Server Clients) window, on the Query tab, replace existing text
with Services | where State == 'Stopped'.
7. Replace existing text with Services | where State == 'Stopped' | summarize count() by Caption.
10. On the Query Results tab, next to the Application Information row, click 1.
11. Review results in both the query box and the results area.
Additional Reading: When you have time, try changing “where” to “Where” in one the queries, and then run it. Note the errors generated.
Lab Answer Key: Module 3: Preparing the Configuration Manager management infrastructure
Lab A: Configuring boundaries and resource discovery
Exercise 1: Configuring boundaries, boundary groups, and fallback relationships

Task 1: Configure boundaries
1. On LON-CFG, on the taskbar, click the Configuration Manager Console icon.
2. In the System Center Configuration Manager console, click the Administration workspace, and then expand Hierarchy Configuration.
3. Click Discovery Methods, and then click Active Directory Forest Discovery.
4. On the ribbon, click Properties.
5. In the Active Directory Forest Discovery Properties dialog box, select the following check boxes:
o Enable Active Directory Forest Discovery
o Automatically create Active Directory site boundaries when they are discovered
Do not select the Automatically create IP address range boundaries for IP subnets when they are discovered check box.
6. To close the Active Directory Forest Discovery Properties dialog box, click OK.
7. When you see the Do you want to run full discovery as soon as possible? message, click Yes.
Note: Before continuing, wait approximately one minute for the discovery to complete and for boundary objects to be created.
8. Click the Boundaries node, and then refresh the details pane. It might take a minute or two for the results to display.
Note: Do not continue until you see the following boundaries created by the Active Directory Forest Discovery method:
• Sydney
• Toronto
Task 2: Configure boundary groups and relationships

1. In the Administration workspace, expand Hierarchy Configuration, and then click the Boundary
Groups node.
Note: Notice the London boundary group in the results pane. This has been preconfigured for the labs
in this course.
2. Right-click London, and then click Properties. Notice that AdatumHQ is the only member of this
group.
3. Click the References tab.
Note: Notice that the S01-Adatum Site is used for site assignment for all clients that are part of the
boundaries assigned to this boundary group. LON-CFG.Adatum.com is configured as policy and
content location for the boundary group.
4. To close the London Properties dialog box, click OK.

5. Right-click Boundary Groups, and then click Create Boundary Group.
6. In the Name box, type Toronto, and then click Add.
7. In the Add Boundaries dialog box, select Toronto, and then click OK.
8. In the Create Boundary Group dialog box, click the References tab, and then click Add.
9. In the Add Site Systems dialog box, select \\LON-CFG.Adatum.com, and then click OK.
10. Under Site assignment, select the check box next to Use this boundary group for site assignment.
11. To close the Create Boundary Group dialog box, click OK.
12. Verify that Toronto now displays in the results pane.
13. Right-click Boundary Groups, and then click Create Boundary Group.
14. In the Name box, type Sydney, and then click Add.
15. In the Add Boundaries dialog box, select Sydney, and then click OK.
16. In the Create Boundary Group dialog box, click the References tab.
17. Under Site assignment, select the check box next to Use this boundary group for site assignment.
18. To close the Create Boundary Group dialog box, click OK.
19. Verify that Sydney now displays in the results pane.
Configure fallback
1. In the Administration workspace, click the Boundary Groups node.
2. Right-click Sydney and then click Properties.
3. In the Sydney Properties dialog box, click the Relationships tab, and then click Add.
4. In the Fallback Boundary Groups dialog box, select London.
5. Under Fallback times (in minutes), change the Distribution point value to 10 minutes.
6. Click OK to close the Fallback Boundary Groups dialog box. This will ensure that if a client cannot find a
distribution point within 10 minutes, it will fall back and use the Distribution point in London.
7. Click OK to close the Sydney Properties dialog box.
Result: After completing this exercise, you should have created and configured boundaries and boundary groups.
Exercise 2: Configuring Active Directory discovery methods
Task 1: Configure the Active Directory System Discovery method
1. Click the Administration workspace, expand Hierarchy Configuration, and then click Discovery

Methods.
2. In the results pane, double-click Active Directory System Discovery. Notice that the Enable
Active Directory System Discovery check box is selected and that several organizational units
(OUs) have been configured.
3. Click New.
4. In the Active Directory Container dialog box, click Browse.
5. In the Select New Container dialog box, click the Toronto Clients container, and then click OK.
6. Verify that the Recursively search Active Directory child containers check box is selected, and
then click OK.
7. Repeat steps 3 through 6 for Toronto Servers, Sydney Clients, and Sydney Servers.
8. On the Polling Schedule tab, click Schedule, configure the recurrence to take place every 5 days,

and then click OK.
9. Verify that the Enable delta discovery check box is selected and that the interval is configured
as 5 minutes, and then click OK.
10. Right-click Active Directory System Discovery, and then click Run Full Discovery Now.
11. When Configuration Manager displays the Do you want to run full discovery as soon as
possible? message, click Yes.
Task 2: Configure the Active Directory User Discovery method
1. On LON-CFG, in the System Center Configuration Manager console, click

the Administration workspace, and then expand Hierarchy Configuration.
2. Click the Discovery Methods node, and then double-click Active Directory User Discovery.

3. In the Active Directory User Discovery Properties dialog box, verify that the Enable Active
Directory User Discovery check box is selected.
4. Click New, and then click Browse.
5. In the Select New Container dialog box, click the Adatum container, and then click OK.
6. Verify that the Recursively search Active Directory child containers check box is selected,
and then click OK.
7. On the Polling Schedule tab, click Schedule, configure the recurrence to take place

every 3 days, and then click OK.
8. Verify that the Enable delta discovery check box is selected with an interval of 5 minutes.
9. On the Active Directory Attributes tab, in the Available attributes list, scroll down and

click the department attribute, click Add, and then click OK.
10. Right-click Active Directory User Discovery, and then click Run Full Discovery Now.
11. When Configuration Manager displays the Do you want to run full discovery as soon as
possible? message, click Yes.
Task 3: Examine the discovered resources
1. Click the Assets and Compliance workspace.
2. In the Assets and Compliance workspace, click the Devices node.
3. In the results pane, right-click TOR-CL2, and then click Properties.
Note: Notice that the client was discovered by using the SMS_AD_SYSTEM_DISCOVERY_AGENT component and that it resides in the Toronto Clients OU.
4. Click Close.
5. In the Assets and Compliance workspace, click the Users node. Notice the users that have been discovered in the Adatum domain.
6. In the Assets and Compliance workspace, click the User Collections node. Notice that the Toronto Users collection shows a member count of 5.
7. Click Toronto Users, and then on the ribbon, click Update Membership.
8. In the Configuration Manager dialog box, click Yes.
9.
After the hourglass icon appears on the Toronto Users collection, with the Toronto Users collection selected, click Refresh. (You might need to click Refresh additio
the number does not refresh, first update the All Users and User Groups collection.
10. Click the Administration workspace, expand the Hierarchy Configuration node, and then click the Active Directory Forests node.
11. In the preview pane, click the Domains tab. Notice that the Adatum.com domain has been discovered.
12. Click the Discovery Status tab, and then verify that the discovery has succeeded.
13. Click the Publishing Status tab, and verify that the publishing has succeeded.
14. In the results pane, right-click Adatum.com, and then click Show Active Directory Sites. Notice that three sites have been discovered: AdatumHQ, Sydney, and Tor
15. In the results pane, right-click Adatum.com, and then click Show IP Subnets. Notice that three IP subnets have been discovered:
o 172.16.0.0/24
o 172.16.1.0/24
o 172.16.2.0/24
• Leave the 20703-1B-LON-DC1-A and 20703-1B-LON-CFG-A virtual machines running for use in the next lab.
Result: After completing this exercise, you should have configured discovery methods and viewed the discovery results.
Lab B: Configuring user and device collections
Exercise 1: Creating a device collection

Task 1: Create the Toronto Windows 10 Workstations collection
1. If the Microsoft System Center Configuration Manager (Configuration Manager) console is not already
open, on LON-CFG, on the taskbar, click the Configuration Manager Console icon in the Taskbar.
2. In the System Center Configuration Manager console, click the Assets and Compliance workspace, and
then click the Device Collections node. Notice that several created collections exist.
3. Right-click Device Collections, and then click Create Device Collection.
4. In the Create Device Collection Wizard, in the Name box, type Toronto Windows 10 Workstations.
5. In the Comment box, type Based upon the Active Directory Toronto Clients organizational unit, and
then click Browse.
6. In the Select Collection dialog box, ensure that Device Collections is selected, select the All Windows 10
Workstations collection, and then click OK.
7. In the Create Device Collection Wizard, click Next.
8. On the Membership Rules page, click the Add Rule list, and then click Query Rule.
9. In the Query Rule Properties dialog box, in the Name box, type Toronto Windows 10 Workstations.
10. In the Query Rule Properties dialog box, ensure that System Resource is listed, and then click Edit Query
Statement.
11. In the Query Statement Properties dialog box, click the Criteria tab.
12. On the Criteria page, click New.
13. In the Criterion Properties dialog box, in the Criterion Type box, ensure that Simple value is selected,
and then click Select.
14. In the Select Attribute dialog box, configure the following options, and then click OK:
o Attribute class: System Resource
o Alias as: <No Alias>
o Attribute: System OU Name
15. In the Criterion Properties dialog box, ensure that the Operator value is set to is equal to, and then in
the Value box, type ADATUM.COM/TORONTO CLIENTS.
16. To close the Criterion Properties dialog box, click OK.
17. To close the Query Statement Properties dialog box, click OK.
18. To close the Query Rule Properties dialog box, click OK.
19. In the Create Device Collection Wizard, on the Membership Rules page, ensure that both Use
incremental updates for this collection and Schedule a full update on this collection are selected, and
then click Next.
22. Ensure that the Device Collections node is selected, and then in the results pane, select the Toronto
Windows 10 Workstations collection.
23. To refresh the collection, press F5, and then double-click the Toronto Windows 10
Workstations collection.
24. Verify that TOR-CL1 and TOR-CL2 display.
Note: You might need to refresh the console to view the results.
Result: After this exercise, you should have created device collections based on an Active Directory OU and on queries.
Exercise 2: Creating a user collection

Task 1: Create the Toronto Managers collection
1.
If the Configuration Manager console is not already open, on LON-CFG, on the taskbar, click
the Configuration Manager Console icon in the Taskbar.
2.
In the System Center Configuration Manager console, click the Assets and Compliance workspace, and
then click the User Collections node. Notice that several created collections already exist.
3.
Right-click User Collections, and then click Create User Collection.
4. In the Create User Collection Wizard, in the Name box, type Toronto Managers.
5.
In the Comment box, type Based upon Membership of the Toronto Users collection and the Managers
OU in Active Directory, and then click Browse.
6. In the Select Collections dialog box, ensure that User Collections is selected, select the Toronto

Users collection, and then click OK.
7.
In the Create User Collection Wizard, click Next.
8. On the Membership Rules page, click Add Rule, and then click Query Rule.
9. In the Name box, type Managers, and then click Edit Query Statement.
10.
In the Query Statement Properties dialog box, click Criteria, and then click New.
13.
In the Attribute list, click User OU Name, and then click OK.
14. Verify that the Operator displays is equal to, and then click Value.
15. In the Values dialog box, click ADATUM.COM/MANAGERS, and then click OK four times.
16.
On the Membership Rules page, click Next twice, and then click Close.
17. In the list of user collections, click Toronto Managers, and then on the ribbon, click Update Membership.
18. In the Configuration Manager dialog box, click Yes.
19. With the User Collections node selected, in the results pane, double-click the Toronto
Managers collection.
20. Verify that only the seven Toronto managers are in the collection.
Result: After this exercise, you should have created a user collection that includes and filters members of other collections.
Exercise 3: Configuring a maintenance window
Task 1: Configure a maintenance window for Toronto Windows 10 workstations
1. If the Configuration Manager console is not already open, on LON-CFG, on the taskbar, click
the Configuration Manager Console icon in the Taskbar.
2. In the System Center Configuration Manager console, click the Assets and Compliance workspace,
and then click the Device Collections node.
3. Right-click the Toronto Windows 10 Workstations node, and then click Properties.
4. In the Toronto Windows 10 Workstations Properties dialog box, click the Maintenance

Windows tab.
5. On the Maintenance Windows page, click New.
6. In the <new> Schedule dialog box, in the Name box, type Deployment Window.
7. Configure the schedule as follows, and then click OK:
o Start: 8 P.M.
o End: 4 A.M.
o Recurrence pattern: Daily
8. On the General tab, in the Comment box, type Maintenance Windows: 8 P.M. to 4 A.M.
9. In the Toronto Windows 10 Workstations Properties dialog box, click OK.

Lab Answer Key: Module 4: Deploying and managing the Configuration Manager client
Lab A: Deploying the Configuration Manager client software
Exercise 1: Preparing the site for client installation
Task 1: Install a fallback status point
1. Sign in to LON-CFG as Adatum\Administrator with the password Pa55w.rd.
2. On the taskbar, click Configuration Manager Console.
3. In the Configuration Manager console, click the Administration workspace, expand Site Configuration, and then click Servers and Site System
Roles.
4. In the results pane, right-click \\LON-CFG.Adatum.com, and then click Add Site System Roles.
5. In the Add Site System Roles Wizard, on the General page, click Next.
7. On the System Role Selection page, select the Fallback status point check box, and then click Next.
8. Review the Fallback Status Point page, and then click Next.
9. Review the Summary page, and then click Next.
Note: The summary page should list existing settings plus the fallback status point. If there is an issue, click Previous to change the settings.
10. Review the Completion page, and then click Close.
Note: The completion page should show that everything installed successfully. If it does not, contact your instructor.
After clicking Close, the details pane should display the fallback status point that you have added to the LON-CFG server.
11. In the preview pane, right-click the Management point role, and then click Properties.
12. Select the Generate alert when the management point is not healthy check box.
13. In the Management point Properties dialog box, click OK.
14. Right-click Sites, and then click Hierarchy Settings.
15. In the Hierarchy Settings Properties dialog box, select the Use a fallback site check box, and then click OK.
Result: After completing this exercise, you should have installed and configured a fallback status point.
Exercise 2: Deploying the Configuration Manager client software by using client push installation
Task 1: Configure the client push installation properties
1. In the Configuration Manager console, in the Administration workspace, click the Sites node.
2. On the ribbon, click Settings, click the Client Installation Settings drop-down list box, and then click Client Push Installation.
3. Click the Accounts tab.
4. Verify that Adatum\ClientInstall is configured as a Client Push Installation account. This is pre-configured for the lab and is not a default
account.
5. Click the Installation Properties tab.
6. On the Installation Properties tab, in the Installation properties box, after SMSSITECODE=S01 type the following on one line each separated
by a space:
FSP=LON-CFG DISABLESITEOPT=True SMSCACHEDIR=Cache SMSCACHEFLAGS=MAXDRIVE
7. In the Client Push Installation Properties dialog box, click OK.
Task 2: Perform a client push installation
1. Click the Assets and Compliance workspace, and then click Devices.
2. Right-click LON-CL1, and then click Install Client.
3. In the Install Configuration Manager Client Wizard, on the Before You Begin page, click Next.
4. Review the Installation Options page, and then click Next.
5. Review the Summary page, verify that one resource is going to be installed, and then click Next.
7. Minimize the Configuration Manager console.
Task 3: Verify the client installation

1. Switch to LON-CL1, and then click the desktop.
2. Right-click the taskbar, click Task Manager, click More details, and then click Details.
3. Wait for the ccmsetup.exe process to complete, and then verify that CcmExec.exe displays in the list of processes.
4. After ccmsetup.exe has completed, close Windows Task Manager.
5. In the File Explorer, open the C:\Windows\ccmsetup\logs\ccmsetup.log file.
6. In the log file, click Edit and then click Find, search for Successfully. If the installation was successful, you will see Installation succeeded near
the end of the file.
7. In the ccmsetup.log – Notepad window, search for Installing. Verify that entries for each prerequisite display as installed by ccmsetup.
8. In the ccmsetup.log – Notepad window, search for Fallback. Verify that entries for the state messages display as sent by ccmsetup.
9. Close the ccmsetup.log – Notepad window.
10. Click Start button, and then type Control Panel.
11. Click Control Panel.
12. In Control Panel, click System and Security.
13. Click Configuration Manager, and then on the General tab, verify that the Site code shows SMS: S01.
14. Click the Components tab. Verify that most of the components display as Installed and as Enabled. Verify that the Software Metering
Agent is Enabled.
Note: This indicates that the client has downloaded client settings from a management point.
15. Click the Site tab. Verify that the DISABLESITEOPT=True that was configured in the installation properties was applied, and that the Configure
Settings button is unavailable.
16. Click the Cache tab, and then click the Configure Settings button.
17. Verify that SMSCACHEDIR=Cache SMSCACHEFLAGS=MAXDRIVE that was configured in the installation properties was applied, and that the
Cache folder is set to C:\Cache\ccmcache.
18. Click OK to close the Configuration Manager Properties dialog box.
• Keep the virtual machines running for the next lab.
Result: After completing this exercise, you should have installed a client using the client push method, and verified that the client was installed with
your custom settings.
Lab B: Configuring and monitoring client status
Exercise 1: Configuring and monitoring client health status
Task 1: Configure client status settings
1. On LON-CFG, on the taskbar, click Configuration Manager Console.
2. Click the Monitoring workspace, and then click the Client Status folder.
3. Right-click Client Status, and then click Client Status Settings.
4. In the Client Status Settings Properties dialog box, set all of the evaluation periods to 3 days.
5. In the Client Status Settings Properties dialog box, click OK.
Task 2: Trigger a client health evaluation
1. Switch to LON-CL1, and if necessary, sign in as Adatum\Administrator with the password Pa55w.rd.
2. Right-click the Start button, and then click Computer Management.
3. Expand Task Scheduler, expand Task Scheduler Library, expand Microsoft, and then click Configuration Manager.
4. Right-click Configuration Manager Health Evaluation, and then click Run.
5. Wait for the Last Run Result to change to The operation completed successfully. You might have to click Refresh to view updated results.
Note: The client health report could take up to 10 minutes before status is reported back to the site server, stored in the database, and is ready to
update the display.
Task 3: Use Client Check
1. Switch to LON-CFG.
2. Verify that the Configuration Manager console is still open to the Monitoring workspace, and to the Client Status folder.
3. Right-click Client Status, and then click Refresh Client Status.
4. In the results pane, click the Client Check link.

5. On the Client Check page, review the charts. You may need to click the Refresh Client Status button to refresh the results.
6. On the Client Check pie chart, click the green section.
7. In the Clients that passed client check from All Desktops and Server Clients temporary node, examine the contents of the Summary tab.
8. Click the Client Check Detail tab. Verify whether the client failed any rules.
Task 4: Use Client Activity
1. In the Configuration Manager console, click the Monitoring workspace, and then click the Client Activity node.
2. Review the charts on the Client Activity page.
3. On the Client Activity pie chart, click the green section.
4. Click the Client Activity Detail tab, and then examine the client summary information.
Task 5: Configure alerts
1. In the Configuration Manager console, click the Assets and Compliance workspace, click the Device Collections node.
2. Right-click the All Desktop and Server Clients collection, and then click Properties.
3. In the All Desktop and Server Clients Properties dialog box, click the Alerts tab, and then click Add.
4. In the Add New Collection Alerts dialog box, under Client status, select the following check boxes, and then click OK:
o Client check pass or no results for active clients falls below threshold (%)
o Client remediation success falls below the threshold (%)
o Client activity falls below threshold (%)
5. In the All Desktop and Server Clients Properties dialog box, under Conditions, select Client check, and then in the text box for threshold value,
ensure that it is set to 95.
6. Repeat step 5 for both Client remediation and Client activity.
7. In the All Desktop and Server Clients Properties dialog box, click OK.
Task 6: Test client health automatic remediation
1. Switch to LON-CL1.
2. In Computer Management, expand Services and Applications, and then click Services.
3. Scroll down and double-click Windows Management Instrumentation.
4. In the Windows Management Instrumentation Properties(Local Computer) dialog box, click the Stop button.
5. In the Stop Other Services dialog box, click Yes.
6. In the Startup Type list, click Disabled.
7. In the Windows Management Instrumentation Properties(Local Computer) dialog box, click OK.
8. Click the SMS Agent Host service.
Question: What is its status?
Answer: Its status is blank (Stopped).
9. Click the IP Helper service.
Question: What is its status?
Answer: Its status is blank (Stopped).
10. Expand Task Scheduler, expand Task Scheduler Library, expand Microsoft, and then click Configuration Manager.
11. Right-click Configuration Manager Health Evaluation, and then click Run.
12. Wait for the Last Run Result to change to The operation completed successfully. This will take a few minutes to complete, and you might need
to refresh the display.
13. Click Services.
14. Scroll down, and then click Windows Management Instrumentation.
Question: What is the status and startup type for the Windows Management Instrumentation service?
Answer: The status is Running (Started), and the startup type is Automatic.
Question: What is the status for the SMS Agent Host service?
Answer: The status is Running (Started).
Question: What is the status for the IP Helper service?

Answer: The Status is blank (stopped).
15. Close all open windows, and then sign out of LON-CL1.
• Keep the virtual machines running for the next lab.
Result: After this exercise, you should have configured client status monitoring and verified client remediation.
Lab C: Managing client settings
Exercise 1: Configuring client settings
Task 1: Create a London client collection
2. In the Configuration Manager console, click the Assets and Compliance workspace, and then click the Device Collections node.
3. Right-click Device Collections, and then click Create Device Collection.
4. In the Create Device Collection Wizard, in the Name text box, type London Clients.
5. Next to the Limiting collection field, click the Browse button.
6. Select the All Desktop and Server Clients collection, and then click OK.
7. In the Create Device Collection Wizard, click Next.
8. On the Membership Rules page, in the Add Rule list, click Direct Rule.
9. In the Create Direct Membership Rule Wizard, click Next.
10. In the Attribute name text box, select Name. In the Value text box, type LON-CL1, and then click Next.
11. On the Select Resources page, select LON-CL1, and then click Next.
14. In the Create Device Collection Wizard, on the Membership Rules page, click Next.
17. Click Refresh, and verify that the results pane for the Member Count column displays 1 member in the London Clients collection. You may
need to click Refresh several times over the course of 5 minutes before this information is displayed.
18. Double-click the London Clients collection, and then verify that LON-CL1 is a member.
Task 2: Configure the Default Client Settings
1. In the Configuration Manager console, click the Administration workspace, and then click the Client Settings node.
2. Right-click the Default Client Settings policy, and then click Properties.
3. In the Default Settings dialog box, click the Client Policy setting.
4. Set the Client policy polling interval (minutes) to 30 minutes.
5. Click the Power Management setting.
6. Set Allow power management of devices to No.
7. Click the State Messaging setting.
8. Set the State message reporting cycle (minutes) to 10 minutes.
9. Click OK to accept changes.
Task 3: Create a custom setting for a client device
1. Right-click the Client Settings node, and then click Create Custom Client Device Settings.
2. In the Create Custom Client Device Settings dialog box, in the Name text box, type LON Desktop Systems.
3. In the Description text box, type Client settings for all LON Desktop Systems.
4. In the Select and then configure the custom settings for client devices section, select the Software Metering check box.
5. Click the Software Metering node.
6. Set Enable software metering on clients to No.
7. Click OK to accept changes, and close the Create Custom Client Device Settings dialog box.
Task 4: Deploy a custom client device setting

1. Right-click the LON Desktop Systems client setting, and then click Deploy.
2. In the Select Collection dialog box, click London Clients, and then click OK.
3. In the preview pane, click the Deployments tab to verify the assignment.
Task 5: Verify client device settings
1. Switch to LON-CL1, and if not already signed in, sign in as Adatum\Administrator with the password Pa55w.rd.
2. If the Control Panel is not open, right-click the Start button, and then click Control Panel.
3. In Control Panel, click System and Security, and then click Configuration Manager.
4. Click the Actions tab, click Machine Policy Retrieval & Evaluation Cycle, and then click Run Now.
5. When a message box displays, click OK.
6. In the Configuration Manager Properties dialog box, click the Components tab.
7. Verify that the Power Management Agent is Installed, and that the Software Metering Agent is Disabled.
8. Close all open windows.
Result: After this exercise, you should have created a collection, and configured Default Client Settings. You also should have created and assigned a
custom client device setting. Additionally, you should have verified that both settings were applied to a system.
Exercise 2: Performing management operations
Task 1: Perform management operations
2. In the Configuration Manager console, click the Assets and Compliance workspace, and then click the Devices node.
3. Select LON-CFG.
4. Right-click LON-CFG and then point to Client Notification. Take note of the management tasks that can be run.
5. Click Download Computer Policy.
6. Click OK.
Task 2: Run scripts on target devices
1. In the Configuration Manager console, click the Administration workspace.
2. Expand Site Configuration, and then select Sites.
3. In the Ribbon, click Hierarchy Settings.
4. On the General tab, remove the check mark next to Script authors require additional script approver. Note that this is only done in this lab so
that the administrator can approve the script manually.
5. Click OK to close the Hierarchy Settings Properties box.
6. In the Configuration Manager console, click the Software Library workspace.
7. Click the Scripts node and then on the ribbon, click Create Script.
8. In the Create Script wizard, next to Script name enter Create Folder and File.
9. Open File Explorer and then browse to E:\Software.
10. Open NewFolder.txt and copy the text.
11. In the Create Script window, paste the copied text. Click Next.
12. On the Script Parameters page, click Edit. Take notice of how you can change default values.
13. Click Cancel and then click Next.
14. On the Summary page, click Next and then click Close. Notice that the Approval State shows Waiting for approval.
15. Select the Create Folder and File script and then in the ribbon click Approve/Deny. The Approve or Deny Script wizard starts. Click Next twice.
16. On the Script Approval page, select Approve and then click Next.
17. On the Summary page, click Next and then click Close.
19. Click the Devices node.
20. Select LON-CFG, right click LON-CFG and then click Run Script.
21. In the Run Script wizard, select the Create Folder and File script and then click Next.
22. Next to FileName type C:\Files\Test.txt.

23. Next to FolderName type C:\Files.
24. Click Next.
26. Take note of the Script status. Click Close.
27. Click the Monitoring workspace and then click Script Status.
28. Select the Create Folder and File script and notice its Overall Script Execution State.
29. In the ribbon click Show Status to view the script details.
30. Click OK to close the status information.
Lab Answer Key: Module 5: Managing inventory for PCs and applications
Lab A: Configuring and managing inventory collection
Exercise 1: Configuring and managing hardware inventory
Task 1: Configure the hardware inventory agent for all clients
2. In the console, click the Administration workspace, and then click Client Settings.
3. In the results pane, double-click Default Client Settings.
4. In the Default Settings dialog box, in the left pane, click Hardware Inventory.
5. Verify that the Enable hardware inventory on clients option is set to Yes.
6. Click Schedule.
7. In the Configure Client Setting dialog box, verify that the Simple schedule option is selected.
8. To configure the schedule to run the task every two days, in the Run every box, type or select 2, and then click OK.
9. To close the Default Settings dialog box, click OK.
Task 2: Configure hardware inventory for the All Windows 10 Workstations collection
1. Right-click Client Settings, and then click Create Custom Client Device Settings.
2. In the Create Custom Client Device Settings dialog box, in the Name text box, type All Windows 10 Workstations Client Device Settings.
3. In the Description text box, type Client Device Settings for Windows 10 clients.
4. Under the Select and then configure the custom settings for client devices option, select the Hardware Inventory check box.
5. In the left pane, click Hardware Inventory, and then under Device Settings, verify that the Hardware Inventory schedule is set to 2 days.
6. Next to Hardware inventory classes, click Set Classes.
7. In the Hardware Inventory Classes dialog box, click Filter by category, and then click Windows Clients & Server Classes.
8. Select the following inventory classes, and then click OK:
o BitLocker (Win32_EncryptableVolume)
o Boot Configuration (Win32_BootConfiguration)
o Computer System Product (Win32_ComputerSystemProduct)
9. To close the Create Custom Client Device Settings dialog box, click OK.
10. In the results pane, right-click All Windows 10 Workstations Client Device Settings, and then click Deploy.
11. In the Select Collection dialog box, click the All Windows 10 Workstations collection, and then click OK.
12. With the All Windows 10 Workstations Client Device Settings object selected, in the preview pane, note the information on
the Summary and Deployments tabs.
Task 3: Initiate a policy update for a collection
1. In the Configuration Manager console, click the Assets and Compliance workspace, and then click Device Collections.
2. Right-click the All Windows 10 Workstations collection, point to Client Notification, and then click Download Computer Policy.
3. Read the Configuration Manager pop-up, and then click OK.
Note: Wait a minute for the policy update to finish before you proceed to the next task.
Task 4: Initiate a hardware inventory cycle on the client
1. On LON-CL1, click Start, and then type Control Panel.
4. In the Configuration Manager Properties dialog box, click the Actions tab.
5. Under Actions, click Hardware Inventory Cycle, and then click Run Now.
6. When Configuration Manager displays the message “The selected cycle will run and might take several minutes to finish,” click OK.
7. In the Configuration Manager Properties dialog box, click OK.
Note: Wait at least five minutes for the hardware inventory cycle to finish before you proceed to the next task. You can follow the inventory process
as it occurs by viewing the InventoryAgent.log file on the client, and the Dataldr.log file on the site server.
Task 5: View the hardware inventory by using Resource Explorer
1. On LON-CFG, in the Configuration Manager console, click the Assets and Compliance workspace, and then click Device Collections.
2. In the results pane, right-click All Windows 10 Workstations, and then click Show Members.
3. In the results pane, right-click LON-CL1, point to Start, and then click System Center Configuration Manager - Resource Explorer.
4. In System Center Configuration Manager - Resource Explorer, expand the Hardware node. Verify that the custom inventory classes are visible,
as indicated by the following nodes:
o BitLocker
o Boot Configuration
o Computer System Product
5. Close System Center Configuration Manager - Resource Explorer.
6. Close the Configuration Manager console.
• Leave the 20703-1B-LON-DC1-B, 20703-1B-LON-CFG-B, and 20703-1B-LON-CL1-B VMs running for use in the next lab.
Result: After this exercise, you should have configured hardware inventory agent for all clients, and configured a custom hardware inventory agent
setting for all Windows 10 clients.
Lab B: Configuring software metering
Exercise 1: Configuring software metering
Task 1: Configure a Software Metering Client Agent
1. On LON-CFG, if the Configuration Manager console is not open, on the taskbar, click the Configuration Manager Console icon.
2. Click the Administration workspace, and then click Client Settings.
3. Right-click Default Client Settings, and then click Properties.
4. In the Default Settings dialog box, in the left pane, click Software Metering.
5. Under Device Settings, verify that the Enable software metering on clients option is set to Yes.
6. Click Schedule, and verify that the Simple schedule option is selected. To change the schedule to run every two days, in the Run every box,
type or select 2, and then click OK.
Task 2: Create a software-metering rule to meter WordPad
1. Click the Assets and Compliance workspace, and then click Software Metering.
2. In the navigation pane, right-click Software Metering, and then click Create Software Metering Rule.
3. In the Name text box, type WordPadRule.
4. Click Browse, and then navigate to C:\Program Files\Windows NT\Accessories\wordpad.exe.
5. Click wordpad.exe, and then click Open. Notice that the File name, Original file name, Version, and Language boxes populate automatically.
6. In the Version text box, delete the existing version text, and then type the asterisk wildcard character (*).
7. In the Language drop-down list box, click – Any –, and then click Next.
8. On the Summary page, click Next, and then click Close.
Task 3: Configure autocreation of a software-metering rule
1. In the Configuration Manager console, right-click Software Metering, and then click Software Metering Properties.
2. In the Software Metering Properties dialog box, ensure that Automatically create disabled metering rules from recent usage inventory
data is enabled.
3. In the Specify the percentage of computers in the hierarchy that must use a program before a software metering rule is automatically
created box, type or select a setting of 5.
4. In the Specify the number of software metering rules that must be exceeded in the hierarchy before the automatic creation of rules is
disabled box, type or select a setting of 30.
5. To close the Software Metering Properties dialog box, click OK.
Note: Wait approximately one minute for processing to finish before continuing.
Task 4: Initiate a policy update on the client
4. Click the Actions tab.
5. Under Actions, click Machine Policy Retrieval & Evaluation Cycle, and then click Run Now.
6. In the Machine Policy Retrieval & Evaluation Cycle dialog box, click OK.
7. To close the Configuration Manager Properties dialog box, click OK.
Note: Wait at least two minutes for the policy update to finish before you move to the next task.
Task 5: Create test data on the client
1. On LON-CL1, click Start.
2. Type Wordpad, and then click WordPad.
3. Close WordPad.
4. Click Start, and then type Notepad.
5. Click the Notepad item.
6. Close Notepad.
7. Repeat steps 1 to 6 several times to generate test-metering data in the log files.
Task 6: Initiate a usage report cycle on the client
5. Under Actions, click Software Metering Usage Report Cycle, and then click Run Now.
6. In the Software Metering Usage Report Cycle dialog box, click OK.
Note: Wait at least two minutes for the report cycle to finish before you move to the next task. You also can view the swmproc.log file on the site
server to see when the client data has been processed.
Task 7: Verify software metering on the client
1. On LON-CL1, on the taskbar, click the File Explorer icon.
2. Browse to C:\IT Tools.
3. Double-click cmtrace.exe.
4. On the File menu, click Open.
5. Browse to C:\Windows\CCM\logs\, and then double-click mtrmgr.log.
6. Maximize the Configuration Manager Trace Log Tool window.
7. Click the Tools menu, and then click Find.

8. In the Find what text box, type WordPad, and then click Find.
9. Scroll down, and then verify that the following entries are present for wordpad.exe:
o Creation event received for process xxx
o Process ID xxx is for process C:\Program Files\Windows NT\Accessories\wordpad.exe
o Found match against RuleID S0100yyy
o Tracked usage for process xxx
Note: The Process ID xxx corresponds to the decimal value that this application has in the task manager. The RuleID S0100yyy is the rule
number that is assigned automatically when you create each software-metering rule. The Found match and Tracked usage lines indicate
that the client is metering the configured software.
If the entries do not exist, scroll down, and then verify that the following entries are present for notepad.exe:
o Creation event received for process xxx
o Process ID xxx is for process C:\Windows\system32\notepad.exe
o In addition, notice that there is no matching rule found for Notepad.exe.
10. Close the Configuration Manager Trace Log Tool.
Task 8: Initiate metering summarization
1. On LON-CFG, click Start and then click the Windows PowerShell icon.
2. In Windows PowerShell, type the following command, and then press Enter:
CD “C:\Program Files\Microsoft Configuration Manager\Tools\ServerTools”
3. Type the following command, and then press Enter:
.\RunMeterSumm.exe CM_S01
4. Review the output of the RunMeterSumm command. Verify that the number of rows added to File Usage Summary is greater than 0.
5. At the Windows PowerShell prompt, type exit, and then press Enter.
Task 9: View a software-metering report
1. In the Configuration Manager console, click the Monitoring workspace, and then expand Reporting.
2. Expand Reports, and then click the Software Metering folder.
3. Right-click the Computers that have run a specific metered software program report, and then click Run.
4. In the Rule Name section, click Values.
5. In the Parameter Value dialog box, click WordPadRule, and then click OK.
6. In the Month (1-12) section, click Values.
7. In the Parameter Value dialog box, click the current month, and then click OK.
8. In the Year section, click Values.
9. In the Parameter Value dialog box, click the current year, and then click OK.
10. Click View Report.
11. Review the report, and then close all open windows.
• Leave the 20703-1B-LON-DC1-B, 20703-1B-LON-CFG-B, and 20703-1B-LON-CL1-B VMs running for use in the next lab.
Result: After this exercise, you should have configured software metering, and then viewed software-metering information by using a report.
Lab C: Configuring and managing Asset Intelligence
Exercise 1: Preparing the site for Asset Intelligence
Task 1: Verify that the client settings are enabled
2. Click the Administration workspace, and then click the Client Settings node.
3. In the results pane, right-click Default Client Settings, and then click Properties.
4. In the Default Settings dialog box, click Hardware Inventory. Verify that the Enable hardware inventory on clients option is set to Yes.
5. In the Default Settings dialog box, click Software Metering. Verify that the Enable software metering on clients option is set to Yes.
Task 2: Configure Windows event log settings

1. On LON-DC1, in the Server Manager console, click Tools, and then click Group Policy Management.
2. In the Group Policy Management console tree, expand Forest: Adatum.com, expand Domains, expand Adatum.com, and then click Group
Policy Objects.
3. In the details pane, right-click Default Domain Policy, and then click Edit.
4. In the Group Policy Management Editor, expand Computer Configuration, expand Policies, expand Windows Settings, expand Security
Settings, expand Local Policies, and then click Audit Policy.
5. In the details pane, double-click Audit logon events.
6. On the Audit logon events Properties page, click Define these policy settings. Verify that the Success check box is selected, and then click OK.
7. Close the Group Policy Management Editor, and then close the Group Policy Management Console.
8. On LON-CL1, click Start, and then type Windows PowerShell.
9. Right-click Windows PowerShell, and then click Run as administrator.
10. In the Administrator: Windows PowerShell window, at the command prompt, type the following command, and then press Enter:
gpupdate /force
11. In the Administrator: Windows PowerShell window, at the command prompt, type the following command, and then press Enter:
exit
Result: After this exercise, you should have prepared the site for Asset Intelligence.
Exercise 2: Configuring Asset Intelligence
Task 1: Enable Asset Intelligence reporting classes
1. On LON-CFG, if necessary, on the taskbar, click the Configuration Manager Console icon.
2. In the Configuration Manager console, click the Assets and Compliance workspace, and then click the Asset Intelligence node. Notice the
information that displays on the Asset Intelligence home page.
3. Right-click Asset Intelligence, and then click Edit Inventory Classes.
4. In the Edit Inventory Classes dialog box, verify that the Enable only the selected Asset Intelligence reporting classes option is selected.
5. For the Asset Intelligence reporting classes, select all check boxes except the SMS_InstalledExecutable and SMS_SoftwareShortcut check
boxes.
6. To close the Edit Inventory Classes dialog box, click OK, and then click Yes.
Task 2: Configure an Asset Intelligence synchronization point
1. In the Configuration Manager console, click the Administration workspace, expand the Site Configuration node, and then click Servers and
Site System Roles.
2. In the results pane, right-click \\LON-CFG.Adatum.com, and then click Add Site System Roles.
3. In the Add Site System Roles Wizard, click Next.
5. On the System Role Selection page, select the Asset Intelligence synchronization point check box, and then click Next.
6. On the Asset Intelligence synchronization point settings page, click Next.
7. On the Specify the Asset Intelligence synchronization behavior page, ensure that the option Enable synchronization on a schedule is selected,
and that it is set to run every 7 days, and then click Next.
10. Click the Assets and Compliance workspace, and then click Asset Intelligence. In the results pane, under Catalog Synchronization, review the
status details. Click Refresh. Notice that the Asset Intelligence synchronization point status shows that the Sync point has deployed.
Note: Wait for the installation of the Asset Intelligence synchronization point to complete, and then refresh the console before proceeding to the next
task.
Task 3: Configure an Asset Intelligence catalog synchronization schedule
1. In the Assets and Compliance workspace, right-click Asset Intelligence, point to Synchronize, and then click Schedule Synchronization.
Note: If the option is not available, refresh the console, or click on another node, and then click the Asset Intelligence node again.
2. In the Asset Intelligence Synchronization Point Schedule dialog box, verify that the Simple schedule option is selected.
3. In the Run every (days) box, type or select 2, and then click OK.
Result: After this exercise, you should have enabled Asset Intelligence reporting classes, configured an Asset Intelligence synchronization point, and
scheduled synchronization.
Exercise 3: Monitoring license agreements by using Asset Intelligence
Task 1: Customize the Asset Intelligence catalog
1. On LON-CFG, if necessary, on the taskbar, click the Configuration Manager Console icon.
2. In the Configuration Manager console, click the Assets and Compliance workspace, and then click the Asset Intelligence node.
3. Expand the Asset Intelligence node, and then click Catalog. Take note of the default categories and families that display in the results pane.
4. Right-click Catalog, and then click Create Software Category.
5. In the Create Software Category Wizard, on the General page, in the Category name text box, type Adatum Developed.
6. In the Description text box, type Software developed in-house by Adatum, and then click Next.
9. Right-click Catalog, and then click Create Software Family.
10. In the Create Software Family Wizard, on the General page, in the Family name text box, type Custom Software.
11. In the Description text box, type Special use, custom application software, and then click Next.
14. Right-click Catalog, and then click Create Software Label.
15. In the Create Custom Label Wizard, on the General page, in the Label name text box, type Unsupported. In the Description text box,
type Software not supported by Adatum IT, and then click Next.
Task 2: Import licensing data
1. In the System Center Configuration Manager console, click the Assets and Compliance workspace, and then click the Asset Intelligence node.
2. Right-click Asset Intelligence, and then click Import Software Licenses.
3. In the Import Software Licenses Wizard, click Next.
4. On the Import page, click General License Statement (.csv file).
5. In the Path text box, type \\LON-CFG\E$\Licenses\LicenseData.csv, and then click Next.
Note: LicenseData.csv was created for the lab, and it contains information about Microsoft Silverlight.
Task 3: Initiate a policy update on the client
5. Under Actions, select Machine Policy Retrieval & Evaluation Cycle, and then click Run Now.
6. In the Machine Policy Retrieval & Evaluation Cycle dialog box, click OK.
Note: Wait at least two minutes for the policy update to finish before you proceed to the next task.
Task 4: Initiate a hardware inventory cycle on the client
4. In the Configuration Manager Properties dialog box, click the Actions tab.
5. Under Actions, select Hardware Inventory Cycle, and then click Run Now.
6. In the Hardware Inventory Cycle dialog box, click OK.
7. In the Configuration Manager Properties dialog box, click OK.

Note: Be sure to wait several minutes for the hardware inventory cycle to finish before you proceed to the next exercise.
Result: After this exercise, you should have customized the Asset Intelligence Catalog to reflect a number of custom software settings, and then
created a new software category, a new software family, and a new software label. You also should have imported a license statement into Asset
Intelligence.
Exercise 4: Viewing Asset Intelligence reports
Task 1: View Asset Intelligence reports
2. In the Configuration Manager console, click the Monitoring workspace, and then click the Reporting node.
3. Expand the Reporting node, and then expand Reports.
4. Click the Asset Intelligence folder. Notice the various Asset Intelligence reports that display in the results pane.
5. In the results pane, right-click Hardware 03A - Primary computer users, and then click Run.
6. In the Collection area, click Values.
7. In the Parameter Value dialog box, click the All Systems collection, and then click OK.
8. Click View Report. In the results pane, click adatum\administrator, and then review the results.
9. Close the Hardware 03B - Computer for a specific primary console user window.
10. In the Configuration Manager console, in the results pane, right-click License 15A - General License Reconciliation Report, and then click Run.
11. In the License 15A - General License Reconciliation Report window, in the Collection area, click Values.
12. In the Parameter Value dialog box, click the All Systems collection, and then click OK.
13. Click View Report, and then review the report.
14. Close the License 15A - General License Reconciliation Report window.
15. In the results pane of the Configuration Manager console, right-click Software 01A - Summary of installed software in a specific collection,
and then click Run.
16. In the Software 01A - Summary of installed software in a specific collection window, in the Collection area, click Values.
17. In the Parameter Value dialog box, click the All Windows 10 Workstations collection, and then click OK.
18. In the Publisher area, click Values.
19. In the Parameter Value dialog box, click (All), and then click OK.
20. In the maximum rows to return text box, type 100, and then click View Report.
21. Review the report, and then close the Software 01A - Summary of installed software in a specific collection window.
Task 2: Review Product Lifecycle dashboard
2. In the Configuration Manager console, click the Asset and Compliance workspace, and then expand the Asset Intelligence node.
3. Click the Product Lifecycle node.
4. Review the Product Lifecycle dashboard.
5. In the Lifecycle data for installed products table, on the System Center Configuration Manager current branch, version 1810 row, record the
end date for mainstream support.
6. In the Number in environment column, click 3.
7. In the Lifecyle 01A – Computer with a specific software product window, review the results, and then close the window.
8. Expand the Product category drop-down list and review the available categories.
11. Click the Asset Intelligence folder. Notice the various Asset Intelligence reports that are displayed in the results pane.
12. In the results pane, right-click Lifecycle 02A - List of machines with expired products in the organization, and then click Run.
13. In the Category area, click Values.
14. In the Parameter Value dialog box, click the ConfigMgr category, and then click OK.
15. In the Product name area, click Values.
Note: If you are running this lab on April 30, 2020 or later, System Center Configuration Manager current branch, version 1810 will be listed in
the Lifecycle 02A - List of machines with expired products in the organization report.
16. Verify that there are no expired Products, and then click Cancel.
17. Close the Lifecycle 02A - List of machines with expired products in the organization window.
21. In the results pane, right-click Lifecycle 03A - List of expired products found in the organization, and then click Run.
Note: If you are running this lab on April 30, 2020 or later, System Center Configuration Manager current branch, version 1810 will be listed in
the Lifecycle 03A - List of expired products found in the organization report.
22. Verify that there are no expired products.
23. Close the Lifecycle 03A - List of expired products found in the organization window.
27. In the results pane, right-click Lifecycle 04A - General product lifecycle overview, and then click Run.
30. In the Group name area, click Values.
31. In the Parameter Value dialog box, click the System Center Configuration Manager current branch, version 1810 group name, and then
click OK.
32. In the End date area, click the calendar icon next to Values.
33. In the Calendar dialog box, click May 1 2020.
35. Verify that the report shows three computers are running System Center Configuration Manager current branch, version 1810, and there is a
link to get more details about upgrading Configuration Manager.
36. Close the Lifecycle 04A - General product lifecycle overview window.
40. In the results pane, right-click Lifecycle 05A - Product lifecycle dashboard, and then click Run.
44. Verify that the report shows three computers running System Center Configuration Manager current branch, version 1810; the mainstream
support end Date is given as 4/30/2020; the remaining numbers of days for which the product will receive support; and a link to learn more
about upgrading Configuration Manager.
45. Close the Lifecycle 05A - Product lifecycle dashboard window.
Task 3: Prepare for the next module
After you finish the lab, revert the VMs to their initial state. To do this, complete the following steps.
1. On the host computer, start Hyper- V Manager.
2. In the Virtual Machines list, right-click 20703-1B-LON-DC1-B, and then click Revert.
3. In the Revert Virtual Machine dialog box, click Revert.
4. Repeat steps 2 and 3 for 20703-1B-LON-CFG-B and 20703-1B-LON-CL1-B.
Result: After this exercise, you should have reviewed Asset Inventory data by using reports.

3.exercise - SCCM Microsoft

Uploaded by

Copyright:

Available Formats

3.exercise - SCCM Microsoft

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3.exercise - SCCM Microsoft

Uploaded by

Copyright:

Available Formats

Lab Answer Key: Module 1: Managing computers and mobile devices in the enterprise

Lab: Exploring the Configuration Manager tools

2. On the taskbar, click the Configuration Manager console icon.

3. In the Configuration Manager console, in the Assets and Compliance workspace, click the Users node.

4. In the search bar, type ch, and then click Search.

5. The Users indicator shows that there are 2 items.

Task 2: Using search criteria

2. Click the Add Criteria link. Note the available criteria for devices.

3. Click Name, and click Add.

5. Verify that the Devices indicator now shows that there are 6 items.

6. Click the Add Criteria link.

7. Scroll down, click Operating System, and then click Add.

Task 3: Create and save a local node search

4. Next to the Search button, click Add Criteria, select the Name check box, and then

7. On the ribbon, in the Save group, click Save Current Search.

8. In the Configuration Manager dialog box, type T users, and then click OK.

Task 4: Create and save a global search

2. In the Search text box, type Configuration Manager, and then click Search.

3. On the ribbon, in the Save group, click Save Current Search.

4. In the Configuration Manager dialog box, in the Search name field, type Configuration

5. Close the Configuration Manager console.

Task 5: Use saved searches

3. In the Configuration Manager console, click the Assets and Compliance workspace.

4. Click the User Collections node.

6. Double-click the All Users collection.

7. On the ribbon, click the Home tab.

9. Click the Device Collections node.

11. Click the Configuration Manager Objects search, and click OK.

Note: This displays the same results as before.

Exercise 2: Using Windows PowerShell with Configuration Manager

Get-Command –Module ConfigurationManager | Out-Gridview

4. Review the commands, and close the Get-Command –Module ConfigurationManager | Out-

Task 2: View Configuration Manager information

Get-CMDevice | ft Name, ADSiteName, SiteCode, DeviceOS

Get-CMManagementPoint | ft NetworkOSPath, RoleName, SiteCode, RoleCount

Get-CMPackage | ft Name, Description, PkgSourcePath

Get-CMApplication | ft LocalizedDisplayName, SourceSite

Get-CMSite | ft SiteName, SiteCode, ServerName

Get-CMUser | ft Name, Domain

Get-CMUserCollection | ft Name, Comment, MemberCount

Get-CMDeviceCollection | ft Name, Comment, MemberCount

10. Close the Administrator: Windows PowerShell window.

Exercise 3: Using Configuration Manager Service Manager to manage components

Task 1: Configure the log file size for a single component

1. Click the Monitoring workspace, and expand the System Status folder.

2. Click the Component Status node.

4. Click to expand S01, and click Components.

5. In the right pane, scroll down, right-click SMS_POLICY_PROVIDER, and then click Logging.

6. In the Configuration Manager Component Logging – Single Component dialog box, set the Log

8. To close the Configuration Manager Component Logging – Single Component dialog box,

Task 2: Manage Configuration Manager components

2. Right-click one of the selected components, and click Query.

6. Right-click SMS_POLICY_PROVIDER, and click Query.

7. Right-click SMS_POLICY_PROVIDER, and click Start.

8. Right-click SMS_POLICY_PROVIDER, and click Query.

9. Close the Configuration Manager Service Manager.

Exercise 4: Monitoring Site and Component Status

2. Examine the Site Status node.