Applications must match the CPU/processor for the operating system architecture.
32-bit application: An application that can only run on a 32-bit (x86) processor.
64-bit application: An application that can only run on a 64-bit (x64) processor.
32-bit processors have 2³² addressable memory spaces, which totals to 4 GB of RAM, whereas 64-bit processors can support 2⁶⁴ addressable memory spaces, allowing for significantly more RAM, theoretically up to 16 exabytes (17 billion GB).
32-bit and 64-bit drivers have hardware-specific drivers.
64-bit processors can run both 32-bit and 64-bit applications, providing greater flexibility and compatibility for users.
\Program Files (x86)
: Windows folder used to store 32-bit applications.
\Program Files
: Windows folder used to store 64-bit applications.
When installing applications, check if the software can run using the dedicated graphics card, or exceeds the integrated graphics card capabilities, and requires a dedicated graphics card.
Integrated graphics card: CPU and GPU are on the same chip, and system memory is used for graphics. Common in laptops.
Dedicated graphics card (GPU): Also called a discrete graphics card. Provides VRAM (Video RAM) and has higher graphics processing power for high-end use (e.g., gaming, video editing).
RAM: Random Access Memory - a temporary, volatile location for computer applications, data, and instructions.
RAM requirements: Specifications that dictate how much RAM is required to run an application. Critical specification - without enough RAM, the application may perform poorly, or not at all. Typically listed above and beyond the OS requirements.
CPU: Central Processing Unit - often referred to as the brain of the computer, it executes instructions from applications and the operating system.
CPU requirements: Specifications that outline the minimum and recommended processing power needed for applications to function correctly. This includes factors such as clock speed, core count, and architecture.
External hardware tokens: Physical tokens (typically USB storage devices) that allow users to unlock/use applications. The application will only operate with the hardware token connected. Often used with high-end/niche software.
Storage requirements: Applications require drive space to be installed, and for application use - pay attention to your available storage space, and the developer’s storage requirements.
Applications have to match the OS they’re being installed onto (Windows applications have to match the Windows OS).
Physical media: Installing applications from a physical flash drive (e.g., CD, DVD, USB). Increasingly rare method, and commonly used for when a machine cannot connect to the Internet (e.g., data centers).
Mountable ISO files: Use to install operating systems. Disk image that contains operating system files organized into folders within its own filesystem. Mounted into your main OS as a separate drive (i.e., separate drive letter).
Downloadable package: Applications installed directly from the Internet - install from the developer website, or from a centralized app store for better security.
Image deployment: Allows installation of an entire operating system, with the desired application, on an OS image. This image can then be duplicated and installed on other machines. Useful for companies - images can contain all relevant security updates, enterprise applications, and corporate network configurations.
Often used for virtual machines, as virtual machine hardware (i.e., hypervisors) is identical.
Can be problematic if system hardware (drivers) don’t match the software configuration.
Very fast deployment - often used when operating systems are damaged or infected with malware.
Device impact for new applications: Refers to issues seen after an upgrade - such as slowdowns, non-functioning applications, and deleted files
Network impact for new applications: Access to internal services - rights and permissions to file shares.
Operation impact for new applications: Time-sensitive application installation - updated applications may also require workflow changes.
Business considerations: Critical processes are sensitive to downtime and outages. Applications have the same rights and permissions as the user who is logged in (sensitive files, networked shares, etc.) Unknown/untested applications can therefore cause significant issues.