Deploy dRofus (EXE) to Microsoft Intune
dRofus ASWindowsversion 2.18.17, 26 August 2026
dRofus (EXE) is in the PatchBee catalog as a Windows app from dRofus AS, 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.
Install from the command line
winget install --id dRofus.dRofus.EXE -e --silentPatchBee runs the same silent install of dRofus (EXE) for you in Intune: the installer winget points at, verified, packaged with the switches and detection rule below, and published to your tenant.
The plan PatchBee writes
dRofus (EXE) as an Intune app
The standard form for a EXE installer (x86 (32-bit), per user). 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
- "dRofusEXE.exe" --silent
- Uninstall
- The uninstall string from the app's uninstall key
- Detection
- Registry: the app's uninstall key. DisplayVersion under the app's uninstall key, current version or newer.
- Requirements
- x86 (32-bit) · per user
Why these values: silent install switches and detection rules, explained.
Installers in version 2.18.17
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x86 (32-bit) | EXE installer | per user | 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 dRofus (EXE) in its winget manifest. PatchBee uses them as the installer's unattended switches, so the package installs without a click.
- Silent
- --silent
About dRofus (EXE)
dRofus is a unique planning, data management and BIM collaboration tool that provides all stakeholders with extensive workflow support and access to building information throughout the building lifecycle.
Unlike any other planning tool on the market, dRofus was developed directly on behalf of public building owners. Capturing client requirements (EIR), validating design solutions (BIM) against client requirements, management of public standards and equipment planning are core features in the software.
dRofus has strong ArchiCAD, Revit and IFC integration with bi-directional data sync capabilities.
Model data from each discipline is captured, together with planning data, non-geometric data and documents, in a centralized database accessible to all project stakeholders via the dRofus desktop client and dRofus Web.
Typically, stakeholders produce data using different software programs that have different data schemas, with different filetypes, distributed across multiple servers, located in multiple different locations - and often this data is not re-usable by others.
This is why dRofus has become an essential tool for BIM projects - we consolidate disparate data sets and convert them into project information, insight and intelligence accessible to all project stakeholders.
- Publisher
- dRofus AS
- Homepage
- www.drofus.com/download
- License
- Proprietary
- Source
- winget · dRofus.dRofus.EXE
- Versions in catalog
- 7
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find dRofus (EXE) 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 dRofus AS 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.