Module 12: Maintaining Windows 10 Lab: Maintaining Windows 10 (VMs: 10982D-LON-DC1, 10982D-LON-CL1) Exercise 1: Resolve a Performance-Related Issue Task 1: Establish a performance baseline 1. If necessary, sign in to LON-CL1 as Adatum\administrator by using the password Pa55w.rd. 2. On the task bar, in the search box type Performance Monitor and in the search results select Performance Monitor. 3. In the Performance Monitor, in the navigation pane, expand Data Collector Sets and then click User Defined. 4. Right-click User Defined, select New, and then click Data Collector Set. 5. In the Create new Data Collector Set Wizard, on the How would you like to create this new data collector set? page, in the Name text box, type Adatum Baseline. 6. Select the Create manually (Advanced) option, and then click Next. 7. On the What type of data do you want to include? page, select the Performance counter check box, and then click Next. 8. On the Which performance counters would you like to log? page, in the Sample interval field, type 1, and then click Add. 9. In the Available counters list, expand Memory, click Pages/sec, and then click Add. 10. In the Available counters list, expand Network Interface, select Packets/sec, and then click Add. 11. In the Available counters list, expand Physical Disk, click % Disk Time, click 0 C:, and then click Add. 12. Under Physical Disk, click Avg. Disk Queue Length, click 0 C:, and then click Add. 13. In the Available counters list, expand Processor, click % Processor Time, and then click Add. 14. In the Available counters list, expand System, click Processor Queue Length, click Add, and then click OK. 15. On the Which performance counters would you like to log? page, click Next. 16. On the Where would you like the data to be saved? page, click Next. 17. On the Create the data collector set page, click Finish. 18. In the navigation pane, right-click Adatum Baseline, and then click Start. 19. Click the Start button, and then click Word. 20. Click the Start button, and then click Excel. 21. Click the Start button, and then click PowerPoint. 22. Close all open Microsoft Office apps. 23. Switch to the Performance Monitor. 24. In the Performance Monitor, in the navigation pane, right-click Adatum Baseline, and then click Stop. 25. In the Performance Monitor, in the navigation pane, expand Reports, expand User Defined, expand Adatum Baseline, and then click the report that has a name that begins with LON-CL1. 26. View the chart. 27. On the toolbar, click the drop-down arrow, and then click Report. 28. Record the following values: o Memory Pages per second o Network Interface Packets per second o Physical Disk (0 C:) % Disk Time o Physical Disk (0 C:) Avg. Disk Queue Length o Processor % Processor Time o System Processor Queue Length Task 2: Read the help-desk Incident Record for incident 728533 • Read the help-desk Incident Record 728533 in the Student Handbook exercise scenario. Task 3: Discuss recommendations 1. Read the Additional Information section of the incident record in the Student Handbook exercise scenario. 2. Discuss your recommendations with other students: o Visit the user’s computer. o Load the Performance Monitor to collect performance data by using a data collector set. o Compare with the baseline report generated in the test environment. o Identify the bottlenecked resource, if any. Task 4: Simulate the problem 1. If necessary, switch to LON-CL1. 2. If necessary, sign in using the following credentials: o User name: Adatum\Administrator o Password: Pa55w.rd 3. On the desktop, on the taskbar, click the File Explorer icon. 4. In File Explorer, expand drive D, expand Labfiles, and then click Mod12. 5. Double-click on the Exercise1.vbs file. 6. Verify that the script starts to generate load. Task 5: Attempt to resolve the problem 1. Switch to the Performance Monitor. 2. Under Data Collector Sets, click User Defined. 3. Right-click Adatum Baseline, and then click Start. 4. Right-click the Start button, and select Run. 5. Type perfmon /res and then press Enter. Note: In Resource Monitor, notice the components that are under strain. This will vary depending on the usage scenario and host configuration. However, the central processing unit (CPU) is likely to be heavily used. 6. After a few minutes, in the Windows Script Host prompt, click OK. 7. Close the instance of C:\Windows\System32\cmd.exe that the script launched. 8. Switch to the Performance Monitor. 9. In the navigation pane, right-click Adatum Baseline, and then click Stop. 10. In the Performance Monitor, in the navigation pane, expand Reports, expand User Defined, expand Adatum Baseline, and then click the second report that has a name that begins with LON-CL1. 11. View the chart. 12. On the toolbar, click the drop-down arrow, and then click Report. 13. Record the component details: o Memory Pages per second o Network Interface Packets per second o Physical Disk % Disk Time o Physical Disk Avg. Disk Queue Length o Processor % Processor Time o System Processor Queue Length Note: Notice that the CPU and the network are being affected the most by the script. 14. Close all open windows and programs. 15. Update the Resolution section of the incident record with the following comment: o The user should either: . Run fewer programs simultaneously. . Get a computer with a faster CPU. 16. Sign out of LON-CL1. Results: After completing this exercise, you should have identified the cause of the performance bottleneck.

Exercise 2: Configure Windows Update Settings Task 1: Configure update settings for a single device 1. Switch to LON-CL1. 2. If necessary, sign in as Adatum\Administrator by using the password of Pa55w.rd. 3. Click Start, and then select the Settings icon. 4. In Settings, select Update & Security. 5. Select the Delivery Optimization tab. 6. On the Delivery Optimization page, verify that the Allow downloads from other PCs option is enabled. 7. Select PCs on my local network and PCs on the Internet, and then select the Windows Update tab. 8. Select Advanced options. 9. On the Advanced options page, select the Receive updates for other Microsoft products when you update Windows option. 10. Click Back. 11. In the navigation pane, select Windows Insider Program. Notice that the Get started option is available. 12. In the navigation pane, select Windows Update. 13. On the Windows Update page, select View update history. 14. Review the updates listed, if any, and then click Uninstall updates. If no updates are installed, go to step 16. 15. Review the updates listed in Installed Updates. Close Installed Updates. 16. On the View update history page, click Back. Task 2: Configure update settings by using GPOs 1. Right-click Start, and then select Run. 2. In Run, type gpedit.msc and then press Enter. 3. In Local Group Policy Editor, navigate to Computer Configuration/ Administrative Templates/Windows Components/Data Collection and Preview Builds. 4. In the right pane, double-click Toggle user control over Insider builds. 5. In the Toggle user control over Insider builds dialog box, click Disabled, and then click OK. 6. In Local Group Policy Editor, navigate to Computer Configuration/ Administrative Templates/Windows Components/Windows Update/Windows Update for Business. 7. In the right pane, double-click Select when Preview Builds and Feature Updates are received. 8. In the Select when Preview Builds and Feature Updates are received dialog box, click Enabled. 9. In the Select the Windows readiness level for the updates you want to receive list, click SemiAnnual Channel. 10. In the After a Preview build or Feature Update is released, defer receiving it for this many days text box, type 45, and then click OK. Results: After completing this exercise, you should have successfully configured Windows Update settings. Prepare for the course completion When you have finished the lab, revert the virtual machines to their initial state. 1. On the host computer, start Hyper-V Manager. 2. In the Virtual Machines list, right-click 10982D-LON-DC1, and then click Revert. 3. In the Revert Virtual Machine dialog box, click Revert. 4. Repeat steps 2 and 3 for 10982D-LON-CL1