Home
Domain 1 Notes
CompTIA A+ Core 2 220-1202Domain 1 Original Course Notes

1.0 Operating Systems

Concise review notes for operating system types, Windows installation and administration, Windows networking, macOS, Linux, application support, and cloud productivity tools. Written as original classroom notes for the Core 2 curriculum.

Domain Weight28% of Core 2
Objectives Covered1.1 through 1.11
Study GoalChoose the right OS tool, setting, command, or support workflow.
Exam LensExpect scenarios asking for the best next step with verification.
How to use these notes: Read each objective as a technician decision. Identify the platform, match the clue to the right tool or setting, make the smallest useful change, verify the workflow, and document the result.
Platform Support
Windows, macOS, Linux, mobile operating systems, and cloud productivity environments each have different tools, permissions, update models, and support boundaries.
Technician Pattern
Plan first, protect user data, use the right source, change only what is needed, test from the user's perspective, and record what changed.
Notes:
1.1 Operating System Types and PurposesCore 2 Domain 1

1.1 - Operating System Types

Support mindset
  • Start by identifying device type, user workflow, application requirements, lifecycle status, and management needs.
  • The right OS supports the hardware, software, security, and business requirement with the least friction.
  • Compatibility includes drivers, architecture, processor support, file system support, management tools, and vendor support timelines.

Major Operating Systems

  • Windows fits many business desktops, laptops, legacy applications, Active Directory environments, and broad hardware platforms.
  • macOS is tied to Apple hardware and emphasizes hardware/software integration, creative workflows, iCloud services, and Apple ecosystem features.
  • Linux is open source and common on servers, developer systems, embedded devices, security labs, and specialized workloads.
  • iOS, iPadOS, Android, and ChromeOS support mobile, tablet, managed, and browser-first workflows.

File Systems

  • NTFS supports Windows permissions, encryption, compression, quotas, and journaling.
  • ReFS emphasizes resiliency for supported Windows storage scenarios.
  • FAT32 is widely compatible but limited; exFAT is useful for larger removable storage shared across platforms.
  • ext4 and XFS are common Linux file systems; APFS is Apple's modern file system.

Lifecycle and Architecture

  • End-of-life systems lose regular security updates and should be upgraded, isolated, or replaced.
  • 32-bit, 64-bit, ARM, and x86/x64 support affect RAM limits, app builds, and driver availability.
Scenario pattern: Look for device, application, storage, security, management, and support lifecycle clues before choosing.
Notes:
1.2 Installation and Upgrade PlanningCore 2 Domain 1

1.2 - OS Installation and Upgrades

Plan before booting media
  • Confirm hardware requirements, OS edition, architecture, firmware mode, disk layout, drivers, applications, and user data.
  • Back up data, document settings, and verify recovery options before destructive changes.
  • Choose clean install, upgrade, repair, recovery, image deployment, or remote deployment based on the requirement.

Installation Sources

  • Bootable USB, network boot, recovery partitions, Internet recovery, external drives, and ISO files each solve different deployment problems.
  • Trusted media matters because installation source integrity affects security and reliability.

Partition and Boot Choices

  • GPT commonly pairs with UEFI and supports modern boot requirements and large drives.
  • MBR appears in legacy BIOS scenarios.
  • Secure Boot, TPM, boot order, storage controller mode, and firmware settings can affect installation success.

Upgrade Readiness

  • Check OS version, feature update path, edition, app compatibility, driver support, storage space, and rollback plan.
  • Plan timing, bandwidth, user communication, and restart windows to reduce disruption.
Scenario ClueLikely DirectionTechnician Check
User data must remainUpgrade, migration, or backup firstConfirm backup and app compatibility
Many matching devicesImage or managed deploymentUse tested hardware model and drivers
Disk is being repurposedClean installPreserve data elsewhere first
System will not bootRecovery or repair pathCheck boot media and recovery tools
Notes:
1.3 Microsoft Windows EditionsCore 2 Domain 1

1.3 - Windows Editions and Features

Match edition to requirement
  • Windows editions differ by management, security, hardware support, and enterprise feature availability.
  • Choose by feature need, not by the edition name that sounds most powerful.

Home, Pro, and Enterprise

  • Home is consumer-focused and lacks several business administration features.
  • Pro adds domain join, Group Policy support, BitLocker support on supported hardware, and Remote Desktop hosting.
  • Enterprise adds organization-scale deployment, management, and security capabilities.

Feature Clues

  • Domain join and centralized policy point beyond Home.
  • Remote Desktop hosting is a Pro or higher clue.
  • BitLocker depends on edition and hardware support.
  • N editions omit some media features and may require media components.

Windows 11 Readiness

  • Windows 11 has modern security and firmware expectations, including TPM and UEFI-based requirements on supported devices.
  • Processor support, RAM, storage, graphics, firmware, and edition all affect eligibility.
Scenario pattern: Match the needed business feature without overshooting the requirement.
Notes:
1.4 Windows Features and ToolsCore 2 Domain 1

1.4 - Windows Administration Tools

Use the tool that shows evidence
  • Windows tools overlap, but each answers a different support question.
  • Use logs, device state, counters, startup state, or configuration details to prove the issue before changing settings.

Monitoring and Performance

  • Task Manager identifies running apps, processes, startup impact, and resource use.
  • Resource Monitor gives deeper CPU, memory, disk, and network activity.
  • Performance Monitor tracks counters over time for intermittent issues.

MMC and Administrative Tools

  • Event Viewer reviews system, application, setup, and security logs.
  • Device Manager manages drivers, device status, disabled hardware, and conflicts.
  • Disk Management manages partitions, volumes, drive letters, and formatting.
  • Task Scheduler, Local Users and Groups, Certificates, and Group Policy tools support focused administration.

Configuration Tools

  • System Information provides hardware, software, BIOS/UEFI, and driver inventory.
  • System Configuration supports startup and boot diagnosis.
  • Registry Editor changes low-level configuration and should be used with care and backup.
NeedToolReason
App crash detailsEvent ViewerApplication and system logs
Driver missingDevice ManagerDevice state and driver actions
Drive letter missingDisk ManagementVolume and partition view
High CPU after sign-inTask ManagerProcesses and startup impact
Notes:
1.5 Microsoft Command LineCore 2 Domain 1

1.5 - Windows Command-Line Tools

Commands give fast proof
  • Use Command Prompt or PowerShell to inspect files, network configuration, user context, disk state, and repair status.
  • Use help syntax before unfamiliar commands: command /?.
  • When paths contain spaces, wrap the full path in quotation marks.

File and Folder Commands

  • cd changes directories; dir lists files and folders.
  • md creates folders and rmdir removes folders.
  • robocopy performs resilient file copy operations and is useful for migrations and backups.

Network Commands

  • ipconfig shows IP configuration; ipconfig /all gives more detail.
  • ping tests reachability; tracert and pathping show route behavior.
  • nslookup tests DNS; netstat shows connections; net use manages network drives.

System and Repair Commands

  • hostname, whoami, and winver confirm identity and version.
  • gpupdate refreshes Group Policy and gpresult reports applied policy.
  • chkdsk, sfc, format, and diskpart support disk and system repair tasks.
Scenario pattern: Prove IP, gateway, DNS, route, file path, or policy state before changing configuration.
Notes:
1.6 Control Panel and Windows SettingsCore 2 Domain 1

1.6 - Windows Settings and Control Panel

Find the right settings home
  • Windows exposes many settings in both modern Settings and classic Control Panel.
  • Use the interface that directly maps to the task, then verify from the user's workflow.

Classic Control Panel Areas

  • Internet Options, Devices and Printers, Programs and Features, Network and Sharing Center, System, Windows Defender Firewall, Mail, Sound, User Accounts, Device Manager, Indexing Options, Administrative Tools, File Explorer Options, Power Options, and Ease of Access support common support tasks.

