Adding Applications

Applications install during the first-boot phase, silently, as SYSTEM, from a staged folder.

Upload steps

1. Content Library → Upload Content.
2. Name the app, e.g. 7-Zip 24.08.
3. Set Type to Application.
4. Provide the Install command — the silent-install command run as SYSTEM from the staged folder, e.g. msiexec /i "7z2408-x64.msi" /quiet.
5. (Optional) Success codes — extra exit codes to treat as success, e.g. 0, 3010, 1641.
6. (Optional) Install timeout (minutes) — how long this app's install may run before it's marked failed. Leave blank for the 30-minute default; raise it for large suites (see below).
7. Upload the installer or zip.

Add the app to a Task Sequence's Install Applications step to include it in a deployment.

Large or multi-file apps (ZIP) — e.g. Adobe Creative Cloud

Some applications aren't a single .msi / .exe — they're a folder of many files (Adobe Creative Cloud packages, Microsoft 365 ODT, etc.). You don't need to upload the files individually: upload the whole thing as a single .zip.

CloudImage detects a .zip and automatically extracts it on the device before installing. Your install command then runs from the extracted folder, so you point it at the setup file inside the zip.

1. On a normal Windows PC, gather the app into one folder and zip its contents (see the path note below).
2. Upload the .zip as an Application (as above).
3. Set the Install command to the extracted entry point, using the path inside the zip, e.g. Build\setup.exe --silent.

Adobe Creative Cloud specifically

1. In the Adobe Admin Console, create a managed (named) package. This produces a folder containing Build\, Exceptions\, and Adobe's own Install.cmd script (plus PackageInfo.txt and a .ccp file).
2. Zip that folder's contents — so the zip root directly contains Build, Exceptions, Install.cmd, etc. (don't zip the wrapper folder).
3. Install command: Install.cmd
   Run Adobe's own Install.cmd rather than calling setup.exe yourself — it's the multi-line script Adobe generates and it launches the install correctly. A .cmd / .bat runs as a script, so all its lines execute. (If you prefer to call it directly instead, that's Build\setup.exe --silent.)

Path note (important)

After extraction, the install command runs with its working directory set to the root of the extracted zip. Relative paths must match the zip's internal structure:

• If the zip contains Build\setup.exe at its root → use Build\setup.exe --silent.
• If you zipped the parent folder (so the zip contains MyPackage\Build\setup.exe) → use MyPackage\Build\setup.exe --silent.

To keep it simple, zip the contents, not the wrapper folder.

Two limits to be aware of

• Install timeout: each application defaults to a 30-minute install timeout. A full Creative Cloud suite can exceed this on slower hardware. Set the app's Install timeout (minutes) field higher — e.g. 90 — to give it the time it needs; if an install runs past its limit it's marked failed. Where you can, prefer smaller, targeted packages over the entire suite.
• Size & bandwidth: a multi-GB zip is uploaded once, but is downloaded to every device at deploy time and counts toward your storage usage. Peer caching and a Site Server cache greatly reduce the repeat download cost when imaging many machines on one network.