mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Merge branch 'public' into master
This commit is contained in:
Dani Halfin
GitHub
@ -1,43 +1,43 @@
|
||||
---
|
||||
title: Windows Autopilot support
|
||||
description: Support information for Windows Autopilot
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: low
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.date: 10/31/2018
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows Autopilot support information
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
The following table displays support information for the Windows Autopilot program.
|
||||
|
||||
Before contacting the resources listed below for Windows Autopilot-related issues, check the [Windows Autopilot FAQ](autopilot-faq.md).
|
||||
|
||||
|
||||
| Audience | Support contact |
|
||||
|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| OEM or Channel Partner registering devices as a CSP (via MPC) | Use the help resources available in MPC. Whether you are a named partner or a channel partner (distributor, reseller, SI, etc.), if you’re a CSP registering Autopilot devices through MPC (either manually or through the MPC API), your first-line of support should be the help resources within MPC. |
|
||||
| OEM registering devices using OEM Direct API | Contact MSOEMOPS@microsoft.com. Response time depends on priority: <br>Low – 120 hours <br>Normal – 72 hours <br>High – 24 hours <br>Immediate – 4 hours |
|
||||
| Partners with a Partner Technology Strategist (PTS) | If you have a PTS (whether you’re a CSP or not), you may first try working through your account’s specific Partner Technology Strategist (PTS). |
|
||||
| Partners with an Ecosystem PM | If you have an Ecosystem PM (whether you’re a CSP or not), you may first try working through your account’s specific Ecosystem PM, especially for technical issues. To learn more about Ecosystem PMs and the services they offer, contact epsoinfo@microsoft.com. |
|
||||
| Enterprise customers | Contact your Technical Account Manager (TAM), or Account Technology Strategist (ATS), or Customer Service Support (CSS) representative. |
|
||||
| End-user | Contact your IT administrator. |
|
||||
| Microsoft Partner Center (MPC) users | Use the [help resources](https://partner.microsoft.com/support) available in MPC. |
|
||||
| Microsoft Store for Business (MSfB) users | Use the help resources available in MSfB. |
|
||||
| Intune users | From the Microsoft Azure portal, click [Help + support](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview). |
|
||||
| Microsoft 365 Business | Support is accessible directly through the Microsoft 365 Business portal when logged in: https://support.microsoft.com/en-us. |
|
||||
| Queries relating to MDA testing | Contact MDAHelp@microsoft.com. |
|
||||
| All other queries, or when unsure who to contact | Contact msoemops@microsoft.com. |
|
||||
|
||||
---
|
||||
title: Windows Autopilot support
|
||||
description: Support information for Windows Autopilot
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: low
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.date: 10/31/2018
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows Autopilot support information
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
The following table displays support information for the Windows Autopilot program.
|
||||
|
||||
Before contacting the resources listed below for Windows Autopilot-related issues, check the [Windows Autopilot FAQ](autopilot-faq.md).
|
||||
|
||||
|
||||
| Audience | Support contact |
|
||||
|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| OEM or Channel Partner registering devices as a CSP (via MPC) | Use the help resources available in MPC. Whether you are a named partner or a channel partner (distributor, reseller, SI, etc.), if you’re a CSP registering Autopilot devices through MPC (either manually or through the MPC API), your first-line of support should be the help resources within MPC. |
|
||||
| OEM registering devices using OEM Direct API | Contact MSOEMOPS@microsoft.com. Response time depends on priority: <br>Low – 120 hours <br>Normal – 72 hours <br>High – 24 hours <br>Immediate – 4 hours |
|
||||
| Partners with a Partner Technology Strategist (PTS) | If you have a PTS (whether you’re a CSP or not), you may first try working through your account’s specific Partner Technology Strategist (PTS). |
|
||||
| Partners with an Ecosystem PM | If you have an Ecosystem PM (whether you’re a CSP or not), you may first try working through your account’s specific Ecosystem PM, especially for technical issues. To learn more about Ecosystem PMs and the services they offer, contact epsoinfo@microsoft.com. |
|
||||
| Enterprise customers | Contact your Technical Account Manager (TAM), or Account Technology Strategist (ATS), or Customer Service Support (CSS) representative. |
|
||||
| End-user | Contact your IT administrator. |
|
||||
| Microsoft Partner Center (MPC) users | Use the [help resources](https://partner.microsoft.com/support) available in MPC. |
|
||||
| Microsoft Store for Business (MSfB) users | Use the help resources available in MSfB. |
|
||||
| Intune users | From the Microsoft Azure portal, click [Help + support](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview). |
|
||||
| Microsoft 365 Business | Support is accessible directly through the Microsoft 365 Business portal when logged in: https://support.microsoft.com/en-us. |
|
||||
| Queries relating to MDA testing | Contact MDAHelp@microsoft.com. |
|
||||
| All other queries, or when unsure who to contact | Contact msoemops@microsoft.com. |
|
||||
|
||||
|
||||
@ -1,315 +1,317 @@
|
||||
---
|
||||
title: Windows Autopilot for existing devices
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows Autopilot for existing devices
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
Modern desktop deployment with Windows Autopilot enables you to easily deploy the latest version of Windows 10 to your existing devices. The apps you need for work can be automatically installed. Your work profile is synchronized, so you can resume working right away.
|
||||
|
||||
This topic describes how to convert Windows 7 or Windows 8.1 domain-joined computers to Windows 10 devices joined to either Azure Active Directory or Active Directory (Hybrid Azure AD Join) by using Windows Autopilot.
|
||||
|
||||
>[!NOTE]
|
||||
>Windows Autopilot for existing devices only supports user-driven Azure Active Directory and Hybrid Azure AD profiles. Self-deploying profiles are not supported.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- System Center Configuration Manager Current Branch (1806) OR System Center Configuration Manager Technical Preview (1808)
|
||||
- The [Windows ADK](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) 1803 or later
|
||||
- Note: Config Mgr 1806 or later is required to [support](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk) the Windows ADK 1809.
|
||||
- Assigned Microsoft Intune Licenses
|
||||
- Azure Active Directory Premium
|
||||
- Windows 10 version 1809 or later imported into Config Mgr as an Operating System Image
|
||||
|
||||
## Procedures
|
||||
|
||||
### Configure the Enrollment Status Page (optional)
|
||||
|
||||
If desired, you can set up an [enrollment status page](https://docs.microsoft.com/windows/deployment/windows-autopilot/enrollment-status) for Autopilot using Intune.
|
||||
|
||||
To enable and configure the enrollment and status page:
|
||||
|
||||
1. Open [Intune in the Azure portal](https://aka.ms/intuneportal).
|
||||
2. Access **Intune > Device enrollment > Windows enrollment** and [Set up an enrollment status page](https://docs.microsoft.com/intune/windows-enrollment-status).
|
||||
3. Access **Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune** and [Configure automatic MDM enrollment](https://docs.microsoft.com/sccm/mdm/deploy-use/enroll-hybrid-windows#enable-windows-10-automatic-enrollment) and configure the MDM user scope for some or all users.
|
||||
|
||||
See the following examples.
|
||||
|
||||
<br><br>
|
||||
|
||||
|
||||
### Create the JSON file
|
||||
|
||||
>[!TIP]
|
||||
>To run the following commands on a computer running Windows Server 2012/2012 R2 or Windows 7/8.1, you must first download and install the [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=54616).
|
||||
|
||||
1. On an Internet connected Windows PC or Server open an elevated Windows PowerShell command window
|
||||
2. Enter the following lines to install the necessary modules
|
||||
|
||||
#### Install required modules
|
||||
|
||||
```powershell
|
||||
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
|
||||
Install-Module AzureAD -Force
|
||||
Install-Module WindowsAutopilotIntune -Force
|
||||
```
|
||||
|
||||
3. Enter the following lines and provide Intune administrative credentials
|
||||
- In the following command, replace the example user principal name for Azure authentication (admin@M365x373186.onmicrosoft.com) with your user account. Be sure that the user account you specify has sufficient administrative rights.
|
||||
|
||||
```powershell
|
||||
Connect-AutopilotIntune -user admin@M365x373186.onmicrosoft.com
|
||||
```
|
||||
The password for your account will be requested using a standard Azure AD form. Type your password and then click **Sign in**.
|
||||
<br>See the following example:
|
||||
|
||||
|
||||
|
||||
If this is the first time you’ve used the Intune Graph APIs, you’ll also be prompted to enable read and write permissions for Microsoft Intune PowerShell. To enable these permissions:
|
||||
- Select **Consent on behalf or your organization**
|
||||
- Click **Accept**
|
||||
|
||||
4. Next, retrieve and display all the Autopilot profiles available in the specified Intune tenant in JSON format:
|
||||
|
||||
#### Retrieve profiles in Autopilot for existing devices JSON format
|
||||
|
||||
```powershell
|
||||
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON
|
||||
```
|
||||
|
||||
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
|
||||
{
|
||||
"CloudAssignedTenantId": "1537de22-988c-4e93-b8a5-83890f34a69b",
|
||||
"CloudAssignedForcedEnrollment": 1,
|
||||
"Version": 2049,
|
||||
"Comment_File": "Profile Autopilot Profile",
|
||||
"CloudAssignedAadServerData": "{\"ZeroTouchConfig\":{\"CloudAssignedTenantUpn\":\"\",\"ForcedEnrollment\":1,\"CloudAssignedTenantDomain\":\"M365x373186.onmicrosoft.com\"}}",
|
||||
"CloudAssignedTenantDomain": "M365x373186.onmicrosoft.com",
|
||||
"CloudAssignedDomainJoinMethod": 0,
|
||||
"CloudAssignedOobeConfig": 28,
|
||||
"ZtdCorrelationId": "7F9E6025-1E13-45F3-BF82-A3E8C5B59EAC"
|
||||
}</pre>
|
||||
|
||||
Each profile is encapsulated within braces **{ }**. In the previous example, a single profile is displayed.
|
||||
|
||||
See the following table for a description of properties used in the JSON file.
|
||||
|
||||
|
||||
| Property | Description |
|
||||
|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Version (number, optional) | The version number that identifies the format of the JSON file. For Windows 10 1809, the version specified must be 2049. |
|
||||
| CloudAssignedTenantId (guid, required) | The Azure Active Directory tenant ID that should be used. This is the GUID for the tenant, and can be found in properties of the tenant. The value should not include braces. |
|
||||
| CloudAssignedTenantDomain (string, required) | The Azure Active Directory tenant name that should be used, e.g. tenant.onmicrosoft.com. |
|
||||
| CloudAssignedOobeConfig (number, required) | This is a bitmap that shows which Autopilot settings were configured. Values include: SkipCortanaOptIn = 1, OobeUserNotLocalAdmin = 2, SkipExpressSettings = 4, SkipOemRegistration = 8, SkipEula = 16 |
|
||||
| CloudAssignedDomainJoinMethod (number, required) | This property specifies whether the device should join Azure Active Directory or Active Directory (Hybrid Azure AD Join). Values include: Active AD Join = 0, Hybrid Azure AD Join = 1 |
|
||||
| CloudAssignedForcedEnrollment (number, required) | Specifies that the device should require AAD Join and MDM enrollment. <br>0 = not required, 1 = required. |
|
||||
| ZtdCorrelationId (guid, required) | A unique GUID (without braces) that will be provided to Intune as part of the registration process. ZtdCorrelationId will be included in enrollment message as “OfflineAutoPilotEnrollmentCorrelator”. This attribute will be present only if the enrollment is taking place on a device registered with Zero Touch Provisioning via offline registration. |
|
||||
| CloudAssignedAadServerData (encoded JSON string, required) | An embedded JSON string used for branding. It requires AAD corp branding enabled. <br> Example value: "CloudAssignedAadServerData": "{\"ZeroTouchConfig\":{\"CloudAssignedTenantUpn\":\"\",\"CloudAssignedTenantDomain\":\"tenant.onmicrosoft.com\"}}" |
|
||||
| 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: (use the horizontal scroll bar at the bottom if needed to view the entire command string)
|
||||
|
||||
```powershell
|
||||
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON | Out-File c:\Autopilot\AutopilotConfigurationFile.json -Encoding ASCII
|
||||
```
|
||||
**IMPORTANT**: The file name must be named **AutopilotConfigurationFile.json** in addition to being encoded as ASCII/ANSI.
|
||||
|
||||
If preferred, you can save the profile to a text file and edit in Notepad. In Notepad, when you choose **Save as** you must select Save as type: **All Files** and choose ANSI from the drop-down list next to **Encoding**. See the following example.
|
||||
|
||||
|
||||
|
||||
After saving the file, move the file to a location suitable as an SCCM package source.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Multiple JSON profile files can be used, but each must be named **AutopilotConfigurationFile.json** in order for OOBE to follow the Autopilot experience. The file also must be encoded as ANSI. <br><br>**Saving the file with Unicode or UTF-8 encoding or saving it with a different file name will cause Windows 10 OOBE to not follow the Autopilot experience**.<br>
|
||||
|
||||
|
||||
### Create a package containing the JSON file
|
||||
|
||||
1. In Configuration Manager, navigate to **\Software Library\Overview\Application Management\Packages**
|
||||
2. On the ribbon, click **Create Package**
|
||||
3. In the **Create Package and Program Wizard** enter the following **Package** and **Program Type** details:<br>
|
||||
- <u>Name</u>: **Autopilot for existing devices config**
|
||||
- Select the **This package contains source files** checkbox
|
||||
- <u>Source folder</u>: Click **Browse** and specify a UNC path containing the AutopilotConfigurationFile.json file.
|
||||
- Click **OK** and then click **Next**.
|
||||
- <u>Program Type</u>: **Do not create a program**
|
||||
4. Click **Next** twice and then click **Close**.
|
||||
|
||||
**NOTE**: If you change user-driven Autopilot profile settings in Intune at a later date, you must also update the JSON file and redistribute the associated Config Mgr package.
|
||||
|
||||
### Create a target collection
|
||||
|
||||
>[!NOTE]
|
||||
>You can also choose to reuse an existing collection
|
||||
|
||||
1. Navigate to **\Assets and Compliance\Overview\Device Collections**
|
||||
2. On the ribbon, click **Create** and then click **Create Device Collection**
|
||||
3. In the **Create Device Collection Wizard** enter the following **General** details:
|
||||
- <u>Name</u>: **Autopilot for existing devices collection**
|
||||
- Comment: (optional)
|
||||
- <u>Limiting collection</u>: Click **Browse** and select **All Systems**
|
||||
|
||||
>[!NOTE]
|
||||
>You can optionally choose to use an alternative collection for the limiting collection. The device to be upgraded must be running the ConfigMgr agent in the collection that you select.
|
||||
|
||||
4. Click **Next**, then enter the following **Membership Rules** details:
|
||||
- Click **Add Rule** and specify either a direct or query based collection rule to add the target test Windows 7 devices to the new collection.
|
||||
- For example, if the hostname of the computer to be wiped and reloaded is PC-01 and you wish to use Name as the attribute, click **Add Rule > Direct Rule > (wizard opens) > Next** and then enter **PC-01** next to **Value**. Click **Next** and then choose **PC-01** under **Resources**. See the following examples.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Continue creating the device collection with the default settings:
|
||||
- Use incremental updates for this collection: not selected
|
||||
- Schedule a full update on this collection: default
|
||||
- Click **Next** twice and then click **Close**
|
||||
|
||||
### Create an Autopilot for existing devices Task Sequence
|
||||
|
||||
>[!TIP]
|
||||
>The next procedure requires a boot image for Windows 10 1803 or later. Review your available boot images in the Configuration Manager conole under **Software Library\Overview\Operating Systems\Boot images** and verify that the **OS Version** is 10.0.17134.1 (Windows 10 version 1803) or later.
|
||||
|
||||
1. In the Configuration Manager console, navigate to **\Software Library\Overview\Operating Systems\Task Sequences**
|
||||
2. On the Home ribbon, click **Create Task Sequence**
|
||||
3. Select **Install an existing image package** and then click **Next**
|
||||
4. In the Create Task Sequence Wizard enter the following details:
|
||||
- <u>Task sequence name</u>: **Autopilot for existing devices**
|
||||
- <u>Boot Image</u>: Click **Browse** and select a Windows 10 boot image (1803 or later)
|
||||
- Click **Next**, and then on the Install Windows page click **Browse** and select a Windows 10 **Image package** and **Image Index**, version 1803 or later.
|
||||
- Select the **Partition and format the target computer before installing the operating system** checkbox.
|
||||
- Select or clear **Configure task sequence for use with Bitlocker** checkbox. This is optional.
|
||||
- <u>Product Key</u> and <u>Server licensing mode</u>: Optionally enter a product key and server licencing mode.
|
||||
- <u>Randomly generate the local administrator password and disable the account on all support platforms (recommended)</u>: Optional.
|
||||
- <u>Enable the account and specify the local administrator password</u>: Optional.
|
||||
- Click **Next**, and then on the Configure Network page choose **Join a workgroup** and specify a name (ex: workgroup) next to **Workgroup**.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The Autopilot for existing devices task sequence will run the **Prepare Windows for capture** action which calls the System Preparation Tool (syeprep). This action will fail if the target machine is joined to a domain.
|
||||
|
||||
5. Click **Next** and then click **Next** again to accept the default settings on the Install Configuration Manager page.
|
||||
6. On the State Migration page, enter the following details:
|
||||
- Clear the **Capture user settings and files** checkbox.
|
||||
- Clear the **Capture network settings** checkbox.
|
||||
- Clear the **Capture Microsoft Windows settings** checkbox.
|
||||
- Click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Autopilot for existing devices task sequence will result in an Azure Active Directory Domain (AAD) joined device. The User State Migration Toolkit (USMT) does not support AAD joined or hybrid AAD joined devices.
|
||||
|
||||
7. On the Include Updates page, choose one of the three available options. This selection is optional.
|
||||
8. On the Install applications page, add applications if desired. This is optional.
|
||||
9. Click **Next**, confirm settings, click **Next** and then click **Close**.
|
||||
10. Right click on the Autopilot for existing devices task sequence and click **Edit**.
|
||||
11. In the Task Sequence Editor under the **Install Operating System** group, click the **Apply Windows Settings** action.
|
||||
12. Click **Add** then click **New Group**.
|
||||
13. Change the group **Name** from **New Group** to **Autopilot for existing devices config**.
|
||||
14. Click **Add**, point to **General**, then click **Run Command Line**.
|
||||
15. Verify that the **Run Command Line** step is nested under the **Autopilot for existing devices config** group.
|
||||
16. Change the **Name** to **Apply Autopilot for existing devices config file** and paste the following into the **Command line** text box, and then click **Apply**:
|
||||
```
|
||||
cmd.exe /c xcopy AutopilotConfigurationFile.json %OSDTargetSystemDrive%\windows\provisioning\Autopilot\ /c
|
||||
```
|
||||
- **AutopilotConfigurationFile.json** must be the name of the JSON file present in the Autopilot for existing devices package created earlier.
|
||||
|
||||
17. In the **Apply Autopilot for existing devices config file** step, select the **Package** checkbox and then click **Browse**.
|
||||
18. Select the **Autopilot for existing devices config** package created earlier and click **OK**. An example is displayed at the end of this section.
|
||||
19. Under the **Setup Operating System** group, click the **Setup Windows and Configuration Manager** task.
|
||||
20. Click **Add** and then click **New Group**.
|
||||
21. Change **Name** from **New Group** to **Prepare Device for Autopilot**
|
||||
22. Verify that the **Prepare Device for Autopilot** group is the very last step in the task sequence. Use the **Move Down** button if necessary.
|
||||
23. With the **Prepare device for Autopilot** group selected, click **Add**, point to **Images** and then click **Prepare ConfigMgr Client for Capture**.
|
||||
24. Add a second step by clicking **Add**, pointing to **Images**, and clicking **Prepare Windows for Capture**. Use the following settings in this step:
|
||||
- <u>Automatically build mass storage driver list</u>: **Not selected**
|
||||
- <u>Do not reset activation flag</u>: **Not selected**
|
||||
- <u>Shutdown the computer after running this action</u>: **Optional**
|
||||
|
||||
|
||||
|
||||
25. Click **OK** to close the Task Sequence Editor.
|
||||
|
||||
### Deploy Content to Distribution Points
|
||||
|
||||
Next, ensure that all content required for the task sequence is deployed to distribution points.
|
||||
|
||||
1. Right click on the **Autopilot for existing devices** task sequence and click **Distribute Content**.
|
||||
2. Click **Next**, **Review the content to distribute** and then click **Next**.
|
||||
3. On the Specify the content distribution page click **Add** to specify either a **Distribution Point** or **Distribution Point Group**.
|
||||
4. On the a Add Distribution Points or Add Distribution Point Groups wizard specify content destinations that will allow the JSON file to be retrieved when the task sequence is run.
|
||||
5. When you are finished specifying content distribution, click **Next** twice then click **Close**.
|
||||
|
||||
### Deploy the OS with Autopilot Task Sequence
|
||||
|
||||
1. Right click on the **Autopilot for existing devices** task sequence and then click **Deploy**.
|
||||
2. In the Deploy Software Wizard enter the following **General** and **Deployment Settings** details:
|
||||
- <u>Task Sequence</u>: **Autopilot for existing devices**.
|
||||
- <u>Collection</u>: Click **Browse** and then select **Autopilot for existing devices collection** (or another collection you prefer).
|
||||
- Click **Next** to specify **Deployment Settings**.
|
||||
- <u>Action</u>: **Install**.
|
||||
- <u>Purpose</u>: **Available**. You can optionally select **Required** instead of **Available**. This is not recommended during the test owing to the potential impact of inadvertent configurations.
|
||||
- <u>Make available to the following</u>: **Only Configuration Manager Clients**. Note: Choose the option here that is relevant for the context of your test. If the target client does not have the Configuration Manager agent or Windows installed, you will need to select an option that includes PXE or Boot Media.
|
||||
- Click **Next** to specify **Scheduling** details.
|
||||
- <u>Schedule when this deployment will become available</u>: Optional
|
||||
- <u>Schedule when this deployment will expire</u>: Optional
|
||||
- Click **Next** to specify **User Experience** details.
|
||||
- <u>Show Task Sequence progress</u>: Selected.
|
||||
- <u>Software Installation</u>: Not selected.
|
||||
- <u>System restart (if required to complete the installation)</u>: Not selected.
|
||||
- <u>Commit changed at deadline or during a maintenance windows (requires restart)</u>: Optional.
|
||||
- <u>Allow task sequence to be run for client on the Internet</u>: Optional
|
||||
- Click **Next** to specify **Alerts** details.
|
||||
- <u>Create a deployment alert when the threshold is higher than the following</u>: Optional.
|
||||
- Click **Next** to specify **Distribution Points** details.
|
||||
- <u>Deployment options</u>: **Download content locally when needed by the running task sequence**.
|
||||
- <u>When no local distribution point is available use a remote distribution point</u>: Optional.
|
||||
- <u>Allow clients to use distribution points from the default site boundary group</u>: Optional.
|
||||
- Click **Next**, confirm settings, click **Next**, and then click **Close**.
|
||||
|
||||
### Complete the client installation process
|
||||
|
||||
1. Open the Software Center on the target Windows 7 or Windows 8.1 client computer. You can do this by clicking Start and then typing **software** in the search box, or by typing the following at a Windows PowerShell or command prompt:
|
||||
|
||||
```
|
||||
C:\Windows\CCM\SCClient.exe
|
||||
```
|
||||
|
||||
2. In the software library, select **Autopilot for existing devices** and click **Install**. See the following example:
|
||||
|
||||
|
||||
|
||||
|
||||
The Task Sequence will download content, reboot, format the drives and install Windows 10. The device will then proceed to be prepared for Autopilot. Once the task sequence has completed the device will boot into OOBE and provide an Autopilot experience.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>If joining devices to Active Directory (Hybrid Azure AD Join), it is necessary to create a Domain Join device configuration profile that is targeted to "All Devices" (since there is no Azure Active Directory device object for the computer to do group-based targeting). See [User-driven mode for hybrid Azure Active Directory join](https://docs.microsoft.com/windows/deployment/windows-autopilot/user-driven#user-driven-mode-for-hybrid-azure-active-directory-join) for more information.
|
||||
|
||||
### Register the device for Windows Autopilot
|
||||
|
||||
Devices provisioned through Autopilot will only receive the guided OOBE Autopilot experience on first boot. Once updated to Windows 10, the device should be registered to ensure a continued Autopilot experience in the event of PC reset. You can enable automatic registration for an assigned group using the **Convert all targeted devices to Autopilot** setting. For more information, see [Create an Autopilot deployment profile](https://docs.microsoft.com/intune/enrollment-autopilot#create-an-autopilot-deployment-profile).
|
||||
|
||||
Also see [Adding devices to Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/add-devices).
|
||||
|
||||
## Speeding up the deployment process
|
||||
|
||||
---
|
||||
title: Windows Autopilot for existing devices
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows Autopilot for existing devices
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
Modern desktop deployment with Windows Autopilot enables you to easily deploy the latest version of Windows 10 to your existing devices. The apps you need for work can be automatically installed. Your work profile is synchronized, so you can resume working right away.
|
||||
|
||||
This topic describes how to convert Windows 7 or Windows 8.1 domain-joined computers to Windows 10 devices joined to either Azure Active Directory or Active Directory (Hybrid Azure AD Join) by using Windows Autopilot.
|
||||
|
||||
>[!NOTE]
|
||||
>Windows Autopilot for existing devices only supports user-driven Azure Active Directory and Hybrid Azure AD profiles. Self-deploying profiles are not supported.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- System Center Configuration Manager Current Branch (1806) OR System Center Configuration Manager Technical Preview (1808)
|
||||
- The [Windows ADK](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) 1803 or later
|
||||
- Note: Config Mgr 1806 or later is required to [support](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk) the Windows ADK 1809.
|
||||
- Assigned Microsoft Intune Licenses
|
||||
- Azure Active Directory Premium
|
||||
- Windows 10 version 1809 or later imported into Config Mgr as an Operating System Image
|
||||
- **Important**: See [Known issues](known-issues.md) if you are using Windows 10 1903 with Configuration Manager’s built-in **Windows Autopilot existing device** task sequence template. Currently, one of the steps in this task sequence must be edited to work properly with Windows 10, version 1903.
|
||||
|
||||
## Procedures
|
||||
|
||||
### Configure the Enrollment Status Page (optional)
|
||||
|
||||
If desired, you can set up an [enrollment status page](https://docs.microsoft.com/windows/deployment/windows-autopilot/enrollment-status) for Autopilot using Intune.
|
||||
|
||||
To enable and configure the enrollment and status page:
|
||||
|
||||
1. Open [Intune in the Azure portal](https://aka.ms/intuneportal).
|
||||
2. Access **Intune > Device enrollment > Windows enrollment** and [Set up an enrollment status page](https://docs.microsoft.com/intune/windows-enrollment-status).
|
||||
3. Access **Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune** and [Configure automatic MDM enrollment](https://docs.microsoft.com/sccm/mdm/deploy-use/enroll-hybrid-windows#enable-windows-10-automatic-enrollment) and configure the MDM user scope for some or all users.
|
||||
|
||||
See the following examples.
|
||||
|
||||
<br><br>
|
||||
|
||||
|
||||
### Create the JSON file
|
||||
|
||||
>[!TIP]
|
||||
>To run the following commands on a computer running Windows Server 2012/2012 R2 or Windows 7/8.1, you must first download and install the [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=54616).
|
||||
|
||||
1. On an Internet connected Windows PC or Server open an elevated Windows PowerShell command window
|
||||
2. Enter the following lines to install the necessary modules
|
||||
|
||||
#### Install required modules
|
||||
|
||||
```powershell
|
||||
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
|
||||
Install-Module AzureAD -Force
|
||||
Install-Module WindowsAutopilotIntune -Force
|
||||
```
|
||||
|
||||
3. Enter the following lines and provide Intune administrative credentials
|
||||
- In the following command, replace the example user principal name for Azure authentication (admin@M365x373186.onmicrosoft.com) with your user account. Be sure that the user account you specify has sufficient administrative rights.
|
||||
|
||||
```powershell
|
||||
Connect-AutopilotIntune -user admin@M365x373186.onmicrosoft.com
|
||||
```
|
||||
The password for your account will be requested using a standard Azure AD form. Type your password and then click **Sign in**.
|
||||
<br>See the following example:
|
||||
|
||||
|
||||
|
||||
If this is the first time you’ve used the Intune Graph APIs, you’ll also be prompted to enable read and write permissions for Microsoft Intune PowerShell. To enable these permissions:
|
||||
- Select **Consent on behalf or your organization**
|
||||
- Click **Accept**
|
||||
|
||||
4. Next, retrieve and display all the Autopilot profiles available in the specified Intune tenant in JSON format:
|
||||
|
||||
#### Retrieve profiles in Autopilot for existing devices JSON format
|
||||
|
||||
```powershell
|
||||
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON
|
||||
```
|
||||
|
||||
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
|
||||
{
|
||||
"CloudAssignedTenantId": "1537de22-988c-4e93-b8a5-83890f34a69b",
|
||||
"CloudAssignedForcedEnrollment": 1,
|
||||
"Version": 2049,
|
||||
"Comment_File": "Profile Autopilot Profile",
|
||||
"CloudAssignedAadServerData": "{\"ZeroTouchConfig\":{\"CloudAssignedTenantUpn\":\"\",\"ForcedEnrollment\":1,\"CloudAssignedTenantDomain\":\"M365x373186.onmicrosoft.com\"}}",
|
||||
"CloudAssignedTenantDomain": "M365x373186.onmicrosoft.com",
|
||||
"CloudAssignedDomainJoinMethod": 0,
|
||||
"CloudAssignedOobeConfig": 28,
|
||||
"ZtdCorrelationId": "7F9E6025-1E13-45F3-BF82-A3E8C5B59EAC"
|
||||
}</pre>
|
||||
|
||||
Each profile is encapsulated within braces **{ }**. In the previous example, a single profile is displayed.
|
||||
|
||||
See the following table for a description of properties used in the JSON file.
|
||||
|
||||
|
||||
| Property | Description |
|
||||
|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Version (number, optional) | The version number that identifies the format of the JSON file. For Windows 10 1809, the version specified must be 2049. |
|
||||
| CloudAssignedTenantId (guid, required) | The Azure Active Directory tenant ID that should be used. This is the GUID for the tenant, and can be found in properties of the tenant. The value should not include braces. |
|
||||
| CloudAssignedTenantDomain (string, required) | The Azure Active Directory tenant name that should be used, e.g. tenant.onmicrosoft.com. |
|
||||
| CloudAssignedOobeConfig (number, required) | This is a bitmap that shows which Autopilot settings were configured. Values include: SkipCortanaOptIn = 1, OobeUserNotLocalAdmin = 2, SkipExpressSettings = 4, SkipOemRegistration = 8, SkipEula = 16 |
|
||||
| CloudAssignedDomainJoinMethod (number, required) | This property specifies whether the device should join Azure Active Directory or Active Directory (Hybrid Azure AD Join). Values include: Active AD Join = 0, Hybrid Azure AD Join = 1 |
|
||||
| CloudAssignedForcedEnrollment (number, required) | Specifies that the device should require AAD Join and MDM enrollment. <br>0 = not required, 1 = required. |
|
||||
| ZtdCorrelationId (guid, required) | A unique GUID (without braces) that will be provided to Intune as part of the registration process. ZtdCorrelationId will be included in enrollment message as “OfflineAutoPilotEnrollmentCorrelator”. This attribute will be present only if the enrollment is taking place on a device registered with Zero Touch Provisioning via offline registration. |
|
||||
| CloudAssignedAadServerData (encoded JSON string, required) | An embedded JSON string used for branding. It requires AAD corp branding enabled. <br> Example value: "CloudAssignedAadServerData": "{\"ZeroTouchConfig\":{\"CloudAssignedTenantUpn\":\"\",\"CloudAssignedTenantDomain\":\"tenant.onmicrosoft.com\"}}" |
|
||||
| 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: (use the horizontal scroll bar at the bottom if needed to view the entire command string)
|
||||
|
||||
```powershell
|
||||
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON | Out-File c:\Autopilot\AutopilotConfigurationFile.json -Encoding ASCII
|
||||
```
|
||||
**IMPORTANT**: The file name must be named **AutopilotConfigurationFile.json** in addition to being encoded as ASCII/ANSI.
|
||||
|
||||
If preferred, you can save the profile to a text file and edit in Notepad. In Notepad, when you choose **Save as** you must select Save as type: **All Files** and choose ANSI from the drop-down list next to **Encoding**. See the following example.
|
||||
|
||||
|
||||
|
||||
After saving the file, move the file to a location suitable as an SCCM package source.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Multiple JSON profile files can be used, but each must be named **AutopilotConfigurationFile.json** in order for OOBE to follow the Autopilot experience. The file also must be encoded as ANSI. <br><br>**Saving the file with Unicode or UTF-8 encoding or saving it with a different file name will cause Windows 10 OOBE to not follow the Autopilot experience**.<br>
|
||||
|
||||
|
||||
### Create a package containing the JSON file
|
||||
|
||||
1. In Configuration Manager, navigate to **\Software Library\Overview\Application Management\Packages**
|
||||
2. On the ribbon, click **Create Package**
|
||||
3. In the **Create Package and Program Wizard** enter the following **Package** and **Program Type** details:<br>
|
||||
- <u>Name</u>: **Autopilot for existing devices config**
|
||||
- Select the **This package contains source files** checkbox
|
||||
- <u>Source folder</u>: Click **Browse** and specify a UNC path containing the AutopilotConfigurationFile.json file.
|
||||
- Click **OK** and then click **Next**.
|
||||
- <u>Program Type</u>: **Do not create a program**
|
||||
4. Click **Next** twice and then click **Close**.
|
||||
|
||||
**NOTE**: If you change user-driven Autopilot profile settings in Intune at a later date, you must also update the JSON file and redistribute the associated Config Mgr package.
|
||||
|
||||
### Create a target collection
|
||||
|
||||
>[!NOTE]
|
||||
>You can also choose to reuse an existing collection
|
||||
|
||||
1. Navigate to **\Assets and Compliance\Overview\Device Collections**
|
||||
2. On the ribbon, click **Create** and then click **Create Device Collection**
|
||||
3. In the **Create Device Collection Wizard** enter the following **General** details:
|
||||
- <u>Name</u>: **Autopilot for existing devices collection**
|
||||
- Comment: (optional)
|
||||
- <u>Limiting collection</u>: Click **Browse** and select **All Systems**
|
||||
|
||||
>[!NOTE]
|
||||
>You can optionally choose to use an alternative collection for the limiting collection. The device to be upgraded must be running the ConfigMgr agent in the collection that you select.
|
||||
|
||||
4. Click **Next**, then enter the following **Membership Rules** details:
|
||||
- Click **Add Rule** and specify either a direct or query based collection rule to add the target test Windows 7 devices to the new collection.
|
||||
- For example, if the hostname of the computer to be wiped and reloaded is PC-01 and you wish to use Name as the attribute, click **Add Rule > Direct Rule > (wizard opens) > Next** and then enter **PC-01** next to **Value**. Click **Next** and then choose **PC-01** under **Resources**. See the following examples.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Continue creating the device collection with the default settings:
|
||||
- Use incremental updates for this collection: not selected
|
||||
- Schedule a full update on this collection: default
|
||||
- Click **Next** twice and then click **Close**
|
||||
|
||||
### Create an Autopilot for existing devices Task Sequence
|
||||
|
||||
>[!TIP]
|
||||
>The next procedure requires a boot image for Windows 10 1803 or later. Review your available boot images in the Configuration Manager conole under **Software Library\Overview\Operating Systems\Boot images** and verify that the **OS Version** is 10.0.17134.1 (Windows 10 version 1803) or later.
|
||||
|
||||
1. In the Configuration Manager console, navigate to **\Software Library\Overview\Operating Systems\Task Sequences**
|
||||
2. On the Home ribbon, click **Create Task Sequence**
|
||||
3. Select **Install an existing image package** and then click **Next**
|
||||
4. In the Create Task Sequence Wizard enter the following details:
|
||||
- <u>Task sequence name</u>: **Autopilot for existing devices**
|
||||
- <u>Boot Image</u>: Click **Browse** and select a Windows 10 boot image (1803 or later)
|
||||
- Click **Next**, and then on the Install Windows page click **Browse** and select a Windows 10 **Image package** and **Image Index**, version 1803 or later.
|
||||
- Select the **Partition and format the target computer before installing the operating system** checkbox.
|
||||
- Select or clear **Configure task sequence for use with Bitlocker** checkbox. This is optional.
|
||||
- <u>Product Key</u> and <u>Server licensing mode</u>: Optionally enter a product key and server licensing mode.
|
||||
- <u>Randomly generate the local administrator password and disable the account on all support platforms (recommended)</u>: Optional.
|
||||
- <u>Enable the account and specify the local administrator password</u>: Optional.
|
||||
- Click **Next**, and then on the Configure Network page choose **Join a workgroup** and specify a name (ex: workgroup) next to **Workgroup**.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The Autopilot for existing devices task sequence will run the **Prepare Windows for capture** action which calls the System Preparation Tool (syeprep). This action will fail if the target machine is joined to a domain.
|
||||
|
||||
5. Click **Next** and then click **Next** again to accept the default settings on the Install Configuration Manager page.
|
||||
6. On the State Migration page, enter the following details:
|
||||
- Clear the **Capture user settings and files** checkbox.
|
||||
- Clear the **Capture network settings** checkbox.
|
||||
- Clear the **Capture Microsoft Windows settings** checkbox.
|
||||
- Click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Autopilot for existing devices task sequence will result in an Azure Active Directory Domain (AAD) joined device. The User State Migration Toolkit (USMT) does not support AAD joined or hybrid AAD joined devices.
|
||||
|
||||
7. On the Include Updates page, choose one of the three available options. This selection is optional.
|
||||
8. On the Install applications page, add applications if desired. This is optional.
|
||||
9. Click **Next**, confirm settings, click **Next** and then click **Close**.
|
||||
10. Right click on the Autopilot for existing devices task sequence and click **Edit**.
|
||||
11. In the Task Sequence Editor under the **Install Operating System** group, click the **Apply Windows Settings** action.
|
||||
12. Click **Add** then click **New Group**.
|
||||
13. Change the group **Name** from **New Group** to **Autopilot for existing devices config**.
|
||||
14. Click **Add**, point to **General**, then click **Run Command Line**.
|
||||
15. Verify that the **Run Command Line** step is nested under the **Autopilot for existing devices config** group.
|
||||
16. Change the **Name** to **Apply Autopilot for existing devices config file** and paste the following into the **Command line** text box, and then click **Apply**:
|
||||
```
|
||||
cmd.exe /c xcopy AutopilotConfigurationFile.json %OSDTargetSystemDrive%\windows\provisioning\Autopilot\ /c
|
||||
```
|
||||
- **AutopilotConfigurationFile.json** must be the name of the JSON file present in the Autopilot for existing devices package created earlier.
|
||||
|
||||
17. In the **Apply Autopilot for existing devices config file** step, select the **Package** checkbox and then click **Browse**.
|
||||
18. Select the **Autopilot for existing devices config** package created earlier and click **OK**. An example is displayed at the end of this section.
|
||||
19. Under the **Setup Operating System** group, click the **Setup Windows and Configuration Manager** task.
|
||||
20. Click **Add** and then click **New Group**.
|
||||
21. Change **Name** from **New Group** to **Prepare Device for Autopilot**
|
||||
22. Verify that the **Prepare Device for Autopilot** group is the very last step in the task sequence. Use the **Move Down** button if necessary.
|
||||
23. With the **Prepare device for Autopilot** group selected, click **Add**, point to **Images** and then click **Prepare ConfigMgr Client for Capture**.
|
||||
24. Add a second step by clicking **Add**, pointing to **Images**, and clicking **Prepare Windows for Capture**. Use the following settings in this step:
|
||||
- <u>Automatically build mass storage driver list</u>: **Not selected**
|
||||
- <u>Do not reset activation flag</u>: **Not selected**
|
||||
- <u>Shutdown the computer after running this action</u>: **Optional**
|
||||
|
||||
|
||||
|
||||
25. Click **OK** to close the Task Sequence Editor.
|
||||
|
||||
### Deploy Content to Distribution Points
|
||||
|
||||
Next, ensure that all content required for the task sequence is deployed to distribution points.
|
||||
|
||||
1. Right click on the **Autopilot for existing devices** task sequence and click **Distribute Content**.
|
||||
2. Click **Next**, **Review the content to distribute** and then click **Next**.
|
||||
3. On the Specify the content distribution page click **Add** to specify either a **Distribution Point** or **Distribution Point Group**.
|
||||
4. On the a Add Distribution Points or Add Distribution Point Groups wizard specify content destinations that will allow the JSON file to be retrieved when the task sequence is run.
|
||||
5. When you are finished specifying content distribution, click **Next** twice then click **Close**.
|
||||
|
||||
### Deploy the OS with Autopilot Task Sequence
|
||||
|
||||
1. Right click on the **Autopilot for existing devices** task sequence and then click **Deploy**.
|
||||
2. In the Deploy Software Wizard enter the following **General** and **Deployment Settings** details:
|
||||
- <u>Task Sequence</u>: **Autopilot for existing devices**.
|
||||
- <u>Collection</u>: Click **Browse** and then select **Autopilot for existing devices collection** (or another collection you prefer).
|
||||
- Click **Next** to specify **Deployment Settings**.
|
||||
- <u>Action</u>: **Install**.
|
||||
- <u>Purpose</u>: **Available**. You can optionally select **Required** instead of **Available**. This is not recommended during the test owing to the potential impact of inadvertent configurations.
|
||||
- <u>Make available to the following</u>: **Only Configuration Manager Clients**. Note: Choose the option here that is relevant for the context of your test. If the target client does not have the Configuration Manager agent or Windows installed, you will need to select an option that includes PXE or Boot Media.
|
||||
- Click **Next** to specify **Scheduling** details.
|
||||
- <u>Schedule when this deployment will become available</u>: Optional
|
||||
- <u>Schedule when this deployment will expire</u>: Optional
|
||||
- Click **Next** to specify **User Experience** details.
|
||||
- <u>Show Task Sequence progress</u>: Selected.
|
||||
- <u>Software Installation</u>: Not selected.
|
||||
- <u>System restart (if required to complete the installation)</u>: Not selected.
|
||||
- <u>Commit changed at deadline or during a maintenance windows (requires restart)</u>: Optional.
|
||||
- <u>Allow task sequence to be run for client on the Internet</u>: Optional
|
||||
- Click **Next** to specify **Alerts** details.
|
||||
- <u>Create a deployment alert when the threshold is higher than the following</u>: Optional.
|
||||
- Click **Next** to specify **Distribution Points** details.
|
||||
- <u>Deployment options</u>: **Download content locally when needed by the running task sequence**.
|
||||
- <u>When no local distribution point is available use a remote distribution point</u>: Optional.
|
||||
- <u>Allow clients to use distribution points from the default site boundary group</u>: Optional.
|
||||
- Click **Next**, confirm settings, click **Next**, and then click **Close**.
|
||||
|
||||
### Complete the client installation process
|
||||
|
||||
1. Open the Software Center on the target Windows 7 or Windows 8.1 client computer. You can do this by clicking Start and then typing **software** in the search box, or by typing the following at a Windows PowerShell or command prompt:
|
||||
|
||||
```
|
||||
C:\Windows\CCM\SCClient.exe
|
||||
```
|
||||
|
||||
2. In the software library, select **Autopilot for existing devices** and click **Install**. See the following example:
|
||||
|
||||
|
||||
|
||||
|
||||
The Task Sequence will download content, reboot, format the drives and install Windows 10. The device will then proceed to be prepared for Autopilot. Once the task sequence has completed the device will boot into OOBE and provide an Autopilot experience.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>If joining devices to Active Directory (Hybrid Azure AD Join), it is necessary to create a Domain Join device configuration profile that is targeted to "All Devices" (since there is no Azure Active Directory device object for the computer to do group-based targeting). See [User-driven mode for hybrid Azure Active Directory join](https://docs.microsoft.com/windows/deployment/windows-autopilot/user-driven#user-driven-mode-for-hybrid-azure-active-directory-join) for more information.
|
||||
|
||||
### Register the device for Windows Autopilot
|
||||
|
||||
Devices provisioned through Autopilot will only receive the guided OOBE Autopilot experience on first boot. Once updated to Windows 10, the device should be registered to ensure a continued Autopilot experience in the event of PC reset. You can enable automatic registration for an assigned group using the **Convert all targeted devices to Autopilot** setting. For more information, see [Create an Autopilot deployment profile](https://docs.microsoft.com/intune/enrollment-autopilot#create-an-autopilot-deployment-profile).
|
||||
|
||||
Also see [Adding devices to Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/add-devices).
|
||||
|
||||
## Speeding up the deployment process
|
||||
|
||||
To remove around 20 minutes from the deployment process, see Michael Niehaus's blog with instructions for [Speeding up Windows Autopilot for existing devices](https://blogs.technet.microsoft.com/mniehaus/2018/10/25/speeding-up-windows-autopilot-for-existing-devices/).
|
||||
|
||||
@ -1,46 +1,68 @@
|
||||
---
|
||||
title: Windows Autopilot known issues
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot - known issues
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
<table>
|
||||
<th>Issue<th>More information
|
||||
<tr><td>The following known issues are resolved by installing the July 26, 2019 KB4505903 update (OS Build 18362.267):
|
||||
|
||||
- Windows Autopilot white glove does not work for a non-English OS and you see a red screen that says "Success."
|
||||
- Windows Autopilot reports an AUTOPILOTUPDATE error during OOBE after sysprep, reset or other variations. This typically happens if you reset the OS or used a custom sysprepped image.
|
||||
- BitLocker encryption is not correctly configured. Ex: BitLocker didn’t get an expected notification after policies were applied to begin encryption.
|
||||
- You are unable to install UWP apps from the Microsoft Store, causing failures during Windows Autopilot. If you are deploying Company Portal as a blocking app during Windows Autopilot ESP, you’ve probably seen this error.
|
||||
- A user is not granted administrator rights in the Windows Autopilot user-driven Hybrid Azure AD join scenario. This is another non-English OS issue.
|
||||
<td>Download and install the <a href="https://support.microsoft.com/help/4505903">KB4505903 update</a>. <br><br>See the section: <b>How to get this update</b> for information on specific release channels you can use to obtain the update.
|
||||
<tr><td>White glove gives a red screen and the <b>Microsoft-Windows-User Device Registration/Admin</b> event log displays <b>HResult error code 0x801C03F3</b><td>This can happen if Azure AD can’t find an AAD device object for the device that you are trying to deploy. This will occur if you manually delete the object. To fix it, remove the device from AAD, Intune, and Autopilot, then re-register it with Autopilot, which will recreate the AAD device object.<br>
|
||||
<br>To obtain troubleshooting logs use: <b>Mdmdiagnosticstool.exe -area Autopilot;TPM -cab c:\autopilot.cab</b>
|
||||
<tr><td>White glove gives a red screen<td>White glove is not supported on a VM.
|
||||
<tr><td>Error importing Windows Autopilot devices from a .csv file<td>Ensure that you have not edited the .csv file in Microsoft Excel or an editor other than Notepad. Some of these editors can introduce extra characters causing the file format to be invalid.
|
||||
<tr><td>Windows Autopilot for existing devices does not follow the Autopilot OOBE experience.<td>Ensure that the JSON profile file is saved in <b>ANSI/ASCII</b> format, not Unicode or UTF-8.
|
||||
<tr><td><b>Something went wrong</b> is displayed page during OOBE.<td>The client is likely unable to access all the required AAD/MSA-related URLs. For more information, see <a href="windows-autopilot-requirements.md#networking-requirements">Networking requirements</a>.
|
||||
</table>
|
||||
|
||||
## Related topics
|
||||
|
||||
[Diagnose MDM failures in Windows 10](https://docs.microsoft.com/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10)<br>
|
||||
---
|
||||
title: Windows Autopilot known issues
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot - known issues
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
<table>
|
||||
<th>Issue<th>More information
|
||||
<tr><td>Windows Autopilot for existing devices does not work for Windows 10, version 1903; you see screens that you've disabled in your Windows Autopilot profile, such as the Windows 10 License Agreement screen.
|
||||
<br> <br>
|
||||
This happens because Windows 10, version 1903 deletes the AutopilotConfigurationFile.json file.
|
||||
<td>To fix this issue: <ol><li>Edit the Configuration Manager task sequence and disable the <b>Prepare Windows for Capture</b> step.
|
||||
<li>Add a new <b>Run command line</b> step that runs <b>c:\windows\system32\sysprep\sysprep.exe /oobe /reboot</b>.</ol>
|
||||
<a href="https://oofhours.com/2019/09/19/a-challenge-with-windows-autopilot-for-existing-devices-and-windows-10-1903/">More information</a>
|
||||
<tr><td>The following known issue will be resolved by installing the KB4517211 update, due to be released in late September 2019.
|
||||
<br> <br>
|
||||
TPM attestation fails on Windows 10 1903 due to missing AKI extension in EK certificate. (An additional validation added in Windows 10 1903 to check that the TPM EK certs had the proper attributes according to the TCG specifications uncovered that a number of them don’t, so that validation will be removed).
|
||||
<td>Download and install the KB4517211 update</a>. <br><br>This update is currently pending release.
|
||||
<tr><td>The following known issues are resolved by installing the August 30, 2019 KB4512941 update (OS Build 18362.329):
|
||||
|
||||
- Windows Autopilot for existing devices feature does not properly suppress “Activities” page during OOBE. (Because of this, you’ll see that extra page during OOBE).
|
||||
- TPM attestation state is not cleared by sysprep /generalize, causing TPM attestation failure during later OOBE flow. (This isn’t a particularly common issue, but you could run into it while testing if you are running sysprep /generalize and then rebooting or reimaging the device to go back through an Autopilot white glove or self-deploying scenario).
|
||||
- TPM attestation may fail if the device has a valid AIK cert but no EK cert. (This is related to the previous item).
|
||||
- If TPM attestation fails during the Windows Autopilot white glove process, the landing page appears to be hung. (Basically, the white glove landing page, where you click “Provision” to start the white glove process, isn’t reporting errors properly).
|
||||
- TPM attestation fails on newer Infineon TPMs (firmware version > 7.69). (Prior to this fix, only a specific list of firmware versions was accepted).
|
||||
- Device naming templates may truncate the computer name at 14 characters instead of 15.
|
||||
- Assigned Access policies cause a reboot which can interfere with the configuration of single-app kiosk devices.
|
||||
<td>Download and install the <a href="https://support.microsoft.com/help/4512941">KB4512941 update</a>. <br><br>See the section: <b>How to get this update</b> for information on specific release channels you can use to obtain the update.
|
||||
<tr><td>The following known issues are resolved by installing the July 26, 2019 KB4505903 update (OS Build 18362.267):
|
||||
|
||||
- Windows Autopilot white glove does not work for a non-English OS and you see a red screen that says "Success."
|
||||
- Windows Autopilot reports an AUTOPILOTUPDATE error during OOBE after sysprep, reset or other variations. This typically happens if you reset the OS or used a custom sysprepped image.
|
||||
- BitLocker encryption is not correctly configured. Ex: BitLocker didn’t get an expected notification after policies were applied to begin encryption.
|
||||
- You are unable to install UWP apps from the Microsoft Store, causing failures during Windows Autopilot. If you are deploying Company Portal as a blocking app during Windows Autopilot ESP, you’ve probably seen this error.
|
||||
- A user is not granted administrator rights in the Windows Autopilot user-driven Hybrid Azure AD join scenario. This is another non-English OS issue.
|
||||
<td>Download and install the <a href="https://support.microsoft.com/help/4505903">KB4505903 update</a>. <br><br>See the section: <b>How to get this update</b> for information on specific release channels you can use to obtain the update.
|
||||
|
||||
<tr><td>White glove gives a red screen and the <b>Microsoft-Windows-User Device Registration/Admin</b> event log displays <b>HResult error code 0x801C03F3</b><td>This can happen if Azure AD can’t find an AAD device object for the device that you are trying to deploy. This will occur if you manually delete the object. To fix it, remove the device from AAD, Intune, and Autopilot, then re-register it with Autopilot, which will recreate the AAD device object.<br>
|
||||
<br>To obtain troubleshooting logs use: <b>Mdmdiagnosticstool.exe -area Autopilot;TPM -cab c:\autopilot.cab</b>
|
||||
<tr><td>White glove gives a red screen<td>White glove is not supported on a VM.
|
||||
<tr><td>Error importing Windows Autopilot devices from a .csv file<td>Ensure that you have not edited the .csv file in Microsoft Excel or an editor other than Notepad. Some of these editors can introduce extra characters causing the file format to be invalid.
|
||||
<tr><td>Windows Autopilot for existing devices does not follow the Autopilot OOBE experience.<td>Ensure that the JSON profile file is saved in <b>ANSI/ASCII</b> format, not Unicode or UTF-8.
|
||||
<tr><td><b>Something went wrong</b> is displayed page during OOBE.<td>The client is likely unable to access all the required AAD/MSA-related URLs. For more information, see <a href="windows-autopilot-requirements.md#networking-requirements">Networking requirements</a>.
|
||||
</table>
|
||||
|
||||
## Related topics
|
||||
|
||||
[Diagnose MDM failures in Windows 10](https://docs.microsoft.com/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10)<br>
|
||||
[Troubleshooting Windows Autopilot](troubleshooting.md)
|
||||
|
||||
@ -1,99 +1,103 @@
|
||||
---
|
||||
title: Windows Autopilot User-Driven Mode
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot user-driven mode
|
||||
|
||||
Windows Autopilot user-driven mode is designed to enable new Windows 10 devices to be transformed from their initial state, directly from the factory, into a ready-to-use state without requiring that IT personnel ever touch the device. The process is designed to be simple so that anyone can complete it, enabling devices to be shipped or distributed to the end user directly with simple instructions:
|
||||
|
||||
- Unbox the device, plug it in, and turn it on.
|
||||
- Choose a language, locale and keyboard.
|
||||
- Connect it to a wireless or wired network with internet access.
|
||||
- Specify your e-mail address and password for your organization account.
|
||||
|
||||
After completing those simple steps, the remainder of the process is completely automated, with the device being joined to the organization, enrolled in Intune (or another MDM service), and fully configured as defined by the organization. Any additional prompts during the Out-of-Box Experience (OOBE) can be supressed; see [Configuring Autopilot Profiles](profiles.md) for options that are available.
|
||||
|
||||
Today, Windows Autopilot user-driven mode supports joining devices to Azure Active Directory. Support for Hybrid Azure Active Directory Join (with devices joined to an on-premises Active Directory domain) will be available in a future Windows 10 release. See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
|
||||
|
||||
## Available user-driven modes
|
||||
|
||||
The following options are available for user-driven deployment:
|
||||
|
||||
- [Azure Active Directory join](#user-driven-mode-for-azure-active-directory-join) is available if devices do not need to be joined to an on-prem Active Directory domain.
|
||||
- [Hybrid Azure Active Directory join](#user-driven-mode-for-hybrid-azure-active-directory-join) is available for devices that must be joined to both Azure Active Directory and your on-prem Active Directory domain.
|
||||
|
||||
### User-driven mode for Azure Active Directory join
|
||||
|
||||
In order to perform a user-driven deployment using Windows Autopilot, the following preparation steps need to be completed:
|
||||
|
||||
- Ensure that the users who will be performing user-driven mode deployments are able to join devices to Azure Active Directory. See [Configure device settings](https://docs.microsoft.com/azure/active-directory/device-management-azure-portal#configure-device-settings) in the Azure Active Directory documentation for more information.
|
||||
- Create an Autopilot profile for user-driven mode with the desired settings. In Microsoft Intune, this mode is explicitly chosen when creating the profile. With Microsoft Store for Business and Partner Center, user-driven mode is the default and does not need to be selected.
|
||||
- If using Intune, create a device group in Azure Active Directory and assign the Autopilot profile to that group.
|
||||
|
||||
For each device that will be deployed using user-driven deployment, these additional steps are needed:
|
||||
|
||||
- Ensure that the device has been added to Windows Autopilot. This can be done automatically by an OEM or partner at the time the device is purchased, or it can be done through a manual harvesting process later. See [Adding devices to Windows Autopilot](add-devices.md) for more information.
|
||||
- Ensure an Autopilot profile has been assigned to the device:
|
||||
- If using Intune and Azure Active Directory dynamic device groups, this can be done automatically.
|
||||
- If using Intune and Azure Active Directory static device groups, manually add the device to the device group.
|
||||
- If using other methods (e.g. Microsoft Store for Business or Partner Center), manually assign an Autopilot profile to the device.
|
||||
|
||||
Also see the [Validation](#validation) section below.
|
||||
|
||||
### User-driven mode for hybrid Azure Active Directory join
|
||||
|
||||
Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid Azure Active Directory (AAD) joined](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).
|
||||
|
||||
#### Requirements
|
||||
|
||||
To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
|
||||
|
||||
- A Windows Autopilot profile for user-driven mode must be created and
|
||||
- **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile.
|
||||
- If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group.
|
||||
- The device must be running Windows 10, version 1809 or later.
|
||||
- The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user).
|
||||
- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements.md).
|
||||
- The Intune Connector for Active Directory must be installed.
|
||||
- Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf.
|
||||
- If using Proxy, WPAD Proxy settings option must be enabled and configured.
|
||||
|
||||
**AAD device join**: The hybrid AAD join process uses the system context to perform device AAD join, therefore it is not affected by user based AAD join permission settings. In addition, all users are enabled to join devices to AAD by default.
|
||||
|
||||
#### Step by step instructions
|
||||
|
||||
See [Deploy hybrid Azure AD joined devices using Intune and Windows Autopilot](https://docs.microsoft.com/intune/windows-autopilot-hybrid).
|
||||
|
||||
Also see the **Validation** section in the [Windows Autopilot user-driven mode](user-driven.md) topic.
|
||||
|
||||
## Validation
|
||||
|
||||
When performing a user-driven deployment using Windows Autopilot, the following end-user experience should be observed:
|
||||
|
||||
- If multiple languages are preinstalled in Windows 10, the user must pick a language.
|
||||
- The user must pick a locale and a keyboard layout, and optionally a second keyboard layout.
|
||||
- If connected via Ethernet, no network prompt is expected. If no Ethernet connection is available and Wi-fi is built in, the user needs to connect to a wireless network.
|
||||
- Once connected to a network, the Autopilot profile will be downloaded.
|
||||
- Windows 10 will check for critical OOBE updates, and if any are available they will be automatically installed (rebooting if required).
|
||||
- The user will be prompted for Azure Active Directory credentials, with a customized user experience showing the Azure AD tenant name, logo, and sign-in text.
|
||||
- Once correct credentials have been entered, the device will join Azure Active Directory.
|
||||
- After joining Azure Active Directory, the device will enroll in Intune (or other configured MDM services).
|
||||
- If configured, the [enrollment status page](enrollment-status.md) will be displayed.
|
||||
- Once the device configuration tasks have completed, the user will be signed into Windows 10 using the credentials they previously provided.
|
||||
- Once signed in, the enrollment status page will again be displayed for user-targeted configuration tasks.
|
||||
|
||||
---
|
||||
title: Windows Autopilot User-Driven Mode
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot user-driven mode
|
||||
|
||||
Windows Autopilot user-driven mode is designed to enable new Windows 10 devices to be transformed from their initial state, directly from the factory, into a ready-to-use state without requiring that IT personnel ever touch the device. The process is designed to be simple so that anyone can complete it, enabling devices to be shipped or distributed to the end user directly with simple instructions:
|
||||
|
||||
- Unbox the device, plug it in, and turn it on.
|
||||
- Choose a language, locale and keyboard.
|
||||
- Connect it to a wireless or wired network with internet access.
|
||||
- Specify your e-mail address and password for your organization account.
|
||||
|
||||
After completing those simple steps, the remainder of the process is completely automated, with the device being joined to the organization, enrolled in Intune (or another MDM service), and fully configured as defined by the organization. Any additional prompts during the Out-of-Box Experience (OOBE) can be suppressed; see [Configuring Autopilot Profiles](profiles.md) for options that are available.
|
||||
|
||||
Today, Windows Autopilot user-driven mode supports joining devices to Azure Active Directory. Support for Hybrid Azure Active Directory Join (with devices joined to an on-premises Active Directory domain) will be available in a future Windows 10 release. See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
|
||||
|
||||
## Available user-driven modes
|
||||
|
||||
The following options are available for user-driven deployment:
|
||||
|
||||
- [Azure Active Directory join](#user-driven-mode-for-azure-active-directory-join) is available if devices do not need to be joined to an on-prem Active Directory domain.
|
||||
- [Hybrid Azure Active Directory join](#user-driven-mode-for-hybrid-azure-active-directory-join) is available for devices that must be joined to both Azure Active Directory and your on-prem Active Directory domain.
|
||||
|
||||
### User-driven mode for Azure Active Directory join
|
||||
|
||||
In order to perform a user-driven deployment using Windows Autopilot, the following preparation steps need to be completed:
|
||||
|
||||
- Ensure that the users who will be performing user-driven mode deployments are able to join devices to Azure Active Directory. See [Configure device settings](https://docs.microsoft.com/azure/active-directory/device-management-azure-portal#configure-device-settings) in the Azure Active Directory documentation for more information.
|
||||
- Create an Autopilot profile for user-driven mode with the desired settings. In Microsoft Intune, this mode is explicitly chosen when creating the profile. With Microsoft Store for Business and Partner Center, user-driven mode is the default and does not need to be selected.
|
||||
- If using Intune, create a device group in Azure Active Directory and assign the Autopilot profile to that group.
|
||||
|
||||
For each device that will be deployed using user-driven deployment, these additional steps are needed:
|
||||
|
||||
- Ensure that the device has been added to Windows Autopilot. This can be done automatically by an OEM or partner at the time the device is purchased, or it can be done through a manual harvesting process later. See [Adding devices to Windows Autopilot](add-devices.md) for more information.
|
||||
- Ensure an Autopilot profile has been assigned to the device:
|
||||
- If using Intune and Azure Active Directory dynamic device groups, this can be done automatically.
|
||||
- If using Intune and Azure Active Directory static device groups, manually add the device to the device group.
|
||||
- If using other methods (e.g. Microsoft Store for Business or Partner Center), manually assign an Autopilot profile to the device.
|
||||
|
||||
Also see the [Validation](#validation) section below.
|
||||
|
||||
>[!NOTE]
|
||||
>If the device reboots during the device enrollment status page (ESP) in the user-driven Azure Active Directoy join scenario, the user will not automatically sign on because the user's credentials cannot be saved across reboots. In this scenario, the user will need to sign in manually after the device ESP completes.
|
||||
|
||||
### User-driven mode for hybrid Azure Active Directory join
|
||||
|
||||
Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid Azure Active Directory (AAD) joined](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).
|
||||
|
||||
#### Requirements
|
||||
|
||||
To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
|
||||
|
||||
- A Windows Autopilot profile for user-driven mode must be created and
|
||||
- **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile.
|
||||
- If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group.
|
||||
- The device must be running Windows 10, version 1809 or later.
|
||||
- The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user).
|
||||
- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements.md).
|
||||
- The Intune Connector for Active Directory must be installed.
|
||||
- Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf.
|
||||
- If using Proxy, WPAD Proxy settings option must be enabled and configured.
|
||||
|
||||
**AAD device join**: The hybrid AAD join process uses the system context to perform device AAD join, therefore it is not affected by user based AAD join permission settings. In addition, all users are enabled to join devices to AAD by default.
|
||||
|
||||
#### Step by step instructions
|
||||
|
||||
See [Deploy hybrid Azure AD joined devices using Intune and Windows Autopilot](https://docs.microsoft.com/intune/windows-autopilot-hybrid).
|
||||
|
||||
Also see the **Validation** section in the [Windows Autopilot user-driven mode](user-driven.md) topic.
|
||||
|
||||
## Validation
|
||||
|
||||
When performing a user-driven deployment using Windows Autopilot, the following end-user experience should be observed:
|
||||
|
||||
- If multiple languages are preinstalled in Windows 10, the user must pick a language.
|
||||
- The user must pick a locale and a keyboard layout, and optionally a second keyboard layout.
|
||||
- If connected via Ethernet, no network prompt is expected. If no Ethernet connection is available and Wi-fi is built in, the user needs to connect to a wireless network.
|
||||
- Once connected to a network, the Autopilot profile will be downloaded.
|
||||
- Windows 10 will check for critical OOBE updates, and if any are available they will be automatically installed (rebooting if required).
|
||||
- The user will be prompted for Azure Active Directory credentials, with a customized user experience showing the Azure AD tenant name, logo, and sign-in text.
|
||||
- Once correct credentials have been entered, the device will join Azure Active Directory.
|
||||
- After joining Azure Active Directory, the device will enroll in Intune (or other configured MDM services).
|
||||
- If configured, the [enrollment status page](enrollment-status.md) will be displayed.
|
||||
- Once the device configuration tasks have completed, the user will be signed into Windows 10 using the credentials they previously provided.
|
||||
- Once signed in, the enrollment status page will again be displayed for user-targeted configuration tasks.
|
||||
|
||||
If your results do not match these expectations, see the [Windows Autopilot Troubleshooting](troubleshooting.md) documentation.
|
||||
|
||||
Reference in New Issue
Block a user