deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-20 17:27:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Changes to Windows Autopilot Reset docs

Browse Source
This commit is contained in:
Michael Niehaus 2018-07-10 16:28:32 -07:00
parent 66e4eda874
commit ae4b19d605
4 changed files with 78 additions and 94 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -15,13 +15,13 @@ ms.date: 06/01/2018
# Windows Autopilot Self-Deploying mode (Preview)
**Applies to: Windows 10 build 17672 or later**
**Applies to: Windows 10, build 17672 or later**
Windows Autopilot self-deploying mode offers truly zero touch provisioning. With this mode, all you need to do is power on a device, plug it into Ethernet, and watch Windows Autopilot fully configure the device. No additional user interaction is required.
![The user experience with Windows Autopilot self-deploying mode](images/self-deploy-welcome.png)
>[!NOTE]
>[!NOTE]
>While today there is a “Next” button that must be clicked to continue the deployment process, and an Activities opt-in page in OOBE, both of these will be removed in future Insider Preview builds to enable a completely automated deployment process – no user authentication or user interaction will be required.
Self-deploying mode can register the device into an organization’s Azure Active Directory tenant, enroll the device in the organization’s mobile device management (MDM) provider (leveraging Azure AD for automatic MDM enrollment), and ensure that all policies, applications, certificates, and networking profiles are provisioned on the device before the user ever logs on (levering the enrollment status page to prevent access to the desktop until the device is fully provisioned).

71
windows/deployment/windows-autopilot/windows-autopilot-reset-local.md
View File

