From e1f85cae95287e0e83408867d54cc6e48c952efa Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Thu, 1 Dec 2016 12:36:03 -0800 Subject: [PATCH 1/9] new content; Surface Wake On LAN --- devices/surface/TOC.md | 1 + devices/surface/change-history-for-surface.md | 6 ++ devices/surface/update.md | 1 + .../wake-on-lan-for-surface-devices.md | 55 +++++++++++++++++++ 4 files changed, 63 insertions(+) create mode 100644 devices/surface/wake-on-lan-for-surface-devices.md diff --git a/devices/surface/TOC.md b/devices/surface/TOC.md index ee3fbbd2b8..e4fd6d25d3 100644 --- a/devices/surface/TOC.md +++ b/devices/surface/TOC.md @@ -13,6 +13,7 @@ ### [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md) ### [Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md) ### [Surface Dock Updater](surface-dock-updater.md) +### [Wake on LAN for Surface devices](wake-on-lan-for-surface-devices.md) ## [Considerations for Surface and System Center Configuration Manager](considerations-for-surface-and-system-center-configuration-manager.md) ## [Deploy Surface app with Windows Store for Business](deploy-surface-app-with-windows-store-for-business.md) ## [Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md) diff --git a/devices/surface/change-history-for-surface.md b/devices/surface/change-history-for-surface.md index b3601e729a..4c58aaa0c5 100644 --- a/devices/surface/change-history-for-surface.md +++ b/devices/surface/change-history-for-surface.md @@ -11,6 +11,12 @@ author: jdeckerMS This topic lists new and updated topics in the Surface documentation library. +## December 2016 + +|New or changed topic | Description | +| --- | --- | +|[Wake on LAN for Surface devices](wake-on-lan-for-surface-devices.md) | New | + ## November 2016 |New or changed topic | Description | diff --git a/devices/surface/update.md b/devices/surface/update.md index 3e00c77e71..46d1f3b6bd 100644 --- a/devices/surface/update.md +++ b/devices/surface/update.md @@ -16,6 +16,7 @@ Find out how to download and manage the latest firmware and driver updates for y | Topic | Description | | --- | --- | +|[Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) | See how you can use Wake On LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically. | | [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)| Get a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.| | [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)| Explore the available options to manage firmware and driver updates for Surface devices.| | [Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md)| Read about the different methods you can use to manage the process of Surface Dock firmware updates.| diff --git a/devices/surface/wake-on-lan-for-surface-devices.md b/devices/surface/wake-on-lan-for-surface-devices.md new file mode 100644 index 0000000000..4aa2aa0a12 --- /dev/null +++ b/devices/surface/wake-on-lan-for-surface-devices.md @@ -0,0 +1,55 @@ +--- +title: Wake On LAN for Surface devices (Surface) +description: See how you can use Wake on LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically – even if the devices are powered down. +keywords: update, deploy, driver, wol +ms.prod: w10 +ms.mktglfcycl: manage +ms.pagetype: surface, devices +ms.sitesec: library +author: jobotto +--- + +# Wake On LAN for Surface devices + +Surface devices that run Windows 10, version 1607 (also known as Windows 10 Anniversary Update) or later and use a Surface Ethernet adapter to connect to a wired network, are capable of Wake On LAN from Connected Standby. With Wake On LAN, you can remotely wake up devices to perform management or maintenance tasks or enable management solutions (such as System Center Configuration Manager) automatically – even if the devices are powered down. For example, you can deploy applications to Surface devices left docked with a Surface Dock or Surface Pro 3 Docking Station by using System Center Configuration Manager during a window in the middle of the night, when the office is empty. + +>[!NOTE] +>Surface devices must be connected to AC power to support Wake On LAN. + +## Supported devices + +The following devices are supported for Wake On LAN: + +* Surface Book +* Surface Pro 4 +* Surface Pro 3 +* Surface 3 +* Surface Ethernet adapter +* Surface Dock +* Surface Docking Station for Surface Pro 3 + +## Wake On LAN driver + +To enable Wake On LAN support on Surface devices, a specific driver for the Surface Ethernet adapter is required. This driver is not included in the standard driver and firmware pack for Surface devices – you must download and install it separately. You can download the Surface Wake On LAN driver, SurfaceWOL.msi, from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center. + +You can run this Microsoft Windows Installer (.msi) file on a Surface device to install the Surface Wake On LAN driver, or you can distribute it to Surface devices with an application deployment solution, such as System Center Configuration Manager. To include the Surface Wake On LAN driver during deployment, you can install the .msi file as an application during the deployment process. You can also extract the Surface Wake On LAN driver files to include them in the deployment process. For example, you can include them in your Microsoft Deployment Toolkit (MDT) deployment share. You can read more about Surface deployment with MDT in [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/deploy-windows-10-to-surface-devices-with-mdt). + +>[!NOTE] +>During the installation of SurfaceWOL.msi, the following registry key is set to a value of 1, which allows easy identification of systems where the Wake On LAN driver has been installed. If you chose to extract and install these drivers separately during deployment, this registry key will not be configured and must be configured manually or with a script. + +>**HKLM\SYSTEM\CurrentControlSet\Control\Power AllowSystemRequiredPowerRequests** + +To extract the contents of SurfaceWOL.msi, use the MSIExec administrative installation option (**/a**), as shown in the following example, to extract the contents to the **C:\WOL\** folder: +**msiexec /a surfacewol.msi targetdir=C:\WOL /qn** + +## Using Surface Wake On LAN + +The Surface Wake On LAN driver conforms to the Wake On LAN standard, whereby the device is woken by a special network communication known as a magic packet. The magic packet consists of 6 bytes of 255 (or FF in hexadecimal) followed by 16 repetitions of the target computer’s MAC address. You can read more about the magic packet and the Wake On LAN standard at [Wake-on-LAN](https://wikipedia.org/wiki/Wake-on-LAN#Magic_packet) on Wikipedia. + +>[!NOTE] +>To send a magic packet and wake up a device by using Wake On LAN, you must know the MAC address of the target device and Ethernet adapter. Because the magic packet does not use the IP network protocol, it is not possible to use the IP address or DNS name of the device. + +Many management solutions, such as System Center Configuration Manager, provide built-in support for Wake On LAN. There are also many solutions, including Windows Store apps, PowerShell modules, third-party applications, and third-party management solutions that allow you to send a magic packet to wake up a device. For example, you can use the [Wake On LAN PowerShell module](https://gallery.technet.microsoft.com/scriptcenter/Wake-On-Lan-815424c4) from the TechNet Script Center. + +>[!NOTE] +>After a device has been woken up with a magic packet, the device will return to sleep if an application is not actively preventing sleep on the system or if the AllowSystemRequiredPowerRequests registry key is not configured to 1, which allows applications to prevent sleep. See the [Wake On LAN driver](#wake-on-lan-driver) section of this article for more information about this registry key. From c7061f80d4cb5210cc72b67d06042a7d8362293d Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Thu, 1 Dec 2016 13:16:10 -0800 Subject: [PATCH 2/9] edits --- devices/surface/TOC.md | 2 +- devices/surface/change-history-for-surface.md | 2 +- devices/surface/wake-on-lan-for-surface-devices.md | 7 ++++--- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/devices/surface/TOC.md b/devices/surface/TOC.md index e4fd6d25d3..0ce34a2dfe 100644 --- a/devices/surface/TOC.md +++ b/devices/surface/TOC.md @@ -13,7 +13,7 @@ ### [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md) ### [Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md) ### [Surface Dock Updater](surface-dock-updater.md) -### [Wake on LAN for Surface devices](wake-on-lan-for-surface-devices.md) +### [Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) ## [Considerations for Surface and System Center Configuration Manager](considerations-for-surface-and-system-center-configuration-manager.md) ## [Deploy Surface app with Windows Store for Business](deploy-surface-app-with-windows-store-for-business.md) ## [Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md) diff --git a/devices/surface/change-history-for-surface.md b/devices/surface/change-history-for-surface.md index 4c58aaa0c5..a91317837d 100644 --- a/devices/surface/change-history-for-surface.md +++ b/devices/surface/change-history-for-surface.md @@ -15,7 +15,7 @@ This topic lists new and updated topics in the Surface documentation library. |New or changed topic | Description | | --- | --- | -|[Wake on LAN for Surface devices](wake-on-lan-for-surface-devices.md) | New | +|[Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) | New | ## November 2016 diff --git a/devices/surface/wake-on-lan-for-surface-devices.md b/devices/surface/wake-on-lan-for-surface-devices.md index 4aa2aa0a12..5dce70e3f7 100644 --- a/devices/surface/wake-on-lan-for-surface-devices.md +++ b/devices/surface/wake-on-lan-for-surface-devices.md @@ -1,6 +1,6 @@ --- title: Wake On LAN for Surface devices (Surface) -description: See how you can use Wake on LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically – even if the devices are powered down. +description: See how you can use Wake On LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically – even if the devices are powered down. keywords: update, deploy, driver, wol ms.prod: w10 ms.mktglfcycl: manage @@ -30,7 +30,7 @@ The following devices are supported for Wake On LAN: ## Wake On LAN driver -To enable Wake On LAN support on Surface devices, a specific driver for the Surface Ethernet adapter is required. This driver is not included in the standard driver and firmware pack for Surface devices – you must download and install it separately. You can download the Surface Wake On LAN driver, SurfaceWOL.msi, from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center. +To enable Wake On LAN support on Surface devices, a specific driver for the Surface Ethernet adapter is required. This driver is not included in the standard driver and firmware pack for Surface devices – you must download and install it separately. You can download the Surface Wake On LAN driver (SurfaceWOL.msi) from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center. You can run this Microsoft Windows Installer (.msi) file on a Surface device to install the Surface Wake On LAN driver, or you can distribute it to Surface devices with an application deployment solution, such as System Center Configuration Manager. To include the Surface Wake On LAN driver during deployment, you can install the .msi file as an application during the deployment process. You can also extract the Surface Wake On LAN driver files to include them in the deployment process. For example, you can include them in your Microsoft Deployment Toolkit (MDT) deployment share. You can read more about Surface deployment with MDT in [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/deploy-windows-10-to-surface-devices-with-mdt). @@ -40,7 +40,8 @@ You can run this Microsoft Windows Installer (.msi) file on a Surface device to >**HKLM\SYSTEM\CurrentControlSet\Control\Power AllowSystemRequiredPowerRequests** To extract the contents of SurfaceWOL.msi, use the MSIExec administrative installation option (**/a**), as shown in the following example, to extract the contents to the **C:\WOL\** folder: -**msiexec /a surfacewol.msi targetdir=C:\WOL /qn** + + `msiexec /a surfacewol.msi targetdir=C:\WOL /qn` ## Using Surface Wake On LAN From 815e2f66dd2ba8c477f81932f7d54c7752a008fb Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Wed, 25 Jan 2017 09:21:33 -0800 Subject: [PATCH 3/9] update change document --- devices/surface/change-history-for-surface.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/surface/change-history-for-surface.md b/devices/surface/change-history-for-surface.md index a91317837d..22c48934fe 100644 --- a/devices/surface/change-history-for-surface.md +++ b/devices/surface/change-history-for-surface.md @@ -11,7 +11,7 @@ author: jdeckerMS This topic lists new and updated topics in the Surface documentation library. -## December 2016 +## January 2017 |New or changed topic | Description | | --- | --- | From df4d063ad6c640d1dda6d2d35a613b4ad665f2bc Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Wed, 25 Jan 2017 10:58:34 -0800 Subject: [PATCH 4/9] fix formatting --- devices/surface/wake-on-lan-for-surface-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/surface/wake-on-lan-for-surface-devices.md b/devices/surface/wake-on-lan-for-surface-devices.md index 5dce70e3f7..be64599ce4 100644 --- a/devices/surface/wake-on-lan-for-surface-devices.md +++ b/devices/surface/wake-on-lan-for-surface-devices.md @@ -39,7 +39,7 @@ You can run this Microsoft Windows Installer (.msi) file on a Surface device to >**HKLM\SYSTEM\CurrentControlSet\Control\Power AllowSystemRequiredPowerRequests** -To extract the contents of SurfaceWOL.msi, use the MSIExec administrative installation option (**/a**), as shown in the following example, to extract the contents to the **C:\WOL\** folder: +To extract the contents of SurfaceWOL.msi, use the MSIExec administrative installation option (**/a**), as shown in the following example, to extract the contents to the C:\WOL\ folder: `msiexec /a surfacewol.msi targetdir=C:\WOL /qn` From 68ae2a0ea26dd40813e8d0e4bc104eb6d74f19b3 Mon Sep 17 00:00:00 2001 From: Justinha Date: Wed, 25 Jan 2017 11:18:36 -0800 Subject: [PATCH 5/9] just removing blank line --- windows/keep-secure/credential-guard.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/keep-secure/credential-guard.md b/windows/keep-secure/credential-guard.md index 27813be3bc..c038a4d588 100644 --- a/windows/keep-secure/credential-guard.md +++ b/windows/keep-secure/credential-guard.md @@ -48,7 +48,7 @@ The following tables provide more information about the hardware, firmware, and > [!NOTE] > For new computers running Windows 10, Trusted Platform Module (TPM 2.0) must be enabled by default. This requirement is not restated in the tables that follow.
-> If you are an OEM, see the requirements information at [PC OEM requirements for Device Guard and Credential Guard](https://msdn.microsoft.com/library/windows/hardware/mt767514(v=vs.85).aspx).
+> If you are an OEM, see the requirements information at [PC OEM requirements for Device Guard and Credential Guard](https://msdn.microsoft.com/library/windows/hardware/mt767514.aspx).
> Starting in Widows 10, 1607, TPM 2.0 is required. @@ -61,7 +61,7 @@ The following tables provide more information about the hardware, firmware, and | Hardware: **Trusted Platform Module (TPM)** | **Requirement**: TPM 1.2 or TPM 2.0, either discrete or firmware.

**Security benefits**: A TPM provides protection for VBS encryption keys that are stored in the firmware. This helps protect against attacks involving a physically present user with BIOS access. | | Firmware: **UEFI firmware version 2.3.1.c or higher with UEFI Secure Boot** | **Requirements**: See the following Windows Hardware Compatibility Program requirement: [System.Fundamentals.Firmware.UEFISecureBoot](http://msdn.microsoft.com/library/windows/hardware/dn932805.aspx#system-fundamentals-firmware-uefisecureboot)

**Security benefits**: UEFI Secure Boot helps ensure that the device boots only authorized code. This can prevent boot kits and root kits from installing and persisting across reboots. | | Firmware: **Secure firmware update process** | **Requirements**: UEFI firmware must support secure firmware update found under the following Windows Hardware Compatibility Program requirement: [System.Fundamentals.Firmware.UEFISecureBoot](http://msdn.microsoft.com/library/windows/hardware/dn932805.aspx#system-fundamentals-firmware-uefisecureboot).

**Security benefits**: UEFI firmware just like software can have security vulnerabilities that, when found, need to be patched through firmware updates. Patching helps prevent root kits from getting installed. | -| Software: Qualified **Windows operating system** | **Requirement**: Windows 10 Enterprise, Windows 10 Education, Windows 2016 Server, or Windows Enterprise IoT

Important:
Windows Server 2016 running as a domain controller does not support Credential Guard. Only Device Guard is supported in this configuration.


**Security benefits**: Support for VBS and for management features that simplify configuration of Credential Guard. | +| Software: Qualified **Windows operating system** | **Requirement**: Windows 10 Enterprise, Windows 10 Education, Windows 2016 Server, or Windows Enterprise IoT

Important:
Windows Server 2016 running as a domain controller does not support Credential Guard. Only Device Guard is supported in this configuration.


**Security benefits**: Support for VBS and for management features that simplify configuration of Credential Guard. | > [!IMPORTANT] > The preceding table lists requirements for baseline protections. The following tables list requirements for improved security. You can use Credential Guard with hardware, firmware, and software that support baseline protections, even if they do not support protections for improved security. However, we strongly recommend meeting the requirements for improved security, to significantly strengthen the level of security that Credential Guard can provide. From a36764c5cc76ec446b48b216906c6cdcc924744e Mon Sep 17 00:00:00 2001 From: Justinha Date: Wed, 25 Jan 2017 11:28:43 -0800 Subject: [PATCH 6/9] just removing blank line --- ...ments-and-deployment-planning-guidelines-for-device-guard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/requirements-and-deployment-planning-guidelines-for-device-guard.md b/windows/keep-secure/requirements-and-deployment-planning-guidelines-for-device-guard.md index 5de3da4f21..fad266b5ee 100644 --- a/windows/keep-secure/requirements-and-deployment-planning-guidelines-for-device-guard.md +++ b/windows/keep-secure/requirements-and-deployment-planning-guidelines-for-device-guard.md @@ -54,7 +54,7 @@ The following tables provide more information about the hardware, firmware, and | Firmware: **UEFI firmware version 2.3.1.c or higher with UEFI Secure Boot** | **Requirements**: See the following Windows Hardware Compatibility Program requirement: [System.Fundamentals.Firmware.UEFISecureBoot](http://msdn.microsoft.com/library/windows/hardware/dn932805.aspx#system-fundamentals-firmware-uefisecureboot)

**Security benefits**: UEFI Secure Boot helps ensure that the device boots only authorized code. This can prevent boot kits and root kits from installing and persisting across reboots. | | Firmware: **Secure firmware update process** | **Requirements**: UEFI firmware must support secure firmware update found under the following Windows Hardware Compatibility Program requirement: [System.Fundamentals.Firmware.UEFISecureBoot](http://msdn.microsoft.com/library/windows/hardware/dn932805.aspx#system-fundamentals-firmware-uefisecureboot).

**Security benefits**: UEFI firmware just like software can have security vulnerabilities that, when found, need to be patched through firmware updates. Patching helps prevent root kits from getting installed. | | Software: **HVCI compatible drivers** | **Requirements**: See the Windows Hardware Compatibility Program requirements under [Filter.Driver.DeviceGuard.DriverCompatibility](https://msdn.microsoft.com/library/windows/hardware/mt589732(v=vs.85).aspx).

**Security benefits**: [HVCI Compatible](https://blogs.msdn.microsoft.com/windows_hardware_certification/2015/05/22/driver-compatibility-with-device-guard-in-windows-10/) drivers help ensure that VBS can maintain appropriate memory permissions. This increases resistance to bypassing vulnerable kernel drivers and helps ensure that malware cannot run in kernel. Only code verified through code integrity can run in kernel mode. | -| Software: Qualified **Windows operating system** | **Requirement**: Windows 10 Enterprise, Windows 10 Education, Windows 2016 Server, or Windows Enterprise IoT

Important:
Windows Server 2016 running as a domain controller does not support Credential Guard. Only Device Guard is supported in this configuration.


**Security benefits**: Support for VBS and for management features that simplify configuration of Device Guard. | +| Software: Qualified **Windows operating system** | **Requirement**: Windows 10 Enterprise, Windows 10 Education, Windows 2016 Server, or Windows Enterprise IoT

Important:
Windows Server 2016 running as a domain controller does not support Credential Guard. Only Device Guard is supported in this configuration.


**Security benefits**: Support for VBS and for management features that simplify configuration of Device Guard. | > **Important**  The preceding table lists requirements for baseline protections. The following tables list requirements for improved security. You can use Device Guard with hardware, firmware, and software that support baseline protections, even if they do not support protections for improved security. However, we strongly recommend meeting the requirements for improved security, to significantly strengthen the level of security that Device Guard can provide. From b401b85a72f9ede6d7c6e988154aaa804ab33d68 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 25 Jan 2017 11:34:45 -0800 Subject: [PATCH 7/9] c --- windows/deploy/windows-10-poc.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/windows/deploy/windows-10-poc.md b/windows/deploy/windows-10-poc.md index fceb199fec..d2d418cbda 100644 --- a/windows/deploy/windows-10-poc.md +++ b/windows/deploy/windows-10-poc.md @@ -850,9 +850,11 @@ The second Windows Server 2012 R2 VHD needs to be expanded in size from 40GB to Copy-VMFile "PC1" –SourcePath "C:\VHD\pc1.ps1" –DestinationPath "C:\pc1.ps1" –CreateFullPath –FileSource Host - >In order for this command to work properly, PC1 must be running the vmicguestinterface (Hyper-V Guest Service Interface) service. If this service is not installed, you can try updating integration services on the VM. This can be done by mounting the Hyper-V Integration Services Setup (vmguest.iso), which is located in C:\Windows\System32 on Windows Server operating systems that are running the Hyper-V role service. + >In order for this command to work properly, PC1 must be running the vmicguestinterface (Hyper-V Guest Service Interface) service. If this service is not installed, you can try updating integration services on the VM by mounting the Hyper-V Integration Services Setup (vmguest.iso), which is located in C:\Windows\System32 on Windows Server 2012 and 2012 R2 operating systems that are running the Hyper-V role service. You can also try running the following command from an elevated Windows PowerShell prompt on the Hyper-V host: + + 
Enable-VMIntegrationService -VMName PC1 -Name "Guest Service Interface"
- If the copy-vmfile command does not work and you cannot properly upgrade integration services on PC1, then create the file c:\pc1.ps1 on the VM by typing the commands into this file manually. The copy-vmfile command is only used in this procedure as a demonstration. After typing the script file manually, be sure to save the file as a Windows PowerShell script file with the .ps1 extension and not as a text (.txt) file. + If the copy-vmfile command does not work and you cannot properly enable or upgrade integration services on PC1, then create the file c:\pc1.ps1 on the VM by typing the commands into this file manually. The copy-vmfile command is only used in this procedure as a demonstration. After typing the script file manually, be sure to save the file as a Windows PowerShell script file with the .ps1 extension and not as a text (.txt) file. 21. On PC1, type the following commands at an elevated Windows PowerShell prompt: From 3d1dcf1d259f70f6e9d66fd3cd1c6045f515437c Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Wed, 25 Jan 2017 11:41:40 -0800 Subject: [PATCH 8/9] Tbl caption ambiguity - added white space --- .../keep-secure/choose-the-right-bitlocker-countermeasure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/choose-the-right-bitlocker-countermeasure.md b/windows/keep-secure/choose-the-right-bitlocker-countermeasure.md index 1c6c64a34a..241eadd7f7 100644 --- a/windows/keep-secure/choose-the-right-bitlocker-countermeasure.md +++ b/windows/keep-secure/choose-the-right-bitlocker-countermeasure.md @@ -64,7 +64,7 @@ Tables 1 and 2 summarize the recommended mitigations for different types of atta -**Table 1.**  How to choose the best countermeasures for Windows 8.1 +**Table 1.**  How to choose the best countermeasures for Windows 8.1

From 965d2c702ad573ed235f58a49d8ac0c3ddedc620 Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Wed, 25 Jan 2017 12:45:26 -0800 Subject: [PATCH 9/9] add Wake On Lan acronym throughout --- .../wake-on-lan-for-surface-devices.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/devices/surface/wake-on-lan-for-surface-devices.md b/devices/surface/wake-on-lan-for-surface-devices.md index be64599ce4..cee0c58856 100644 --- a/devices/surface/wake-on-lan-for-surface-devices.md +++ b/devices/surface/wake-on-lan-for-surface-devices.md @@ -1,7 +1,7 @@ --- title: Wake On LAN for Surface devices (Surface) description: See how you can use Wake On LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically – even if the devices are powered down. -keywords: update, deploy, driver, wol +keywords: update, deploy, driver, wol, wake-on-lan ms.prod: w10 ms.mktglfcycl: manage ms.pagetype: surface, devices @@ -11,14 +11,14 @@ author: jobotto # Wake On LAN for Surface devices -Surface devices that run Windows 10, version 1607 (also known as Windows 10 Anniversary Update) or later and use a Surface Ethernet adapter to connect to a wired network, are capable of Wake On LAN from Connected Standby. With Wake On LAN, you can remotely wake up devices to perform management or maintenance tasks or enable management solutions (such as System Center Configuration Manager) automatically – even if the devices are powered down. For example, you can deploy applications to Surface devices left docked with a Surface Dock or Surface Pro 3 Docking Station by using System Center Configuration Manager during a window in the middle of the night, when the office is empty. +Surface devices that run Windows 10, version 1607 (also known as Windows 10 Anniversary Update) or later and use a Surface Ethernet adapter to connect to a wired network, are capable of Wake On LAN (WOL) from Connected Standby. With WOL, you can remotely wake up devices to perform management or maintenance tasks or enable management solutions (such as System Center Configuration Manager) automatically – even if the devices are powered down. For example, you can deploy applications to Surface devices left docked with a Surface Dock or Surface Pro 3 Docking Station by using System Center Configuration Manager during a window in the middle of the night, when the office is empty. >[!NOTE] ->Surface devices must be connected to AC power to support Wake On LAN. +>Surface devices must be connected to AC power to support WOL. ## Supported devices -The following devices are supported for Wake On LAN: +The following devices are supported for WOL: * Surface Book * Surface Pro 4 @@ -28,14 +28,14 @@ The following devices are supported for Wake On LAN: * Surface Dock * Surface Docking Station for Surface Pro 3 -## Wake On LAN driver +## WOL driver -To enable Wake On LAN support on Surface devices, a specific driver for the Surface Ethernet adapter is required. This driver is not included in the standard driver and firmware pack for Surface devices – you must download and install it separately. You can download the Surface Wake On LAN driver (SurfaceWOL.msi) from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center. +To enable WOL support on Surface devices, a specific driver for the Surface Ethernet adapter is required. This driver is not included in the standard driver and firmware pack for Surface devices – you must download and install it separately. You can download the Surface WOL driver (SurfaceWOL.msi) from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center. -You can run this Microsoft Windows Installer (.msi) file on a Surface device to install the Surface Wake On LAN driver, or you can distribute it to Surface devices with an application deployment solution, such as System Center Configuration Manager. To include the Surface Wake On LAN driver during deployment, you can install the .msi file as an application during the deployment process. You can also extract the Surface Wake On LAN driver files to include them in the deployment process. For example, you can include them in your Microsoft Deployment Toolkit (MDT) deployment share. You can read more about Surface deployment with MDT in [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/deploy-windows-10-to-surface-devices-with-mdt). +You can run this Microsoft Windows Installer (.msi) file on a Surface device to install the Surface WOL driver, or you can distribute it to Surface devices with an application deployment solution, such as System Center Configuration Manager. To include the Surface WOL driver during deployment, you can install the .msi file as an application during the deployment process. You can also extract the Surface WOL driver files to include them in the deployment process. For example, you can include them in your Microsoft Deployment Toolkit (MDT) deployment share. You can read more about Surface deployment with MDT in [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/deploy-windows-10-to-surface-devices-with-mdt). >[!NOTE] ->During the installation of SurfaceWOL.msi, the following registry key is set to a value of 1, which allows easy identification of systems where the Wake On LAN driver has been installed. If you chose to extract and install these drivers separately during deployment, this registry key will not be configured and must be configured manually or with a script. +>During the installation of SurfaceWOL.msi, the following registry key is set to a value of 1, which allows easy identification of systems where the WOL driver has been installed. If you chose to extract and install these drivers separately during deployment, this registry key will not be configured and must be configured manually or with a script. >**HKLM\SYSTEM\CurrentControlSet\Control\Power AllowSystemRequiredPowerRequests** @@ -43,14 +43,14 @@ To extract the contents of SurfaceWOL.msi, use the MSIExec administrative instal `msiexec /a surfacewol.msi targetdir=C:\WOL /qn` -## Using Surface Wake On LAN +## Using Surface WOL -The Surface Wake On LAN driver conforms to the Wake On LAN standard, whereby the device is woken by a special network communication known as a magic packet. The magic packet consists of 6 bytes of 255 (or FF in hexadecimal) followed by 16 repetitions of the target computer’s MAC address. You can read more about the magic packet and the Wake On LAN standard at [Wake-on-LAN](https://wikipedia.org/wiki/Wake-on-LAN#Magic_packet) on Wikipedia. +The Surface WOL driver conforms to the WOL standard, whereby the device is woken by a special network communication known as a magic packet. The magic packet consists of 6 bytes of 255 (or FF in hexadecimal) followed by 16 repetitions of the target computer’s MAC address. You can read more about the magic packet and the WOL standard on [Wikipedia](https://wikipedia.org/wiki/Wake-on-LAN#Magic_packet). >[!NOTE] ->To send a magic packet and wake up a device by using Wake On LAN, you must know the MAC address of the target device and Ethernet adapter. Because the magic packet does not use the IP network protocol, it is not possible to use the IP address or DNS name of the device. +>To send a magic packet and wake up a device by using WOL, you must know the MAC address of the target device and Ethernet adapter. Because the magic packet does not use the IP network protocol, it is not possible to use the IP address or DNS name of the device. -Many management solutions, such as System Center Configuration Manager, provide built-in support for Wake On LAN. There are also many solutions, including Windows Store apps, PowerShell modules, third-party applications, and third-party management solutions that allow you to send a magic packet to wake up a device. For example, you can use the [Wake On LAN PowerShell module](https://gallery.technet.microsoft.com/scriptcenter/Wake-On-Lan-815424c4) from the TechNet Script Center. +Many management solutions, such as System Center Configuration Manager, provide built-in support for WOL. There are also many solutions, including Windows Store apps, PowerShell modules, third-party applications, and third-party management solutions that allow you to send a magic packet to wake up a device. For example, you can use the [Wake On LAN PowerShell module](https://gallery.technet.microsoft.com/scriptcenter/Wake-On-Lan-815424c4) from the TechNet Script Center. >[!NOTE] ->After a device has been woken up with a magic packet, the device will return to sleep if an application is not actively preventing sleep on the system or if the AllowSystemRequiredPowerRequests registry key is not configured to 1, which allows applications to prevent sleep. See the [Wake On LAN driver](#wake-on-lan-driver) section of this article for more information about this registry key. +>After a device has been woken up with a magic packet, the device will return to sleep if an application is not actively preventing sleep on the system or if the AllowSystemRequiredPowerRequests registry key is not configured to 1, which allows applications to prevent sleep. See the [WOL driver](#wol-driver) section of this article for more information about this registry key.