![]() ![]() In Part 2, I get into the details on the BIOS/UEFI specific settings for current model HP desktops and in Part 3, I cover the BIOS/UEFI specific settings for current model Dell desktops. If you run into any other blockers, feel free to list them in the comments below. Test first to see if it works and if it does not, then you might need to work with your 802.1x team. Something else that may or may not block WoL (again – depending on how it is configured), is 802.1x. If you have an out dated pre-boot authentication mechanism in place (legacy 3rd party disk encryption products use ‘cached’ credentials as a method of ‘unlocking’ the disk so that it can boot into Windows), then this will likely prevent a successful WoL, as the system will never boot up to Windows. Lastly, there are some other considerations to account for that may impact the ability to perform a successful WoL. There could be other settings that might conflict with WoL success but in testing with the latest set of drivers I did not experience any issues (even though Energy Efficient Ethernet and Ultra Low Power Mode were set to Enabled). Out of the box Windows drivers may or may not have this setting at all and therefore, I do not recommend using the out of the box Windows drivers for the network card. If you are using the manufacturer’s NIC card driver, then most of the time the Wake on Magic Packet setting will be Enabled by default. In addition to these NIC card settings, there are a few other settings that need to be enabled. On the Power Management tab of the network adapter card properties, you will now see all three check boxes enabled for clients that have this policy applied: This setting will automatically configure one of the NIC card settings that need to be enabled (that we previously had to script). In my test lab, I have the following options configured: Be sure to enable both Wake on LAN starting in version 1810 and Wake on LAN for version 1806 and earlier for best results (see How to configure Wake on LAN in Configuration Manager). ![]() New in Current Branch 2002 is the ability to wake up machines from the CAS (if you are unfortunate to have a CAS, which you can now remove in 2002). This last iteration works amazingly well and has eliminated the need for any 3rd party wake-on-lan solutions (thankfully!). The Microsoft MEMCM Team has finally gotten WoL right. I will be using this registry setting (HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberBootEnabled=0) and CI in my subsequent WoL blog posts.ĬM Client Settings
0 Comments
Leave a Reply. |