Deploy ScaleFT with Intune

Overview

Follow these Intune deployment steps for ScaleFT 1.83.4 from ScaleFT to keep packaging, assignment, and troubleshooting consistent.

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.

Package the App for Intune

Start by organizing a dedicated packaging folder for ScaleFT to keep input binaries and generated .intunewin files traceable.

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 App

In Intune, create the Win32 app object for ScaleFT and align core settings before moving to assignments.

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

Use this stage to lock in program, requirement, and detection values for ScaleFT before assignment expansion.

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.

Assign the App and Deploy

Assign ScaleFT in rollout rings (pilot -> controlled broad) so you can gate expansion on install and detection quality.

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.

Sync Policy to Target Devices

Use a controlled sync check for ScaleFT to separate assignment timing issues from installer failures.

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.

Review Deployment and Install State

Track first-wave deployment signals for ScaleFT and focus on repeatable patterns before broadening scope.

Troubleshooting

When deployment results drift from expected behavior, run the checks below in order to isolate scope, command, detection, and policy timing problems quickly.

For persistent failures, capture the exact return code, rerun the install command in the same context, and re-check Intune Management Extension logs.

Deployment Validation Checklist

• Run a pilot rollout of ScaleFT 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.

Rollback and Recovery Notes

• Document a rollback baseline for ScaleFT (target version: 1.83.4) 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