Deploy i-bus Tool to Microsoft Intune
ABBWindowsversion 1.9.56.0
i-bus Tool is in the PatchBee catalog as a Windows app from ABB, synced from the Windows Package Manager community repository (winget). Pick it in the App Library and PatchBee writes the deployment plan below, builds the package, publishes it to your Intune tenant and assigns it to the Entra groups you choose. New versions then follow through your update rings.
The plan PatchBee writes
i-bus Tool as an Intune app
The standard form for a MSI (WiX) (x64, per machine). The real plan is generated from the installer when you package, and shown in full before anything is published; every field can be changed.
- Intune app type
- Windows app (Win32), .intunewin
- Install
- msiexec /i "i-busTool.msi" /qn /norestart
- Uninstall
- msiexec /x {2F617DDC-3100-4D26-947B-3DB6D53CB4E5} /qn /norestart
- Detection
- MSI product code. Product code {2F617DDC-3100-4D26-947B-3DB6D53CB4E5}, version 1.9.56.0 or newer.
- Requirements
- x86 (32-bit), x64 · per machine
Installers in version 1.9.56.0
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x86 (32-bit) | MSI (WiX) | per machine | SHA-256 published |
| x64 | MSI (WiX) | per machine | SHA-256 published |
PatchBee downloads the installer from the publisher's own URL and verifies its SHA-256 against the catalog before packaging. "None published" means the source carries no hash for this download, so that check has nothing to compare against; packaging still works.
Silent install switches
Recorded for i-bus Tool in its winget manifest. PatchBee uses them as the installer's unattended switches, so the package installs without a click.
- Install location
- INSTALLFOLDER="<INSTALLPATH>"
About i-bus Tool
Through the i-bus® Tool, ABB provides a fully innovative software concept for supporting KNX system integrators. The i-bus® Tool accesses an ABB KNX device via a standardized KNX interface (USB, IP) with the assistance of the physical address. The integrator can trigger the desired functions, read values, simulate states and make settings for the connected device. Internal information and states of the device hardware and applications, which were not available to the integrators or only available after considerable effort, are now available in a transparent manner and can be specifically retrieved and partly influenced. The information from status bytes can, for example, be represented as plain text. An important principle is that no divergences to the ETS project can result through the i-bus® Tool.
The supported KNX IP devices can be accessed via the IP network, and it's possible to use functions such as Discovery, Firmware Update, etc.
ABB provides a unique user interface within the i-bus® Tool, a so-called plug-in, for every supported device. The device-specific information is displayed via this user interface and the required settings can be made.
The i-bus® Tool is being expanded continuously with new functions and supported devices. The expansions are automatically made available by an online update and can be installed as required.
The i-bus® Tool is optional, i.e. the ABB i-bus® KNX devices can still be commissioned using just the ETS.
The i-bus® Tool is free of charge and can be downloaded at http://www.abb.com/knx.
- Publisher
- ABB
- Homepage
- new.abb.com/low-voltage/products/building-automation/service-and-tools/engineering-tools/i-bus-tool
- License
- Proprietary
- Source
- winget · ABB.i-busTool
- Versions in catalog
- 1
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find i-bus Tool in the App Library, open its plan (the commands, detection rule and requirements above, editable) and publish: PatchBee downloads and verifies the installer, builds the package, creates the Intune app and assigns your groups. When ABB ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.
Read the step-by-step guideMore Windows apps
Catalog data as of 11 October 2026, from the Windows Package Manager community repository (winget). The product re-reads the source every night and plans against the live catalog, so the version here may already be one behind. Nothing is published to a tenant without an administrator approving the plan.