Use NIC Configurator 2026 to create NIC Policy that secure's the Wake-On-LAN feature of Network Adapters. Review the demonstration videos on this page to learn how to centrally manage and monitor Wake-On-LAN with NIC Configurator 2026.

The primary risk is that malicious actors could potentially send "magic packets" to turn on computers, especially if they are on the same local network. 

Security Risks

Unauthorized Wake-up: If WoL is enabled and not secured, an attacker on the same network could send a "magic packet" to wake up a computer, potentially gaining access to it if other security measures are not in place. 

Bypassing Security: In some cases, WoL combined with PXE booting (Preboot Execution Environment) can allow attackers to boot a computer from an attacker-controlled image, bypassing the operating system's security. 

Malware Propagation: Malware can also use WoL to wake up other computers on the network to spread or encrypt offline devices. 

Security Considerations and Best Practices

Secure Networks: Enable WoL only on secure, trusted networks, and consider using VPNs or other secure connections to access the network remotely. 

Monitor WoL Activity: Keep track of WoL activity to detect and investigate any suspiciouswake-up requests. 

Disable When Not Needed: If WoL is not actively required, it's best to disable it to minimize the attack surface.

Conclusion

While WoL can be a valuable tool for remote management, it's crucial to implement appropriate security measures such as a monitoring and NIC policy to mitigate the risks associated with unauthorized access and potential malware propagation. 

The following 64-bit operating systems are supported:

Windows Server 2025, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 11, Windows 10.