Skip to content
English - United States
Contact BodyMetrix Support
  • There are no suggestions because the search field is empty.

BodyMetrix Managed Deployment

Silent installs, detection rules, driver pre-staging, return codes, and logs for IT fleet deployment using Intune, SCCM, or Jamf

This guide is for IT teams deploying BodyMetrix Software to multiple computers. For requirements, downloads, standard installation, and network requirements, see the BodyMetrix IT Installation Guide.

Windows: choose one deployment model per fleet
Setup never installs two copies on one PC. A machine-wide install is refused while per-user copies exist in any profile, and a silent per-user install is refused while a machine-wide copy exists. Both refusals return exit code 2, with nothing changed.

Model A: User context Model B: Machine-wide
Best for Matching the standard install. Recommended default. Shared or locked-down machines managed centrally
Installs to Each user's profile All users on the PC
In-app updates No administrator prompt Need administrator approval

Model A: User context (default)
Each Windows account that uses BodyMetrix installs its own copy, about 0.8 GB under its profile. The app appears in Apps & features only for that account.

Setting Value
Intune Win32 app install behavior User
Install "BodyMetrix-Setup-<version>.exe" /S or /currentuser /S
Uninstall "%LOCALAPPDATA%\Programs\BodyMetrix\Uninstall BodyMetrix.exe" /S /currentuser
Detection File %LOCALAPPDATA%\Programs\BodyMetrix\BodyMetrix.exe, version greater than or equal to the deployed version

Pre-stage the prerequisites. Silent per-user installs skip them:

  • Wand driver: run pnputil /add-driver <inf> /install as SYSTEM through your MDM. Use bodymetrix-winusb.inf and .cat from the installed app's resources\winusb-driver\ folder. Exit codes 0, 259, and 3010 mean success.
  • Access Database Engine 2016 (x86): only if legacy BodyView .mdb conversions are needed.

Watch for:

  • A PC that still has a machine-wide 1.0.x copy exits with code 2. Run Setup once interactively there, or migrate it with a system-context push (Model B).
  • An unelevated /allusers /S run also exits with code 2, with nothing installed, rather than raising a prompt.

Model B: Machine-wide (system context)

Setting Value
Install "BodyMetrix-Setup-<version>.exe" /allusers /S
Install location C:\Program Files\BodyMetrix
Uninstall "C:\Program Files\BodyMetrix\Uninstall BodyMetrix.exe" /S
Detection C:\Program Files\BodyMetrix\BodyMetrix.exe
  • Setup stages the prerequisites directly.
  • Installs made with /allusers stay machine-wide, because Setup records the scope. In-app updates on these PCs need administrator approval, so push new versions through your deployment tool.
  • System-context pushes must pass /allusers /S for the model to persist.
  • /S alone from an elevated context installs machine-wide without recording the scope, and Setup won't remove that copy on its own later (exit code 2). To fix it, uninstall that copy as an administrator, then run Setup as the operator.
  • Only 1.0.0 to 1.0.3 machine-wide copies are converted automatically.

Version upgrades
Deploy the new installer over the top with the same switches and the same model.

Updates by install type

  • Per-user installs (the default since v1.0.6) update in the app with no administrator prompt.
  • Machine-wide installs made with /allusers need administrator approval for in-app updates. Push new versions through your deployment tool, or move the PC to the per-user model by uninstalling the machine-wide copy and running Setup as the operator.
  • Legacy 1.0.0 to 1.0.3 machine-wide installs convert to per-user on their next interactive update, with one approval.
  • Update activity is logged locally for audit.

Return codes

Code Meaning
0 Success
2 Refused or aborted, nothing changed. The reason is in the Setup log.

Common causes of code 2:

  • BodyMetrix is open.
  • Mixed deployment models on the same PC.
  • An unelevated /allusers run.
  • The shared folder C:\Program Files\IntelaMetrix Setup is in an unexpected state. Remove it and run Setup again.
  • A previous machine-wide copy that Setup won't remove on its own, because it isn't a BodyMetrix release Setup recognizes, or it isn't a plain folder under Program Files. Remove it from Apps & features as an administrator, then run Setup again.

No reboot is enforced.

Logs

Log Location
Setup log, run by the user %TEMP%\BodyMetrix-Setup.log
Setup log, elevated C:\Program Files\IntelaMetrix Setup\BodyMetrix-Setup.log
Driver staging log, per-user installs C:\Program Files\IntelaMetrix Setup\winusb-driver-install.log
Driver staging log, machine-wide installs C:\Program Files\BodyMetrix\resources\winusb-driver\install.log

C:\Program Files\IntelaMetrix Setup\BodyMetrix-Setup-relaunch.exe may remain after a hand-off. It's removed at the next reboot.

Prerequisite notes

  • A driver staged while the wand is unplugged binds on first connection.
  • On PCs with 64-bit Microsoft Office, the 32-bit Access engine is intentionally skipped, because Microsoft blocks side-by-side installs. Legacy .mdb import on those PCs needs the 64-bit provider. Contact support.

macOS: Jamf and other MDM
We ship signed, notarized .dmg and .zip artifacts. A PKG isn't available at this time. Deploy directly from the DMG, or repackage with your standard tooling. Contact us if your workflow requires a PKG.

Verify deployment

  • The app launches from the Start Menu or Applications.
  • On Windows, pnputil /enum-drivers lists the BodyMetrix WinUSB package, or the wand appears in Device Manager as BodyMetrix when connected.

Deployment questions? Open a support case at bodymetrix.com/pages/contact-support-form and choose Software & App Support.