Enterprise Wake-On-LAN Infrastructure

Unified Power Management across VLANs, Subnets, and the Internet. No hardware reconfiguration required.

VLAN Routing Native SCCM Integration Zero-Touch Client Config

Flexible
Triggering

Instant WOL
  • One-click from ASDM Console
  • One-click from SCCM Console
  • Command Line Interface (CLI)
  • UPS - On return to AC power

Cross-Network
Routing

WOL across Remote Locations
SCCM Integration
  • Sync Deployments schedules
  • Sync Update schedules
  • Sync Package schedules
  • Learn more ->

Advanced
Scenarios

Reliability
*) For detailed technical specifications, please download the Technical Manual.

Supported Infrastructure & Topology

Auto Shutdown Manager abstracts network complexity, allowing you to treat segmented, multi-VLAN networks as a single flat entity for power management.

Enterprise Wake On LAN Architecture Diagram

Solving the "WOL across Subnets" Challenge

The Scenario

You need to wake clients on a remote subnet (e.g., 192.168.20.0/24) while your server resides on 192.168.10.100. Standard broadcasts are blocked by routers.

Method 1: The WOL Proxy (Recommended)

Zero Router Config. 100% Reliable. Designate any existing PC, Server, or Raspberry Pi in the target subnet to act as a relay.

  1. Select a Proxy: Install the client agent on any device in the target subnet.
  2. Configure: In the console, assign that device as the WOL Proxy for 192.168.20.xxx.
  3. Done: The server sends unicast TCP to the proxy; the proxy broadcasts locally.

* The WOL Proxy Generator can automatically detect and assign proxies as your topology changes.

Configuring a Raspberry Pi as a WOL Proxy
VLAN Strategy: You do not need a physical proxy in every subnet. A single Virtual Machine acting as a WOL Proxy can handle your entire infrastructure. Simply configure the VM with multiple virtual network interfaces (vNICs) connected to your various VLANs (Switch connection via Trunk-Port).

Method 2: Directed Broadcasts (Static ARP)

If your security policy permits, you can configure routers to forward specific UDP packets. Below is an example for an Ubiquiti EdgeRouter.

admin@router:~$ configure
admin@router:~$ set protocols static arp 192.168.20.254 hwaddr FF:FF:FF:FF:FF:FF
admin@router:~$ commit
admin@router:~$ save

Next, configure the firewall rules to forward UDP port 7 or 9 to this static IP:

Firewall Configuration

Final Step: Server Configuration

Once the router is configured, you must instruct the Auto Shutdown Manager Server to use this specific broadcast address for the target subnet.

Tip: For multiple clients, select all of them, right-click, and choose "Edit Remote WOL Address" and "Edit Remote WOL Port" to configure them in bulk.

Ensuring 100% WOL Success Rates

The Admin's Nightmare: Windows 10/11 Fast Startup and outdated drivers often disable the NIC during shutdown, making WOL impossible regardless of the server setup.

Auto Shutdown Manager solves the "Client Side" problem automatically. Simply enable "Fix WOL on Clients" in your global Policy Group Settings. The client agent will automatically:

  • Disable Windows "Fast Startup" (which blocks WOL).
  • Configure the NIC to allow "Wake on Magic Packet".
  • Ensure the NIC does not power down in S5 state.
Auto Fix WOL Settings checkbox in policy manager

* For very old hardware, BIOS configuration may still be required.

Ready to simplify your network power management?

Join thousands of admins who trust Auto Shutdown Manager for reliable enterprise Wake-on-LAN.