Deploy Windows Mobile 6.5 Apps Without an App Store

Before modern cloud app stores became the enterprise standard, deploying custom line-of-business (LOB) software to Windows Mobile 6.5 devices relied on direct packaging, manual sideloading, tethered desktop synchronization, and early enterprise device management solutions. Organizations bypassed public marketplaces entirely by packaging their applications into Cabinet (CAB) files and distributing them through direct file transfers, intranet download links, or centralized administrative tools.

The Core Package: Windows CE Cabinet (.CAB) Files

At the heart of Windows Mobile software distribution was the CAB file. Developers compiled their .NET Compact Framework or native C++ code into executable binaries and packaged them using tools like cabwiz.exe (Cabinet Wizard). These files contained the application binaries, necessary registry keys, shortcut definitions, and targeted directory paths. When an end user or automated process launched a CAB file, the operating system's native installer utility, wceload.exe, extracted the components, registered dependencies, created shortcuts in the Start Menu, and cleanly registered uninstall entries.

Tethered Installation via ActiveSync and WMDC

For single-device deployments or field staging, administrators frequently used physical USB or serial connections:

  • ActiveSync (Windows XP): Enterprise PCs running Windows XP utilized Microsoft ActiveSync to communicate with connected handhelds.
  • Windows Mobile Device Center (Windows Vista/7): Replaced ActiveSync on newer Windows operating systems.

Software vendors commonly bundled their programs inside a standard desktop installer (.exe). When executed on a connected PC, the installer leveraged the Windows CE Application Manager (CeAppMgr.exe) to remotely push the CAB file across the tethered connection to the handheld and trigger the installation process without requiring manual user intervention on the device screen.

Manual Sideloading via Storage Cards and Internal Memory

Field workers and warehouse technicians frequently installed software by manually loading CAB files onto physical media:

  • SD/CF Cards: Administrators loaded the setup files onto full-size or microSD cards. Inserting the card into the handheld allowed workers to open File Explorer, browse to the storage directory, and tap the CAB file to execute it.
  • Direct Copy via Mass Storage Mode: Some devices supported USB Mass Storage mode, allowing administrators to drag and drop installation files into internal flash storage partitions (such as \Application or \Storage Card).

Over-The-Air (OTA) Intranet Downloads

For semi-automated distribution across Wi-Fi or cellular-connected devices, IT departments established internal web servers. Pocket Internet Explorer on the mobile device was navigated to an internal HTTP or FTP portal. Tapping a hyperlink pointing to an .arm.cab file prompted the browser to download the file directly to the device's temporary memory, automatically launching wceload.exe once the transfer finished.

Enterprise Device Management (MDM) and Staging Tools

Large-scale fleets—such as rugged barcode scanners manufactured by Motorola/Symbol, Intermec, or Honeywell—relied on specialized mobile management suites rather than consumer-facing services:

  • Dedicated MDMs: Platforms like SOTI MobiControl, Wavelink Avalanche, and Microsoft System Center Mobile Device Manager (SCMDM) 2008 allowed administrators to silently push packages over enterprise networks.
  • Persistent Staging Partitions: Enterprise-grade hardware included non-volatile memory partitions (such as \Application). Administrators placed CAB files along with custom execution scripts inside these folders. When a worker performed a cold boot or battery pull, the operating system automatically re-executed the setup packages, preventing data loss in rugged enterprise environments.

Security Certificates and Code Signing

Unlike consumer platforms that enforce strict store-curated policies, Windows Mobile 6.5 security could be adapted to internal business needs. Enterprises operated private Public Key Infrastructures (PKIs) to sign their internal CAB packages using enterprise root certificates. By pre-provisioning these root certificates onto the device's Privileged Certificate Store—often using provisioning XML files (.provxml)—applications ran with full administrative rights without triggering security warnings or requiring user confirmation during the setup process.