Scripts

Scripts in iiDeploy are used for two purposes:

• Automated software installation installs your apps offline during deployment, so the deployed machine comes fully installed with all the apps you want the moment it boots.
• PowerShell scripts run custom logic on the target machine during deployment.

One script, one job

For peace of mind, each script should do just one thing. You cannot drop multiple installer files into a single script and have the auto install agent handle them. If you have more than one installer file in the drag and drop section, write your own custom PowerShell script that guides each installer instead.

Automated software installation

For the iiDeploy Automatic Software Install Agent to work properly, the software must support silent install.

Finding installers

We curate an app store with over 10,000 apps at store.iideploy.com. Every app listed there links to the official website to download the installer. We simply make it easy to find them.

Creating an auto install script

PowerShell scripts

Use a PowerShell script when you need custom logic during deployment, for example installing software the auto install agent can't handle on its own, applying a wallpaper, or configuring Windows settings.

To create one, click Create in the same Scripts section and give it a name. You can drag and drop assets the script needs, for example a custom software installer or a wallpaper you want to use in the script. Below the assets, the Script Code section lets you write the PowerShell that tells the deployment what to do with these assets.

How scripts are laid out on the machine

During deployment, each script gets its own folder, and everything you dropped in as assets lives inside that folder next to the script. A wallpaper script, for example, ends up like this:

set-wallpaper/
├── set-wallpaper.ps1
└── wallpaper.jpg

If one of your assets is a folder, the script still runs outside that folder, not inside it. The folder sits next to the script, so you reach files inside it with a relative path:

install-browsers/
├── install-browsers.ps1
└── installers/          ← asset dropped as a folder
    ├── chrome.exe
    └── firefox.exe

For example the install-browsers.ps1 could be written as:

.\installers\chrome.exe /silent /install
.\installers\firefox.exe /S

Since the script executes from outside the installers folder, paths like .\installers\chrome.exe point to the files inside it.

Support

For any issues, email support@iideploy.com.