User Guide
OneSite Wake (formerly Green planet) provides peer-to-peer Wake on LAN (WoL), Load Leveling and Service Window functionality for Configuration Manager (ConfigMgr). The Load Leveling features dramatically reduce peak load on your ConfigMgr Servers and your network infrastructure, while the Service Windows allow you to perform potentially disruptive operations such as patch deployments and software installations outside of normal business hours.
Integration with ConfigMgr's Software Deployment configuration ensures that clients are automatically powered on exactly when they are assigned to perform a ConfigMgr operation, such as inventory, software distribution, or software updates.
Instant client actions allow you to remotely perform policy polling, inventory collection, and other ConfigMgr tasks using simple point and click. Integration with Wake on LAN means that the target clients will automatically power up, perform the specified actions, and go back to sleep after performing necessary actions.
Configuring Global Wake On LAN Settings
Start in the Global Wake on LAN settings Workbench folder, and edit the Global Wake on LAN Settings.
The most important consideration here is to enable Last Machine on Subnet and set to at least, however, two or more is recommended for redundancy. Timing Settings should be kept as their default values. Additionally, you can customize the Wake On LAN Workflow and can be set here.

Within the Global Wake on LAN Settings pane, you also have settings for each type of ConfigMgr content, where you can apply different configurations based on the content type in ConfigMgr.

Select one or more of these settings to configure how to leverage WOL for each type of content. Each setting will have the following options:

Check Use Wake on LAN Setting in ConfigMgr Deployment to enable Wake On LAN for the deployment. This allows OneSite Wake to handle the WOL function when you select to use WOL in a ConfigMgr deployment.
Note that if Enable Wake On LAN is checked first, it will become greyed out once the deployment setting is selected.
Choose your WOL methods. You can chose more than one.
Use P2P Wake On Lan Magic Packets is required if you want to utilize peers sending magic packs to perform the WOL.
Use Subnet Directed Broadcast Magic Packets is recommended, as this will direct a peer on the last known subnet for the device to broadcast the magic packs to wake the device(s).
Use Unicast Magic Packets is recommended if there are vLANs in an environment, where broadcast messaging is not allowed.
Wake on Schedule is a great option, as this option does not have a reliance on WOL magic packs from another device. Of note though, this option only works if a machine is in sleep or hibernate mode, where if the machine has received a policy before going down, so our client can create the wake schedule with the chip set.
Wake on Schedule can be configured for non-laptop and or laptop machines. However, many customers do not wish to utilize this option for laptops, due to concerns of a laptop being in a computer bag, or a confined environment, where over heating could be an issue.
Configure Service Windows
If you want to use service windows, these can be created in the Service Window Profile Explorer.

Click on Service Windows
Select the green plus button to create a new service window.
Launch the Service Window Constraints.

Define the allowed time slots, days of the week, as well as load leveling and override duration settings.
Configure Instant or Scheduled Wake on LAN for ConfigMgr client actions
In the Workbench, you can also setup an instant WOL job for a specific machine or ConfigMgr collection, and scheduled WOL jobs targeting a ConfigMgr collection.
These instant WOL policies have the same options available for wake methods as for the ConfigMgr deployments. Of note, wake on schedule will only work for scheduled policies, and not instant policies.

These jobs can be set to wake up computers to run the following actions, and can be targeted to specific collections using the Add Collection button as shown below.

When in the Instant Wake On Lan For Machine pane, you can filter for a machine name in the Machine Explorer, and drag and drop machines into the policy form under the ClientID field.

Last updated
Was this helpful?