Endpoint Central offers half a dozen ways to land its agent on a PC, and picking the wrong one costs real hours. Here is each method, honestly compared, with the network size and setup it actually suits.
New admins usually discover agent deployment methods in the order the console shows them, not in the order that fits their network. The result: someone pushes agents one by one to three hundred PCs, or builds a GPO for a five-PC office. This page lines up the real methods — console push install, GPO startup script, GPO scheduler, the lightweight GPO tool, manual install and imaging — and states plainly when each one wins, what it needs, and where it breaks.
Whichever method you choose, it delivers this same package. The methods differ only in how the package reaches the PC and who triggers it.
Every deployment method ships the same agent package. Choose by delivery, not by package.
A honest shortlist. The detailed trade-offs for each method are in the sections below.
In Admin → Scope of Management, select the computers and click Install Agent. The server reaches out to each PC and installs the agent for you. It needs ports 135 and 445 open on the clients and a credential with local admin rights on every target.
Best for: small networks, the free edition’s 25 endpoints, pilot groups, and one-off additions. Where it breaks: PCs that are switched off, laptops away from the office, and any client firewall that blocks the push — those machines simply stay unmanaged until you chase them.
Download the agent from the console (Agent → Deployment → Agent Installation → Using Active Directory → GPO tab), place the .msi and .mst files — plus DCAgentServerInfo.json on build 10.1.2124.1 and above — into the GPO startup folder at \\<Domain>\SysVol\<Domain>\Policies\{ID}\Machine\Scripts\Startup, and link the policy. The agent installs itself at next reboot, and the script safely skips PCs that already have it, so you can map it to the whole domain.
Best for: domain networks of any size with a steady rollout rhythm. Honest cost: installation waits for a reboot, so full coverage takes days, not minutes.
Instead of waiting for reboots, a scheduled task created through Group Policy Preferences runs the installer — LocalOffice_Agent.exe placed in a SYSVOL scripts folder — at a set time or at the next policy refresh. ManageEngine positions this as the fastest GPO method because agents land in the next refresh cycle rather than the next restart.
Best for: domain rollouts with a deadline. Watch out: the network share path and task permissions must be exactly right, or three hundred PCs all fail quietly at the same scheduled minute.
ManageEngine’s lightweight GPO tool exists for admins who find full GPO scripting heavy: it is described by the vendor as the simplest way to install the agent in an Active Directory network. Best for: small IT teams in a domain who want GPO reliability without hand-building scripts and transforms. If you already live comfortably in gpmc.msc, the startup script gives you more control; if you do not, start here.
Manual installation — running the downloaded agent package on the PC itself, silently with LocalOffice_Agent.exe /silent — is the right method for the odd machine: a VIP laptop, a PC that refuses every push, a remote user you are guiding on a call. For build teams, the agent can also be pre-installed in a golden image: install it on one machine, confirm it talks to the server, then image. ManageEngine supports this, with one warning — create separate images per network when proxy settings differ between networks.
Under roughly 25 machines or a workgroup: push install, manual for stragglers. Domain and no deadline: startup script. Domain with a deadline: scheduler. Domain and a small team: lightweight tool. Image-based provisioning: bake it in. And whichever you choose, deploy to a pilot OU first and check gpresult /h report.html on a test PC when a GPO method seems to do nothing — nine times out of ten the policy simply never applied.
Every setting on this page is shown live in the ManageEngine configuration video — watch it once and your own setup becomes easy.
▶️ Watch Full VideoFor a small workgroup or the free edition, push install from Admin → Scope of Management. In an Active Directory domain, ManageEngine’s lightweight GPO tool is the simplest route, while the GPO startup script is the most common one in larger networks.
Check whether the policy applied at all with gpresult /h on the client, confirm the agent files are in the correct SYSVOL startup folder, and remember the startup script method installs at reboot — a PC that has only slept for a week has never run it.
Yes. The downloaded executable supports a silent install with the /silent switch, which is also how imaging tools and deployment systems install it without user interaction.