Make sure your BIOS supports Wake-on-LAN, and that this option has been enabled. (This step pertains to PC only; Mac users can ignore this.) 2. Configure your computer to be Wake-on-LAN ready. Please note that the term in BIOS might vary. For example, it might be 'Wake on LAN,' or 'Onboard LAN Boot ROM,' or something else.

Applies to: Configuration Manager (current branch)

Configuration Manager supports traditional wake-up packets to wake up computers in sleep mode when you want to install required software, such as software updates and applications.

Note

This article describes how an older version of Wake on LAN functions. This functionality still exists in Configuration Manager version 1810, which also includes a newer version of Wake on LAN too. Both versions of Wake on LAN can, and in many cases will, be enabled simultaneously. For more information about how the new version of Wake on LAN functions starting in 1810 and enabling either or both versions, see How to configure Wake on LAN.

How to wake up clients in Configuration Manager

Configuration Manager supports traditional wake-up packets to wake up computers in sleep mode when you want to install required software, such as software updates and applications.

You can supplement the traditional wake-up packet method by using the wake-up proxy client settings. Wake-up proxy uses a peer-to-peer protocol and elected computers to check whether other computers on the subnet are awake, and to wake them if necessary. When the site is configured for Wake On LAN and clients are configured for wake-up proxy, the process works as follows:

1. Computers with the Configuration Manager client installed and that aren't asleep on the subnet check whether other computers on the subnet are awake. They do this check by sending each other a TCP/IP ping command every five seconds.

