Schedule Software Deployment After Office Hours with Wake on LAN Reality Check
The best deployment is the one nobody notices. Scheduling installs for the evening keeps users working — but a schedule only works on machines that are awake, plugged in and listening, and Wake on LAN has honest limits.
✍️ Technical Anshu🏢 Office IT⏱️ 7 minute read
🎥 See a deployment window and schedule being set in the video
Daytime deployments compete with users for CPU, disk and patience. Endpoint Central's deployment policy and schedule let you copy the package down during the day and install it in an evening window, or run the whole job overnight. The catch is physical: software cannot install on a machine that is off, asleep, or at an employee's home with the lid closed. Here is how to schedule honestly around that reality.
console — deployment policy, evening window
Copy filesAny time (background, resumable)
Install window19:00 — 23:00
Wake on LANEnabled — wired desktops only
Retry failed targets2 times
Next morning report47 of 50 done — 3 laptops pending
A realistic overnight result. The three pending machines are not a failure of the schedule — they were never on the network.
1
Split the Job — Copy Early, Install Late
A deployment has two halves with very different costs. Copying the installer to the PC is quiet background work — and if the connection drops, the download resumes instead of starting over. Installing is the disruptive half: CPU spikes, possible reboots, an app that cannot be used while it upgrades.
Let the package copy to targets during the day
Set the deployment window for the evening, when installs cannot interrupt anyone's work
Keep the window generous — four hours absorbs slow PCs and one retry round
2
Wake on LAN — What It Can and Cannot Do
Wake on LAN (WoL) sends a magic packet that powers on a PC whose network card is listening. When it works, it is wonderful. Be honest about its conditions:
The PC must be wired — most Wi-Fi adapters cannot receive the wake packet while asleep
WoL must be enabled in the PC's BIOS and in the network adapter settings, and the machine needs mains power
It wakes machines that are shut down or sleeping on your LAN; it does nothing for a laptop in a bag at someone's home
Test WoL on five machines before promising an overnight rollout to fifty
3
Design the Schedule Around Real Office Life
Pick a night with a quiet next morning — not the night before the monthly closing or a client audit
Avoid the same window as your patch deployments and backups; three heavy jobs at 8 PM help nobody
Leave laptops and remote workers a daytime path too — a second configuration with a user notification for when they next connect
If your policy supports it, set the configuration to expire after a few days so a forgotten test deployment never fires next month
4
The Morning After Is Part of the Schedule
An overnight deployment is not finished when you go home — it is finished when you read the report with your first tea. Check the execution status, list the machines still pending or failed, and tell the office what changed before the tickets tell you. The pattern you will see most: every wired desktop done, a handful of laptops pending. That is the schedule working exactly as physics allows.
5
When After Hours Is the Wrong Choice
Some deployments should happen while you watch: the first pilot ring, anything that touches the finance team's closing week, and any package whose installer you have not yet seen behave. Scheduling is a multiplier — it multiplies smooth rollouts and messy ones with equal enthusiasm. Earn the overnight window with a boring daytime pilot first.
🌙 Honest expectation to set with your boss: an after-hours deployment typically lands every switched-on wired PC in one night, and the laptop fleet over the following days as machines come and go. Plan the report, and the follow-up, for exactly that shape — not for a fantasy 100 percent by morning.
🎥 Watch the Full Deployment in the Video
Watch scheduling and deployment policies being configured in the full video.
Will Endpoint Central wake PCs that are fully shut down?
Only if Wake on LAN is enabled in the BIOS and the network adapter, the PC is wired and has power. It is a hardware feature the console can request, not a guarantee. Desktops usually cooperate; Wi-Fi laptops asleep at home do not.
What happens to PCs that miss the window?
With retry on failed targets and an active policy, they pick the configuration up at the next opportunity — the status waits at Ready to Execute until the agent checks in. Check the morning report and chase only the genuinely stuck ones.
Should I deploy at night or during lunch?
Night windows suit big or reboot-heavy packages. Lunch windows suit small, quick tools in offices where PCs are shut down every evening. Match the window to when your machines are actually on and idle.
This guide is based on the Technical Anshu video on remote software deployment with ManageEngine Endpoint Central • Stuck on a step? Ask in the video comments and you will get a reply 🙏