Installing Applications

Installing an application seems simple — run the installer, click through the wizard, done. The A+ exam is not testing whether you can click Next. It is testing whether you know what to check before you install: does the hardware meet requirements, how does the software arrive on the machine, and what are the downstream effects on the device, the network, users, and the business? This lesson covers those three areas — system requirements, distribution methods, and impact assessment.

System Requirements

Every application publishes minimum and recommended hardware requirements. A technician's job before installation is to verify the target machine meets them. Hardware specs are covered in the Core 1 Hardware module — this lesson applies those concepts to the installation decision.

32-bit vs 64-bit Compatibility

Applications are compiled for a specific CPU architecture — 32-bit or 64-bit. The compatibility rule is one-directional:

• A 64-bit OS can run 32-bit applications through a compatibility layer (Windows uses WOW64 — covered in L1 of this module; do not re-install it here)
• A 32-bit OS cannot run 64-bit applications — the 64-bit instruction set is not available
• Some applications require 64-bit specifically because they need to address more than 4GB of RAM — a 32-bit process cannot access memory beyond that ceiling

Graphics Requirements: Dedicated vs Integrated GPU and VRAM

Applications with intensive graphics workloads — 3D modeling, video editing, gaming, CAD, machine learning with GPU acceleration — often require a dedicated graphics card. A dedicated GPU has its own processor (GPU) and its own pool of high-speed video memory (VRAM).

Integrated graphics (the GPU built into the CPU or motherboard chipset) does not have dedicated VRAM — it borrows a portion of the system's RAM. This sharing has two consequences: less total system RAM is available to other processes, and the memory bandwidth is shared with the CPU rather than dedicated to graphics workloads.

When an application lists a minimum VRAM requirement, integrated graphics typically cannot satisfy it because it has no fixed VRAM allocation. An application that requires 8GB of VRAM will fail to launch or perform poorly on a machine with integrated graphics, even if the machine has 32GB of system RAM.

Productivity and office applications — word processors, spreadsheets, web browsers, email clients — run on integrated graphics without issue.

RAM Requirements

Applications publish minimum and recommended RAM figures. These are distinct:

• Below minimum: the application may refuse to install, crash on launch, or be unstable in use
• Between minimum and recommended: the application runs but may be slow, especially with large files or multiple simultaneous tasks
• At or above recommended: expected performance for normal workloads

RAM requirements interact with the OS, other running applications, and background services. A machine that technically meets an application's minimum may still underperform if many other applications are competing for the same memory.

CPU Requirements

Applications may specify a minimum processor speed (GHz), minimum core count, CPU generation, or required CPU features. Some applications require specific CPU instruction sets — for example, virtualization software requires hardware virtualization extensions (Intel VT-x or AMD-V) in the CPU. These were covered in the Core 1 Virtualization module; the point here is that a CPU without the required instruction set makes the application non-functional even if speed and core count are adequate.

Storage Requirements

Every application lists a minimum free disk space requirement. What the spec often does not make obvious:

• Installation space: the final installed size once setup is complete
• Temporary space during installation: installers extract files, create temporary directories, and write logs before the final install; the working space needed during setup often exceeds the final installed footprint

A machine with exactly the minimum free space may fail mid-install because the temp files push it over the limit. Best practice: ensure available space clearly exceeds the listed requirement.

External Hardware Tokens (Dongles)

Some enterprise and specialized software uses a hardware token — a physical USB device that must be plugged in for the software to run. This is a software licensing and copy-protection mechanism: the application checks for the token at launch and periodically during use; without it, the software refuses to open or stops working.

Hardware tokens (often called dongles) are common in high-value software categories: CAD tools, specialized engineering applications, legal document management, and some audio/video production software. They are a real and current practice in enterprise licensing — flag for verification.

Application to OS Compatibility

An application built for one operating system will not run natively on another. A Windows .exe will not execute on macOS or Linux without a compatibility layer. macOS apps will not run on Windows. Before purchasing or deploying software, verify the application supports the target OS version — not just the OS family, but the specific version (e.g., Windows 11 support may have been added in a later release, while the initial version only supported Windows 10).