2. If there's no response from other computers, they're assumed to be asleep. The computers that are awake become manager computer for the subnet.

   Because it's possible that a computer might not respond because of a reason other than it's asleep (for example, it's turned off, removed from the network, or the proxy wake-up client setting is no longer applied), the computers are sent a wake-up packet every day at 2 P.M. local time. Computers that don't respond will no longer be assumed to be asleep and will not be woken up by wake-up proxy.

   To support wake-up proxy, at least three computers must be awake for each subnet. To achieve this requirement, three computers are non-deterministically chosen to be guardian computers for the subnet. This state means that they stay awake, despite any configured power policy to sleep or hibernate after a period of inactivity. Guardian computers honor shutdown or restart commands, for example, as a result of maintenance tasks. If this action happens, the remaining guardian computers wake up another computer on the subnet so that the subnet continues to have three guardian computers.

3. Manager computers ask the network switch to redirect network traffic for the sleeping computers to themselves.

   The redirection is achieved by the manager computer broadcasting an Ethernet frame that uses the sleeping computer's MAC address as the source address. This behavior makes the network switch behave as if the sleeping computer has moved to the same port that the manager computer is on. The manager computer also sends ARP packets for the sleeping computers to keep the entry fresh in the ARP cache. The manager computer also responds to ARP requests on behalf of the sleeping computer and replies with the MAC address of the sleeping computer.

   Warning

   During this process, the IP-to-MAC mapping for the sleeping computer remains the same. Wake-up proxy works by informing the network switch that a different network adapter is using the port that was registered by another network adapter. However, this behavior is known as a MAC flap and is unusual for standard network operation. Some network monitoring tools look for this behavior and can assume that something is wrong. Consequently, these monitoring tools can generate alerts or shut down ports when you use wake-up proxy.

   Do not use wake-up proxy if your network monitoring tools and services do not allow MAC flaps.

4. When a manager computer sees a new TCP connection request for a sleeping computer and the request is to a port that the sleeping computer was listening on before it went to sleep, the manager computer sends a wake-up packet to the sleeping computer, and then stops redirecting traffic for this computer.

5. The sleeping computer receives the wake-up packet and wakes up. The sending computer automatically retries the connection and this time, the computer is awake and can respond.

   Wake-up proxy has the following prerequisites and limitations:

Important

If you have a separate team that is responsible for the network infrastructure and network services, notify and include this team during your evaluation and testing period. For example, on a network that uses 802.1X network access control, wake-up proxy will not work and can disrupt the network service. In addition, wake-up proxy could cause some network monitoring tools to generate alerts when the tools detect the traffic to wake-up other computers.

• All Windows operating systems listed as supported clients in Supported operating systems for clients and devices are supported for Wake On LAN.

• Guest operating systems that run on a virtual machine are not supported.

• Clients must be enabled for wake-up proxy by using client settings. Although wake-up proxy operation does not depend on hardware inventory, clients do not report the installation of the wake-up proxy service unless they are enabled for hardware inventory and submitted at least one hardware inventory.

• Network adapters (and possibly the BIOS) must be enabled and configured for wake-up packets. If the network adapter is not configured for wake-up packets or this setting is disabled, Configuration Manager will automatically configure and enable it for a computer when it receives the client setting to enable wake-up proxy.

• If a computer has more than one network adapter, you cannot configure which adapter to use for wake-up proxy; the choice is non-deterministic. However, the adapter chosen is recorded in the SleepAgent_<DOMAIN>@SYSTEM_0.log file.

• The network must allow ICMP echo requests (at least within the subnet). You cannot configure the five-second interval that is used to send the ICMP ping commands.

• Communication is unencrypted and unauthenticated, and IPsec is not supported.

• The following network configurations are not supported:

  • 802.1X with port authentication

  • Wireless networks

  • Network switches that bind MAC addresses to specific ports

  • IPv6-only networks

  • DHCP lease durations less than 24 hours

If you want to wake up computers for scheduled software installation, you must configure each primary site to use wake-up packets.

To use wake-up proxy, you must deploy Power Management wake-up proxy client settings in addition to configuring the primary site.

Decide whether to use subnet-directed broadcast packets, or unicast packets, and what UDP port number to use. By default, traditional wake-up packets are transmitted by using UDP port 9, but to help increase security, you can select an alternative port for the site if this alternative port is supported by intervening routers and firewalls.

Can Microsoft Remote Desktop 10 Mac Wake On Lan Mac

Choose Between Unicast and Subnet-Directed Broadcast for Wake-on-LAN

If you chose to wake up computers by sending traditional wake-up packets, you must decide whether to transmit unicast packets or subnet-direct broadcast packets. If you use wake-up proxy, you must use unicast packets. Otherwise, use the following table to help you determine which transmission method to choose.

Warning

There are security risks associated with subnet-directed broadcasts: An attacker could send continuous streams of Internet Control Message Protocol (ICMP) echo requests from a falsified source address to the directed broadcast address, which cause all the hosts to reply to that source address. This type of denial of service attack is commonly called a smurf attack and is typically mitigated by not enabling subnet-directed broadcasts.

Applies to: Configuration Manager (current branch)

Specify Wake on LAN settings for Configuration Manager when you want to bring computers out of a sleep state.

Wake on LAN starting in version 1810

Starting in Configuration Manager 1810, there's a new way to wake up sleeping machines. You can wake up clients from the Configuration Manager console, even if the client isn't on the same subnet as the site server. If you need to do maintenance or query devices, you're not limited by remote clients that are asleep. The site server uses the client notification channel to identify other clients that are awake on the same remote subnet, then uses those clients to send a wake on LAN request (magic packet). Using the client notification channel helps avoid MAC flaps, which could cause the port to be shut down by the router. The new version of Wake on LAN can be enabled at the same time as the older version.

Limitations

• At least one client in the target subnet must be awake.
• This feature doesn't support the following network technologies:
  • IPv6
  • 802.1x network authentication

    Note

    802.1x network authentication may work with additional configuration depending on the hardware and its configuration.

• Machines only wake when you notify them through the Wake Up client notification.
  • For wake-up when a deadline occurs, the older version of Wake on LAN is used.
  • If the older version isn't enabled, client wake up won't occur for deployments created with the settings Use Wake-on-LAN to wake up clients for required deployments or Send wake-up packets.

Important

The Wake On LAN feature is recommended for use on only a limited amount of devices (100) at a time.

When you use the Wake On LAN feature to wake up machines from Configuration Manager admin console, the wake up requests are put in to an internal queue that's shared by other real-time action features. Examples of those other features are Run Scripts, CMPivot, and other fast-channel client notifications. Depending on the performance of your site systems, the wake up actions may take an extended amount of time and delay the other real-time action. It is suggested to not wake up more than 100 machines at a single time. To know if you are getting a backlog in this area that may cause delays, you can look in the ...inboxesobjmgr.box directory to see if there are a large number of files with .OPA extension.

Security role permissions

• Notify resource under the Collection category

Configure the clients to use Wake on LAN starting in version 1810

Previously you had to manually enable the client for wake on LAN in the properties of the network adapter. Configuration Manager 1810 includes a new client setting called Allow network wake-up. Configure and deploy this setting instead of modifying the properties of the network adapter.

1. Under Administration, go to Client Settings.

2. Select the client settings you want to edit, or create new custom client settings to deploy. For more information, see How to configure client settings.

3. Under the Power Management client settings, select Enable for the Allow network wake-up setting. For more information about this setting, see About client settings.

4. Starting in Configuration Manager 1902, the new version of Wake on LAN honors the custom UDP port you specify for the Wake On LAN port number (UDP)client setting. This setting is shared by both the new and older version of Wake on LAN.

Wake up a client using client notification starting in 1810

You can wake up a single client or any sleeping clients in a collection. For devices that are already awake in the collection, no action is taken for them. Only clients that are asleep will be sent a Wake on LAN request. For more information on how to notify a client to wake, see Client notification.

• To wake up a single client:Right-click on the client, go to Client Notification, then select Wake up.

• To wake up all sleeping clients in a collection: Right-click on the device collection, go to Client Notification, then select Wake up.

  • This action can't be run on built-in collections.
  • When you have a mix of asleep and awake clients in a collection, only the clients that are asleep are sent a Wake on LAN request.
  • Starting in Configuration Manager 2002, this action is available from a console connected to a Central Administration site, a stand-alone site, or child primary site.
  • In versions 1910 and earlier, this action is only active when the Configuration Manager console is connected to a stand-alone or child primary site. When connected to a Central Administration Site, the action is not available.

What to expect when only the new version of Wake on LAN is enabled

When you have only the new version of Wake on LAN enabled, only the Wake Up client notification is enabled. Clients aren't sent a notification when a deadline is received on deployments such as task sequences, software distribution, or software updates installation. Once a sleeping machine is back online, it will be reflected in the console when it checks in with the Management Point.

Starting in Configuration Manager version 1902, you can specify the Wake on LAN port. This setting is shared by both the new and older version of Wake on LAN.

What to expect when both versions of Wake on LAN are enabled

When you have both versions of Wake on LAN enabled, you can use the Wake Up client notification and wake up on deadline. The client notification functions a little differently than traditional Wake on LAN. For a brief explanation of how the client notification works, see the Wake on LAN starting in version 1810 section. The new client setting Allow network wake-up will change the NIC properties to allow Wake on LAN. You no longer need to manually change it for new machines that are added to your environment. All other functionality of Wake on LAN hasn't been changed.

Starting in version 1902, the Wake Up client notification honors your existing Wake On LAN port number (UDP) setting.

Wake on LAN for version 1806 and earlier

Specify Wake on LAN settings for Configuration Manager when you want to bring computers out of a sleep state to install required software, such as software updates, applications, task sequences, and programs.

You can supplement Wake on LAN by using the wake-up proxy client settings. However, to use wake-up proxy, you must first enable Wake on LAN for the site and specify Use wake-up packets only and the Unicast option for the Wake on LAN transmission method. This wake-up solution also supports ad-hoc connections, such as a remote desktop connection.

Use the first procedure to configure a primary site for Wake on LAN. Then, use the second procedure to configure the wake-up proxy client settings. This second procedure configures the default client settings for the wake-up proxy settings to apply to all computers in the hierarchy. If you want these settings to apply to only selected computers, create a custom device setting and assign it to a collection that contains the computers that you want to configure for wake-up proxy. For more information about how to create custom client settings, see How to configure client settings.

A computer that receives the wake-up proxy client settings will likely pause its network connection for 1-3 seconds. This occurs because the client must reset the network interface card to enable the wake-up proxy driver on it.

Warning

To avoid unexpected disruption to your network services, first evaluate wake-up proxy on an isolated and representative network infrastructure. Then use custom client settings to expand your test to a selected group of computers on several subnets. For more information about how wake-up proxy works, see Plan how to wake up clients.

To configure Wake on LAN for a site for version 1806 and earlier

To use Wake on LAN, you need to enable it for each site in a hierarchy.

1. In the Configuration Manager console, go to Administration > Site Configuration > Sites.
2. Click the primary site to configure, and then click Properties.
3. Click the Wake on LAN tab, and configure the options that you require for this site. To support wake-up proxy, make sure you select Use wake-up packets only and Unicast. For more information, see Plan how to wake up clients.
4. Click OK and repeat the procedure for all primary sites in the hierarchy.

To configure wake-up proxy client settings

Can Microsoft Remote Desktop 10 Mac Wake On Lan Free

1. In the Configuration Manager console, go to Administration > Client Settings.
2. Click Default Client Settings, and then click Properties.
3. Select Power Management and then choose Yes for Enable wake-up proxy.
4. Review and if necessary, configure the other wake-up proxy settings. For more information on these settings, see Power management settings.
5. Click OK to close the dialog box, and then click OK to close the Default Client Settings dialog box.

You can use the following Wake On LAN reports to monitor the installation and configuration of wake-up proxy:

Can Microsoft Remote Desktop 10 Mac Wake On Lan Password

• Wake-Up Proxy Deployment State Summary
• Wake-Up Proxy Deployment State Details

Can Microsoft Remote Desktop 10 Mac Wake On Lan Wifi

Tip

Can Microsoft Remote Desktop 10 Mac Wake On Lan Windows 7

To test whether wake-up proxy is working, test a connection to a sleeping computer. For example, connect to a shared folder on that computer, or try connecting to the computer using Remote Desktop. If you use Direct Access, check that the IPv6 prefixes work by trying the same tests for a sleeping computer that is currently on the Internet.