When WOL is used to install software updates during non business hours, it would be great if there is an option to shutdown computers which were woke up by WOL only post installation of software updates/application, so this will avoid using third part software's to initiate shutdown.

Would like Config Manager to ignore a bad battery if the device is running on Power Supply. Today a lot of things stop working with Config Manager if the device has a bad battery, logfiles says Battery Critical=TRUE

The client notification WoL feature neatly avoids the MAC spoofing and broadcast limitations of the site-based WoL capabilities of ConfigMgr, but it is only available as a client action.

If we could schedule a deployment and have an option to initiate a client notification for WoL when the deployment time arrived, this would be a very elegant way to get WoL functionality in environments where the network team do not support any of the other approaches.

SCCM should change the Wake-Up proxy functionality so that it doesn't cause MAC flapping. IBM BigFix and IE are able to use WOL forwarders which are very reliable, and they don't cause issues on networks that use Port Security. The Wake-Up proxy idea is great, but in practice it falls short because many large networks just can't use it. It's incredibly important to have a reliable WOL tool, and Microsoft really needs to step their game up in this aspect.

With ConfigMgr you have an option to wake up desktop computers on a specific time. The similar option is needed for laptops. This is especially important in school environment where student laptop are in carts. Student take a laptop from a cart and return it after the class. The problem is that you cannot update those devices when they are in the cart, because they are laptops. Please add an option (that is not selected by default) to allow wake up also laptops.

Include in SCCM's power management options the ability to set processor performance. I am currently doing power management through SCCM and I needed to use the GPO to set this configuration.

Allow SCCM to restore previous user power profile after changing power management of a collection for a deployment - Currently the number of power management options available on collections are limited to what SCCM displays but there are more options available to clients, either expand what is available in SCCM or make it possible to add new power options using the guids for those options.

WOL does not run on repeating deployments with WOL enabled deployment Task.

At the end of a shift, users often shut the lid on their devices, and head home. If the device has a pending reboot, it will often get rebooted very shortly after coming out of sleep/hibernate.

When devices with a pending reboot from a deployment are coming out of sleep or hibernate, allow a one-time grace period of 1-4 hours, so that they are not immediately rebooted at the beginning of their work hours.

For example: Add Balanced Power, High Power, Battery Saver as a install inside Software Center.

Add options to control power management by days of the week.

For example our organizations peek hours would be between 7am and 5pm M-F, it would be great to put all the PC's in a power saving mode all day Sat. and Sun.

WOL should be a basic function in SCCM. You should have the ability to select a single device as well as multiple devices or collections to Wake a system to perform some task like software installation, image deployment, or even establishing a remote session. We are currently evaluating SCCM 1806 and find it discouraging that WOL abilities are not there. Thank you for your consideration.

Add WakeOnLan option to the Collection Maintenance Windows to send out a WOL packet at the start of the Maintenance Window. There is a WOL option on the Power Management tab which works in most cases and there are other work-arounds but doesn't it make more sense to have a WOL option at the start of the MW?