Distribution Methods

Software reaches machines in three ways. The delivery method affects what the technician needs to do before installation begins.

Physical Media vs Mountable ISO

Physical media — a CD, DVD, or USB drive containing the installer — is the traditional distribution method. The technician inserts the media, runs the installer, and proceeds. Physical media is increasingly rare for software distribution but still exists in enterprise environments and for certain specialized tools.

A mountable ISO file is a disk image — a file that contains the complete contents of what would be on a physical disc. The OS mounts the ISO as a virtual drive: it appears in File Explorer (or Finder, or Linux's file manager) exactly like a physical disc was inserted, and the installer runs from it. No physical media is required. ISO mounting is built into Windows 10/11 (right-click → Mount), macOS (double-click), and Linux.

Both methods deliver identical installer content — the ISO is just the physical disc without the plastic.

Downloadable Package

The most common current distribution method: the vendor provides a download link for an installer file. The file format depends on the platform:

• Windows: .exe (self-extracting installer) or .msi (Windows Installer package)
• macOS: .dmg (disk image) or .pkg (installer package) — covered in L8 of this module
• Linux: .deb (Debian/Ubuntu) or .rpm (Red Hat/Fedora) — installed via the package manager covered in L9

The distribution method is "downloadable package" regardless of which platform-specific format is used.

Image Deployment

In enterprise environments, administrators deploy applications by pushing a pre-configured system image — an OS installation with applications already installed — to multiple machines simultaneously. The image was prepared once on a reference machine and packaged for distribution. This was covered in L2 of this module (OS Installations).

Image deployment installs both the OS and all required applications in a single operation. The "application installation" happens when the image is created, not when it is deployed — machines receive an already-configured environment.

Impact Assessment Before Deployment

Before installing new software in a business environment, a technician evaluates four categories of impact. The A+ exam tests your ability to classify a consequence into the correct category.

Device Impact

The effect on the local machine's performance and resources:

• CPU and RAM consumption — particularly from background services that run even when the app is not actively in use
• Storage usage — initial install footprint plus ongoing data (logs, caches, synced files)
• GPU usage — applications that run background rendering or processing
• Battery drain — on laptops, a CPU-intensive background process significantly reduces battery life
• System stability — applications that install drivers or kernel-level components can affect overall system stability

An application with a persistent background agent that continuously syncs, indexes, or processes data is a device-impact concern even if the user rarely opens the application directly.

Network Impact

The effect on the network and organizational security:

• Bandwidth consumption — cloud-sync apps, streaming services, or applications that phone home frequently can saturate limited connections, particularly on metered or low-bandwidth links
• Firewall exceptions — applications that receive incoming connections (servers, collaboration tools, remote-access software) require firewall rules; each exception is a potential security exposure
• Listening ports — applications that open listening ports create network attack surface; the security team needs to be aware of what ports new software opens
• Data exfiltration risk — applications that transmit data to vendor cloud services may inadvertently send confidential business data outside the organization

Operation Impact

The effect on how the business and its users work:

• Workflow changes — a new application may change how existing processes are performed, requiring staff to learn new procedures
• User retraining — significant interface or feature changes require time and resources to train affected employees
• Software conflicts — a new application may conflict with existing software through DLL conflicts, shared library version differences, or port conflicts with other services
• Downtime during deployment — installation may require system restarts or service interruptions

Business Impact

The organizational and financial consequences:

• Licensing costs — per-seat, subscription, or perpetual license fees; hidden costs like annual maintenance fees or required support contracts
• Compliance implications — regulated industries (healthcare, finance, legal) have requirements about what software is used and how data is processed; a new application may introduce compliance obligations or violations
• Vendor support — what support does the vendor provide, under what SLA, for how long? Choosing software from a vendor with limited or uncertain support is a business risk
• Total cost of ownership — the purchase price is rarely the full cost; ongoing subscription fees, training costs, hardware upgrades needed to meet requirements, and IT labor for deployment and maintenance all factor in

The check questions below test your ability to apply system requirements to a scenario, identify the correct distribution method, and classify installation consequences into the correct impact category.