LIMEHAWK - Managed IT
Wake-on-LAN Setup — automation
dateNov 28, 2024
statusRESOLVED
Incident

Law firm with 85 workstations needed to deploy critical security patches after hours. Scheduled maintenance window at 2 AM to avoid disrupting billable work. Morning report: only 34 machines patched. The rest were powered off or sleeping - RMM agent couldn't wake them.

The Challenge
Dell OptiPlex45 machines
HP EliteDesk28 machines
Lenovo ThinkCentre12 machines
WoL statusunknown/inconsistent

Wake-on-LAN requires both BIOS and Windows NIC configuration. Each manufacturer has different BIOS access methods. Manually configuring 85 machines would take days. Needed automated solution that handles Dell, HP, and Lenovo BIOS differences.

Solution

Unified WoL enablement script that detects manufacturer and applies appropriate BIOS settings via Dell BIOS Provider, HP CMSL, or Lenovo WMI. Also configures Windows NIC settings.

Manufacturer Handling
DellDellBIOSProvider PowerShell module
HPHP Client Management Script Library
LenovoWMI (Lenovo_SetBiosSetting)
Windows NICMSPower_DeviceWakeEnable WMI class

Script auto-detects manufacturer via Win32_ComputerSystem, installs required PowerShell modules if missing, configures BIOS WoL setting, and enables wake capability on all network adapters.

Outcome
machines configured85 of 85
next patch window100% reached
deployment time15 minutes (parallel)

Deployed via RMM to entire fleet. Rebooted machines to apply BIOS changes. Next maintenance window: RMM sent magic packets at 1:55 AM, all 85 machines woke up, patches installed, machines back to sleep by 4 AM. Zero user disruption.

WoL requires both BIOS and OS configuration
each manufacturer needs different approach
reboot required after BIOS changes
enables true after-hours maintenance without user impact
Get Help

Need after-hours maintenance without disrupting users? We configure Wake-on-LAN and automated patching across mixed-vendor fleets.