@ -1,5 +1,5 @@
---
title: Reset devices with Local Autopilot Reset
title: Reset devices using local Windows Autopilot Reset
description: Gives an overview of Local Autopilot Reset and how to use it.
keywords: Autopilot Reset, Windows 10
ms.prod: w10
@ -13,34 +13,27 @@ ms.author: coreyp
ms.date: 06/01/2018
---
# Reset devices with Local Autopilot Reset
# Reset devices with local Windows Autopilot Reset
**Applies to: Windows 10, version 1709"
**Applies to: Windows 10, version 1709 and above
IT admins can use Local Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With Local Autopilot Reset, devices are returned to a fully configured or known IT-approved state.
IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state.
To enable Local Autopilot Reset in Windows 10:
To enable local Autopilot Reset in Windows 10:
1. [Enable the policy for the feature](#enable-autopilot-reset)
2. [Trigger a reset for each device](#trigger-autopilot-reset)
## Enable Local Autopilot Reset
## Enable local Windows Autopilot Reset
To use Local Autopilot Reset, [Windows Recovery Environment (WinRE) must be enabled on the device](#winre).
**DisableAutomaticReDeploymentCredentials** is a policy that enables or disables the visibility of the credentials for Local Autopilot Reset. It is a policy node in the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-credentialproviders), **CredentialProviders/DisableAutomaticReDeploymentCredentials**. By default, this policy is set to 1 (Disable). This ensures that Local Autopilot Reset isn't triggered by accident.
To enable a local Windows Autopilot Reset, the **DisableAutomaticReDeploymentCredentials** policy must be configured. This policy is documented in the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-credentialproviders), **CredentialProviders/DisableAutomaticReDeploymentCredentials**. By default, this policy is set to 1 (Disable). This ensures that a local Autopilot Reset isn't triggered by accident.
You can set the policy using one of these methods:
- MDM provider
- Local Autopilot Reset in Intune -. New tenants automatically have the Local Autopilot Reset setting enabled by default on the **All devices** group as part of initial tenant configuration. You can manage this setting to target different groups in the admin console.
- If you're using an MDM provider other than Intune, check your MDM provider documentation on how to set this policy. If your MDM provider doesn't explicitly support this policy, you can manually set this policy if your MDM provider allows specific OMA-URIs to be manually set.
For example, in Intune, create a new configuration policy and add an OMA-URI.
- OMA-URI: ./Vendor/MSFT/Policy/Config/CredentialProviders/DisableAutomaticReDeploymentCredentials
- Data type: Integer
- Value: 0
- When using Intune, you can create a new device configuration profile, specifying "Windows 10 or later" for the platform, "Device restrictions" for the profile type, and "General" for the settings category. The **Automatic Redeployment** setting should be set to **Allow**. Deploy this setting to all devices where a local reset should be permitted.
- If you're using an MDM provider other than Intune, check your MDM provider documentation on how to set this policy.
- Windows Configuration Designer
@ -48,59 +41,29 @@ You can set the policy using one of these methods:
- Set up School PCs app
Local Autopilot Reset in the Set up School PCs app is available in the latest release of the app. Make sure you are running Windows 10, version 1709 on the student PCs if you want to use Local Autopilot Reset through the Set up School PCs app. You can check the version several ways:
- Reach out to your device manufacturer.
- If you manage your PCs using Intune, you can check the OS version by checking the **OS version** info for the device. If you are using another MDM provider, check the documentation for the MDM provider to confirm the OS version.
- Log into the PCs, go to the **Settings > System > About** page, look in the **Windows specifications** section and confirm **Version** is set to 1709.
The latest release of the Set up School PCs app supports enabling local Windows Autopilot Reset.
## Trigger local Windows Autopilot Reset
## Trigger Local Autopilot Reset
Autopilot Reset is a two-step process: trigger it and then authenticate. Once you've done these two steps, you can let the process execute and once it's done, the device is again ready for use.
Performing a local Windows Autopilot Reset is a two-step process: trigger it and then authenticate. Once you've done these two steps, you can let the process execute and once it is done, the device is again ready for use.
**To trigger Local Autopilot Reset**
**To trigger a local Autopilot Reset**
1. From the Windows device lock screen, enter the keystroke: **CTRL + ![Windows key](images/windows_glyph.png) + R**.
![Enter CTRL+Windows key+R on the Windows lockscreen](images/autopilot-reset-lockscreen.png)
This will open up a custom login screen for Local Autopilot Reset. The screen serves two purposes:
This will open up a custom login screen for the local Autopilot Reset. The screen serves two purposes:
1. Confirm/verify that the end user has the right to trigger Local Autopilot Reset
2. Notify the user in case a provisioning package, created using Windows Configuration Designer, will be used as part of the process.
![Custom login screen for Local Autopilot Reset](images/autopilot-reset-customlogin.png)
![Custom login screen for local Autopilot Reset](images/autopilot-reset-customlogin.png)
2. Sign in with the admin account credentials. If you created a provisioning package, plug in the USB drive and trigger Local Autopilot Reset.
2. Sign in with the admin account credentials. If you created a provisioning package, plug in the USB drive and trigger the local Autopilot Reset.
>[!IMPORTANT]
>To reestablish Wi-Fi connectivity after reset, make sure the **Connect automatically** box is checked for the device's wireless network connection.
Once Local Autopilot Reset is triggered, the reset process starts.
After reset, the device:
- Sets the region, language, and keyboard.
- Connects to Wi-Fi.
- If you provided a provisioning package when Local Autopilot Reset is triggered, the system will apply this new provisioning package. Otherwise, the system will re-apply the original provisioning package on the device.
- Is returned to a known good managed state, connected to Azure AD and MDM.
Once the local Autopilot Reset is triggered, the reset process starts.
![Notification that provisioning is complete](images/autopilot-reset-provisioningcomplete.png)
Once provisioning is complete, the device is again ready for use.
<span id="winre"/>
## Troubleshoot Local Autopilot Reset
Local Autopilot Reset will fail when the [Windows Recovery Environment (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference) is not enabled on the device. You will see `Error code: ERROR_NOT_SUPPORTED (0x80070032)`.
To make sure WinRE is enabled, use the [REAgentC.exe tool](https://docs.microsoft.com/windows-hardware/manufacture/desktop/reagentc-command-line-options) to run the following command:
```
reagentc /enable
```
If Windows Automatic Reployment fails after enabling WinRE, or if you are unable to enable WinRE, please contact [Microsoft Support](https://support.microsoft.com) for assistance.

32
windows/deployment/windows-autopilot/windows-autopilot-reset-remote.md
View File

@ -1,6 +1,6 @@
---
title: Reset devices with Remote Autopilot Reset (Preview)
description: Gives an overview of Remote Autopilot Reset and how to use it.
title: Reset devices with remote Autopilot Reset (Preview)
description: Gives an overview of remote Autopilot Reset and how to use it.
keywords: Autopilot Reset, Windows 10
ms.prod: w10
ms.technology: Windows
@ -13,22 +13,24 @@ ms.author: coreyp
ms.date: 06/01/2018
---
# Reset devices with Remote Autopilot Reset (Preview)
# Reset devices with remote Windows Autopilot Reset (Preview)
**Applies to: Windows 10**
**Applies to: Windows 10, build 17672 or later**
Windows Autopilot Reset removes personal files, apps, and settings and reapplies a device’s original settings, maintaining its identity connection to Azure AD and its management connection to Intune so that the device is once again ready for use. Windows Autopilot Reset takes the device back to a business-ready state, allowing the next user to sign in and get productive quickly and simply.
When performing a remote Windows Autopilot Reset, an MDM service such an Microsoft Intune can be used to initiate the reset process, avoiding the need for IT staff or other administrators to visit each machine to initiate the process.
Once either local or remote Windows Autopilot Reset is complete, the device can automatically:
To enable a device for a remote Windows Autopilot Reset, the device must be MDM managed, joined to Azure AD, and configured to use the [enrollment status page](enrollment-status.md).
Set the region, language, and keyboard.
Connect to Wi-Fi.
Apply a new provisioning package (if a provisioning package is inserted via USB when Windows Autopilot Reset is triggered), or reapply the original provisioning package to the device.
Return to a known, good, managed state, connected to Azure AD and MDM.
Block the user from accessing the desktop until all provisioning package policies have been applied. If MDM is set up, Windows Autopilot Reset will block the user from the desktop until a successful MDM sync is complete.
To enable a device for remote Windows Autopilot Reset, the device must be MDM managed, joined to an Azure AD tenant, and configured to use the Enrollment Status Page. Instructions for triggering remote Windows Autopilot Reset via Intune are as follows:
## Triggering a remote Windows Autopilot Reset
Navigate to **Devices** tab in the Intune console.
In the **All devices** view, select the targeted reset devices and then click **More** to view device actions.
Select **Autopilot Reset** to kick-off the reset task.
To trigger a remote Windows Autopilot Reset via Intune, follow these steps:
- Navigate to **Devices** tab in the Intune console.
- In the **All devices** view, select the targeted reset devices and then click **More** to view device actions.
- Select **Autopilot Reset** to kick-off the reset task.
>[!NOTE]
>The Autopilot Reset option will not be enabled in Microsoft Intune for devices not running Windows 10 build 17672 or higher.
Once the reset is complete, the device is again ready for use.

43
windows/deployment/windows-autopilot/windows-autopilot-reset.md
View File

@ -1,5 +1,5 @@
---
title: Reset devices with Remote Autopilot Reset (Preview)
title: Windows Autopilot Reset
description: Gives an overview of Remote Autopilot Reset and how to use it.
keywords: Autopilot Reset, Windows 10
ms.prod: w10
@ -13,22 +13,41 @@ ms.author: coreyp
ms.date: 06/01/2018
---
# Reset devices with Remote Autopilot Reset (Preview)
# Windows Autopilot Reset
**Applies to: Windows 10**
Windows Autopilot Reset removes personal files, apps, and settings and reapplies a device’s original settings, maintaining its identity connection to Azure AD and its management connection to Intune so that the device is once again ready for use. Windows Autopilot Reset takes the device back to a business-ready state, allowing the next user to sign in and get productive quickly and simply.
Once either local or remote Windows Autopilot Reset is complete, the device can automatically:
The Windows Autopilot Reset process automatically retains information from the existing device:
Set the region, language, and keyboard.
Connect to Wi-Fi.
Apply a new provisioning package (if a provisioning package is inserted via USB when Windows Autopilot Reset is triggered), or reapply the original provisioning package to the device.
Return to a known, good, managed state, connected to Azure AD and MDM.
Block the user from accessing the desktop until all provisioning package policies have been applied. If MDM is set up, Windows Autopilot Reset will block the user from the desktop until a successful MDM sync is complete.
To enable a device for remote Windows Autopilot Reset, the device must be MDM managed, joined to an Azure AD tenant, and configured to use the Enrollment Status Page. Instructions for triggering remote Windows Autopilot Reset via Intune are as follows:
- Set the region, language, and keyboard to the originally-configured values.
- Wi-Fi connection details.
- Provisioning packages previously applied to the device, as well as a provisioning package present on a USB drive when the reset process is initiated.
- Azure Active Directory device membership and MDM enrollment information.
Navigate to **Devices** tab in the Intune console.
In the **All devices** view, select the targeted reset devices and then click **More** to view device actions.
Select **Autopilot Reset** to kick-off the reset task.
Windows Autopilot Reset will block the user from accessing the desktop until this information is restored, including re-applying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset will also block until an MDM sync is completed. This requires configuring the device to use the [enrollment status page](enrollment-status.md).
>[!IMPORTANT]
>To reestablish Wi-Fi connectivity after reset, make sure the **Connect automatically** box is checked for the device's wireless network connection.
## Scenarios
Windows Autopilot Reset supports two scenarios:
- [Local reset](windows-autopilot-reset-local.md), initiated by IT personnel or other administrators from the organization.
- [Remote reset](windows-autopilot-reset-remote.md), initiated remotely by IT personnel via an MDM service such as Microsoft Intune.
Additional requirements and configuration details apply with each scenario; see the detailed links above for more information.
## Troubleshooting
Windows Autopilot Reset requires that the [Windows Recovery Environment (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference) is correctly configured and enabled on the device. If it is not configured and enabled, an error such as `Error code: ERROR_NOT_SUPPORTED (0x80070032)` will be reported.
To make sure WinRE is enabled, use the [REAgentC.exe tool](https://docs.microsoft.com/windows-hardware/manufacture/desktop/reagentc-command-line-options) to run the following command:
```
reagentc /enable
```
If Windows Autopilot Reset fails after enabling WinRE, or if you are unable to enable WinRE, please contact [Microsoft Support](https://support.microsoft.com) for assistance.