From ff25cd6af576d115ec48cf40d3470a531802bd06 Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Wed, 18 May 2016 19:23:40 -0700 Subject: [PATCH] fix notes --- ...nced-uefi-security-features-for-surface.md | 4 +- ...tomize-the-oobe-for-surface-deployments.md | 6 +-- ...irmware-and-drivers-for-surface-devices.md | 4 +- ...-adapters-and-surface-device-deployment.md | 2 +- .../manage-surface-dock-firmware-updates.md | 11 +++-- .../surface/microsoft-surface-data-eraser.md | 6 +-- ...icrosoft-surface-deployment-accelerator.md | 4 +- ...-by-step-surface-deployment-accelerator.md | 19 ++++---- devices/surface/surface-diagnostic-toolkit.md | 44 +++++++++---------- devices/surface/surface-dock-updater.md | 4 +- 10 files changed, 51 insertions(+), 53 deletions(-) diff --git a/devices/surface/advanced-uefi-security-features-for-surface.md b/devices/surface/advanced-uefi-security-features-for-surface.md index 916ff69bf3..9eb6cc703e 100644 --- a/devices/surface/advanced-uefi-security-features-for-surface.md +++ b/devices/surface/advanced-uefi-security-features-for-surface.md @@ -24,7 +24,7 @@ Before you can configure the advanced security features of your Surface device, ## Manually configure additional security settings -**Note**  To enter firmware setup on a Surface device, begin with the device powered off, press and hold the **Volume Up** button, then press and release the **Power** button, then release the **Volume Up** button after the device has begun to boot. +>**Note:**  To enter firmware setup on a Surface device, begin with the device powered off, press and hold the **Volume Up** button, then press and release the **Power** button, then release the **Volume Up** button after the device has begun to boot. After the v3.11.760.0 UEFI update is installed on a Surface device, an additional UEFI menu named **Advanced Device Security** becomes available. If you click this menu, the following options are displayed: @@ -55,7 +55,7 @@ As an IT professional with administrative privileges, you can automate the confi **Sample scripts** -**Note**  The UEFI password used in the sample scripts below is presented in clear text. We strongly recommend saving the scripts in a protected location and running them in a controlled environment. +>**Note**:  The UEFI password used in the sample scripts below is presented in clear text. We strongly recommend saving the scripts in a protected location and running them in a controlled environment. Show all configurable options: diff --git a/devices/surface/customize-the-oobe-for-surface-deployments.md b/devices/surface/customize-the-oobe-for-surface-deployments.md index 9bf808c8a3..9b85678e22 100644 --- a/devices/surface/customize-the-oobe-for-surface-deployments.md +++ b/devices/surface/customize-the-oobe-for-surface-deployments.md @@ -16,13 +16,13 @@ This article walks you through the process of customizing the Surface out-of-box It is common practice in a Windows deployment to customize the user experience for the first startup of deployed computers — the out-of-box experience, or OOBE. -**Note**  OOBE is also often used to describe the phase, or configuration pass, of Windows setup during which the user experience is displayed. For more information about the OOBE phase of setup, see [How Configuration Passes Work](http://msdn.microsoft.com/library/windows/hardware/dn898581(v=vs.85).aspx). +>**Note:**  OOBE is also often used to describe the phase, or configuration pass, of Windows setup during which the user experience is displayed. For more information about the OOBE phase of setup, see [How Configuration Passes Work](http://msdn.microsoft.com/library/windows/hardware/dn898581.aspx). In some scenarios, you may want to provide complete automation to ensure that at the end of a deployment, computers are ready for use without any interaction from the user. In other scenarios, you may want to leave key elements of the experience for users to perform necessary actions or select between important choices. For administrators deploying to Surface devices, each of these scenarios presents a unique challenge to overcome. This article provides a summary of the scenarios where a deployment might require additional steps. It also provides the required information to ensure that the desired experience is achieved on any newly deployed Surface device. This article is intended for administrators who are familiar with the deployment process, as well as concepts such as answer files and [reference images](http://go.microsoft.com/fwlink/p/?LinkID=618042). -**Note**  Although the OOBE phase of setup is still run during a deployment with an automated deployment solution such as the [Microsoft Deployment Toolkit (MDT)](http://go.microsoft.com/fwlink/p/?LinkId=618117) or System Center Configuration Manager Operating System Deployment (OSD), it is automated by the settings supplied in the Deployment Wizard and task sequence. For more information see: +>**Note:**  Although the OOBE phase of setup is still run during a deployment with an automated deployment solution such as the [Microsoft Deployment Toolkit (MDT)](http://go.microsoft.com/fwlink/p/?LinkId=618117) or System Center Configuration Manager Operating System Deployment (OSD), it is automated by the settings supplied in the Deployment Wizard and task sequence. For more information see: - [Deploy Windows 10 with the Microsoft Deployment Toolkit](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit) @@ -49,7 +49,7 @@ To provide the factory Surface Pen pairing experience in OOBE, you must copy fou - %windir%\\system32\\oobe\\info\\default\\1033\\PenError\_en-US.png - %windir%\\system32\\oobe\\info\\default\\1033\\PenSuccess\_en-US.png -**Note**  You should copy the files from a factory image for the same model Surface device that you intend to deploy to. For example, you should use the files from a Surface Pro 3 to deploy to Surface Pro 3, and the files from Surface Book to deploy Surface Book, but you should not use the files from a Surface Pro 3 to deploy Surface Book or Surface Pro 4. +>**Note:**  You should copy the files from a factory image for the same model Surface device that you intend to deploy to. For example, you should use the files from a Surface Pro 3 to deploy to Surface Pro 3, and the files from Surface Book to deploy Surface Book, but you should not use the files from a Surface Pro 3 to deploy Surface Book or Surface Pro 4.   diff --git a/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md b/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md index 1f54650639..61d56fa1b9 100644 --- a/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md +++ b/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md @@ -26,12 +26,12 @@ Driver and firmware updates for Surface devices are released in one of two ways: Installation files for administrative tools, drivers for accessories, and updates for Windows are also available for some devices and are detailed here in this article. -**Note**  To simplify the process of locating drivers for your device, downloads for Surface devices have been reorganized to separate pages for each model. Bookmark the Microsoft Download Center page for your device from the links provided on this page. Many of the filenames contain a placeholder denoted with *xxxxxx*, which identifies the current version number or date of the file. +>**Note:**  To simplify the process of locating drivers for your device, downloads for Surface devices have been reorganized to separate pages for each model. Bookmark the Microsoft Download Center page for your device from the links provided on this page. Many of the filenames contain a placeholder denoted with *xxxxxx*, which identifies the current version number or date of the file.   Recent additions to the downloads for Surface devices provide you with options to install Windows 10 on your Surface devices and update LTE devices with the latest Windows 10 drivers and firmware. -**Note**  A battery charge of 40% or greater is required before you install firmware to a Surface device. See [Microsoft Support article KB2909710](http://go.microsoft.com/fwlink/p/?LinkId=618106) for more information. +>**Note:**  A battery charge of 40% or greater is required before you install firmware to a Surface device. See [Microsoft Support article KB2909710](http://go.microsoft.com/fwlink/p/?LinkId=618106) for more information.   diff --git a/devices/surface/ethernet-adapters-and-surface-device-deployment.md b/devices/surface/ethernet-adapters-and-surface-device-deployment.md index db8c55a949..fb580c032f 100644 --- a/devices/surface/ethernet-adapters-and-surface-device-deployment.md +++ b/devices/surface/ethernet-adapters-and-surface-device-deployment.md @@ -53,7 +53,7 @@ To boot a Surface device from an alternative boot device, follow these steps: 3. Press and release the **Power** button. 4. After the system begins to boot from the USB stick or Ethernet adapter, release the **Volume Down** button. -**Note**  In addition to an Ethernet adapter, a keyboard must also be connected to the Surface device to enter the preinstallation environment and navigate the deployment wizard. +>**Note:**  In addition to an Ethernet adapter, a keyboard must also be connected to the Surface device to enter the preinstallation environment and navigate the deployment wizard.   diff --git a/devices/surface/manage-surface-dock-firmware-updates.md b/devices/surface/manage-surface-dock-firmware-updates.md index 093579d4a5..3dd3741b56 100644 --- a/devices/surface/manage-surface-dock-firmware-updates.md +++ b/devices/surface/manage-surface-dock-firmware-updates.md @@ -17,7 +17,7 @@ The Surface Dock provides external connectivity to Surface devices through a sin Like the firmware for Surface devices, firmware for Surface Dock is also contained within a downloaded driver that is visible in Device Manager. This driver stages the firmware update files on the Surface device. When a Surface Dock is connected and the driver is loaded, the newer version of the firmware staged by the driver is detected and firmware files are copied to the Surface Dock. The Surface Dock then begins a two-phase process to apply the firmware internally. Each phase requires the Surface Dock to be disconnected from the Surface device before the firmware is applied. The driver copies the firmware into the dock, but only applies it when the user disconnects the Surface device from the Surface Dock. This ensures that there are no disruptions because the firmware is only applied when the user leaves their desk with the device. -**Note**  You can learn more about the firmware update process for Surface devices and how firmware is updated through driver installation at the following links: +>**Note:**  You can learn more about the firmware update process for Surface devices and how firmware is updated through driver installation at the following links: - [How to manage and update your drivers and firmware for Surface](http://go.microsoft.com/fwlink/p/?LinkId=785353) from Microsoft Mechanics @@ -69,7 +69,7 @@ There are three methods you can use to update the firmware of the Surface Dock: Windows Update is the method that most users will use. The drivers for the Surface Dock are downloaded automatically from Windows Update and the dock update process is initiated without additional user interaction. The two-phase dock update process described earlier occurs in the background as the user connects and disconnects the Surface Dock during normal use. -**Note**  The driver version that is displayed in Device Manager may be different from the firmware version that the Surface Dock is using. +>**Note:**  The driver version that is displayed in Device Manager may be different from the firmware version that the Surface Dock is using.   @@ -80,9 +80,8 @@ This method is used mostly in environments where Surface device drivers and firm For more information about how to deploy MSI packages see [Create and deploy an application with System Center Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=785355). -**Note**  When drivers are installed through Windows Update or the MSI package, registry keys are added that indicate the version of firmware installed on the Surface Dock and contained within the Surface Dock driver. These registry keys can be found in: - -**HLKM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WUDF\\Services\\SurfaceDockFwUpdate\\Parameters** +>**Note:**  When drivers are installed through Windows Update or the MSI package, registry keys are added that indicate the version of firmware installed on the Surface Dock and contained within the Surface Dock driver. These registry keys can be found in:

