Lab 4 / Using Management Interfaces

In this lab, you will learn how to access the principal management interfaces in Windows 10.

1) If necessary, start your computer and sign in.

2) Right-click the Start button or press START+X.

This opens the Quick Access menu. This contains
shortcuts to most of the tools required by "power users."
Quick Access menu. Screenshot used with permission from Microsoft.x

3) From the Quick Access menu, select System.

This settings page provides information about the PC
status and the version of Windows currently installed.

4) Take some time to browse other pages in the Settings app.

5) Press CTRL+SHIFT+ESC to open Task Manager. Alternatively, use the Quick Access menu
or right-click the taskbar. If necessary, click More details at the bottom of the window to show
the tabs.
6) On the Processes tab, right-click Settings and select End Task.
You can "kill" this task without risk of data loss but note that if you end a task that is
processing unsaved data, the information will be lost.

7) Start Paint and draw a

picture in the window.
Do not save the file.
8) In the Task Manager, right-click Paint and select End Task.

"Killing" a process using Task Manager. Screenshot used with permission from Microsoft.

The Paint window closes without prompting you to save the image you
created.

9) Note the division of processes into apps and background processes. The background
processes run without a window, though some may be configurable via notification area icons.
Click each of the CPU, Memory, Disk, and Network headings in turn to sort processes by how
much of the computer's resources each is consuming.

10) Close Task Manager.

11) Press START+X and select Computer

Management.
Computer Management is the default management console. Management
consoles can be configured with snap-ins to control most of the "power"
configuration options in Windows.
12) Select each of the following snap-ins to view them:
o Task Scheduler—expand the node to view items in the
task scheduler library. You can see that Windows runs
many processes automatically.
o Disk Management—this shows you a summary of the
disks attached to the computer and the drives (partitions
and file systems) configured on them.
 o Services (expand Services and Applications)—the
shortcut menu for each service allows you to stop and
start it or configure its properties.

13) Close Computer Management.

14) Press the START key and type control panel. Open the Control Panel icon
that appears in the search results.

Microsoft has removed Control Panel (and the legacy

command prompt) from the Quick Access menu in recent
updates. You have to directly edit the registry to recreate the
shortcut.

With the latest feature update, there are relatively few configuration options
left in the Control Panel.
15) Optionally, browse some of the applets then close the Control
Panel window.

16) Right-click Start and select

Windows PowerSheIl.
Windows PowerShell is an
example of a Command
Line Interface (CLI).
17) Type the following command then execute it by pressing ENTER.
Get—NetIPConfiguration
This PowerShell commandlet displays configuration information for
the computer's network adapters.
 You do not actually have to match the case of the
command when using PowerShell. The command

environment is typically case insensitive. Using case

makes the command easier to read and typing
mistakes less common however. In Linux, the
command environment is case-sensitive.

18) Type the following command then execute it by pressing ENTER.

ipconfig
This is an older command that displays similar information.
PowerShell can run both Windows command prompt
commands and native commandlets.
19) Press the START key and type cmd. Open the Command Prompt icon
that appears in the search results.

20) Type the following command then execute it by pressing ENTER.

ipconfig
Note that this executes in the same way as in the PowerShell CLI.

21) Type the following command then execute it by pressing ENTER.

Get—NetIPConfiguration

This produces an error message. The command prompt environment cannot understand
(parse) PowerShell commandlets. When using a CLI you need to understand which
commands it can run as they are not all the same.

20) Close any open windows.