kitzyandAllen Houchins
332d8a2cee
**Related issue:** Resolves #50325 Adds Microsoft Access Database Engine 2016 Redistributable as a Windows Fleet-maintained app, from winget `Microsoft.AccessDatabaseEngine2016` (16.0.5044.1000, x64). Found in a customer's Windows deployment catalog with no Fleet equivalent. ## No ingester change was needed after all When I scoped this I expected to need a one-line change, because winget types the installer as `portable`, which is not in the ingester's `vendorTypes` or `fileTypes`. I tested it first: `"installer_type": "portable"` with an empty scope matches cleanly, and since the generated output carries no installer type (Fleet infers `.exe` from the URL), the result is correct as-is. This is the first FMA input to use `portable`. If reviewers would rather not establish that precedent, adding `portable` alongside `wix`/`nullsoft`/`inno` in `vendorTypes` would let the type fall through to the URL extension and the input could then say `exe`. Both work. I chose the one that touches no shared code. ## Identity: winget's name is wrong twice over winget's locale manifest says `Microsoft Access Database Engine 2016 Redistributable`. The MSI says: ``` ProductName Microsoft Access database engine 2016 (English) Manufacturer Microsoft Corporation ProductCode {90160000-00D1-0409-1000-0000000FF1CE} UpgradeCode {00160000-00D1-0000-1000-0000000FF1CE} ALLUSERS 1 ``` Two traps: the real name is lowercase `database engine`, and it carries an `(English)` locale suffix with the LCID (`0409`) embedded in the ProductCode. osquery's `=` on TEXT is case-sensitive, so the winget-derived name would have matched nothing. ## x64 only, deliberately The customer deploys both architectures, but **x86 and x64 register the identical DisplayName**. I confirmed this by extracting both installers: | Arch | ProductName | UpgradeCode | |---|---|---| | x64 | `Microsoft Access database engine 2016 (English)` | `{00160000-00D1-0000-1000-0000000FF1CE}` | | x86 | `Microsoft Access database engine 2016 (English)` | `{00160000-00D1-0000-0000-0000000FF1CE}` | They differ only by product and upgrade code. Two FMAs could not be told apart by an exists query, so installing one would make the other report itself installed. Shipping x64 only avoids that. This also corrects my earlier note on the issue suggesting the architecture go in the catalog name; that would distinguish the catalog entries but not the detection queries, so it would not have helped. The uninstall script resolves the product from the x64 upgrade code rather than a product code, so it removes the x64 build and leaves an x86 install alone. ## The Office conflict is handled, not hidden This redistributable refuses to install when Office of the opposite bitness is present. Following the same approach @allenhouchins set out for HandBrake in #50323, the install script checks the Click-to-Run platform first and exits with an actionable message instead of a bare installer failure: ``` 32-bit Microsoft Office is installed on this host (Click-to-Run platform: x86). The 64-bit Access Database Engine cannot be installed alongside it. Use the 32-bit redistributable instead. ``` **A green validator here proves less than usual.** The CI runner has no Office installed, so it exercises the happy path only. The conflict this app is known for cannot be reproduced there. That is a limitation of the environment, not evidence the app is safe on managed hosts, and it is the main thing worth weighing before merging. ## Other notes - Installer SHA confirmed against a local download of `accessdatabaseengine_X64.exe` (`04e96c9f…03de`). - The download is a self-extracting package. Its `setup.cmd` runs `InstallUCRT.exe` and then `msiexec %1 /i AceRedist.msi`, which is why `/quiet` reaches the MSI. - **No icon.** The MSI has no `ARPPRODUCTICON` and no Icon table, so there is nothing to extract. The app falls back to the generic software icon, which suits a redistributable with no user-facing app. # Checklist for submitter - [x] QA'd all new/changed functionality manually <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added Microsoft Access Database Engine 2016 Redistributable as a supported Windows application. * Added silent installation and uninstallation workflows with architecture checks, registration detection, timeout handling, and standard success-code support. * Included package metadata, version information, download verification, Developer tools categorization, and reliable installation-state detection. * Added handling for existing installations and validated installer outcomes. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Allen Houchins <allenhouchins@mac.com>
News · Report a bug · Docs · Why open source? · Art
Open-source platform for IT and security teams with thousands of computers. Designed for APIs, GitOps, webhooks, YAML, and humans.
What's it for?
Fleet gives you a single system to secure and maintain all your computing devices over the air. You can do MDM, patch stuff, deploy software, and verify anything, all from one place, across every OS your organization uses.
Fleet works directly with data and events from the native operating system, down to the bare metal. Strong diagnostics let you investigate errors on end-user devices and collect accurate audit evidence in minutes.
Get started
You can try Fleet out for yourself, or grab time with one of the maintainers to chat.
Is it any good?
Fleet is used in production by IT and security teams managing thousands of devices. Many deployments support tens of thousands of hosts, and a few large organizations manage 400,000 or more.
Supported platforms
- Linux (all distros)
- macOS
- Windows
- Chromebooks
- iOS and Android (BYOD or corporate-owned)
- Amazon Web Services (AWS)
- Google Cloud (GCP)
- Azure (Microsoft cloud)
- Data centers
- Containers (kube, etc)
- Linux-based IoT devices
Infrastructure as code
Manage your fleet with GitOps, or use the GUI, REST API, webhook events, and the fleetctl command-line tool.
Linux support
First-class support for all major distros. Linux gets the same attention and visibility as macOS and Windows.
Visibility and compliance
Fleet can report on hundreds of attributes across your devices and ships with CIS benchmarks for macOS and Windows and comprehensive operating system, hardware, and software data. Check out the table reference documentation to see what's available.
Open by design
Fleet is open source and transparent about what it can and can't see. End users can verify exactly how the agent works and what data their company collects. Fleet collects only the data needed to manage and secure devices, not private activity like keystrokes, emails, or webcams.
Good neighbors
Ready-to-use, enterprise-friendly integrations exist for Snowflake, Splunk, GitHub Actions, Vanta, Elastic Jira, Zendesk, and more. Fleet also works with tools such as Munki, Chef, Puppet, Ansible, CrowdStrike, and SentinelOne.
Lighter than air
Fleet is lightweight and modular. You can use it for MDM without using it for security, and vice versa. You can turn off features you are not using.
Free as in free
The free version of Fleet will always be free. Fleet is independently backed and actively maintained with the help of many amazing contributors.
Longevity
The company behind Fleet is founded (and majority-owned) by true believers in open source. The company's business model is influenced by GitLab (NYSE: GTLB), with great investors, happy customers, and the capacity to become profitable at any time.
Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and our commitment to improving the product.
Chat
The Fleet community is full of kind and helpful people. Whether or not you are a paying customer, if you need help, just reach out.
Contributing 
Contributions are welcome, whether you answer questions on Slack / GitHub / LinkedIn, improve the documentation or website, write a tutorial, give a talk at a conference or local meetup, give an interview on a podcast, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
License
The free version of Fleet is available under the MIT license. The commercial license is also designed to allow contributions to paid features for users whose employment agreements allow them to contribute to open source projects. (See LICENSE.md for details.)
Fleet is built on osquery, nanoMDM, Nudge, and swiftDialog.