Software Install
Installing software during deployment
The deployer copies the Softwares folder from the iiDeploy Extra USB partition to the target machine. After Windows setup completes, the post-deploy sequence auto-installs everything in that folder.
When to use Softwares vs. bake into the golden image
Most software should be installed inside the golden image, hence the capture once, deploy everywhere. Use the Softwares folder for software that cannot be baked in because it needs a unique identity per machine.
Bake into the golden image
Software that is identical across all deployments. Install it in the reference VM before capture:
- Browsers (Chrome, Firefox, Edge)
- Office suites (Microsoft 365, LibreOffice)
- PDF readers, media players, archive tools
- Development tools, runtimes (.NET, Java)
- Line-of-business applications shared by all machines
Baking in gives you faster deployment (no install time), works offline, and guarantees consistency.
Use the Softwares folder
Software that generates or requires a unique per-machine identity. Install it post-deploy so each target gets its own:
| Category | Examples | Why |
|---|---|---|
| Antivirus / EDR | SentinelOne, CrowdStrike, Defender for Endpoint | Unique agent ID per device |
| Remote control | TeamViewer, AnyDesk, Splashtop, ConnectWise, ScreenConnect | Unique client ID per machine |
| RMM agents | NinjaRMM, Datto Atera, Level, N-able | Unique agent registration |
| Backup agents | Veeam, Acronis, Backblaze, Druva | Per-machine client identity |
| Asset management | Lansweeper, PDQ Inventory | Unique inventory records |
| MDM enrollment | Intune, Workspace ONE | Per-device enrollment |
Also use the Softwares folder for software that:
- Requires per-machine online activation or licensing that would break after sysprep
- Needs internet to install (not available offline during capture)
- You want to update regularly without re-capturing the golden image
Decision table
| Question | If yes → Bake | If no → Softwares |
|---|---|---|
| Is it the exact same config on every machine? | Bake | Softwares |
| Does it need a unique per-machine ID or license? | Softwares | Bake |
| Does it need internet to install? | Softwares | Bake |
| Do you want to update it without re-capturing? | Softwares | Bake |
Supported file types
| Type | Behavior |
|---|---|
.ps1 | Custom install script — runs first, with the Softwares folder as the working directory |
.msi | Installed silently with /qn /norestart |
.exe | Auto-detects installer type (Inno, NSIS, WiX, InstallShield, Wise) and applies the correct silent switch |
.msix / .appx / .appxbundle | Provisioned system-wide |
Driver update tools
You can use manufacturer driver update tools to keep drivers current during deployment. Drop the tool's installer into the Softwares folder and the post-deploy sequence will run it automatically.
Before adding to your USB
Manufacturer tools vary in how they handle silent installs. Some may need .NET Framework pre-installed, refuse to run without real OEM hardware present, or require custom flags beyond what the auto-detector applies. Before deploying to real hardware:
- Check the manufacturer's documentation to confirm silent/command-line install is supported
- Download the tool and test it manually on a Windows machine — run it with the silent flags and verify it installs, updates drivers, and exits without user interaction
- Once confirmed, drop the tool (or a custom
.ps1wrapper with the correct flags) into theSoftwaresfolder on the USB
Dell Command Update
- Download Dell Command Update
- Rename the downloaded executable to
dcu-cli.exe - In the
Softwaresfolder, create a new file calleddcu-cli.ps1 - In that
.ps1file, write:dcu-cli.exe /applyUpdates -silent
Make sure the file extension is exactly .ps1. On Windows, enable File name extensions in File Explorer to confirm the file doesn't have a hidden .txt appended (e.g., dcu-cli.ps1.txt).
When the machine is connected to the internet, the update will run automatically during the post-deploy sequence.
Other manufacturers
For HP use HP Image Assistant (HPIA). For Lenovo use Lenovo System Update. Follow the same pattern: test the tool manually first, then place it in the Softwares folder with a .ps1 wrapper or as-is for the auto-detector to handle.
Support
For any issues, email support@iideploy.com.