Modern Settings Areas

  • System, Devices/Bluetooth, Network and Internet, Apps, Accounts, Privacy, Time and Language, Personalization, Gaming, Accessibility, and Windows Update cover user and device configuration.

Best Practice

  • Change only the setting tied to the requirement.
  • Document the original state when troubleshooting user-impacting settings.
  • Prefer narrow firewall and privacy allowances over broad exposure.
Notes:
1.7 Windows Client NetworkingCore 2 Domain 1

1.7 - Windows Client Networking

Think in layers
  • Separate local configuration, network profile, addressing, DNS, route, firewall, proxy, and resource permission issues.
  • Identify the layer, protect the endpoint, make one targeted change, and verify access.

Workgroups and Domains

  • Workgroups are peer-oriented; domains provide centralized authentication, policy, and resource control.
  • Mapped drives, UNC paths, hidden shares, administrative shares, and permissions affect access.

IP Configuration

  • DHCP supplies IP, subnet mask, gateway, and DNS automatically.
  • APIPA addresses often mean DHCP did not provide a usable lease.
  • Static settings must match subnet, gateway, DNS, and backup DHCP needs.

Access Controls

  • Wired, Wi-Fi, VPN, WWAN, direct connection, and dial-up each have different authentication and hardware needs.
  • Firewall profiles should match location: public, private, or domain.
  • Proxy and metered settings affect apps, browsing, updates, and costs.
SymptomCheck FirstLikely Layer
Cannot reach anythingIP, gateway, link stateAddressing or connection
Can ping IP but not nameDNS settingsName resolution
Can browse web but not shareProfile, firewall, permissionsResource access
Traffic must go through gatewayProxy or VPN settingsPolicy or route control
Notes:
1.8 macOS Features and ToolsCore 2 Domain 1

1.8 - macOS Support

Use the Mac tool for the Mac problem
  • macOS has its own app installation methods, folder layout, update workflow, security controls, and productivity features.
  • Respect system folders, user privacy prompts, and built-in data protection tools.

Apps and Updates

  • .dmg files mount like disk images and often require dragging the app to Applications.
  • .pkg files run an installer and may place support files in system locations.
  • .app bundles are self-contained applications.
  • The Mac App Store provides updates for supported apps and some OS updates.

Folders and Settings

  • /Applications stores installed apps; /Users contains user home folders.
  • /Library stores shared support files; ~/Library stores current-user preferences.
  • /System contains protected OS files.

Tools and Features

  • Apple Account, Time Machine, FileVault, Keychain, Mission Control, Spaces, Spotlight, Finder, Dock, Continuity, FaceTime, iMessage, and iCloud Drive support security and workflow.
  • Terminal, Force Quit, and Disk Utility support command-line tasks, frozen apps, disks, partitions, erasing, and disk images.
Notes:
1.9 Linux Features and ToolsCore 2 Domain 1

1.9 - Linux Support

Read the command clue carefully
  • Linux support often depends on identifying file management, permissions, packages, storage, networking, service control, or process inspection.
  • Use man and test in a safe environment when impact is uncertain.

Files and Permissions

  • ls, pwd, mv, cp, and rm handle everyday file tasks.
  • chmod changes read, write, and execute permissions; chown changes ownership.

Storage and Packages

  • find locates files; fsck checks file systems; mount attaches storage.
  • apt manages Debian/Ubuntu packages; dnf manages many RPM-based systems.

Network, Processes, and Files

  • ip, ping, curl, dig, and traceroute support network testing.
  • top, ps, du, df, cat, grep, and nano inspect processes, storage, and text files.
  • /etc/passwd, /etc/shadow, /etc/hosts, /etc/fstab, and /etc/resolv.conf are common configuration clues.
Scenario pattern: Permission denied may point to execute permission, ownership, path, or administrative rights.
Notes:
1.10 Application SupportCore 2 Domain 1

1.10 - Application Installation Requirements

Requirements before installation
  • Compare vendor requirements to the real device and workflow before installing.
  • Minimum requirements may only mean the app launches; recommended requirements are often the better support target.