+ **HLKM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WUDF\\Services\\SurfaceDockFwUpdate\\Parameters** Firmware status is displayed for both the main chipset (displayed as **Component10**) and the DisplayPort chipset (displayed as **Component20**). For each chipset there are four keys, where *xx* is **10** or **20** corresponding to each chipset: @@ -94,7 +93,7 @@ Firmware status is displayed for both the main chipset (displayed as **Component - **Component*xx*FirmwareUpdateStatusRejectReason** – This key changes as the firmware update is processed. It should result in 0 after the successful installation of Surface Dock firmware. -These registry keys are not present unless you have installed updated Surface Dock drivers through Windows Update or MSI deployment. +>**Note:**  These registry keys are not present unless you have installed updated Surface Dock drivers through Windows Update or MSI deployment.   diff --git a/devices/surface/microsoft-surface-data-eraser.md b/devices/surface/microsoft-surface-data-eraser.md index 7a26697d0f..e35e41bbf8 100644 --- a/devices/surface/microsoft-surface-data-eraser.md +++ b/devices/surface/microsoft-surface-data-eraser.md @@ -40,9 +40,9 @@ Some scenarios where Microsoft Surface Data Eraser can be helpful include: - Standard practice when performing reimaging for devices used with sensitive data -**Note**  Third-party devices, Surface devices running Windows RT (including Surface and Surface 2), and Surface Pro are not compatible with Microsoft Surface Data Eraser. +>**Note:**  Third-party devices, Surface devices running Windows RT (including Surface and Surface 2), and Surface Pro are not compatible with Microsoft Surface Data Eraser. -**Note**  Because the ability to boot to USB is required to run Microsoft Surface Data Eraser, if the device is not configured to boot from USB or if the device is unable to boot or POST successfully, the Microsoft Surface Data Eraser tool will not function. +>**Note:**  Because the ability to boot to USB is required to run Microsoft Surface Data Eraser, if the device is not configured to boot from USB or if the device is unable to boot or POST successfully, the Microsoft Surface Data Eraser tool will not function. ## How to create a Microsoft Surface Data Eraser USB stick @@ -69,7 +69,7 @@ After the creation tool is installed, follow these steps to create a Microsoft S Figure 1. Start the Microsoft Surface Data Eraser tool 4. Select the USB drive of your choice from the **USB Thumb Drive Selection** page as shown in Figure 2, and then click **Start** to begin the USB creation process. The drive you select will be formatted and any existing data on this drive will be lost. - **Note**  If the Start button is disabled, check that your removable drive has a total capacity of at least 4 GB. + >**Note:**  If the Start button is disabled, check that your removable drive has a total capacity of at least 4 GB.   ![figure 2](images/dataeraser-usb-selection.png) diff --git a/devices/surface/microsoft-surface-deployment-accelerator.md b/devices/surface/microsoft-surface-deployment-accelerator.md index c29e806628..e38d23d94b 100644 --- a/devices/surface/microsoft-surface-deployment-accelerator.md +++ b/devices/surface/microsoft-surface-deployment-accelerator.md @@ -60,7 +60,7 @@ When the Microsoft Surface Deployment Accelerator completes, you can use the dep You can modify the task sequence in the MDT Deployment Workbench to [include your own apps](http://go.microsoft.com/fwlink/p/?linkid=691700), or to [pause the automated installation routine](http://go.microsoft.com/fwlink/p/?linkid=691701). While the installation is paused, you can make changes to customize your reference image. After the image is captured, you can configure a deployment task sequence and distribute this custom configuration by using the same network boot capabilities as before. -**Note**  With Microsoft Surface Deployment Accelerator v1.9.0258, Surface Pro 3, Surface Pro 4, and Surface Book are supported for Windows 10 deployment, and Surface Pro 3 is supported for Windows 8.1 deployment. +>**Note:**  With Microsoft Surface Deployment Accelerator v1.9.0258, Surface Pro 3, Surface Pro 4, and Surface Book are supported for Windows 10 deployment, and Surface Pro 3 is supported for Windows 8.1 deployment.   @@ -75,7 +75,7 @@ Figure 2. Specify a local source for Surface driver and app files You can find a full list of available driver downloads at [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md) -**Note**  Downloaded files do not need to be extracted. The downloaded files can be left as .zip files as long as they are stored in one folder. +>**Note:**  Downloaded files do not need to be extracted. The downloaded files can be left as .zip files as long as they are stored in one folder.   diff --git a/devices/surface/step-by-step-surface-deployment-accelerator.md b/devices/surface/step-by-step-surface-deployment-accelerator.md index faa4f9d57b..b04c37e9b5 100644 --- a/devices/surface/step-by-step-surface-deployment-accelerator.md +++ b/devices/surface/step-by-step-surface-deployment-accelerator.md @@ -37,7 +37,7 @@ The tool installs in the Surface Deployment Accelerator program group, as shown Figure 2. The Surface Deployment Accelerator program group and icon -**Note**  At this point the tool has not yet prepared any deployment environment or downloaded any materials from the Internet. +>**Note:**  At this point the tool has not yet prepared any deployment environment or downloaded any materials from the Internet.   @@ -46,7 +46,7 @@ Figure 2. The Surface Deployment Accelerator program group and icon The following steps show how you create a deployment share for Windows 10 that supports Surface Pro 3, Surface Pro 4, Surface Book, the Surface Firmware Tool, and the Surface Asset Tag Tool. As you follow the steps below, make the selections that are applicable for your organization. For example, you could choose to deploy Windows 10 to Surface Book only, without any of the Surface apps. -**Note**  SDA lets you create deployment shares for both Windows 8.1 and Windows 10 deployments, but you can only create a single deployment share at a time. Therefore, to create both Windows 8.1 and Windows 10 deployment shares, you will need to run the tool twice. +>**Note:**  SDA lets you create deployment shares for both Windows 8.1 and Windows 10 deployments, but you can only create a single deployment share at a time. Therefore, to create both Windows 8.1 and Windows 10 deployment shares, you will need to run the tool twice.   @@ -114,7 +114,7 @@ The following steps show how you create a deployment share for Windows 10 that If you are unable to connect to the Internet with your deployment server, or if you want to download the Surface drivers and apps separately, you can specify a local source for the driver an app files at the time of deployment share creation. On the **Configure** page of the SDA wizard, select the **Copy from a Local Directory** check box, as shown in Figure 6. The **Download from the Internet** check box will be automatically deselected. Enter the folder location where you have placed the driver and app files in the **Local Path** field, as shown in Figure 6. -**Note**  All of the downloaded driver and applications files must be located in the same folder. The driver and app files do not need to be extracted from the downloaded .zip files. +>**Note:**  All of the downloaded driver and applications files must be located in the same folder. The driver and app files do not need to be extracted from the downloaded .zip files.   @@ -122,7 +122,7 @@ If you are unable to connect to the Internet with your deployment server, or if Figure 6. Specify the Surface driver and app files from a local path -**Note**  The **Copy from a Local Directory** check box is only available in SDA version 1.90.0221 or later. +>**Note:**  The **Copy from a Local Directory** check box is only available in SDA version 1.90.0221 or later.   @@ -130,7 +130,7 @@ Figure 6. Specify the Surface driver and app files from a local path You can use USB media to perform an SDA deployment if your Surface device is unable to boot from the network. For example, if you do not have a Microsoft Surface Ethernet Adapter or Microsoft Surface dock to facilitate network boot (PXE boot). The USB drive produced by following these steps includes a complete copy of the SDA deployment share and can be run on a Surface device without a network connection. -**Note**  The offline media files for the complete SDA deployment share are approximately 9 GB in size. Your USB drive must be at least 9 GB in size. A 16 GB USB drive is recommended. +>**Note:**  The offline media files for the complete SDA deployment share are approximately 9 GB in size. Your USB drive must be at least 9 GB in size. A 16 GB USB drive is recommended.   @@ -144,7 +144,7 @@ Before you can create bootable media files within the MDT Deployment Workbench o 4. **clean** – Removes all configuration from your USB drive. - **Warning**  This step will remove all information from your drive. Verify that your USB drive does not contain any needed data before you perform the **clean** command. + >**Warning:**  This step will remove all information from your drive. Verify that your USB drive does not contain any needed data before you perform the **clean** command.   @@ -162,7 +162,7 @@ Before you can create bootable media files within the MDT Deployment Workbench o Figure 7. Use DiskPart to prepare a USB drive for boot - **Note**  You can format your USB drive with FAT32 from Disk Management, but you must still use DiskPart to set the partition as active for the drive to boot properly. + >**Note:**  You can format your USB drive with FAT32 from Disk Management, but you must still use DiskPart to set the partition as active for the drive to boot properly.   @@ -269,7 +269,7 @@ When you run the task sequence, you will be prompted to provide the following in - A product key, if one is required - **Note**  If you are deploying the same version of Windows as the version that came on your device, no product key is required. + >**Note:**  If you are deploying the same version of Windows as the version that came on your device, no product key is required.   @@ -285,8 +285,7 @@ The **2 – Create Windows Reference Image** task sequence is used to perform a Like the **1 – Deploy Microsoft Surface** task sequence, the **2 – Create Windows Reference Image** task sequence performs a deployment of the unaltered Windows image directly from the installation media. Creation of a reference image should always be performed on a virtual machine. Using a virtual machine as your reference system helps to ensure that the resulting image is compatible with different hardware configurations. -**Note**   -Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and System Center Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information see [Deploy a Windows 10 image using MDT 2013 Update 1](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt). +>**Note:**  Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and System Center Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information see [Deploy a Windows 10 image using MDT 2013 Update 1](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt).   diff --git a/devices/surface/surface-diagnostic-toolkit.md b/devices/surface/surface-diagnostic-toolkit.md index 11b81dff40..61e867468f 100644 --- a/devices/surface/surface-diagnostic-toolkit.md +++ b/devices/surface/surface-diagnostic-toolkit.md @@ -16,7 +16,7 @@ Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the ha The [Microsoft Surface Diagnostic Toolkit](http://go.microsoft.com/fwlink/p/?LinkId=618121) is a small, portable diagnostic tool that runs through a suite of tests to diagnose the hardware of Surface devices. The Microsoft Surface Diagnostic Toolkit executable file is less than 3 MB, which allows it to be distributed through email. It does not require installation, so it can be run directly from a USB stick or over the network. The Microsoft Surface Diagnostic Toolkit walks you through several tests of individual components including the touchscreen, cameras, and sensors. -**Note**  A Surface device must boot into Windows to run the Microsoft Surface Diagnostic Toolkit. The Microsoft Surface Diagnostic Toolkit will run only on the following Surface devices: +>**Note:**  A Surface device must boot into Windows to run the Microsoft Surface Diagnostic Toolkit. The Microsoft Surface Diagnostic Toolkit will run only on the following Surface devices: - Surface Book @@ -32,7 +32,7 @@ The [Microsoft Surface Diagnostic Toolkit](http://go.microsoft.com/fwlink/p/?Lin - Surface Pro -**Note**  Security software and built-in security measures in many email applications and services will block executable files that are transferred through email. To email the Surface Diagnostic Toolkit, attach the .zip archive file as downloaded from the Surface Tools for IT page without extracting it first. You can also create a custom .zip archive that contains the .exe file. (For example, if you want to localize the text as described in the [Localization](#localization) section of this article.) +>**Note:**  Security software and built-in security measures in many email applications and services will block executable files that are transferred through email. To email the Surface Diagnostic Toolkit, attach the .zip archive file as downloaded from the Surface Tools for IT page without extracting it first. You can also create a custom .zip archive that contains the .exe file. (For example, if you want to localize the text as described in the [Localization](#localization) section of this article.) Running the Microsoft Surface Diagnostic Toolkit is a hands-on activity. The test sequence includes several tests that require you to perform actions or observe the outcome of the test, and then click the applicable **Pass** or **Fail** button. Some tests require connectivity to external devices, like an external display. Other tests use the built in Windows troubleshooters. At the end of testing, a visual report of the test results is displayed and you are given the option to save a log file or copy the results to the clipboard. @@ -50,7 +50,7 @@ To run a full set of tests with the Microsoft Surface Diagnostic Toolkit, you sh - External speakers or headphones -**Note**  The Microsoft Surface Diagnostic Toolkit tests verify only the hardware of a Surface device and do not test or resolve issues with the operating system or software. +>**Note:**  The Microsoft Surface Diagnostic Toolkit tests verify only the hardware of a Surface device and do not test or resolve issues with the operating system or software.   @@ -115,7 +115,7 @@ These files and logs are stored in a .zip file saved by the Microsoft Surface Di ### Type Cover test -**Note**  A Surface Type Cover is required for this test. +>**Note:**  A Surface Type Cover is required for this test.   @@ -123,7 +123,7 @@ If a Surface Type Cover is not detected, the test prompts you to connect the Typ ### Integrated keyboard test -**Note**  This test is only applicable to Surface Book and requires that the Surface Book be docked to the keyboard. +>**Note:**  This test is only applicable to Surface Book and requires that the Surface Book be docked to the keyboard.   @@ -131,7 +131,7 @@ This test is essentially the same as the Type Cover test, except the integrated ### Canvas mode battery test -**Note**  This test is only applicable to Surface Book. +>**Note:**  This test is only applicable to Surface Book.   @@ -139,7 +139,7 @@ Depending on which mode Surface Book is in, different batteries are used to powe ### Clipboard mode battery test -**Note**  This test is only applicable to Surface Book. +>**Note:**  This test is only applicable to Surface Book.   @@ -147,7 +147,7 @@ Disconnect the Surface Book from the keyboard to work in clipboard mode. In clip ### Laptop mode battery test -**Note**  This test is only applicable to Surface Book. +>**Note:**  This test is only applicable to Surface Book.   @@ -159,7 +159,7 @@ In this test the battery is discharged for a few seconds and tested for health a ### Discrete graphics (dGPU) test -**Note**  This test is only applicable to Surface Book models with a discrete graphics processor. +>**Note:**  This test is only applicable to Surface Book models with a discrete graphics processor.   @@ -167,7 +167,7 @@ This test will query the device information of current hardware to check for the ### Discrete graphics (dGPU) fan test -**Note**  This test is only applicable to Surface Book models with a discrete graphics processor. +>**Note:**  This test is only applicable to Surface Book models with a discrete graphics processor.   @@ -175,7 +175,7 @@ The discrete graphics processor in the Surface Book includes a separate cooling ### Muscle wire test -**Note**  This test is only applicable to Surface Book. +>**Note:**  This test is only applicable to Surface Book.   @@ -183,7 +183,7 @@ To disconnect the Surface Book from the keyboard, software must instruct the mus ### Dead pixel and display artifacts tests -**Note**  Before you run this test, be sure to clean the screen of dust or smudges. +>**Note:**  Before you run this test, be sure to clean the screen of dust or smudges.   @@ -203,7 +203,7 @@ The Surface touchscreen should detect input across the entire screen of the devi ### Digitizer pen test -**Note**  A Microsoft Surface Pen is required for this test. +>**Note:**  A Microsoft Surface Pen is required for this test.   @@ -223,7 +223,7 @@ This test prompts you to use the volume rocker to turn the volume all the way up ### Micro SD or SD slot test -**Note**  This test requires a micro SD or SD card that is compatible with the slot in your Surface device. +>**Note:**  This test requires a micro SD or SD card that is compatible with the slot in your Surface device.   @@ -235,7 +235,7 @@ This test displays the **Recording** tab of the Sound item in Control Panel. The ### Video out test -**Note**  This test requires an external display with the applicable connection for your Surface device. +>**Note:**  This test requires an external display with the applicable connection for your Surface device.   @@ -243,7 +243,7 @@ Surface devices provide a Mini DisplayPort connection for connecting to an exter ### Bluetooth test -**Note**  This test requires a Bluetooth device. The device must be set to pairing mode or made discoverable to perform this test. +>**Note:**  This test requires a Bluetooth device. The device must be set to pairing mode or made discoverable to perform this test.   @@ -255,7 +255,7 @@ Use this test to verify that the cameras on your Surface device are operating pr ### Speaker test -**Note**  Headphones or external speakers are required to test the headphone jack in this test. +>**Note:**  Headphones or external speakers are required to test the headphone jack in this test.   @@ -263,7 +263,7 @@ This test plays audio over left and right channels respectively, both for the in ### Network test -**Note**  Connect the Surface device to a Wi-Fi network before you run this test. Connections that are made during the test are removed when the test is completed. +>**Note:**  Connect the Surface device to a Wi-Fi network before you run this test. Connections that are made during the test are removed when the test is completed.   @@ -295,7 +295,7 @@ The ambient light sensor is used to automatically adjust screen brightness relat ### Device orientation test -**Note**  Before you run this test, disable rotation lock from the Action Center if enabled. +>**Note:**  Before you run this test, disable rotation lock from the Action Center if enabled.   @@ -307,7 +307,7 @@ This test cycles the screen through brightness levels from 0 percent to 100 perc ### System assessment -**Note**  The Surface device must be connected to AC power before you can run this test. +>**Note:**  The Surface device must be connected to AC power before you can run this test.   @@ -326,7 +326,7 @@ If your Surface device has encountered an error that caused the device to fail o You can run the Microsoft Surface Diagnostic Toolkit from the command line or as part of a script. The tool supports the following arguments: -**Note**  Many of the tests performed by the Microsoft Surface Diagnostic Toolkit require technician interaction. The Microsoft Surface Diagnostic Toolkit cannot run unattended. +>**Note:**  Many of the tests performed by the Microsoft Surface Diagnostic Toolkit require technician interaction. The Microsoft Surface Diagnostic Toolkit cannot run unattended.   @@ -481,7 +481,7 @@ By default, the Microsoft Surface Diagnostic Toolkit is available in English onl 6. Save the SurfaceDiagnosticTool\_v1.0.60.0.locale file. -**Note**  The SurfaceDiganosticTool\_v1.0.60.0.locale file must be located in the same folder and have the same name other than the file extension as the Microsoft Surface Diagnostic Toolkit executable file to use the custom prompt text. The SurfaceDiganosticTool\_v1.0.60.0.locale is an .xml file and must use UTF-8 encoding. +>**Note:**  The SurfaceDiganosticTool\_v1.0.60.0.locale file must be located in the same folder and have the same name other than the file extension as the Microsoft Surface Diagnostic Toolkit executable file to use the custom prompt text. The SurfaceDiganosticTool\_v1.0.60.0.locale is an .xml file and must use UTF-8 encoding.   diff --git a/devices/surface/surface-dock-updater.md b/devices/surface/surface-dock-updater.md index 9bd3933aa6..e54a683fd7 100644 --- a/devices/surface/surface-dock-updater.md +++ b/devices/surface/surface-dock-updater.md @@ -17,7 +17,7 @@ The [Microsoft Surface Dock Updater](http://go.microsoft.com/fwlink/p/?LinkId=61 When you run the Microsoft Surface Dock Updater installer you will be prompted to accept an End User License Agreement (EULA). -**Note**  Updating Surface Dock firmware requires connectivity to the Surface Dock, available only on Surface Pro 3, Surface Pro 4, and Surface Book devices. A Surface Pro 3, Surface Pro 4, or Surface Book is required to successfully install Microsoft Surface Dock Updater. +>**Note:**  Updating Surface Dock firmware requires connectivity to the Surface Dock, available only on Surface Pro 3, Surface Pro 4, and Surface Book devices. A Surface Pro 3, Surface Pro 4, or Surface Book is required to successfully install Microsoft Surface Dock Updater. ## Update a Surface Dock with Microsoft Surface Dock Updater @@ -72,7 +72,7 @@ To update a Surface Dock with Microsoft Surface Dock Updater, follow these steps 9. If you want to update multiple Surface Docks in one sitting, you can click the **Update another Surface Dock** button to begin the process on the next Surface Dock. - **Note**  The LED in the Ethernet port of the dock will blink while the update is in progress. Please wait until the LED stops blinking before you unplug your Surface Dock from power. + >**Note:**  The LED in the Ethernet port of the dock will blink while the update is in progress. Please wait until the LED stops blinking before you unplug your Surface Dock from power.