Installing Applications and Cloud Productivity Tools: Requirements, Distribution, Impact, and Cloud Services
Unit 1: Operating Systems and Installation. Lesson 4 of 41 in APlus Academy Core 2.
Two objectives about software rather than the OS: whether a program will run on a machine and how it arrives, and how the cloud versions of everyday tools are set up.
System requirements for applications
Read the box (or the download page) against the machine:
- 32-bit versus 64-bit: a 64-bit application needs a 64-bit OS; a 32-bit application runs on either but is limited to about 4 GB of memory. A driver or plug-in must match the host application's architecture.
- Dedicated versus integrated graphics: gaming, CAD, and video software want a dedicated card with its own VRAM (video memory); integrated graphics borrow system RAM and may not meet the minimum.
- RAM and CPU minimums and recommendations; the recommendation is what makes it usable.
- External hardware tokens: some professional software runs only with a USB license key present.
- Storage for the installation and for its working files, on the type of drive it expects (some insist on an SSD).
Storage requirements mean free disk space for the installer, the installed program, and its data, checked against the drive before installing.
Application-to-OS compatibility
The vendor lists the supported operating systems and versions. An app written for Windows 7 may fail on Windows 11 without compatibility mode; a macOS app compiled for Intel needs a translation layer on Apple silicon; a phone app needs a minimum iOS or Android version. Check before buying, and test on one machine before rolling out.
Application to OS compatibility is the first check: 32-bit or 64-bit, the minimum OS version, and whether the application was built for this operating system at all.
Distribution methods
- Physical media (a DVD or USB stick from the vendor) versus a mountable ISO file: an ISO is a disk image; double-click to mount it as a virtual drive and run setup.
- Downloadable package: an installer from the vendor's site or a store; verify the download's hash or signature.
- Image deployment: the application is baked into the OS image so every new machine has it.
Store-based installs (Microsoft Store, App Store) handle updates automatically; classic installers need their own update mechanism.
Impact considerations for new applications
Before installing across a company, think through four kinds of impact:
- Device: does the machine have the resources; will it slow down; does it conflict with existing software.
- Network: bandwidth for downloads and updates, ports it needs opened, a license server it must reach, cloud dependencies.
- Operation: workflow changes, training, downtime for installation, support load, backups of its data.
- Business: licensing cost, compliance with regulations, vendor viability, data ownership.
This is the same thinking change management formalizes in unit 7.
Cloud-based productivity tools
Most offices now run on hosted suites. The technician's tasks:
- Email systems: configure the client or the browser sign-in; mail lives on the provider's servers; migration from on-premises servers moves mailboxes.
- Storage: cloud drives with sync and folder settings on each device: which folders sync, whether files stay in the cloud until opened (files on demand), and where the local copy lives; watch disk space and data caps.
- Collaboration tools: spreadsheets, videoconferencing, presentation and word processing tools, instant messaging; sharing permissions and external access are the security points.
- Identity synchronization: user accounts from the on-premises directory are synced to the cloud tenant so one login works everywhere; account problems trace back to the sync.
- Licensing assignment: each user gets a license from the pool; a user who cannot open the desktop apps or mailbox usually has no license assigned or an expired one.
The suite typically includes email, file storage and synchronization, word processing, spreadsheet, and presentation tools, plus collaboration and identity synchronization with the directory.
Installing Applications and Cloud Productivity Tools: Requirements, Distribution, Impact, and Cloud Services, explained slowly
Two checklists
Installing an application is a checklist of requirements and impacts; setting up cloud productivity tools is a checklist of accounts, sync, and licenses. Both objectives produce "what should the technician check first" questions.
Requirements versus the machine
requirement check on the machine consequence of ignoring 32-bit versus 64-bit Settings, System, About: OS type 64-bit app will not install on 32-bit OS dedicated graphics and VRAM Device Manager, Display adapters; dxdiag crashes, unplayable frame rates, unsupported RAM About; Task Manager Performance swapping, slowness, out-of-memory errors CPU About; the vendor's list of supported chips slowness or refusal to run (instruction sets) external hardware token the USB key present and its driver software will not start storage free space on the target drive; SSD or HDD install fails or the app crawls
Minimum requirements let it run; recommended requirements let people work. Quote the recommended line when buying.
Compatibility and distribution
distribution how it arrives technician's step physical media DVD or USB from the vendor insert, run setup; keep the media and key mountable ISO file a disk image download right-click, Mount; a virtual drive appears; run setup; eject downloadable package .exe or .msi from the vendor or a store verify the hash or signature; run as needed image deployment already inside the OS image nothing per machine; update the image for new versions
Compatibility mode (right-click the program, Properties, Compatibility) makes Windows imitate an older version for a stubborn program; it is a workaround, not a fix. Apple silicon Macs run Intel apps through a translation layer with a performance cost.
The four impacts, with questions to ask
device Will it run well here? Does it conflict with what is installed? Does it need a driver or a reboot? network How much bandwidth for installs and updates? Which ports and servers must be reachable? Does it need a license server? operation Who needs training? What downtime? How does support change? What happens to its data in backups? business What does licensing cost per seat or per year? Any regulatory or data-residency issue? Is the vendor stable? Who owns the data?
An application that passes the device check and fails the network check (a license server blocked by the firewall) is a common trouble ticket after rollout.
Cloud productivity, the technician's tasks
component what to configure common ticket email systems sign-in in the client or browser; migration of mailboxes "my mail stopped syncing": password, license, or the client profile storage sync client; which folders sync; files on demand; local path "my disk is full": everything set to keep local; "file missing": deleted on another device collaboration tools spreadsheets, videoconferencing, presentations, word processing, instant messaging; sharing and external access "cannot share with a customer": external sharing disabled by policy identity synchronization directory sync to the cloud tenant; same username everywhere "cloud password differs from PC password": sync broken or not yet run licensing assignment assign each user a license from the pool; groups can auto-assign "apps say unlicensed": no license or expired subscription
Worked examples
- A CAD package requires a dedicated GPU with 4 GB VRAM; the office PCs have integrated graphics. The device impact fails; the fix is a graphics card or a workstation, not a driver update.
- A vendor sends an ISO for a licensing server. Mount the ISO, run the installer, then open the license server's port on the firewall so clients can check out licenses (network impact).
- New hires cannot open cloud email though their accounts exist. Their licenses were never assigned; assign from the admin portal.
- A user's cloud drive fills the laptop. Turn on files on demand and stop syncing the archive folders.
How the exam asks it
- "A 64-bit application fails to install on a workstation. Most likely cause?" The OS is 32-bit.
- "Which requirement is checked for a video editing application?" Dedicated graphics card and VRAM.
- "A downloaded ISO must be installed. What is the first step?" Mount the ISO.
- "Which impact category covers user training and downtime?" Operation.
- "A new employee cannot use the cloud office apps. First check?" License assignment.
- "Users want one password for the PC and the cloud suite." Identity synchronization.
What to memorize
- Requirements: 32 versus 64-bit, dedicated graphics and VRAM, RAM, CPU, hardware token, storage.
- Distribution: media, mounted ISO, downloadable package (verify), image deployment.
- Impacts: device, network, operation, business.
- Cloud: email, storage sync and folder settings, collaboration tools, identity synchronization, licensing assignment.