System Requirements

  • Check OS version, edition, architecture, CPU, RAM, GPU, VRAM, storage, drivers, and dependencies.
  • Storage planning includes installer files, temporary extraction, installed app size, updates, caches, logs, user files, and backups.

Access and Compatibility

  • Some apps require USB tokens, smart cards, security keys, dongles, license accounts, or entitlement checks.
  • Network access may require cloud services, APIs, DNS, proxies, VPNs, databases, certificates, or firewalls.

Sources and Verification

  • Use trusted vendor sites, app stores, repositories, managed portals, approved shares, physical media, or verified ISO files.
  • Launch the app, sign in, open files, test hardware, reach network resources, verify integrations, and confirm the user's workflow.
Notes:
1.11 Cloud Productivity SupportCore 2 Domain 1

1.11 - Cloud Productivity Tools

Cloud issues are layered
  • A cloud productivity issue may be licensing, identity, sync, permissions, network access, storage quota, client configuration, or service health.
  • Use the right layer before changing the app.

Productivity and Email

  • Hosted suites provide web apps, local apps, online storage, collaboration, communication, and shared security controls.
  • Cloud email includes mailboxes, calendars, contacts, mobile access, shared mailboxes, security policies, redundancy, backups, and client configuration.

Storage and Collaboration

  • Folder syncing requires selected folders, sync status, offline availability, storage quota, sharing permissions, conflicts, version history, and recovery options.
  • Collaboration tools include shared documents, spreadsheets, presentations, chat, meetings, guest access, notifications, and security policy.

Identity and Licensing

  • Identity providers, directory synchronization, onboarding, offboarding, MFA, conditional access, groups, and provisioning determine who can reach what.
  • Licenses control assigned services, feature access, storage rights, compliance needs, and cost.
Scenario ClueThinkBest Technician Move
User signs in but app is missingLicense or service planVerify assignment and enabled services
New hire cannot access emailIdentity lifecycleCheck account, group, and provisioning status
File shows on one device onlySync stateInspect sync client and folder selection
Guest cannot open shared fileSharing policyReview link settings, guest access, and MFA requirements
Notes:
Domain 1 Rapid ReviewCore 2 Domain 1

Rapid Review Checklist

1.1-1.3 Platform and Windows Planning
  • Match OS to hardware, app, security, lifecycle, and management needs.
  • Know file systems: NTFS, ReFS, FAT32, exFAT, APFS, ext4, and XFS.
  • Back up data before installs, upgrades, recovery, partitioning, or imaging.
  • Match Windows editions to domain join, BitLocker, Remote Desktop hosting, and enterprise features.
1.4-1.7 Windows Tools and Networking
  • Use Task Manager, Resource Monitor, Event Viewer, Device Manager, Disk Management, and Performance Monitor for evidence.
  • Use command-line tools to prove IP, DNS, route, file, disk, user, and policy state.
  • Use Settings or Control Panel based on the exact setting needed.
  • Troubleshoot networking by layer: link, IP, gateway, DNS, firewall, proxy, profile, permission.
1.8-1.9 macOS and Linux
  • macOS apps may use .dmg, .pkg, .app, or App Store workflows.
  • macOS support uses Finder, System Settings, Time Machine, FileVault, Keychain, Spotlight, Terminal, Force Quit, and Disk Utility.
  • Linux support depends on command purpose: files, permissions, packages, storage, network, processes, services, and configuration files.
1.10-1.11 Apps and Cloud
  • Check requirements before installing: CPU, RAM, GPU, VRAM, storage, OS, drivers, dependencies, tokens, network, and permissions.
  • Use trusted sources and verified media.
  • Cloud support requires identity, licensing, service plans, sync status, quotas, permissions, sharing policy, client setup, and service health.
  • Always verify the real user workflow and document the source, change, result, and next step.
Exam moves: Choose the most appropriate action, protect data first, make one controlled change, verify the result, and document what happened.
Notes:

These notes are an original study aid for the Brotocol Joe Core 2 curriculum.