mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 05:13:40 +00:00
Merge branch 'main' into v-jmathew-6038482
This commit is contained in:
Diana Hanson
GitHub
@ -38,9 +38,9 @@ The following table lists the minimum Windows 10 version that supports Delivery
|
||||
|
||||
| Device type | Minimum Windows version
|
||||
|------------------|---------------|
|
||||
| Computers running Windows 10 | Win 10 1511 |
|
||||
| Computers running Windows 10 | Windows 10 1511 |
|
||||
| Computers running Server Core installations of Windows Server | Windows Server 2019 |
|
||||
| Windows IoT devices | Win 10 1803 |
|
||||
| Windows IoT devices | Windows 10 1803 |
|
||||
|
||||
### Types of download content supported by Delivery Optimization
|
||||
|
||||
@ -48,19 +48,19 @@ The following table lists the minimum Windows 10 version that supports Delivery
|
||||
|
||||
| Windows Client | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC)
|
||||
|------------------|---------------|----------------|----------|----------------|
|
||||
| Windows Update (feature updates quality updates, language packs, drivers) | Win 10 1511, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Windows 10 Store files | Win 10 1511, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Windows 10 Store for Business files | Win 10 1511, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Windows Defender definition updates | Win 10 1511, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Intune Win32 apps| Win 10 1709, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Microsoft 365 Apps and updates | Win 10 1709, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Edge Browser Updates | Win 10 1809, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Configuration Manager Express updates| Win 10 1709 + Configuration Manager version Win 10 1711, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Dynamic updates| Win 10 1903, Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| MDM Agent | Win 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Xbox Game Pass (PC) | Win 10 1809, Win 11 | :heavy_check_mark: | | :heavy_check_mark: |
|
||||
| Windows Package Manager| Win 10 1809, Win 11 | :heavy_check_mark: | | |
|
||||
| MSIX | Win 10 2004, Win 11 | :heavy_check_mark: | | |
|
||||
| Windows Update (feature updates quality updates, language packs, drivers) | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Windows 10 Store files | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Windows 10 Store for Business files | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Windows Defender definition updates | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Intune Win32 apps| Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Microsoft 365 Apps and updates | Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Edge Browser Updates | Windows 10 1809, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Configuration Manager Express updates| Windows 10 1709 + Configuration Manager version Windows 10 1711, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Dynamic updates| Windows 10 1903, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| MDM Agent | Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Xbox Game Pass (PC) | Windows 10 1809, Windows 11 | :heavy_check_mark: | | :heavy_check_mark: |
|
||||
| Windows Package Manager| Windows 10 1809, Windows 11 | :heavy_check_mark: | | |
|
||||
| MSIX | Windows 10 2004, Windows 11 | :heavy_check_mark: | | |
|
||||
|
||||
#### Windows Server
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ For Windows Update (WU) scans URLs that are used for update detection ([MS-WUSP]
|
||||
> [!Note]
|
||||
> For intranet WSUS update service URLs, we provide an option via Windows Update policy to select the proxy behavior.
|
||||
|
||||
For WU URLs that _aren't_ used for update detection, such as for download or reporting:
|
||||
For Windows Update URLs that _aren't_ used for update detection, such as for download or reporting:
|
||||
- User proxy is attempted.
|
||||
- If WUA fails to reach the service due to a certain proxy, service, or authentication error code, then the system proxy is attempted.
|
||||
|
||||
@ -116,7 +116,7 @@ For WU URLs that _aren't_ used for update detection, such as for download or rep
|
||||
|
||||
|Service|ServiceId|
|
||||
|-------|---------|
|
||||
|Unspecified / Default|WU, MU, or WSUS <br>00000000-0000-0000-0000-000000000000 |
|
||||
|Unspecified / Default|Windows Update, Microsoft Update, or WSUS <br>00000000-0000-0000-0000-000000000000 |
|
||||
|Windows Update|9482F4B4-E343-43B6-B170-9A65BC822C77|
|
||||
|Microsoft Update|7971f918-a847-4430-9279-4a52d1efe18d|
|
||||
|Store|855E8A7C-ECB4-4CA3-B045-1DFA50104289|
|
||||
|
||||
@ -81,7 +81,7 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
|
||||
| 51 | Unexpected exception when attempting to run Census.exe|
|
||||
| 52 | Could not find Census.exe|
|
||||
| 53 | There are conflicting CommercialID values.|
|
||||
| 54 | Microsoft Account Sign In Assistant (MSA) Service disabled.|
|
||||
| 54 | Microsoft account (MSA) Sign In Assistant Service disabled.|
|
||||
| 55 | Failed to create new registry path for SetDeviceNameOptIn|
|
||||
| 56 | Failed to create property for SetDeviceNameOptIn at registry path|
|
||||
| 57 | Failed to update value for SetDeviceNameOptIn|
|
||||
|
||||
@ -45,8 +45,8 @@ This section lists the error codes for Microsoft Windows Update.
|
||||
| 0x80243002 | `WU_E_INSTALLATION_RESULTS_INVALID_DATA` | The results of download and installation could not be read from the registry due to an invalid data format. |
|
||||
| 0x80243003 | `WU_E_INSTALLATION_RESULTS_NOT_FOUND` | The results of download and installation are not available; the operation may have failed to start. |
|
||||
| 0x80243004 | `WU_E_TRAYICON_FAILURE` | A failure occurred when trying to create an icon in the taskbar notification area. |
|
||||
| 0x80243FFD | `WU_E_NON_UI_MODE` | Unable to show UI when in non-UI mode; WU client UI modules may not be installed. |
|
||||
| 0x80243FFE | `WU_E_WUCLTUI_UNSUPPORTED_VERSION` | Unsupported version of WU client UI exported functions. |
|
||||
| 0x80243FFD | `WU_E_NON_UI_MODE` | Unable to show UI when in non-UI mode; Windows Update client UI modules may not be installed. |
|
||||
| 0x80243FFE | `WU_E_WUCLTUI_UNSUPPORTED_VERSION` | Unsupported version of Windows Update client UI exported functions. |
|
||||
| 0x80243FFF | `WU_E_AUCLIENT_UNEXPECTED` | There was a user interface error not covered by another `WU_E_AUCLIENT_*` error code. |
|
||||
| 0x8024043D | `WU_E_SERVICEPROP_NOTAVAIL` | The requested service property is not available. |
|
||||
|
||||
|
||||
@ -47,8 +47,8 @@ To understand the changes to the Windows Update architecture that UUP introduces
|
||||
>
|
||||
>Store apps aren't installed by USO, today they are separate.
|
||||
|
||||
- **WU Client/ UpdateAgent** - The component running on your PC. It's essentially a DLL that is downloaded to the device when an update is applicable. It surfaces the APIs needed to perform an update, including those needed to generate a list of payloads to download, as well as starts stage and commit operations. It provides a unified interface that abstracts away the underlying update technologies from the caller.
|
||||
- **WU Arbiter handle**- Code that is included in the UpdateAgent binary. The arbiter gathers information about the device, and uses the CompDB(s) to output an action list. It is responsible for determining the final "composition state" of your device, and which payloads (like ESDs or packages) are needed to get your device up to date.
|
||||
- **Windows Update Client/ UpdateAgent** - The component running on your PC. It's essentially a DLL that is downloaded to the device when an update is applicable. It surfaces the APIs needed to perform an update, including those needed to generate a list of payloads to download, as well as starts stage and commit operations. It provides a unified interface that abstracts away the underlying update technologies from the caller.
|
||||
- **Windows Update Arbiter handle**- Code that is included in the UpdateAgent binary. The arbiter gathers information about the device, and uses the CompDB(s) to output an action list. It is responsible for determining the final "composition state" of your device, and which payloads (like ESDs or packages) are needed to get your device up to date.
|
||||
- **Deployment Arbiter**- A deployment manager that calls different installers. For example, CBS.
|
||||
|
||||
Additional components include the following-
|
||||
|
||||
@ -37,7 +37,7 @@ The following table describes some log files and how to use them for troubleshoo
|
||||
|setupact.log|Post-upgrade (after OOBE):<br>Windows\Panther|Contains information about setup actions during the installation.|Investigate post-upgrade related issues.|
|
||||
|setuperr.log|Same as setupact.log|Contains information about setup errors during the installation.|Review all errors encountered during the installation phase.|
|
||||
|miglog.xml|Post-upgrade (after OOBE):<br>Windows\Panther|Contains information about what was migrated during the installation.|Identify post upgrade data migration issues.|
|
||||
|BlueBox.log|Down-Level:<br>Windows\Logs\Mosetup|Contains information communication between setup.exe and Windows Update.|Use during WSUS and WU down-level failures or for 0xC1900107.|
|
||||
|BlueBox.log|Down-Level:<br>Windows\Logs\Mosetup|Contains information communication between setup.exe and Windows Update.|Use during WSUS and Windows Update down-level failures or for 0xC1900107.|
|
||||
|Supplemental rollback logs:<br>Setupmem.dmp<br>setupapi.dev.log<br>Event logs (*.evtx)|$Windows.~BT\Sources\Rollback|Additional logs collected during rollback.|Setupmem.dmp: If OS bug checks during upgrade, setup will attempt to extract a mini-dump.<br>Setupapi: Device install issues - 0x30018<br>Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.|
|
||||
|
||||
## Log entry structure
|
||||
|
||||
@ -184,5 +184,5 @@ Also see the following sequential list of modern setup (mosetup) error codes wit
|
||||
- [Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications)
|
||||
- [Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/home?category=Windows10ITPro)
|
||||
- [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors)
|
||||
- [Win 7 to Win 10 upgrade error (0x800707E7 - 0x3000D)](https://answers.microsoft.com/en-us/windows/forum/all/win-7-to-win-10-upgrade-error-0x800707e7-0x3000d/1273bc1e-8a04-44d4-a6b2-808c9feeb020))
|
||||
- [Win 10 upgrade error: User profile suffix mismatch, 0x800707E7 - 0x3000D](https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/win-10-upgrade-error-user-profile-suffix-mismatch/0f006733-2af5-4b42-a2d4-863fad05273d?page=3)
|
||||
- [Windows 7 to Windows 10 upgrade error (0x800707E7 - 0x3000D)](https://answers.microsoft.com/en-us/windows/forum/all/win-7-to-win-10-upgrade-error-0x800707e7-0x3000d/1273bc1e-8a04-44d4-a6b2-808c9feeb020))
|
||||
- [Windows 10 upgrade error: User profile suffix mismatch, 0x800707E7 - 0x3000D](https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/win-10-upgrade-error-user-profile-suffix-mismatch/0f006733-2af5-4b42-a2d4-863fad05273d?page=3)
|
||||
|
||||
@ -293,7 +293,7 @@ Each rule name and its associated unique rule identifier are listed with a descr
|
||||
39. WimApplyExtractFailure – 746879E9-C9C5-488C-8D4B-0C811FF3A9A8
|
||||
- Matches a wim apply failure during wim extraction phases of setup. Will output the extension, path and error code.
|
||||
40. UpdateAgentExpanderFailure – 66E496B3-7D19-47FA-B19B-4040B9FD17E2
|
||||
- Matches DPX expander failures in the down-level phase of update from WU. Will output the package name, function, expression and error code.
|
||||
- Matches DPX expander failures in the down-level phase of update from Windows Update. Will output the package name, function, expression and error code.
|
||||
41. FindFatalPluginFailure – E48E3F1C-26F6-4AFB-859B-BF637DA49636
|
||||
- Matches any plug-in failure that setupplatform decides is fatal to setup. Will output the plugin name, operation and error code.
|
||||
42. AdvancedInstallerFailed - 77D36C96-32BE-42A2-BB9C-AAFFE64FCADC
|
||||
|
||||
@ -52,15 +52,15 @@ X = unsupported <BR>
|
||||
| **Home > Pro for Workstations** |  |  |  |  |  |  |
|
||||
| **Home > Pro Education** |  |  |  |  |  |  |
|
||||
| **Home > Education** |  |  |  |  |  |  |
|
||||
| **Pro > Pro for Workstations** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Pro > Pro Education** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Pro > Education** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Pro > Enterprise** |  |  |  |  <br>(1703 - PC)<br>(1709 - MSfB) |  |  |
|
||||
| **Pro for Workstations > Pro Education** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Pro for Workstations > Education** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Pro for Workstations > Enterprise** |  |  |  |  <br>(1703 - PC)<br>(1709 - MSfB) |  |  |
|
||||
| **Pro Education > Education** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Enterprise > Education** |  |  |  |  <br>(MSfB) |  |  |
|
||||
| **Pro > Pro for Workstations** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
| **Pro > Pro Education** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
| **Pro > Education** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
| **Pro > Enterprise** |  |  |  |  <br>(1703 - PC)<br>(1709 - Microsoft Store for Business) |  |  |
|
||||
| **Pro for Workstations > Pro Education** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
| **Pro for Workstations > Education** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
| **Pro for Workstations > Enterprise** |  |  |  |  <br>(1703 - PC)<br>(1709 - Microsoft Store for Business) |  |  |
|
||||
| **Pro Education > Education** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
| **Enterprise > Education** |  |  |  |  <br>(Microsoft Store for Business) |  |  |
|
||||
|
||||
> [!NOTE]
|
||||
> - For information about upgrade paths in Windows 10 in S mode (for Pro or Education), check out [Windows 10 Pro/Enterprise in S mode](../windows-10-pro-in-s-mode.md)
|
||||
|
||||
@ -26,7 +26,7 @@ If you are also migrating to a different edition of Windows, see [Windows 10 edi
|
||||
|
||||
- **In-place upgrade from Windows 7, Windows 8.1, or [Windows 10 General Availability Channel](/windows/release-health/release-information)** to Windows 10 LTSC is not supported. Windows 10 LTSC 2015 did not block this in-place upgrade path. This issue was corrected in the Windows 10 LTSC 2016 release, which only allows data-only and clean install options.
|
||||
|
||||
You can upgrade from Windows 10 LTSC to Windows 10 General Availability Channel, provided that you upgrade to the same or a newer build version. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Upgrade is supported using the in-place upgrade process (using Windows setup). You will need to use the Product Key switch if you want to keep your apps. If you don't use the switch, the option **Keep personal files and apps** option is grayed out. The command line would be `setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx`, using your relevant Windows 10 SAC product key. For example, if using a KMS, the command line would be `setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43`.
|
||||
You can upgrade from Windows 10 LTSC to Windows 10 General Availability Channel, provided that you upgrade to the same or a newer build version. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Upgrade is supported using the in-place upgrade process (using Windows setup). You will need to use the Product Key switch if you want to keep your apps. If you don't use the switch, the option **Keep personal files and apps** option is grayed out. The command line would be `setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx`, using your relevant Windows 10 GA Channel product key. For example, if using a KMS, the command line would be `setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43`.
|
||||
|
||||
- **Windows N/KN**: Windows "N" and "KN" SKUs (editions without media-related functionality) follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.
|
||||
|
||||
|
||||
@ -14,6 +14,9 @@ msreviewer: hathind
|
||||
|
||||
# Add and verify admin contacts
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The Admin contacts blade isn't available during public preview. However, we'll use the admin contacts provided by you during public preview onboarding.
|
||||
|
||||
There are several ways that Windows Autopatch service communicates with customers. To streamline communication and ensure we're checking with the right people when you [submit a support request](../operate/windows-autopatch-support-request.md), you must provide a set of admin contacts when you onboard with Windows Autopatch.
|
||||
|
||||
> [!IMPORTANT]
|
||||
|
||||
@ -14,7 +14,7 @@ msreviewer: hathind
|
||||
|
||||
# Microsoft Edge
|
||||
|
||||
Windows Autopatch uses the [Stable channel](/deployedge/microsoft-edge-channels%22%20/l%20%22stable-channel) of Microsoft Edge.
|
||||
Windows Autopatch uses the [Stable Channel](/deployedge/microsoft-edge-channels#stable-channel) of Microsoft Edge.
|
||||
|
||||
## Device eligibility
|
||||
|
||||
@ -31,7 +31,7 @@ Microsoft Edge will check for updates every 10 hours. Quality updates occur week
|
||||
|
||||
Browser updates with critical security fixes will have a faster rollout cadence than updates that don't have critical security fixes to ensure prompt protection from vulnerabilities.
|
||||
|
||||
Devices in the Test device group receive feature updates from the [Beta channel](/deployedge/microsoft-edge-channels#beta-channel). This channel is fully supported and automatically updated with new features approximately every four weeks.
|
||||
Devices in the Test device group receive feature updates from the [Beta Channel](/deployedge/microsoft-edge-channels#beta-channel). This channel is fully supported and automatically updated with new features approximately every four weeks.
|
||||
|
||||
## Pausing and resuming updates
|
||||
|
||||
|
||||
@ -42,8 +42,9 @@ sections:
|
||||
- [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses)
|
||||
- [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
|
||||
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
|
||||
Additional pre-requisites for devices managed by Configuration Manager:
|
||||
- [Co-management](/prepare/windows-autopatch-prerequisites.md#co-management-requirements)
|
||||
- [Configuration Manager version 2010 or later](/mem/configmgr/core/plan-design/changes/whats-new-in-version-2010)
|
||||
- [A supported version of Configuration Manager](/mem/configmgr/core/servers/manage/updates#supported-versions)
|
||||
- [Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune](/mem/configmgr/comanage/how-to-switch-workloads) (minimum Pilot Intune)
|
||||
- question: What are the licensing requirements for Windows Autopatch?
|
||||
answer: |
|
||||
@ -103,4 +104,4 @@ sections:
|
||||
Programmatic access to Autopatch isn't currently available.
|
||||
additionalContent: |
|
||||
## Additional Content
|
||||
[Provide feedback](https://go.microsoft.com/fwlink/?linkid=2195593) or start a discussion in our [Windows Autopatch Tech Community](https://aka.ms/Community/WindowsAutopatch
|
||||
[Provide feedback](https://go.microsoft.com/fwlink/?linkid=2195593) or start a discussion in our [Windows Autopatch Tech Community](https://aka.ms/Community/WindowsAutopatch)
|
||||
|
||||
@ -396,7 +396,7 @@ For the purposes of this demo, select **All** under the **MDM user scope** and s
|
||||
|
||||
## Register your VM
|
||||
|
||||
Your VM (or device) can be registered either via Intune or Microsoft Store for Business (MSfB). Both processes are shown here, but *only pick one* for the purposes of this lab. It's highly recommended that you use Intune rather than MSfB.
|
||||
Your VM (or device) can be registered either via Intune or Microsoft Store for Business (MSfB). Both processes are shown here, but *only pick one* for the purposes of this lab. It's highly recommended that you use Intune rather than Microsoft Store for Business.
|
||||
|
||||
### Autopilot registration using Intune
|
||||
|
||||
@ -430,7 +430,7 @@ Optional: see the following video for an overview of the process.
|
||||
|
||||
> [!video https://www.youtube.com/embed/IpLIZU_j7Z0]
|
||||
|
||||
First, you need a MSfB account. You can use the same one you created above for Intune, or follow [these instructions](/microsoft-store/windows-store-for-business-overview) to create a new one.
|
||||
First, you need a Microsoft Store for Business account. You can use the same one you created above for Intune, or follow [these instructions](/microsoft-store/windows-store-for-business-overview) to create a new one.
|
||||
|
||||
Next, to sign in to [Microsoft Store for Business](https://businessstore.microsoft.com/en-us/store) with your test account, select **Sign in** on the upper-right-corner of the main page.
|
||||
|
||||
@ -445,16 +445,16 @@ Select the **Add devices** link to upload your CSV file. A message appears that
|
||||
## Create and assign a Windows Autopilot deployment profile
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Autopilot profiles can be created and assigned to your registered VM or device either through Intune or MSfB. Both processes are shown here, but only *pick one for the purposes of this lab*:
|
||||
> Autopilot profiles can be created and assigned to your registered VM or device either through Intune or Microsoft Store for Business. Both processes are shown here, but only *pick one for the purposes of this lab*:
|
||||
|
||||
Pick one:
|
||||
- [Create profiles using Intune](#create-a-windows-autopilot-deployment-profile-using-intune)
|
||||
- [Create profiles using MSfB](#create-a-windows-autopilot-deployment-profile-using-msfb)
|
||||
- [Create profiles using Microsoft Store for Business](#create-a-windows-autopilot-deployment-profile-using-msfb)
|
||||
|
||||
### Create a Windows Autopilot deployment profile using Intune
|
||||
|
||||
> [!NOTE]
|
||||
> Even if you registered your device in MSfB, it still appears in Intune. Although, you might have to **sync** and then **refresh** your device list.
|
||||
> Even if you registered your device in Microsoft Store for Business, it still appears in Intune. Although, you might have to **sync** and then **refresh** your device list.
|
||||
|
||||
|
||||
|
||||
@ -533,13 +533,13 @@ Select **OK**, and then select **Create**.
|
||||
|
||||
If you already created and assigned a profile via Intune with the steps immediately above, then skip this section.
|
||||
|
||||
A [video](https://www.youtube.com/watch?v=IpLIZU_j7Z0) is available that covers the steps required to create and assign profiles in MSfB. These steps are also summarized below.
|
||||
A [video](https://www.youtube.com/watch?v=IpLIZU_j7Z0) is available that covers the steps required to create and assign profiles in Microsoft Store for Business. These steps are also summarized below.
|
||||
|
||||
First, sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com/manage/dashboard) using the Intune account you initially created for this lab.
|
||||
|
||||
Select **Manage** from the top menu, then select **Devices** from the left navigation tree.
|
||||
|
||||
|
||||
|
||||
|
||||
Select the **Windows Autopilot Deployment Program** link in the **Devices** tile.
|
||||
|
||||
@ -548,17 +548,17 @@ To CREATE the profile:
|
||||
Select your device from the **Devices** list:
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
> 
|
||||
|
||||
On the Autopilot deployment dropdown menu, select **Create new profile**:
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
> 
|
||||
|
||||
Name the profile, choose your desired settings, and then select **Create**:
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
> 
|
||||
|
||||
The new profile is added to the Autopilot deployment list.
|
||||
|
||||
@ -567,12 +567,12 @@ To ASSIGN the profile:
|
||||
To assign (or reassign) the profile to a device, select the checkboxes next to the device you registered for this lab. Then, select the profile you want to assign from the **Autopilot deployment** dropdown menu, as shown:
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
> 
|
||||
|
||||
To confirm the profile was successfully assigned to the intended device, check the contents of the **Profile** column:
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
> 
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The new profile is only applied if the device hasn't started and gone through OOBE. Settings from a different profile can't be applied when another profile has been applied. Windows would need to be reinstalled on the device for the second profile to be applied to the device.
|
||||
@ -609,7 +609,7 @@ Windows Autopilot takes over to automatically join your device into Azure AD and
|
||||
|
||||
## Remove devices from Autopilot
|
||||
|
||||
To use the device (or VM) for other purposes after completion of this lab, you need to remove (deregister) it from Autopilot via either Intune or MSfB, and then reset it. Instructions for deregistering devices can be found at [Enroll Windows devices in Intune by using Windows Autopilot](/intune/enrollment-autopilot#create-an-autopilot-device-group), [Remove devices by using wipe, retire, or manually unenrolling the device](/intune/devices-wipe#delete-devices-from-the-azure-active-directory-portal), and below.
|
||||
To use the device (or VM) for other purposes after completion of this lab, you need to remove (deregister) it from Autopilot via either Intune or Microsoft Store for Business, and then reset it. Instructions for deregistering devices can be found at [Enroll Windows devices in Intune by using Windows Autopilot](/intune/enrollment-autopilot#create-an-autopilot-device-group), [Remove devices by using wipe, retire, or manually unenrolling the device](/intune/devices-wipe#delete-devices-from-the-azure-active-directory-portal), and below.
|
||||
|
||||
### Delete (deregister) Autopilot device
|
||||
|
||||
|
||||
Reference in New Issue
Block a user