mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 03:43:39 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into DOtrouble
This commit is contained in:
jaimeo
@ -111,7 +111,7 @@ In either of these scenarios, you can make a variety of configuration changes to
|
||||
## Stay up to date
|
||||
|
||||
|
||||
For computers already running Windows 10 on the Current Branch or Current Branch for Business, new upgrades will periodically be deployed, approximately two to three times per year. You can deploy these upgrades by using a variety of methods:
|
||||
For computers already running Windows 10 on the Semi-Annual Channel, new upgrades will periodically be deployed, approximately two to three times per year. You can deploy these upgrades by using a variety of methods:
|
||||
|
||||
- Windows Update or Windows Update for Business, for devices where you want to receive updates directly from the Internet.
|
||||
|
||||
|
||||
@ -85,13 +85,13 @@ Starting with Windows 10, version 1709, the Windows Update for Business settings
|
||||
| Manage Windows Insider Preview builds | System/AllowBuildPreview | Update/ManagePreviewBuilds |
|
||||
| Manage when updates are received | Select when Feature Updates are received | Select when Preview Builds and Feature Updates are received (Update/BranchReadinessLevel) |
|
||||
|
||||
## Managing Windows Update for Business with Software Center Configuration Manager
|
||||
## Managing Windows Update for Business with System Center Configuration Manager
|
||||
|
||||
Starting with Windows 10, version 1709, you can assign a collection of devices to have dual scan enabled and manage that collection with Windows Update for Business policies. Starting with Windows 10, version 1809, you can set a collection of devices to receive the Windows Insider Preview Feature Updates from Windows Update from within Software Center Configuration Manager.
|
||||
Starting with Windows 10, version 1709, you can assign a collection of devices to have dual scan enabled and manage that collection with Windows Update for Business policies. Starting with Windows 10, version 1809, you can set a collection of devices to receive the Windows Insider Preview Feature Updates from Windows Update from within System Center Configuration Manager.
|
||||
|
||||
| Action | Windows 10 versions between 1709 and 1809 | Windows 10 versions after 1809 |
|
||||
| --- | --- | --- |
|
||||
| Manage Windows Update for Business in Configuration Manager | Manage Feature or Quality Updates with Windows Update for Business via Dual Scan | Manage Insider pre-release builds with Windows Update for Business within Software Center Configuration Manager |
|
||||
| Manage Windows Update for Business in Configuration Manager | Manage Feature or Quality Updates with Windows Update for Business via Dual Scan | Manage Insider pre-release builds with Windows Update for Business within System Center Configuration Manager |
|
||||
|
||||
## Managing Windows Update for Business with Windows Settings options
|
||||
Windows Settings includes options to control certain Windows Update for Business features:
|
||||
|
||||
@ -12,21 +12,24 @@ ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows error reporting
|
||||
# Windows Error Reporting
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
>[!NOTE]
|
||||
>This is a 300 level topic (moderately advanced).<br>
|
||||
>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
|
||||
> This is a 300 level topic (moderately advanced).
|
||||
> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
|
||||
|
||||
|
||||
When Windows Setup fails, the result and extend code are recorded as an informational event in the Application log by Windows Error Reporting as event 1001. The event name is **WinSetupDiag02**. You can use Event Viewer to review this event, or you can use Windows PowerShell.
|
||||
|
||||
To use Windows PowerShell, type the following commands from an elevated Windows PowerShell prompt:
|
||||
|
||||
```
|
||||
>[!IMPORTANT]
|
||||
>}The following source will be available only if you have updated from a previous version of Windows 10 to a new version. If you installed the current version and have not updated, the source named **WinSetupDiag02** will be unavailable.
|
||||
|
||||
```Powershell
|
||||
$events = Get-WinEvent -FilterHashtable @{LogName="Application";ID="1001";Data="WinSetupDiag02"}
|
||||
$event = [xml]$events[0].ToXml()
|
||||
$event.Event.EventData.Data
|
||||
@ -40,19 +43,20 @@ To use Event Viewer:
|
||||
Note: For legacy operating systems, the Event Name was WinSetupDiag01.
|
||||
|
||||
Ten parameters are listed in the event:
|
||||
<br>
|
||||
<table border="0">
|
||||
<tr><td>P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool)</td></tr>
|
||||
<tr><td>P2: Setup Mode (x=default,1=Downlevel,5=Rollback)</td></tr>
|
||||
<tr><td>P3: New OS Architecture (x=default,0=X86,9=AMD64)</td></tr>
|
||||
<tr><td>P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked)</td></tr>
|
||||
<tr><td><b>P5: Result Error Code</b> (Ex: 0xc1900101)</td></tr>
|
||||
<tr><td><b>P6: Extend Error Code</b> (Ex: 0x20017)</td></tr>
|
||||
<tr><td>P7: Source OS build (Ex: 9600)</td></tr>
|
||||
<tr><td>P8: Source OS branch (not typically available)</td></tr>
|
||||
<tr><td>P9: New OS build (Ex: 16299}</td></tr>
|
||||
<tr><td>P10: New OS branch (Ex: rs3_release}</td></tr>
|
||||
</table>
|
||||
|
||||
| Parameters |
|
||||
| ------------- |
|
||||
|P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool) |
|
||||
|P2: Setup Mode (x=default,1=Downlevel,5=Rollback) |
|
||||
|P3: New OS Architecture (x=default,0=X86,9=AMD64) |
|
||||
|P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked) |
|
||||
|**P5: Result Error Code** (Ex: 0xc1900101) |
|
||||
|**P6: Extend Error Code** (Ex: 0x20017) |
|
||||
|P7: Source OS build (Ex: 9600) |
|
||||
|P8: Source OS branch (not typically available) |
|
||||
|P9: New OS build (Ex: 16299} |
|
||||
|P10: New OS branch (Ex: rs3_release} |
|
||||
|
||||
|
||||
The event will also contain links to log files that can be used to perform a detailed diagnosis of the error. An example of this event from a successful upgrade is shown below.
|
||||
|
||||
@ -60,8 +64,8 @@ The event will also contain links to log files that can be used to perform a det
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 FAQ for IT professionals](https://technet.microsoft.com/windows/dn798755.aspx)
|
||||
<br>[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
|
||||
<br>[Windows 10 Specifications](https://www.microsoft.com/en-us/windows/Windows-10-specifications)
|
||||
<br>[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
<br>[Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/kb/947821)
|
||||
[Windows 10 FAQ for IT professionals](https://technet.microsoft.com/windows/dn798755.aspx)
|
||||
[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
|
||||
[Windows 10 Specifications](https://www.microsoft.com/en-us/windows/Windows-10-specifications)
|
||||
[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
[Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/kb/947821)
|
||||
|
||||
@ -455,9 +455,9 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
<p>USMT migrates all user accounts on the computer, unless you specifically exclude an account with either the /<strong>ue</strong> or /<strong>uel</strong> options. For this reason, you do not need to specify this option on the command line. However, if you choose to specify the /<strong>all</strong> option, you cannot also use the /<strong>ui</strong>, /<strong>ue</strong> or /<strong>uel</strong> options.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/<strong>ui</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<td align="left"><p>/<strong>ui</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<p>or</p>
|
||||
<p>/<strong>ui</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<p>/<strong>ui</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<td align="left"><p><strong>(User include)</strong></p>
|
||||
<p>Migrates the specified users. By default, all users are included in the migration. Therefore, this option is helpful only when used with the /<strong>ue</strong> or /<strong>uel</strong> options. You can specify multiple /<strong>ui</strong> options, but you cannot use the /<strong>ui</strong> option with the /<strong>all</strong> option. <em>DomainName</em> and <em>UserName</em> can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you will need to surround it with quotation marks.</p>
|
||||
<div class="alert">
|
||||
@ -469,10 +469,10 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
</div>
|
||||
<p>For example:</p>
|
||||
<ul>
|
||||
<li><p>To include only User2 from the Fabrikam domain, type:</p>
|
||||
<p><code>/ue:*\* /ui:fabrikam\user2</code></p></li>
|
||||
<li><p>To migrate all users from the Fabrikam domain, and only the user accounts from other domains that have been active or otherwise modified in the last 30 days, type:</p>
|
||||
<p><code>/uel:30 /ui:fabrikam\*</code></p>
|
||||
<p>To include only User2 from the Fabrikam domain, type:</p>
|
||||
<p><code>/ue:*\* /ui:fabrikam\user2</code></p>
|
||||
<p>To migrate all users from the Fabrikam domain, and only the user accounts from other domains that have been active or otherwise modified in the last 30 days, type:</p>
|
||||
<p><code>/uel:30 /ui:fabrikam\*</code></p>
|
||||
<p>In this example, a user account from the Contoso domain that was last modified 2 months ago will not be migrated.</p></li>
|
||||
</ul>
|
||||
<p>For more examples, see the descriptions of the /<strong>ue</strong> and /<strong>ui</strong> options in this table.</p></td>
|
||||
@ -500,17 +500,17 @@ By default, all users are migrated. The only way to specify which users to inclu
|
||||
<li><p><strong>/uel:2002/1/15</strong> migrates users who have logged on or been modified January 15, 2002 or afterwards.</p></li>
|
||||
</ul>
|
||||
<p>For example:</p>
|
||||
<p><code>scanstate /i:migapp.xml /i:migdocs.xml \\server\share\migration\mystore /uel:0</code></p></td>
|
||||
<p><code>scanstate /i:migapp.xml /i:migdocs.xml \\server\share\migration\mystore /uel:0</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>/<strong>ue</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<td align="left"><p>/<strong>ue</strong>:<em><DomainName></em>\<em><UserName></em></p>
|
||||
<p>-or-</p>
|
||||
<p></p>
|
||||
<p>/<strong>ue</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<p>/<strong>ue</strong>:<em><ComputerName></em>\<em><LocalUserName></em></p></td>
|
||||
<td align="left"><p><strong>(User exclude)</strong></p>
|
||||
<p>Excludes the specified users from the migration. You can specify multiple /<strong>ue</strong> options. You cannot use this option with the /<strong>all</strong> option. <em><DomainName></em> and <em><UserName></em> can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you need to surround it with quotation marks.</p>
|
||||
<p>For example:</p>
|
||||
<p><code>scanstate /i:migdocs.xml /i:migapp.xml \\server\share\migration\mystore /ue:contoso\user1</code></p></td>
|
||||
<p><code>scanstate /i:migdocs.xml /i:migapp.xml \\server\share\migration\mystore /ue:contoso\user1</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -548,15 +548,15 @@ The following examples apply to both the /**ui** and /**ue** options. You can re
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Exclude all domain users.</p></td>
|
||||
<td align="left"><p><code>/ue:Domain\*</code></p></td>
|
||||
<td align="left"><p><code>/ue:Domain\*</code></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Exclude all local users.</p></td>
|
||||
<td align="left"><p><code>/ue:%computername%\*</code></p></td>
|
||||
<td align="left"><p><code>/ue:%computername%\*</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Exclude users in all domains named User1, User2, and so on.</p></td>
|
||||
<td align="left"><p><code>/ue:*\user*</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\user*</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -586,23 +586,23 @@ The /**uel** option takes precedence over the /**ue** option. If a user has logg
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Include only User2 from the Fabrikam domain and exclude all other users.</p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:fabrikam\user2</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:fabrikam\user2</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Include only the local user named User1 and exclude all other users.</p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:user1</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:user1</code></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Include only the domain users from Contoso, except Contoso\User1.</p></td>
|
||||
<td align="left"><p>This behavior cannot be completed using a single command. Instead, to migrate this set of users, you will need to specify the following:</p>
|
||||
<ul>
|
||||
<li><p>On the <strong>ScanState</strong> command line, type: <code>/ue:*\* /ui:contoso\*</code></p></li>
|
||||
<li><p>On the <strong>ScanState</strong> command line, type: <code>/ue:*\* /ui:contoso\*</code></p></li>
|
||||
<li><p>On the <strong>LoadState</strong> command line, type: <code>/ue:contoso\user1</code></p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Include only local (non-domain) users.</p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:%computername%\*</code></p></td>
|
||||
<td align="left"><p><code>/ue:*\* /ui:%computername%\*</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -25,8 +25,8 @@ IT admins can perform a local Windows Autopilot Reset to quickly remove personal
|
||||
|
||||
To enable local Autopilot Reset in Windows 10:
|
||||
|
||||
1. [Enable the policy for the feature](#enable-local-autopilot-reset)
|
||||
2. [Trigger a reset for each device](#trigger-local-autopilot-reset)
|
||||
1. [Enable the policy for the feature](#enable-local-windows-autopilot-reset)
|
||||
2. [Trigger a reset for each device](#trigger-local-windows-autopilot-reset)
|
||||
|
||||
## Enable local Windows Autopilot Reset
|
||||
|
||||
|
||||
Reference in New Issue
Block a user