Enable Wake on LAN in Windows

The title Enable Wake on LAN in Windows is a bit generic on purpose as this article is targeting any system. Specifically, the screenshots are take from a DELL Optiplex Micro 3040 system, but applies to any other vendor as well (screenshots will differ). The reason why I’m specifically writing this article is because I struggled a bit more than usual with a Micro 3040 model running Windows 10 and I had the 3020 working with no issues. Again, these steps apply to any system running Windows!

Also note that normally, you do not have to set all of the below up (like Firewall etc).

Let’s go in steps, starting with the basics BIOS settings.

  • Make sure the BIOS is up to date.
  • Go in the BIOS by starting the computer up and by pressing F2.
  • On a DELL system, go to Power Management and Disable Deep Sleep Control. If you’re not configuring a DELL, find the option (if it exists) to prevent the system from fully shutting down or hibernating.
    • dell_optiplex_3040_wake_on_lan_disable_deep_sleep
  • Enable Wake on Lan (or Wan or both).
    • dell_optiplex_3040_wake_on_lan_enabled

In order to fully Enable Wake on Lan in Windows, there are a few settings to be changed at the OS level. This process covers Windows 10’s settings, if you’re on Windows 7 or earlier, you may need to skip a setting or two as not present in these versions of Windows.

  • Upgrade the network interface card (NIC) drivers to the latest available.
  • Open the Network Card’s hardware settings and, under Adavanced:
    • Make sure Speed&Duplex is set to Auto Negotiation.
      • nic_advanced_speedAndDuplex_auto-negotiation
    • Enable Wake on Magic Packet.
      • nic_advanced_wakeonlan_wake-on-magic-packet-enabled
  • Go to the NIC’s Power Management tab and select Allow this device to wake the computer.
    • nic_power-management_allow-this-device-to-wake-the-computer
  • In Windows 10, go to the Power Options under Control Panel.
    • On the left hand of the window, click Choose what the power buttons do.
      • power-options_choose-what-the-power-buttons-do
    • Disable the option Turn on fast startup (recommended).
      • power-options_turn-on-fast-startup_disabled
      • Note that this option might get reset after running Windows Update. I have not encountered this problem myself yet.
  • Go to Control Panel > Windows FirewallAdvanced Settings.
    • windows-firewall_advanced-settings
    • Right click on Inbound Rules and select New Rule.
      • windows-firewall_new-rule
    • In the New Rule Wizard, select Port and click Next.
      • windows-firewall_new-rule_port
    • Under Protocol and Ports, select UDP and Specific local ports and type 9.
      • windows-firewall_new-rule_UDP_Port-9
    • See the screenshots for the rest of the steps:
      • windows-firewall_new-rule_Action
      • windows-firewall_new-rule_Profile
      • windows-firewall_new-rule_Name

This should be enough for you to get Wake On Lan configured on the machine you want.

Read More

Add Windows 10 key to existing Windows Server 2008 R2 KMS

Adding a Windows 10 key to an existing Windows Server 2008 R2 KMS should be easy enough but for some reason I found a lot of users on forum having issues with this. There was also a lot of bad information which I think are related to the fact that Microsoft didn’t include old KMS servers from the start of Windows 10’s era. This article has been written on the 1st of November 2016 and at today the steps to add a Windows 10 key to an existing Windows Server 2008 R2 KMS are just a few.

A few notes before proceeding:

  • You will have to follow these steps on all of your KMS servers.
  • slmgr has to be ran from system32 (%windir%\system32).
  • I suggest to run slmgr.vbs /dlv and take a screenshot of the info you see on screen before and after the procedure.
  • slmgr.vbs takes a few seconds before completing.

The procedure

  1. On the KMS server, check if KB3079821 is installed. If not installed it, downloading from the following link: https://support.microsoft.com/en-us/kb/3079821 . A reboot is required.
    • Repeat this operation on all of your KMS Servers.
  2. Now you need to grab the correct key: in fact you will have to get the key called Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 from the Microsoft Volume Licensing Service Center. In order to get that product key, follow the steps below:
    • Log on to the Volume Licensing Service Center (VLSC).
    • Click License.
    • Click Relationship Summary.
    • Click on the License ID of the Active License you own.
    • Finally locate Windows Srv 2012R2 DataCtr/Std KMS for Windows 10‘s key.
  3. We’re ready to install this key by running the following in an elevated command prompt of the KMS Server:

    Needless to say: replace MYKEY-MYKEY-MYKEY-MYKEY with the key you’ve got from Step 2.
  4. You will receive a message that the key has been successfully installed. You will also note that Windows, on the KMS server(s) is no longer activated. Don’t worry, you will just need to run:


Test that everything is working as expected

You may test that the newly added key is working fine by installing Windows 10 VL to a new machine or by Migrating an existing Windows MAK key to KMS.

Read More