Deploy SEP Agent to Multiple Devices From the Manager
Installing an antivirus one PC at a time works for five computers, not for fifty. Symantec Endpoint Protection is built for the second case: one manager console, one install package, and a wizard that pushes the agent to every machine on your network. This guide walks the rollout in the right order — package first, then the push, then the checking — so you finish with every PC protected and reporting in, not with a list of silent failures.
✍️ Technical Anshu🖥️ SEPM Console⏱️ One rollout, every PC
🎥 Watch the full deployment in the video — SEPM console, wizard and push, step by step
SEP is managed from one place: the Symantec Endpoint Protection Manager (SEPM). You build a client install package once, and the Client Deployment Wizard copies it to the computers you choose and starts the installation automatically. One honest note before we begin: Symantec's enterprise security business is owned by Broadcom now, so licences and downloads come through Broadcom channels — the console and the deployment flow are the same ones your video shows. Work through the steps in order; most failed rollouts fail in the preparation, not in the push.
Computer Result
OFFICE-PC01 Package copied, installation startedOFFICE-PC02 Package copied, installation started
ACCOUNTS-PC04 Copied, restart pending
LAB-PC03 Package copied, installation started
The wizard reports each computer separately. A copied package is only step one — the client still has to install, restart once and check in with the manager. (Illustrative panel.)
1
Build or Pick the Install Package First
The wizard can use an existing install package or create a new one on the spot. For a rollout, decide these four things before you touch the wizard — changing them afterwards means pushing again:
Client version and feature set — start with the standard protection feature set for office PCs; extra features can be added later by policy.
The client group — pushed PCs land in the group you choose, and the group carries their policies. Decide the group first, not after the push.
Install settings — including whether existing third-party security software should be removed during the install. That switch lives here, not in the wizard's later screens.
Content options — include the current definitions in the package, so a freshly installed client is not running on empty until its first update.
2
Start the Client Deployment Wizard
Everything happens inside the SEPM console. This is the exact route the video uses:
Log in to the Symantec Endpoint Protection Manager console.
On the Home page, open the Common Tasks menu and select Install protection client to computers — the Client Deployment Wizard starts.
Choose the install package you prepared (or create a new one here) and click Next.
Choose Remote Push as the deployment method and click Next.
Find the target computers: Browse Network to pick them from the network list, or Search Network and search by IP address or computer name. Add each one to the list with the >> button.
3
Authenticate With an Admin Account and Send
Remote Push installs software on somebody else's machine, so Windows rightly treats it as an administrator's job. When the wizard asks for credentials:
On domain computers, use a domain administrator account — the push requires elevated privileges.
On workgroup PCs, use an administrator account that exists on those target PCs.
Click Next, then Send. The wizard copies the package to each computer and the Deployment Summary shows the result machine by machine.
Installation now starts by itself on the clients and takes several minutes per computer. Click Next and Finish when the summary is done.
4
Let the PCs Restart and Check the Clients Page
Do not judge the rollout the moment the copy finishes. A brand-new client commonly does not appear in the manager until its PC has restarted once, so:
Let each PC restart (the install may restart it, or the user restarts at the end of the day).
Open the Clients page in SEPM and look inside the group you pushed to.
Every computer should appear there and report an online status — that is a finished deployment.
A PC that is still missing after a restart and a reasonable wait has a specific cause. Do not just push again; work the causes in order using the failure guide in this set.
🔴 Honest limit: Remote Push can only install on a PC that is switched on, reachable on the network, and where your account has admin rights. A machine that is off, on another network, or guarded by another antivirus's uninstall password will fail — that is expected, and the right fix is different for each cause.
🎥 Watch the Full Video
See the complete SEP agent deployment on screen — every wizard screen and the result in the console.
Once you click Send, copying the package and starting the install usually takes a few minutes per computer. The client becomes fully visible in the manager only after the PC restarts and checks in, so judge the rollout after a restart, not the moment the copy finishes.
Which account should I use for Remote Push?
An account with administrator rights on the target computers — on a domain, a domain administrator account. Remote Push installs software on another machine, so a normal user account will be refused and the deployment will fail.
A few PCs never appeared in the console. What should I do?
First restart those PCs and wait — new clients commonly appear only after a reboot. If a PC is still missing, work through the causes in order: the machine is off or unreachable, the credentials had no admin rights, the target firewall blocked the push, or the client installed but cannot reach the manager.
This guide is based on the Technical Anshu video on deploying the SEP agent • Stuck on a step? Ask in the video comments 🙏