Technical Anshu
Tutorials Blog
🏢 Office Deployment

Deploy Software to All Office PCs With ManageEngine Endpoint Central

Installing software desk by desk does not scale past about five PCs. A deployment package does it once, from your chair, with a report to prove it.

✍️ Technical Anshu🪟 Windows⏱️ 8 minute read
🎥 Watch all three methods side by side in the full video

ManageEngine Endpoint Central turns an installer file into a package, and a package into a configuration aimed at the computers you choose. The agent on each PC does the actual work. This guide covers the package-creation basics - the part people get wrong is almost always the silent command, because a package that pops up a setup window on forty screens is not automation. Get that right once and the same package serves every future PC.

Endpoint Central - Software Deployment Status (example)
ACCOUNTS-PC03Executed - installed successfully
ACCOUNTS-PC07Executed - installed successfully
LAB-PC02Yet to deploy - agent offline
RECEPTION-PCFailed - installer returned exit code 1603

Example statuses. The per-computer report is the whole point - you always know which desk still needs a visit.

Deployment is only finished when the report says so - per PC, not per hope
1

Prepare the Installer and Its Silent Command First

  1. Download the app's official MSI or EXE and keep it in a tidy packages folder on the server
  2. Find its silent command before touching the console - for MSI that is typically msiexec /i app.msi /quiet /norestart; EXE switches vary by maker (there is a full guide to silent switches in this series)
  3. Test the silent command by hand on one spare PC. If it shows a window there, it will show windows everywhere
2

Create the Package

  1. In the console, open Software Deployment → Packages → Add Package and choose Windows
  2. Pick MSI or EXE format, name the package clearly (app name plus version), and upload the installer - or choose from Endpoint Central's built-in template library, which already knows the silent switches for common apps
  3. Enter the install and uninstall commands exactly as tested, and add any licence or configuration files the app needs beside the installer
  4. Save. The package is now reusable forever - versions change, the routine does not
3

Create the Configuration and Choose Targets

  1. Create a deployment configuration from your package and select the target computers, groups or the whole domain
  2. Set Install as System User so the install runs with full rights even when nobody is logged in - this one option removes most permission failures
  3. Add pre-deployment checks if you need them (enough free disk space, a specific OS) and a post-deployment message or reboot only if the app truly needs one
  4. Schedule it - deploy now, deploy at next logon, or deploy in tonight's window so nobody watches installers during work hours
4

Deploy to a Pilot Group, Then Everyone ⭐

  1. First deploy to two or three friendly PCs and read the execution report
  2. Exit code 0 (or the app's own success code) plus the app present in the console's software inventory means the package is proven
  3. Then widen the same configuration to all targets. Machines that were off simply receive it when their agent next checks in
  4. Chase only the failures the report names - an offline laptop is a scheduling fact, while exit code 1603 means your package needs a fix on the server, not forty desk visits
⚠️ Honest requirements: every target PC needs the Endpoint Central agent installed and reaching the server, and the free edition covers 25 endpoints with one technician. Deployment also only ever installs what you packaged - a wrong silent command fails identically on every machine, which is why the pilot group step is not optional.

🎥 Watch the Full Comparison

The video shows a complete package being created and pushed, including where the silent command goes and how the report reads.

▶️ Watch Full Video
❓ Frequently Asked Questions

Do target PCs need to be switched on at the scheduled time?

No. If a PC is off or its agent is offline, the deployment stays pending for that machine and runs when the agent next contacts the server. The report shows it as yet to deploy until then.

Can Endpoint Central deploy our own in-house application?

Yes - that is one of its main advantages over Ninite and winget. Any MSI or EXE with a working silent command can become a package, including your own line-of-business software.

What does exit code 1603 mean in the report?

It is the Windows Installer generic fatal error. Common causes are a leftover broken previous installation, missing prerequisites or a command that was not truly silent. Fix it on one PC by hand first, correct the package, then redeploy.

This guide is based on the Technical Anshu video on automatic software installation • Stuck on a step? Ask in the video comments and you will get a reply 🙏