To support wake-up proxy, at least three computers must be awake for each subnet. Computers that don't respond will no longer be assumed to be asleep and will not be woken up by wake-up proxy. The computers that are awake become manager computer for the subnet.īecause 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. If there's no response from other computers, they're assumed to be asleep. They do this check by sending each other a TCP/IP ping command every five seconds. When the site is configured for Wake On LAN and clients are configured for wake-up proxy, the process works as follows:Ĭomputers with the Configuration Manager client installed and that aren't asleep on the subnet check whether other computers on the subnet are awake. 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. You can supplement the traditional wake-up packet method by using the wake-up proxy client settings. How to wake up clients in Configuration ManagerĬonfiguration 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. 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. Both versions of Wake on LAN can, and in many cases will, be enabled simultaneously. This functionality still exists in Configuration Manager version 1810, which also includes a newer version of Wake on LAN too. This article describes how an older version of Wake on LAN functions.
0 kommentar(er)
