Chris Warwick, @cjwarwickps, November 2015
Cmdlet to send a Wake-on-Lan packet to a specified target MAC addresses.
Wake on Lan (WOL) uses a "Magic Packet" that consists of six bytes of 0xFF (the physical layer broadcast address), followed by 16 copies of the 6-byte (48-bit) target MAC address (see http://en.wikipedia.org/wiki/Wake-on-LAN).
This packet is sent via UDP to the LAN Broadcast addresses (255.255.255.255) on arbitrary Port 4000.
Construction of this packet in PowerShell is very straight-forward: ("$Packet = Byte[]+($Mac*16)").
This script has a (hard-coded) table of saved MAC addresses to allow machine aliases to be specified as parameters to the function (the real addresses have been obfuscated here) and uses a regex to validate MAC address strings.
It would be possible to use DNS and the ARP Cache to resolve MAC addresses, however, the ARP cache will only be populated with a valid entry for any given target adapter for a relative short period of time after the last use of the address (10 minutes or less depending on usage); ARP cannot be used to dynamically resolve the address of a suspended adapter.
<#
.Synopsis
This cmdlet sends Wake-on-Lan Magic Packets to the specified Mac addresses.
.Description
Wake on Lan (WOL) uses a "Magic Packet" that consists of six bytes of 0xFF (the physical layer broadcast address), followed
by 16 copies of the 6-byte (48-bit) target MAC address (see http://en.wikipedia.org/wiki/Wake-on-LAN).
This packet is sent via UDP to the LAN Broadcast addresses (255.255.255.255) on arbitrary Port 4000.
Construction of this packet in PowerShell is very straight-forward: ("$Packet = [Byte[]](,0xFF*6)+($Mac*16)").
This script has a (hard-coded) table of saved MAC addresses to allow machine aliases to be specified as parameters to the
function (the real addresses have been obfuscated here) and uses a regex to validate MAC address strings. The address
aliases are contained in a hash table in the script - but they could very easily be obtained from an external source such as
a text file or a CSV file (this is left as an exercise for the reader).
It would be possible to use DNS and the ARP Cache to resolve MAC addresses, however, the ARP cache will only be populated with
a valid entry for any given target adapter for a relative short period of time after the last use of the address (10 minutes
or less depending on usage); ARP cannot be used to dynamically resolve the address of a suspended adapter.
.Example
Invoke-WakeOnLan 00-1F-D0-98-CD-44
Sends WOL packets to the specified address
.Example
Invoke-WakeOnLan 00-1F-D0-98-CD-44, 00-1D-92-3B-C2-C8
Sends WOL packets to the specified addresses
.Example
00-1F-D0-98-CD-44, 00-1D-92-3B-C2-C8 | Invoke-WakeOnLan
Sends WOL packets to the specified addresses
.Example
Invoke-WakeOnLan Server3
Sends WOL packets to the specified target using an alias. The alias must currently be hard-coded in the script.
.Inputs
An array of MAC addresses. Each address must be specified as a sequence of 6 hex-coded bytes seperated by ':' or '-'
The input can also contain aliases - these must currently be hard-coded in the script (see examples)
MAC addresses can be piped to the cmdlet.
.Outputs
Wake-on-Lan packets are sent to the specified addresses
.Parameter MacAddress
An array of MAC addresses. Each address must be specified as a sequence of 6 hex-coded bytes seperated by ':' or '-'
.Functionality
Sends Wake-on-Lan Magic Packets to the specified Mac addresses
#>
V1.0 (This Version)
- Initial release to the PowerShell Gallery
V0.1-0.9 Dev versions
See all my other PS Gallery modules:
Find-Module | Where Author -match 'Chris Warwick'