With your installation script written (Part 1) and your custom catalog hosted (Part 2), the final step is mass deployment. Microsoft Intune is the perfect vehicle for this workflow.
There are two primary ways to deploy DCU through Intune: utilizing the automated Dell Management Portal link, or building a Custom Win32 App package. Because we want to bundle the advanced PowerShell configuration script we built in Part 1 to lock down the user interface, the custom Win32 App method is the superior route.
Preparing the Win32 Package
Intune cannot deploy raw .exe or .ps1 files directly as complex applications. You must wrap them into an .intunewin file using the Microsoft Win32 Content Prep Tool.
- Gather Your Files: Create a staging folder on your local machine (e.g.,
C:\DCU_Build). Place the Dell Command Update executable and yourInstall-ConfigureDCU.ps1script inside this folder. - Download the Prep Tool: Grab the
IntuneWinAppUtil.exeutility from Microsoft's official GitHub repository. - Wrap the Application: Open Command Prompt or PowerShell and run the utility pointing to your source folder and setup file.
- Generate: The tool will compress your staging folder and output an
Install-ConfigureDCU.intunewinpackage ready for upload.
Configuring Intune
With your package built, log into the Microsoft Intune admin center to create the deployment configuration.
• Install command:
powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File .\Install-ConfigureDCU.ps1• Uninstall command:
"%ProgramFiles%\Dell\CommandUpdate\dcu-cli.exe" /uninstall• Install behavior: System
• Detection Rule: File exists at
C:\Program Files\Dell\CommandUpdate\dcu-cli.exe
Assign the application to your target device groups. Once your endpoints sync with Intune, they will silently download the package, execute the PowerShell script, lock the application settings, and immediately begin pulling approved drivers from your custom TechDirect catalog.