From 77803dc434f7ce49365f804b16295c23f2705f3a Mon Sep 17 00:00:00 2001 From: jborsecnik Date: Tue, 17 Dec 2019 17:38:22 -0800 Subject: [PATCH 1/3] first pass --- .../windows-autopilot-and-surface-devices.md | 20 ++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/devices/surface/windows-autopilot-and-surface-devices.md b/devices/surface/windows-autopilot-and-surface-devices.md index 6e16d59968..e5604d898a 100644 --- a/devices/surface/windows-autopilot-and-surface-devices.md +++ b/devices/surface/windows-autopilot-and-surface-devices.md @@ -1,5 +1,5 @@ --- -title: Windows Autopilot and Surface Devices +title: Windows Autopilot and Surface devices ms.reviewer: manager: dansimp description: Find out about Windows Autopilot deployment options for Surface devices. @@ -18,21 +18,27 @@ ms.date: 11/26/2019 # Windows Autopilot and Surface devices -Windows Autopilot is a cloud-based deployment technology available in Windows 10. Using Windows Autopilot, you can remotely deploy and configure devices in a zero-touch process right out of the box. Windows Autopilot registered devices are identified over the internet at first boot using a unique device signature, known as a hardware hash, and automatically enrolled and configured using modern management solutions such as Azure Active Directory (AAD) and Mobile Device Management (MDM). +Windows Autopilot is a cloud-based deployment technology in Windows 10. You can use Windows Autopilot to remotely deploy and configure devices in a zero-touch process right out of the box. Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a *hardware hash*. Device are automatically enrolled and configured by using modern management solutions such as Azure Active Directory (AAD) and mobile device management. -With Surface devices, you can choose to register your devices at the time of purchase when purchasing from a Surface partner enabled for Windows Autopilot. New devices can be shipped directly to your end-users and will be automatically enrolled and configured when the units are unboxed and turned on for the first time. This process eliminates need to reimage your devices as part of your deployment process, reducing the work required of your deployment staff and opening up new, agile methods for device management and distribution. +With Surface, you can choose to register your devices at the time of purchase from a Surface partner that's enabled for Windows Autopilot. New devices can be shipped directly to your end-users. The devices will be automatically enrolled and configured when they are unboxed and turned on for the first time. This process eliminates the need to reimage devices as part of deployment, which which allows you to implement new, agile methods for device management and distribution. ## Modern management Autopilot is the recommended deployment option for Surface devices including Surface Pro 7, Surface Laptop 3, and Surface Pro X, which is specifically designed to be deployed with Autopilot. - For the best experience, enroll your Surface devices with the assistance of a Microsoft Cloud Solution Provider. Doing so enables you to manage UEFI firmware settings on Surface devices directly from Intune, eliminating the need to physically touch devices for certificate management. For more information, see [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md). + For the best experience, enroll your Surface devices with the assistance of a Microsoft Cloud Solution Provider. That method allows you to manage UEFI firmware settings on Surface devices directly from Intune, eliminating the need to physically touch devices for certificate management. For more information, see [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md). ## Windows version considerations -Support for broad deployments of Surface devices using Windows Autopilot, including enrollment performed by Surface partners at the time of purchase, requires devices manufactured with or otherwise installed with Windows 10 Version 1709 (Fall Creators Update) or later. These versions support a 4000-byte (4k) hash value to uniquely identify devices for Windows Autopilot that is necessary for deployments at scale. All new Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3 ship with Windows 10 Version 1903 or above. +Broad deployment of Surface devices through Windows Autopilot, including enrollment by Surface partners at the time of purchase, requires Windows 10 Version 1709 (Fall Creators Update) or later. + + These versions support a 4000-byte (4k) hash value to uniquely identify devices for Windows Autopilot that's necessary for deployments at scale. All new Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3, ship with Windows 10 Version 1903 or later. ## Surface partners enabled for Windows Autopilot -Enrolling Surface devices in Windows Autopilot at the time of purchase is performed by select Surface partners that enroll devices on an organization’s behalf. Devices can then be shipped directly to users and configured entirely through the zero-touch process of Windows Autopilot, Azure Active Directory, and Mobile Device Management. -Surface partners enabled for Windows Autopilot include: + +Select Surface partners can enroll Surface devices in Windows Autopilot at the time of purchase for your organization. + +These partners can ship enrolled devices directly to your users. And the devices can be configured entirely through the zero-touch process of Windows Autopilot, Azure AD, and mobile device management. + +Surface partners enabled for Windows Autopilot include: - [ALSO](https://www.also.com/ec/cms5/de_1010/1010_anbieter/microsoft/windows-autopilot/index.jsp) - [Atea](https://www.atea.com/) From 2f510c024ba19f6a9a34322031f688e01500d363 Mon Sep 17 00:00:00 2001 From: jborsecnik Date: Wed, 18 Dec 2019 15:23:27 -0800 Subject: [PATCH 2/3] second pass pass --- .../windows-autopilot-and-surface-devices.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/devices/surface/windows-autopilot-and-surface-devices.md b/devices/surface/windows-autopilot-and-surface-devices.md index e5604d898a..e774a14b45 100644 --- a/devices/surface/windows-autopilot-and-surface-devices.md +++ b/devices/surface/windows-autopilot-and-surface-devices.md @@ -18,27 +18,29 @@ ms.date: 11/26/2019 # Windows Autopilot and Surface devices -Windows Autopilot is a cloud-based deployment technology in Windows 10. You can use Windows Autopilot to remotely deploy and configure devices in a zero-touch process right out of the box. Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a *hardware hash*. Device are automatically enrolled and configured by using modern management solutions such as Azure Active Directory (AAD) and mobile device management. +Windows Autopilot is a cloud-based deployment technology in Windows 10. You can use Windows Autopilot to remotely deploy and configure devices in a zero-touch process right out of the box. -With Surface, you can choose to register your devices at the time of purchase from a Surface partner that's enabled for Windows Autopilot. New devices can be shipped directly to your end-users. The devices will be automatically enrolled and configured when they are unboxed and turned on for the first time. This process eliminates the need to reimage devices as part of deployment, which which allows you to implement new, agile methods for device management and distribution. +Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a *hardware hash*. They're automatically enrolled and configured by using modern management solutions such as Azure Active Directory (AAD) and mobile device management. + +You can register Surface devices at the time of purchase from a Surface partner that's enabled for Windows Autopilot. These partners can ship new devices directly to your users. The devices will be automatically enrolled and configured when they are first turned on. This process eliminates reimaging during deployment, which lets you implement new, agile methods of device management and distribution. ## Modern management -Autopilot is the recommended deployment option for Surface devices including Surface Pro 7, Surface Laptop 3, and Surface Pro X, which is specifically designed to be deployed with Autopilot. +Autopilot is the recommended deployment option for Surface devices including Surface Pro 7, Surface Laptop 3, and Surface Pro X, which is specifically designed to be deployed through Autopilot. - For the best experience, enroll your Surface devices with the assistance of a Microsoft Cloud Solution Provider. That method allows you to manage UEFI firmware settings on Surface devices directly from Intune, eliminating the need to physically touch devices for certificate management. For more information, see [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md). + For the best experience, enroll your Surface devices with the help of a Microsoft Cloud Solution Provider. That method allows you to manage UEFI firmware settings on Surface directly from Intune. It eliminates the need to physically touch devices for certificate management. See [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md) for details. ## Windows version considerations Broad deployment of Surface devices through Windows Autopilot, including enrollment by Surface partners at the time of purchase, requires Windows 10 Version 1709 (Fall Creators Update) or later. - These versions support a 4000-byte (4k) hash value to uniquely identify devices for Windows Autopilot that's necessary for deployments at scale. All new Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3, ship with Windows 10 Version 1903 or later. +These versions support a 4,000-byte (4k) hash value to uniquely identify devices for Windows Autopilot, which is necessary for deployments at scale. All new Surface devices, including Surface Pro 7, Surface Pro X, and Surface Laptop 3, ship with Windows 10 Version 1903 or later. ## Surface partners enabled for Windows Autopilot -Select Surface partners can enroll Surface devices in Windows Autopilot at the time of purchase for your organization. +Select Surface partners can enroll Surface devices in Windows Autopilot at the time of purchase for your organization. These partners can ship enrolled devices directly to your users. And the devices can be configured entirely through the zero-touch process of Windows Autopilot, Azure AD, and mobile device management. -Surface partners enabled for Windows Autopilot include: +Surface partners enabled for Windows Autopilot include: - [ALSO](https://www.also.com/ec/cms5/de_1010/1010_anbieter/microsoft/windows-autopilot/index.jsp) - [Atea](https://www.atea.com/) @@ -53,6 +55,6 @@ Surface partners enabled for Windows Autopilot include: - [Techdata](https://www.techdata.com/) ## Learn more -For more information about Windows Autopilot, refer to: +For more information about Windows Autopilot, see: - [Overview of Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-10-autopilot) - [Windows Autopilot requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements) \ No newline at end of file From 2b735e5c482925c4a3ca42ab7641e017ddc7c966 Mon Sep 17 00:00:00 2001 From: jborsecnik Date: Wed, 18 Dec 2019 16:27:19 -0800 Subject: [PATCH 3/3] proof --- .../windows-autopilot-and-surface-devices.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/devices/surface/windows-autopilot-and-surface-devices.md b/devices/surface/windows-autopilot-and-surface-devices.md index e774a14b45..36283c8d84 100644 --- a/devices/surface/windows-autopilot-and-surface-devices.md +++ b/devices/surface/windows-autopilot-and-surface-devices.md @@ -20,27 +20,25 @@ ms.date: 11/26/2019 Windows Autopilot is a cloud-based deployment technology in Windows 10. You can use Windows Autopilot to remotely deploy and configure devices in a zero-touch process right out of the box. -Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a *hardware hash*. They're automatically enrolled and configured by using modern management solutions such as Azure Active Directory (AAD) and mobile device management. +Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a *hardware hash*. They're automatically enrolled and configured by using modern management solutions such as Azure Active Directory (Azure AD) and mobile device management. You can register Surface devices at the time of purchase from a Surface partner that's enabled for Windows Autopilot. These partners can ship new devices directly to your users. The devices will be automatically enrolled and configured when they are first turned on. This process eliminates reimaging during deployment, which lets you implement new, agile methods of device management and distribution. ## Modern management -Autopilot is the recommended deployment option for Surface devices including Surface Pro 7, Surface Laptop 3, and Surface Pro X, which is specifically designed to be deployed through Autopilot. +Autopilot is the recommended deployment option for Surface devices, including Surface Pro 7, Surface Laptop 3, and Surface Pro X, which is specifically designed for deployment through Autopilot. - For the best experience, enroll your Surface devices with the help of a Microsoft Cloud Solution Provider. That method allows you to manage UEFI firmware settings on Surface directly from Intune. It eliminates the need to physically touch devices for certificate management. See [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md) for details. + It's best to enroll your Surface devices with the help of a Microsoft Cloud Solution Provider. This step allows you to manage UEFI firmware settings on Surface directly from Intune. It eliminates the need to physically touch devices for certificate management. See [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md) for details. ## Windows version considerations Broad deployment of Surface devices through Windows Autopilot, including enrollment by Surface partners at the time of purchase, requires Windows 10 Version 1709 (Fall Creators Update) or later. -These versions support a 4,000-byte (4k) hash value to uniquely identify devices for Windows Autopilot, which is necessary for deployments at scale. All new Surface devices, including Surface Pro 7, Surface Pro X, and Surface Laptop 3, ship with Windows 10 Version 1903 or later. +These Windows versions support a 4,000-byte (4k) hash value that uniquely identifies devices for Windows Autopilot, which is necessary for deployments at scale. All new Surface devices, including Surface Pro 7, Surface Pro X, and Surface Laptop 3, ship with Windows 10 Version 1903 or later. ## Surface partners enabled for Windows Autopilot -Select Surface partners can enroll Surface devices in Windows Autopilot at the time of purchase for your organization. +Select Surface partners can enroll Surface devices in Windows Autopilot for you at the time of purchase. They can also ship enrolled devices directly to your users. The devices can be configured entirely through a zero-touch process by using Windows Autopilot, Azure AD, and mobile device management. -These partners can ship enrolled devices directly to your users. And the devices can be configured entirely through the zero-touch process of Windows Autopilot, Azure AD, and mobile device management. - -Surface partners enabled for Windows Autopilot include: +Surface partners that are enabled for Windows Autopilot include: - [ALSO](https://www.also.com/ec/cms5/de_1010/1010_anbieter/microsoft/windows-autopilot/index.jsp) - [Atea](https://www.atea.com/)