A software deployment fails in Endpoint Central for embarrassingly simple reasons — usually an installer that was never silent to begin with. Build the package right, test the silent switch yourself, then deploy.
Software deployment looks like the simplest Endpoint Central feature: pick an installer, pick computers, click deploy. The failures arrive anyway, and they are almost never the product’s fault. The classic causes are a package built from an interactive installer that waits forever for a click nobody will give, a 'silent' switch copied from the internet and never tested, or a deployment aimed at the whole office before it was proven on one PC. This page builds a package the disciplined way — and explains the honesty rule behind it: if you have not run the silent install yourself, you do not have a silent installer; you have a hope.
Two hundred sessions “in progress” at once almost always means the same thing: the installer opened a window on every PC and is waiting for a click. That is an interactive installer deployed as if it were silent.
Mass 'in progress' is the signature of a non-silent installer. One pilot PC would have revealed it in two minutes.
C:\> Setup.exe /silent
Run it on a spare PC first. A truly silent install shows no window, no prompt, no reboot surprise — and the software simply appears. If anything asks a question, the switch is wrong or the installer does not support silent mode.
Five minutes of testing on one PC is the cheapest quality check in all of software deployment.
Use the vendor’s proper installer — an .msi where one exists, or the full offline .exe, not a small web stub that downloads the real files later (stubs often fail under deployment conditions and behave differently per machine). Download it from the software maker’s own site only. A package you deploy to two hundred PCs multiplies whatever is inside it, good or bad, two hundred times.
MSI packages install silently with msiexec /i package.msi /qn. EXE installers vary: /silent, /S, /quiet and vendor-specific switches all exist, and the same switch can mean different things to different installers. Do not copy a switch from a forum and trust it. Run it yourself on a test PC exactly as the agent will run it, watch for windows and prompts, and confirm the software is present and working afterwards. Endpoint Central’s own agent package is a fair example of the standard: LocalOffice_Agent.exe /silent — one tested, documented switch.
In the console, create the software package and declare what is true: the silent command you actually tested, whether the application installs for the system or the user, and what counts as success (the executable or registry entry that should exist afterwards). If the installer needs the user logged out, or a reboot to finish, configure that behaviour in the deployment instead of letting two hundred users discover it mid-morning.
Aim the first deployment at your pilot computers only. Confirm the package installs, the application opens, and the status in the console reports success for the reason you expect. Only then widen the target — department by department, exactly like patch rings. The console’s per-machine status is your evidence; a deployment you cannot verify is a rumour, not a rollout.
Some installers genuinely have no silent mode. Say so early and choose honestly: wrap the install in a pre-deployment script only if you understand it fully, deploy that application manually or through a scheduled attended window, or pick the vendor’s enterprise installer, which usually exists precisely for this reason. Forcing an interactive installer into an unattended deployment does not make it silent — it makes two hundred PCs wait for a click that will never come.
Every setting on this page is shown live in the ManageEngine configuration video — watch it once and your own setup becomes easy.
▶️ Watch Full VideoThe most common cause is an installer that is not actually silent: it has opened a prompt on each target PC and is waiting. Test the exact install command manually on one machine — if a window appears, the silent switch is wrong or the installer does not support silent installation.
There is no universal answer. Common ones are /silent, /S and /quiet, and MSI packages use msiexec /i with /qn. The only reliable method is to check the vendor’s documentation and then test the command yourself before deploying.
You can, and you should not. Deploy to a pilot group first, verify real success on those machines, then widen in stages. A package problem found on five PCs is a fix; found on two hundred, it is an incident.