IntunePrepTool – Building Blocks Update

Need to configure Registry (HKCU/HKLM), create shortcuts, or perform file/folder actions with Intune?

The new Building Block feature in the IntunePrepTool allows you to easily add customizations to your packages. You can also use this feature to create standalone .intunewin packages.

With Building Blocks, you can mix actions in both user and system context. After defining your actions, simply click Build. If both user and system context actions are included, the IntunePrepTool will automatically generate two separate .intunewin packages.

By using the built-in upload function (leveraging the intunewin32app module), the required dependencies between the apps are set up for you.

When using this during Autopilot as a required setup:

• If you’re primarily using Win32 apps (.intunewin) during Autopilot, there will be no issue with setting a system-context app as a dependency for a user-context app.
• However, if your strategy involves deploying a Win32 app as required to devices and an LOB app as required to users, make sure to test this scenario thoroughly in Autopilot before rolling it out to production.
  If it fails, simply create .intunewin packages for all your LOB apps using the IntunePrepTool and adjust your strategy accordingly.
  As an alternative, you can always configure the application as available instead of required to avoid potential issues.

Click here for How To Building Blocks:
Building Blocks – IntunePrepTool.com

Scroll down for the Building Blocks YouTube Demo (DEMO later this week!)

Also simplified creating packages from EXE source

IntunePrepTool Release Notes 1.6.6.0:

🔧 New: Building Blocks Feature

• Capture and edit registry changes, then add them as Building Blocks.
  • HKCU entries apply in User context.
  • HKLM entries apply in System context.

• Add shortcuts to the desktop or Start menu:
  • User context: Shortcuts can be removed by users without admin rights.
  • System context: Shortcuts are mandatory for non-admin users.

• Add files or folders:
  • User context gives the option for %USERPROFILE%, %APPDATA% and %LOCALAPPDATA.

Use Building Blocks as a standalone package or add them to a package in progress. (MSI, EXE, Chocolatey, Winget or MSIX)

📦 MSI, EXE, Chocolatey, Winget or MSIX → .intunewin

• Added navigation option to open the Building Blocks menu after clicking Test Install.
• Added the ability to include System Context Building Blocks in the .intunewin package.

📦 MSI → Intunewin Package

• New option to open the selected MSI file in Orca.
• Also added an option to install Orca via the Start > Config menu.

⚙️ EXE → Intunewin Package

• Added a button to run the EXE with /?.
  Upon clicking, a popup explains:
  • “If the EXE file supports this, a popup will open showing the available install parameters. If not, it might launch the setup. In that case, please close it before continuing.”
• After testing the installation, you can click the ‘Test Done / Show Uninstall Strings’ button to display the uninstall string.
  When you click the ‘Test Install’ button, a temporary pre-test .reg export is created from the HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\ location (including WOW6432Node).
  After testing is complete and you click ‘Test Done’, another backup is created. The two exports are compared and the uninstall string is extracted automatically.

🛠 Winget Integration

• If Winget is missing, the tool installs the latest stable version.
• If dependencies are missing, the tool downloads and installs them.
• When creating a Winget package and the target device lacks Winget, this step is handled as well.