![]() The Configuration Item contains a few scripts and registry values, disables Energy Efficient Ethernet on the network card, disables Windows 10 Fast Startup, enables Wake-On-LAN settings on the card, and adjusts the default two minute timer for when machines go back to sleep after being waken. The built-in ConfigMgr client setting to configure a network card for Wake-On-LAN. ![]() Note: There is a built-in client setting that configures two of the settings I have in my Configuration Item, two of the Wake-On-LAN settings on the network card, but since I want to have more settings anyway, I put them all in a single Configuration Item. And as mentioned earlier I use a ConfigMgr Configuration Item/Baseline for that. Once the BIOS configuration is in place, it's time to make sure Windows is configure for Wake-on-LAN. ![]() The Enable DELL WOL Setting Task Sequence. Note: If you are not using BitLocker (you should, but still), disable the first action in the task sequence. The task sequence I used for this guide is available for download here (but without the DELL Command Configure package): EnableWOLonDellMachines.zip. Once the package is created, you can create a task sequence that runs the script, and then calls the vendor tool to do the configuration. My DELL Command Configure package source. I also added Maurice script to the root folder. In my environment I put cctk.exe version 4.1.0.0 in the root, and cctk.exe version 3.3.0.0 in the Legacy folder. Next step is to download the two cctk.exe versions, put them in a folder, and then create a ConfigMgr package with that folder as a data source. Luckily good friend Maurice Daly has written one of those: This script runs the cctk.exe tool without any parameters, depending on exit code, the script sets a ConfigMgr task sequence variable, DellNewCCTKCmds to either true or false, and then sets another variable, DellCCTKPath, to call the correct version of the tool. So the first thing you need is a script that figures out what cctk.exe version you need. Now, in a perfect world, the latest cctk.exe should work with all DELL models, but of course it doesn't. To configure BIOS unattended I use the DELL cctk.exe tool. When writing this guide, I used a few Dell Optiplex machines, but the steps works on most of DELL's business models. For local-subnet-based wake-up scenarios, this configuration is no longer needed. Note #3: The new option for waking up machines via client notification (fast channel) usually does not require enabling Wake-on-LAN on the ConfigMgr site level, it's only really needed for the wake-up proxy feature that you can enable via client settings. Anyway, I added that setting to my Configuration Item / Configuration Baseline as well. That timeout is easy to change, but still, it's a rather not-that-bright default timeout IMNSHO. That's been the default behavior since Windows Vista, and is usually not what you want. Note #2: When you wake up a machine via Wake-On-LAN, don't be surprised when it goes back to sleep again after being idle for two minutes. More info about these changes in Microsoft KB 2776718: "Wake on LAN"(WOL) behavior in Windows 8, Windows 8.1 and Windows 10. Even with tricks such as setting AllowWakeFromS5 under NDIS settings in the registry, waking up from Shutdown rarely works in Windows 10. Note #1: Due to changes in Windows 10 (and Windows 8.x), most hardware models does not support waking up from a Shutdown, only from sleep (and some hibernation scenarios). Thanks Michael for the heads up, I'll update the post as I learn more. The symptom is that it may soak the fast channel for hours . Update/Warning: I recently learned that there seem to be an issue with using the new WOL notification method when targeting collections with more than 150-200 active clients. You can even download the ones I was using □Ĭredits: Thanks to DarkMallard for the WOL script on TechNet Gallery, and to Maurice Daly for the Invoke-DellCCTKCheck.ps1 script. Anyway, in this guide you learn to use a task sequence for the BIOS configuration, and a Configuration Item / Configuration Baseline for the Windows Wake-On-LAN settings. I typically use a Task Sequence for most hardware (BIOS) configurations, and a Configuration Item / Configuration Baseline for the Windows 10 settings, but sure, a package that runs a script to set it will do just fine as well, or a Configuration Item that does everything. Good news, you can use ConfigMgr for that too. However, your hardware must be configured to allow it, and so does Windows 10. Since ConfigMgr 1810, there is a new, and much improved way to wake up machines on your network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |