Build a management console and record the direct route to twelve settings
Task
Assemble a custom management console from snap-ins, and build a personal reference of direct commands for the settings you will actually use. The deliverable outlives any particular version of Windows, which is the point: click paths describe one release and the commands have been stable for twenty years.
Steps
- Open an empty management console, add at least five snap-ins, and save it into your lab directory. Record the snap-ins in
lab/console/snapins.csvwith headersnapin,what_it_shows,remote_capable. - Write
lab/console/commands.csvwith headersetting,direct_command,surface,verifiedgiving the direct command for at least twelve settings, marking whether each lives in Settings or Control Panel. - Open at least four of them using the command rather than the menu, and set
verifiedtoyeson those rows (noon the rest). - Write
lab/console/eventview.mddescribing the custom Event Viewer view you created -- which logs, which levels, which time range -- and how many events it showed. - Write
lab/console/remote.mdnaming which of your snap-ins can be pointed at another computer and what that requires.
Verify
These checks run in a POSIX shell: Terminal on macOS or Linux, and on Windows Git Bash (it comes with Git for Windows) or WSL. A stock Windows PowerShell or Command Prompt has no awk or grep, so there the first line fails.
awk -F, 'NR>1 && NF>=3 {n++} END {print n" snap-in(s)"}' lab/console/snapins.csv
awk -F, 'NR>1 && NF>=3 {n++} END {print n" setting(s)"}' lab/console/commands.csv
awk -F, 'NR>1 && $4 ~ /yes/ {n++} END {print n" verified route(s)"}' lab/console/commands.csv
grep -Eic 'error|critical|warning' lab/console/eventview.md
grep -Eic 'remote|another computer|target' lab/console/remote.md
Five snap-ins, twelve settings, four verified directly. A command you have not run is a command you copied, and the ones that have been renamed between versions are exactly the ones you will reach for under pressure.
Notes
Save the console into somewhere you will find it again. A .msc file with the five snap-ins you use, pointed at the machine you support most, is a genuinely useful artefact rather than an exercise.
This is an independent study companion for CompTIA A+ Core 2 220-1202 and is not produced by or endorsed by CompTIA.