deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-21 21:33:38 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #512 from MicrosoftDocs/autopilot

Browse Source 
Autopilot updates
This commit is contained in:
Dani Halfin
2019-06-19 14:23:17 -07:00
committed by GitHub
parent b98d5051a5 3c05ed1630
commit d4c56d0800
5 changed files with 14 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md
View File

@ -40,9 +40,8 @@ The Upgrade Readiness workflow steps you through the discovery and rationalizati
## **Related topics**
[Upgrade Readiness architecture](upgrade-readiness-architecture.md)<BR>
[Upgrade Readiness requirements](upgrade-readiness-requirements.md)<BR>
[Upgrade Readiness release notes](upgrade-readiness-requirements.md#important-information-about-this-release)<BR>
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)<BR>
[Use Upgrade Readiness to manage Windows upgrades](use-upgrade-readiness-to-manage-windows-upgrades.md)<BR>
[Troubleshoot Upgrade Readiness](troubleshoot-upgrade-readiness.md)<BR>
[Upgrade Readiness architecture](upgrade-readiness-architecture.md)<br>
[Upgrade Readiness requirements](upgrade-readiness-requirements.md)<br>
[Upgrade Readiness release notes](upgrade-readiness-requirements.md#important-information-about-this-release)<br>
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)<br>
[Use Upgrade Readiness to manage Windows upgrades](use-upgrade-readiness-to-manage-windows-upgrades.md)

2
windows/deployment/upgrade/upgrade-readiness-additional-insights.md
View File

@ -93,4 +93,4 @@ Office add-ins provides a list of the Microsoft Office add-ins in your environme
## Related topics
[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
[Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md)

4
windows/deployment/windows-autopilot/existing-devices.md
View File

@ -91,7 +91,7 @@ See the following examples.
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON
```
See the following sample output:
See the following sample output: (use the horizontal scroll bar at the bottom to view long lines)
<pre style="overflow-y: visible">
PS C:\> Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON
{
@ -124,7 +124,7 @@ See the following examples.
| CloudAssignedDeviceName (string, optional) | The name automatically assigned to the computer. This follows the naming pattern convention that can be configured in Intune as part of the Autopilot profile, or can specify an explicit name to use. |
5. The Autopilot profile must be saved as a JSON file in ASCII or ANSI format. Windows PowerShell defaults to Unicode format, so if you attempt to redirect output of the commands to a file, you must also specify the file format. For example, to save the file in ASCII format using Windows PowerShell, you can create a directory (ex: c:\Autopilot) and save the profile as shown below:
5. The Autopilot profile must be saved as a JSON file in ASCII or ANSI format. Windows PowerShell defaults to Unicode format, so if you attempt to redirect output of the commands to a file, you must also specify the file format. For example, to save the file in ASCII format using Windows PowerShell, you can create a directory (ex: c:\Autopilot) and save the profile as shown below: (use the horizontal scroll bar at the bottom if needed to view the entire command string)
```
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON | Out-File c:\Autopilot\AutopilotConfigurationFile.json -Encoding ASCII

7
windows/deployment/windows-autopilot/self-deploying.md
View File

@ -1,5 +1,5 @@
---
title: Windows Autopilot Self-Deploying mode (Preview)
title: Windows Autopilot Self-Deploying mode
description: Windows Autopilot deployment
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
ms.reviewer: mniehaus
@ -15,10 +15,9 @@ ms.collection: M365-modern-desktop
ms.topic: article
---
# Windows Autopilot Self-Deploying mode
**Applies to: Windows 10, version 1809 or later**
**Applies to: Windows 10, version 1903 or later**
Windows Autopilot self-deploying mode enables a device to be deployed with little to no user interaction. For devices with an Ethernet connection, no user interaction is required; for devices connected via Wi-fi, no interaction is required after making the Wi-fi connection (choosing the language, locale, and keyboard, then making a network connection).
@ -39,7 +38,7 @@ Self-deploying mode is designed to deploy Windows 10 as a kiosk, digital signage
Because self-deploying mode uses a device’s TPM 2.0 hardware to authenticate the device into an organization’s Azure AD tenant, devices without TPM 2.0 cannot be used with this mode. The devices must also support TPM device attestation. (All newly-manufactured Windows devices should meet these requirements.)
>[!NOTE]
>If you attempt a self-deploying mode deployment on a device that does not have support TPM 2.0 or on a virtual machine, the process will fail when verifying the device with an 0x800705B4 timeout error. (Hyper-V virtual TPMs are not supported.)
>If you attempt a self-deploying mode deployment on a device that does not have support TPM 2.0 or on a virtual machine, the process will fail when verifying the device with an 0x800705B4 timeout error (Hyper-V virtual TPMs are not supported).. Also note that Window 10, version 1903 or later is required to use self-deploying mode due to issues with TPM device attestation in Windows 10, version 1809.
In order to display an organization-specific logo and organization name during the Autopilot process, Azure Active Directory Company Branding needs to be configured with the images and text that should be displayed. See [Quickstart: Add company branding to your sign-in page in Azure AD](https://docs.microsoft.com/azure/active-directory/fundamentals/customize-branding) for more details.

3
windows/deployment/windows-autopilot/windows-autopilot-whats-new.md
View File

@ -42,6 +42,9 @@ Windows Autopilot [self-deploying mode](self-deploying.md) enables a zero touch
You can utilize Windows Autopilot self-deploying mode to register the device to an AAD tenant, enroll in your organization’s MDM provider, and provision policies and applications, all with no user authentication or user interaction required.
>[!NOTE]
>Window 10, version 1903 or later is required to use self-deploying mode due to issues with TPM device attestation in Windows 10, version 1809.
## Related topics
[What's new in Microsoft Intune](https://docs.microsoft.com/intune/whats-new)<br>