Deploy RBTools with Intune

Overview

This guide walks through deploying RBTools 6.0 from Beanbag, Inc. with Intune Win32 packaging, policy sync, and rollout verification.

This non-AI draft follows a fixed production-safe template. It keeps the deployment sequence explicit and auditable so operational teams can review every step. For policy timing context, read how Intune device sync works. For assignment strategy, review Required vs Available app assignments.

Download Installer

Download the installer from the vendor source and keep the original file name intact. Store checksum evidence and source URL in your deployment notes so package provenance is clear. If you need packaging guardrails, use .intunewin package preparation and Win32 packaging best practices.

• Use a clean working directory such as D:\Intune.
• Place installer binaries in D:\Intune\Input only.
• Keep build output in D:\Intune\Output to simplify validation.

Create Intune Package

Prepare a clean packaging workspace for RBTools so source files, output artifacts, and wrapper tools stay isolated and repeatable.

IntuneWinAppUtil.exe -c "D:\Intune\Input" -s "installer.exe" -o "D:\Intune\Output" -q

After the build completes, verify that the output package exists and matches the expected naming convention. Keep the package immutable for the rest of the deployment cycle; if any input changes, rebuild and version the package explicitly.

Create the Win32 App Entry

Build the Intune app entry for RBTools with metadata, program settings, and detection prepared for pilot rollout.

1. Go to Apps -> All apps -> Add and choose Windows app (Win32).
2. Upload the .intunewin file from D:\Intune\Output.
3. Set app details (name, publisher, version) to match package evidence.
4. Save and continue to Program, Requirements, and Detection settings.

Configure App Settings

Configure app settings for RBTools with a pilot-first mindset so install, uninstall, and detection behavior remain predictable at scale.

Define requirement and detection rules with conservative logic. Detection should prove install state, not just file copy. Start with one reliable rule, then add complexity only when necessary. For deeper rule guidance, refer to Intune detection rules explained.

Configure Assignment and Rollout

Scope assignments for RBTools by rollout intent and ring maturity instead of moving directly to full production.

1. Create a controlled pilot assignment (Required or Available based on rollout strategy).
2. Trigger sync on test devices and confirm assignment receipt.
3. Review device install status and detection results in Intune.
4. Promote to broader scope only when failure patterns are understood and acceptable.

Run a Device Policy Sync

Trigger and confirm policy sync for RBTools before troubleshooting deeper packaging assumptions.

1. On device: Settings -> Accounts -> Access work or school -> Info -> Sync.
2. In Intune: open the pilot device and trigger Sync.
3. Re-check app state after one full check-in cycle.

Tracking the App Deployment

Monitor install and detection status for RBTools by ring to decide whether to proceed, pause, or remediate.

Troubleshooting and Fixes

Use this troubleshooting pass before changing assignments or detection logic. Validate assignment scope, installer behavior, and Intune Management Extension outcomes first.

If the issue repeats after these checks, collect fresh Intune Management Extension logs and compare against the latest assignment and requirement settings.

Post-Deployment Validation

• Run a pilot rollout of RBTools to a small ring before broad assignment.
• Confirm the install command executes silently in the target context.
• Confirm detection logic (types observed: manual/unspecified) matches real endpoint state after install.
• Monitor return codes and enforcement state in Intune Device install status and Intune Management Extension logs.
• Confirm uninstall intent and rollback readiness are documented for the same pilot devices.

Change Log and Rollback Guidance

• Document a rollback baseline for RBTools (target version: 6.0) before broad rollout.
• Confirm the uninstall command is validated in pilot scope before broader rollout.
• Use phased assignments (pilot -> ring1 -> broad) with explicit go/no-go checkpoints after each ring.
• When replacing an existing deployment, retire superseded assignments only after validation closes successfully.

Related Intune guides