mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'master' into MDBranch20H2Policies
This commit is contained in:
ManikaDhiman
commit
9bff0ff222
@ -63,7 +63,7 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
|
||||
4. Click **Check Names**. If the **Name Not Found** window opens, click **Locations** and select this PC.
|
||||
|
||||
> [!TIP]
|
||||
> When you connect to the remote PC, enter your account name in this format: `AzureAD UPN`. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.
|
||||
> When you connect to the remote PC, enter your account name in this format: AzureAD\yourloginid@domain.com. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.
|
||||
|
||||
> [!Note]
|
||||
> If you cannot connect using Remote Desktop Connection 6.0, you must turn off the new features of RDP 6.0 and revert back to RDP 5.0 by making a few changes in the RDP file. See the details in the [support article](https://support.microsoft.com/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e).
|
||||
|
||||
@ -20,7 +20,7 @@ This article lists new and updated articles for the Mobile Device Management (MD
|
||||
|
||||
|New or updated article | Description|
|
||||
|--- | ---|
|
||||
| [Policy CSP](policy-configuration-service-provider.md) | Added the following new policies<br>- [LocalUsersAndGroups/Configure](policy-csp-localusersandgroups.md#localusersandgroups-configure)<br>- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)<br>- [MixedReality/BrightnessButtonDisabled](policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled)<br>- [MixedReality/FallbackDiagnostics](policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics)<br>- [MixedReality/MicrophoneDisabled](policy-csp-mixedreality.md#mixedreality-microphonedisabled)<br>- [MixedReality/VolumeButtonDisabled](policy-csp-mixedreality.md#mixedreality-volumebuttondisabled)<br>- [Update/DisableWUfBSafeguards](policy-csp-update.md#update-disablewufbsafeguards)<br>- [WindowsSandbox/AllowAudioInput](policy-csp-windowssandbox.md#windowssandbox-allowaudioinput)<br>- [WindowsSandbox/AllowClipboardRedirection](policy-csp-windowssandbox.md#windowssandbox-allowclipboardredirection)<br>- [WindowsSandbox/AllowNetworking](policy-csp-windowssandbox.md#windowssandbox-allownetworking)<br>- [WindowsSandbox/AllowPrinterRedirection](policy-csp-windowssandbox.md#windowssandbox-allowprinterredirection)<br>- [WindowsSandbox/AllowVGPU](policy-csp-windowssandbox.md#windowssandbox-allowvgpu)<br>- [WindowsSandbox/AllowVideoInput](policy-csp-windowssandbox.md#windowssandbox-allowvideoinput) |
|
||||
| [Policy CSP](policy-configuration-service-provider.md) | Added the following new policies<br>- [Experience/DisableCloudOptimizedContent](policy-csp-experience.md#experience-disablecloudoptimizedcontent)<br>- [LocalUsersAndGroups/Configure](policy-csp-localusersandgroups.md#localusersandgroups-configure)<br>- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)<br>- [MixedReality/BrightnessButtonDisabled](policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled)<br>- [MixedReality/FallbackDiagnostics](policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics)<br>- [MixedReality/MicrophoneDisabled](policy-csp-mixedreality.md#mixedreality-microphonedisabled)<br>- [MixedReality/VolumeButtonDisabled](policy-csp-mixedreality.md#mixedreality-volumebuttondisabled)<br>- [Update/DisableWUfBSafeguards](policy-csp-update.md#update-disablewufbsafeguards)<br>- [WindowsSandbox/AllowAudioInput](policy-csp-windowssandbox.md#windowssandbox-allowaudioinput)<br>- [WindowsSandbox/AllowClipboardRedirection](policy-csp-windowssandbox.md#windowssandbox-allowclipboardredirection)<br>- [WindowsSandbox/AllowNetworking](policy-csp-windowssandbox.md#windowssandbox-allownetworking)<br>- [WindowsSandbox/AllowPrinterRedirection](policy-csp-windowssandbox.md#windowssandbox-allowprinterredirection)<br>- [WindowsSandbox/AllowVGPU](policy-csp-windowssandbox.md#windowssandbox-allowvgpu)<br>- [WindowsSandbox/AllowVideoInput](policy-csp-windowssandbox.md#windowssandbox-allowvideoinput) |
|
||||
|
||||
## September 2020
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
|
||||
|New or updated article|Description|
|
||||
|-----|-----|
|
||||
| [Policy CSP](policy-configuration-service-provider.md) | Added the following new policies in Windows 10, version 20H2:<br>- [LocalUsersAndGroups/Configure](policy-csp-localusersandgroups.md#localusersandgroups-configure)<br>- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)<br>- [MixedReality/BrightnessButtonDisabled](policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled)<br>- [MixedReality/FallbackDiagnostics](policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics)<br>- [MixedReality/MicrophoneDisabled](policy-csp-mixedreality.md#mixedreality-microphonedisabled)<br>- [MixedReality/VolumeButtonDisabled](policy-csp-mixedreality.md#mixedreality-volumebuttondisabled) |
|
||||
| [Policy CSP](policy-configuration-service-provider.md) | Added the following new policies in Windows 10, version 20H2:<br>- [Experience/DisableCloudOptimizedContent](policy-csp-experience.md#experience-disablecloudoptimizedcontent)<br>- [LocalUsersAndGroups/Configure](policy-csp-localusersandgroups.md#localusersandgroups-configure)<br>- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)<br>- [MixedReality/BrightnessButtonDisabled](policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled)<br>- [MixedReality/FallbackDiagnostics](policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics)<br>- [MixedReality/MicrophoneDisabled](policy-csp-mixedreality.md#mixedreality-microphonedisabled)<br>- [MixedReality/VolumeButtonDisabled](policy-csp-mixedreality.md#mixedreality-volumebuttondisabled) |
|
||||
| [WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md) | Updated the description of the following node:<br>- Settings/AllowWindowsDefenderApplicationGuard |
|
||||
|
||||
## What’s new in MDM for Windows 10, version 2004
|
||||
|
||||
@ -2983,6 +2983,9 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
<dd>
|
||||
<a href="./policy-csp-experience.md#experience-configurewindowsspotlightonlockscreen" id="experience-configurewindowsspotlightonlockscreen">Experience/ConfigureWindowsSpotlightOnLockScreen</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-experience.md#experience-disablecloudoptimizedcontent" id="experience-disablecloudoptimizedcontent">Experience/DisableCloudOptimizedContent</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-experience.md#experience-donotshowfeedbacknotifications" id="experience-donotshowfeedbacknotifications">Experience/DoNotShowFeedbackNotifications</a>
|
||||
</dd>
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/27/2019
|
||||
ms.date: 11/02/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -1226,6 +1226,76 @@ The following list shows the supported values:
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="experience-disablecloudoptimizedcontent"></a>**Experience/DisableCloudOptimizedContent**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Windows Edition</th>
|
||||
<th>Supported?</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Home</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
<hr/>
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting lets you turn off cloud optimized content in all Windows experiences.
|
||||
|
||||
If you enable this policy setting, Windows experiences that use the cloud optimized content client component will present the default fallback content.
|
||||
|
||||
If you disable or do not configure this policy setting, Windows experiences will be able to use cloud optimized content.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP English name: *Turn off cloud optimized content*
|
||||
- GP name: *DisableCloudOptimizedContent*
|
||||
- GP path: *Windows Components/Cloud Content*
|
||||
- GP ADMX file name: *CloudContent.admx*
|
||||
|
||||
<!--/ADMXMapped-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 (default) – Disabled.
|
||||
- 1 – Enabled.
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="experience-donotshowfeedbacknotifications"></a>**Experience/DoNotShowFeedbackNotifications**
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/21/2020
|
||||
ms.date: 11/03/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -461,11 +461,6 @@ Enables the IT admin to manage automatic update behavior to scan, download, and
|
||||
|
||||
Supported operations are Get and Replace.
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This option should be used only for systems under regulatory compliance, as you will not get security updates as well.
|
||||
|
||||
|
||||
If the policy is not configured, end-users get the default behavior (Auto install and restart).
|
||||
|
||||
<!--/Description-->
|
||||
@ -488,6 +483,11 @@ The following list shows the supported values:
|
||||
- 4 – Auto install and restart without end-user control. Updates are downloaded automatically on non-metered networks and installed during "Automatic Maintenance" when the device is not in use and is not running on battery power. If automatic maintenance is unable to install updates for two days, Windows Update will install updates right away. If a restart is required, then the device is automatically restarted when the device is not actively being used. This setting option also sets the end-user control panel to read-only.
|
||||
- 5 – Turn off automatic updates.
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This option should be used only for systems under regulatory compliance, as you will not get security updates as well.
|
||||
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ manager: dansimp
|
||||
|
||||
Cortana will respond with the information from Bing.
|
||||
|
||||
:::image type="content" source="../screenshot5.png" alt-text="Screenshot: Cortana showing current time in Hyderbad":::
|
||||
:::image type="content" source="../screenshot5.png" alt-text="Screenshot: Cortana showing current time in Hyderabad":::
|
||||
|
||||
>[!NOTE]
|
||||
>This scenario requires Bing Answers to be enabled. To learn more, see [Set up and configure the Bing Answers feature](https://docs.microsoft.com/windows/configuration/cortana-at-work/set-up-and-test-cortana-in-windows-10#set-up-and-configure-the-bing-answers-feature).
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Use MDM Bridge WMI Provider to create a Windows 10 kiosk (Windows 10)
|
||||
description: Environments that use Windows Management Instrumentation (WMI)can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||
description: Environments that use Windows Management Instrumentation (WMI) can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||
ms.assetid: 428680AE-A05F-43ED-BD59-088024D1BFCC
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
@ -22,9 +22,9 @@ ms.topic: article
|
||||
|
||||
- Windows 10 Pro, Enterprise, and Education
|
||||
|
||||
Environments that use [Windows Management Instrumentation (WMI)](https://msdn.microsoft.com/library/aa394582.aspx) can use the [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/desktop/dn905224.aspx) to configure the MDM_AssignedAccess class. See [PowerShell Scripting with WMI Bridge Provider](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/using-powershell-scripting-with-the-wmi-bridge-provider) for more details about using a PowerShell script to configure AssignedAccess.
|
||||
Environments that use [Windows Management Instrumentation (WMI)](https://msdn.microsoft.com/library/aa394582.aspx) can use the [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/desktop/dn905224.aspx) to configure the MDM_AssignedAccess class. For more information about using a PowerShell script to configure AssignedAccess, see [PowerShell Scripting with WMI Bridge Provider](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/using-powershell-scripting-with-the-wmi-bridge-provider).
|
||||
|
||||
Here’s an example to set AssignedAccess configuration:
|
||||
Here's an example to set AssignedAccess configuration:
|
||||
|
||||
1. Download the [psexec tool](https://technet.microsoft.com/sysinternals/bb897553.aspx).
|
||||
2. Run `psexec.exe -i -s cmd.exe`.
|
||||
|
||||
@ -255,7 +255,7 @@ This sample demonstrates that both UWP and Win32 apps can be configured to autom
|
||||
```
|
||||
|
||||
## [Preview] Global Profile Sample XML
|
||||
Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lock down mode, or used as mitigation when a profile cannot be determined for an user.
|
||||
Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lockdown mode, or used as mitigation when a profile cannot be determined for a user.
|
||||
|
||||
This sample demonstrates that only a global profile is used, no active user configured. Global profile will be applied when every non-admin account logs in
|
||||
```xml
|
||||
@ -309,7 +309,7 @@ This sample demonstrates that only a global profile is used, no active user conf
|
||||
</AssignedAccessConfiguration>
|
||||
```
|
||||
|
||||
Below sample shows dedicated profile and global profile mixed usage, aauser would use one profile, everyone else that's non-admin will use another profile.
|
||||
Below sample shows dedicated profile and global profile mixed usage, a user would use one profile, everyone else that's non-admin will use another profile.
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
@ -396,7 +396,7 @@ Below sample shows dedicated profile and global profile mixed usage, aauser woul
|
||||
## [Preview] Folder Access sample xml
|
||||
In Windows 10, version 1809, folder access is locked down so that when common file dialog is opened, IT Admin can specify if the user has access to the Downloads folder, or no access to any folder at all. This restriction has been redesigned for finer granulatity and easier use, and is available in Windows 10 Insider Preview (19H2, 20H1 builds).
|
||||
|
||||
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Note that Downloads and Removable Drives can be allowed at the same time.
|
||||
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Downloads and Removable Drives can be allowed at the same time.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
@ -889,7 +889,7 @@ Schema for Windows 10 Insider Preview (19H2, 20H1 builds)
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the auto-launch feature which is added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||
To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the autolaunch feature that was added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||
```xml
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
|
||||
@ -12,41 +12,41 @@ manager: dansimp
|
||||
ms.topic: troubleshooting
|
||||
---
|
||||
|
||||
# Troubleshoot Start Menu errors
|
||||
# Troubleshoot Start menu errors
|
||||
|
||||
Start failures can be organized into these categories:
|
||||
|
||||
- **Deployment/Install issues** - Easiest to identify but difficult to recover. This failure is consistent and usually permanent. Reset, restore from backup, or rollback to recover.
|
||||
- **Performance issues** - More common with older hardware, low-powered machines. Symptoms include: High CPU utilization, disk contention, memory resources. This makes Start very slow to respond. Behavior is intermittent depending on available resources.
|
||||
- **Crashes** - Also easy to identify. Crashes in Shell Experience Host or related can be found in System or Application event logs. This can be a code defect or related to missing or altered permissions to files or registry keys by a program or incorrect security tightening configurations. Determining permissions issues can be time consuming but a [SysInternals tool called Procmon](https://docs.microsoft.com/sysinternals/downloads/procmon) will show **Access Denied**. The other option is to get a dump of the process when it crashes and depending on comfort level, review the dump in the debugger, or have support review the data.
|
||||
- **Hangs** in Shell Experience host or related. These are the hardest issues to identify as there are few events logged, but behavior is typically intermittent or recovers with a reboot. If a background application or service hangs, Start will not have resources to respond in time. Clean boot may help identify if the issue is related to additional software. Procmon is also useful in this scenario.
|
||||
- **Hangs** - in Shell Experience host or related. These are the hardest issues to identify as there are few events logged, but behavior is typically intermittent or recovers with a reboot. If a background application or service hangs, Start will not have resources to respond in time. Clean boot may help identify if the issue is related to additional software. Procmon is also useful in this scenario.
|
||||
- **Other issues** - Customization, domain policies, deployment issues.
|
||||
|
||||
## Basic troubleshooting
|
||||
|
||||
When troubleshooting basic Start issues (and for the most part, all other Windows apps), there are a few things to check if they are not working as expected. When experiencing issues where the Start Menu or sub-component are not working, there are some quick tests to narrow down where the issue may reside.
|
||||
When troubleshooting basic Start issues (and for the most part, all other Windows apps), there are a few things to check if they are not working as expected. For issues where the Start menu or subcomponent isn't working, you can do some quick tests to narrow down where the issue may reside.
|
||||
|
||||
### Check the OS and update version
|
||||
|
||||
- Is the system running the latest Feature and Cumulative Monthly update?
|
||||
- Did the issue start immediately after an update? Ways to check:
|
||||
- Powershell:[System.Environment]::OSVersion.Version
|
||||
- PowerShell:[System.Environment]::OSVersion.Version
|
||||
- WinVer from CMD.exe
|
||||
|
||||
### Check if Start is installed
|
||||
|
||||
- If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
|
||||
|
||||
- If Start was working and just fails intermittently, it's likely that Start is installed correctly, but the issue occurs downstream. The way to check for this is to look for output from these two PS commands:
|
||||
- If Start was working and just fails intermittently, it's likely that Start is installed correctly, but the issue occurs downstream. The way to check for this problem is to look for output from these two PS commands:
|
||||
|
||||
- `get-AppXPackage -Name Microsoft.Windows.ShellExperienceHost`
|
||||
- `get-AppXPackage -Name Microsoft.Windows.Cortana`
|
||||
|
||||
|
||||
|
||||
Failure messages will appear if they are not installed
|
||||
Failure messages will appear if they aren't installed
|
||||
|
||||
- If Start is not installed the fastest resolution is to revert to a known good configuration. This can be rolling back the update, resetting the PC to defaults (where there is a choice to save to delete user data), or restoring from backup. There is no supported method to install Start Appx files. The results are often problematic and unreliable.
|
||||
- If Start is not installed, then the fastest resolution is to revert to a known good configuration. This can be rolling back the update, resetting the PC to defaults (where there is a choice to save to delete user data), or restoring from backup. No method is supported to install Start Appx files. The results are often problematic and unreliable.
|
||||
|
||||
### Check if Start is running
|
||||
|
||||
@ -54,7 +54,7 @@ If either component is failing to start on boot, reviewing the event logs for er
|
||||
- `get-process -name shellexperiencehost`
|
||||
- `get-process -name searchui`
|
||||
|
||||
If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate 3rd party or additional drivers and applications.
|
||||
If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate third-party or additional drivers and applications.
|
||||
|
||||
### Check whether the system a clean install or upgrade
|
||||
|
||||
@ -76,9 +76,9 @@ If these events are found, Start is not activated correctly. Each event will hav
|
||||
|
||||
### Other things to consider
|
||||
|
||||
When did this start?
|
||||
When did the problem start?
|
||||
|
||||
- Top issues for Start Menu failure are triggered
|
||||
- Top issues for Start menu failure are triggered
|
||||
- After an update
|
||||
- After installation of an application
|
||||
- After joining a domain or applying a domain policy
|
||||
@ -87,7 +87,7 @@ When did this start?
|
||||
- Start or related component crashes or hangs
|
||||
- Customization failure
|
||||
|
||||
To narrow this down further, it's good to note:
|
||||
To narrow down the problem further, it's good to note:
|
||||
|
||||
- What is the install background?
|
||||
- Was this a deployment, install from media, other
|
||||
@ -103,7 +103,7 @@ To narrow this down further, it's good to note:
|
||||
- Some Group Policies intended for Windows 7 or older have been known to cause issues with Start
|
||||
- Untested Start Menu customizations can cause unexpected behavior by typically not complete Start failures.
|
||||
|
||||
- Is this a virtualized environment?
|
||||
- Is the environment virtualized?
|
||||
- VMware
|
||||
- Citrix
|
||||
- Other
|
||||
@ -123,13 +123,13 @@ To narrow this down further, it's good to note:
|
||||
- Microsoft-Windows-CloudStore*
|
||||
|
||||
|
||||
- Check for crashes that may be related to Start (explorer.exe, taskbar, etc)
|
||||
- Check for crashes that may be related to Start (explorer.exe, taskbar, and so on)
|
||||
- Application log event 1000, 1001
|
||||
- Check WER reports
|
||||
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
|
||||
- C:\ProgramData\Micrt\Windowsosof\WER\ReportQueue\
|
||||
|
||||
If there is a component of Start that is consistently crashing, capture a dump which can be reviewed by Microsoft Support.
|
||||
If there is a component of Start that is consistently crashing, capture a dump that can be reviewed by Microsoft Support.
|
||||
|
||||
## Common errors and mitigation
|
||||
|
||||
@ -169,7 +169,8 @@ The PDC registry key is:
|
||||
**Type**=dword:00000001
|
||||
|
||||
In addition to the listed dependencies for the service, Background Tasks Infrastructure Service requires the Power Dependency Coordinator Driver to be loaded. If the PDC does not load at boot, Background Tasks Infrastructure Service will fail and affect Start Menu.
|
||||
Events for both PDC and Background Tasks Infrastructure Service will be recorded in the event logs. PDC should not be disabled or deleted. BrokerInfrastructure is an automatic service. This Service is required for all these operating Systems as running to have a stable Start Menu.
|
||||
|
||||
Events for both PDC and Background Tasks Infrastructure Service will be recorded in the event logs. PDC shouldn't be disabled or deleted. BrokerInfrastructure is an automatic service. This Service is required for all these operating Systems as running to have a stable Start Menu.
|
||||
|
||||
>[!NOTE]
|
||||
>You cannot stop this automatic service when machine is running (C:\windows\system32\svchost.exe -k DcomLaunch -p).
|
||||
@ -179,17 +180,17 @@ Events for both PDC and Background Tasks Infrastructure Service will be recorded
|
||||
|
||||
**Cause**: There was a change in the All Apps list between Windows 10, versions 1511 and 1607. These changes mean the original Group Policy and corresponding registry key no longer apply.
|
||||
|
||||
**Resolution**: This issue was resolved in the June 2017 updates. Please update Windows 10, version 1607 to the latest cumulative or feature updates.
|
||||
**Resolution**: This issue was resolved in the June 2017 updates. Update Windows 10, version 1607, to the latest cumulative or feature updates.
|
||||
|
||||
>[!NOTE]
|
||||
>When the Group Policy is enabled, the desired behavior also needs to be selected. By default, it is set to **None**.
|
||||
|
||||
|
||||
### Symptom: Application tiles like Alarm, Calculator, and Edge are missing from Start Menu and the Settings app fails to open on Windows 10, version 1709 when a local user profile is deleted
|
||||
### Symptom: Application tiles like Alarm, Calculator, and Edge are missing from Start menu and the Settings app fails to open on Windows 10, version 1709 when a local user profile is deleted
|
||||
|
||||
|
||||
|
||||
**Cause**: This is a known issue where the first-time logon experience is not detected and does not trigger the install of some Apps.
|
||||
**Cause**: This issue is known. The first-time sign-in experience is not detected and does not trigger the install of some apps.
|
||||
|
||||
**Resolution**: This issue has been fixed for Windows 10, version 1709 in [KB 4089848](https://support.microsoft.com/help/4089848) March 22, 2018—KB4089848 (OS Build 16299.334)
|
||||
|
||||
@ -202,17 +203,17 @@ Events for both PDC and Background Tasks Infrastructure Service will be recorded
|
||||
- Event ID 22 is logged when the xml is malformed, meaning the specified file simply isn’t valid xml.
|
||||
- When editing the xml file, it should be saved in UTF-8 format.
|
||||
|
||||
- Unexpected information: This occurs when possibly trying to add a tile via unexpected or undocumented method.
|
||||
- Unexpected information: This occurs when possibly trying to add a tile via an unexpected or undocumented method.
|
||||
- **Event ID: 64** is logged when the xml is valid but has unexpected values.
|
||||
- For example: The following error occurred while parsing a layout xml file: The attribute 'LayoutCustomizationRestrictiontype' on the element '{http://schemas.microsoft.com/Start/2014/LayoutModification}DefaultLayoutOverride' is not defined in the DTD/Schema.
|
||||
|
||||
XML files can and should be tested locally on a Hyper-V or other virtual machine before deployment or application by Group Policy
|
||||
|
||||
### Symptom: Start menu no longer works after a PC is refreshed using F12 during start up
|
||||
### Symptom: Start menu no longer works after a PC is refreshed using F12 during startup
|
||||
|
||||
**Description**: If a user is having problems with a PC, is can be refreshed, reset, or restored. Refreshing the PC is a beneficial option because it maintains personal files and settings. When users have trouble starting the PC, "Change PC settings" in Settings is not accessible. So, to access the System Refresh, users may use the F12 key at start up. Refreshing the PC finishes, but Start Menu is not accessible.
|
||||
**Description**: If a user is having problems with a PC, it can be refreshed, reset, or restored. Refreshing the PC is a beneficial option because it maintains personal files and settings. When users have trouble starting the PC, "Change PC settings" in Settings is not accessible. So, to access the System Refresh, users may use the F12 key at startup. Refreshing the PC finishes, but Start Menu is not accessible.
|
||||
|
||||
**Cause**: This is a known issue and has been resolved in a cumulative update released August 30th 2018.
|
||||
**Cause**: This issue is known and was resolved in a cumulative update released August 30, 2018.
|
||||
|
||||
**Resolution**: Install corrective updates; a fix is included in the [September 11, 2018-KB4457142 release](https://support.microsoft.com/help/4457142).
|
||||
|
||||
@ -232,7 +233,7 @@ Specifically, behaviors include
|
||||
- Applications (apps or icons) pinned to the start menu are missing.
|
||||
- Entire tile window disappears.
|
||||
- The start button fails to respond.
|
||||
- If a new roaming user is created, the first logon appears normal, but on subsequent logons, tiles are missing.
|
||||
- If a new roaming user is created, the first sign-in appears normal, but on subsequent sign-ins, tiles are missing.
|
||||
|
||||
|
||||
|
||||
@ -261,12 +262,12 @@ After the upgrade the user pinned tiles are missing:
|
||||
|
||||
|
||||
|
||||
Additionally, users may see blank tiles if logon was attempted without network connectivity.
|
||||
Additionally, users may see blank tiles if sign-in was attempted without network connectivity.
|
||||
|
||||
|
||||
|
||||
|
||||
**Resolution**: This is fixed in [October 2017 update](https://support.microsoft.com/en-us/help/4041676).
|
||||
**Resolution**: This issue was fixed in the [October 2017 update](https://support.microsoft.com/en-us/help/4041676).
|
||||
|
||||
### Symptom: Tiles are missing after upgrade from Windows 10, version 1607 to version 1709 for users with Roaming User Profiles (RUP) enabled and managed Start Menu layout with partial lockdown
|
||||
|
||||
@ -278,13 +279,13 @@ Additionally, users may see blank tiles if logon was attempted without network c
|
||||
|
||||
### Symptom: Start Menu issues with Tile Data Layer corruption
|
||||
|
||||
**Cause**: Windows 10, version 1507 through the release of version 1607 uses a database for the Tile image information. This is called the Tile Data Layer database (The feature was deprecated in [Windows 10 1703](https://support.microsoft.com/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update)).
|
||||
**Cause**: Windows 10, version 1507 through the release of version 1607 uses a database for the Tile image information. This is called the Tile Data Layer database. (The feature was deprecated in [Windows 10 1703](https://support.microsoft.com/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update).)
|
||||
|
||||
**Resolution** There are steps you can take to fix the icons, first is to confirm that is the issue that needs to be addressed.
|
||||
|
||||
1. The App or Apps work fine when you click on the tiles.
|
||||
1. The App or Apps work fine when you select the tiles.
|
||||
2. The tiles are blank, have a generic placeholder icon, have the wrong or strange title information.
|
||||
3. The app is missing, but listed as installed via Powershell and works if you launch via URI.
|
||||
3. The app is missing, but listed as installed via PowerShell and works if you launch via URI.
|
||||
- Example: `windows-feedback://`
|
||||
4. In some cases, Start can be blank, and Action Center and Cortana do not launch.
|
||||
|
||||
@ -301,9 +302,9 @@ Although a reboot is not required, it may help clear up any residual issues afte
|
||||
|
||||
### Symptoms: Start Menu and Apps cannot start after upgrade to Windows 10 version 1809 when Symantec Endpoint Protection is installed
|
||||
|
||||
**Description** Start Menu, Search and Apps do not start after you upgrade a Windows 7-based computer that has Symantec Endpoint Protection installed to Windows 10 version 1809.
|
||||
**Description**: Start menu, Search, and Apps do not start after you upgrade a computer running Windows 7 that has Symantec Endpoint Protection installed to Windows 10 version 1809.
|
||||
|
||||
**Cause** This occurs because of a failure to load sysfer.dll. During upgrade, the setup process does not set the privilege group "All Application Packages" on sysfer.dll and other Symantec modules.
|
||||
**Cause**: This problem occurs because of a failure to load sysfer.dll. During upgrade, the setup process does not set the privilege group "All Application Packages" on sysfer.dll and other Symantec modules.
|
||||
|
||||
**Resolution** This issue was fixed by the Windows Cumulative Update that were released on December 5, 2018—KB4469342 (OS Build 17763.168).
|
||||
|
||||
@ -321,7 +322,7 @@ If you have already encountered this issue, use one of the following two options
|
||||
|
||||
4. Confirm that **All Application Packages** group is missing.
|
||||
|
||||
5. Click **Edit**, and then click **Add** to add the group.
|
||||
5. Select **Edit**, and then select **Add** to add the group.
|
||||
|
||||
6. Test Start and other Apps.
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ As an administrator of User Experience Virtualization (UE-V), you can restore ap
|
||||
## Restore Settings in UE-V when a User Adopts a New Device
|
||||
|
||||
|
||||
To restore settings when a user adopts a new device, you can put a settings location template in **backup** or **roam (default)** profile using the Set-UevTemplateProfile PowerShell cmdlet. This lets computer settings sync to the new computer, in addition to user settings. Templates assigned to the backup profile are backed up for that device and configured on a per-device basis. To backup settings for a template, use the following cmdlet in Windows PowerShell:
|
||||
To restore settings when a user adopts a new device, you can put a settings location template in a **backup** or **roam (default)** profile using the Set-UevTemplateProfile PowerShell cmdlet. This setup lets computer settings sync to the new computer, in addition to user settings. Templates assigned to the backup profile are backed up for that device and configured on a per-device basis. To back up settings for a template, use the following cmdlet in Windows PowerShell:
|
||||
|
||||
```powershell
|
||||
Set-UevTemplateProfile -ID <TemplateID> -Profile <backup>
|
||||
@ -50,7 +50,7 @@ As part of the Backup/Restore feature, UE-V added **last known good (LKG)** to t
|
||||
|
||||
### How to Backup/Restore Templates with UE-V
|
||||
|
||||
These are the key backup and restore components of UE-V:
|
||||
Here are the key backup and restore components of UE-V:
|
||||
|
||||
- Template profiles
|
||||
|
||||
@ -74,7 +74,7 @@ All templates are included in the roaming profile when registered unless otherwi
|
||||
|
||||
Templates can be added to the Backup Profile with PowerShell or WMI using the Set-UevTemplateProfile cmdlet. Templates in the Backup Profile back up these settings to the Settings Storage Location in a special Device name directory. Specified settings are backed up to this location.
|
||||
|
||||
Templates designated BackupOnly include settings specific to that device that should not be synchronized unless explicitly restored. These settings are stored in the same device-specific settings package location on the settings storage location as the Backedup Settings. These templates have a special identifier embedded in the template that specifies they should be part of this profile.
|
||||
Templates designated BackupOnly include settings specific to that device that shouldn't be synchronized unless explicitly restored. These settings are stored in the same device-specific settings package location on the settings storage location as the Backedup Settings. These templates have a special identifier embedded in the template that specifies they should be part of this profile.
|
||||
|
||||
**Settings packages location within the Settings Storage Location template**
|
||||
|
||||
@ -90,10 +90,10 @@ Restoring a user’s device restores the currently registered Template’s setti
|
||||
|
||||
- **Automatic restore**
|
||||
|
||||
If the user’s UE-V settings storage path, domain, and Computer name match the current user then all of the settings for that user are synchronized, with only the latest settings applied. If a user logs on to a new device for the first time and these criteria are met, the settings data is applied to that device.
|
||||
If the user’s UE-V settings storage path, domain, and Computer name match the current user then all of the settings for that user are synchronized, with only the latest settings applied. If a user signs in to a new device for the first time and these criteria are met, the settings data is applied to that device.
|
||||
|
||||
**Note**
|
||||
Accessibility and Windows Desktop settings require the user to re-logon to Windows to be applied.
|
||||
Accessibility and Windows Desktop settings require the user to sign in again to Windows to be applied.
|
||||
|
||||
|
||||
|
||||
@ -104,7 +104,7 @@ Restoring a user’s device restores the currently registered Template’s setti
|
||||
## Restore Application and Windows Settings to Original State
|
||||
|
||||
|
||||
WMI and Windows PowerShell commands let you restore application and Windows settings to the settings values that were on the computer the first time that the application started after the UE-V service was enabled. This restoring action is performed on a per-application or Windows settings basis. The settings are restored the next time that the application runs, or the settings are restored when the user logs on to the operating system.
|
||||
WMI and Windows PowerShell commands let you restore application and Windows settings to the settings values that were on the computer the first time that the application started after the UE-V service was enabled. This restoring action is performed on a per-application or Windows settings basis. The settings are restored the next time that the application runs, or the settings are restored when the user signs in to the operating system.
|
||||
|
||||
**To restore application settings and Windows settings with Windows PowerShell for UE-V**
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ Administrators can still define which user-customized application settings can s
|
||||
|
||||
### Upgrading from UE-V 1.0 to the in-box version of UE-V is blocked
|
||||
|
||||
Version 1.0 of UE-V used Offline Files (Client Side Caching) for settings synchronization and pinned the UE-V sync folder to be available when the network was offline, however, this technology was removed in UE-V 2.x. As a result, UE-V 1.0 users are blocked from upgrading to UE-V for Windows 10, version 1607.
|
||||
Version 1.0 of UE-V used Offline Files (Client-Side Caching) for settings synchronization and pinned the UE-V sync folder to be available when the network was offline, however, this technology was removed in UE-V 2.x. As a result, UE-V 1.0 users are blocked from upgrading to UE-V for Windows 10, version 1607.
|
||||
|
||||
WORKAROUND: Remove the UE-V 1.0 sync folder from the Offline Files configuration and then upgrade to the in-box version of UE-V for Windows, version 1607 release.
|
||||
|
||||
@ -55,13 +55,13 @@ WORKAROUND: To resolve this problem, run the application by selecting one of the
|
||||
|
||||
### Unpredictable results when both Office 2010 and Office 2013 are installed on the same device
|
||||
|
||||
When a user has both Office 2010 and Office 2013 installed, any common settings between the two versions of Office are roamed by UE-V. This could cause the Office 2010 package size to be quite large or result in unpredictable conflicts with 2013, particularly if Office 365 is used.
|
||||
When a user has both Office 2010 and Office 2013 installed, any common settings between the two versions of Office are roamed by UE-V. This could cause the Office 2010 package size to be large or result in unpredictable conflicts with 2013, particularly if Office 365 is used.
|
||||
|
||||
WORKAROUND: Install only one version of Office or limit which settings are synchronized by UE-V.
|
||||
|
||||
### Uninstall and re-install of Windows 8 applications reverts settings to initial state
|
||||
### Uninstallation and reinstallation of Windows 8 applications reverts settings to initial state
|
||||
|
||||
While using UE-V settings synchronization for a Windows 8 application, if the user uninstalls the application and then reinstalls the application, the application’s settings revert to their default values. This happens because the uninstall removes the local (cached) copy of the application’s settings but does not remove the local UE-V settings package. When the application is reinstalled and launched, UE-V gather the application settings that were reset to the application defaults and then uploads the default settings to the central storage location. Other computers running the application then download the default settings. This behavior is identical to the behavior of desktop applications.
|
||||
While using UE-V settings synchronization for a Windows 8 application, if the user uninstalls the application and then reinstalls the application, the application’s settings revert to their default values. This result happens because the uninstall removes the local (cached) copy of the application’s settings but does not remove the local UE-V settings package. When the application is reinstalled and launched, UE-V gathers the application settings that were reset to the application defaults and then uploads the default settings to the central storage location. Other computers running the application then download the default settings. This behavior is identical to the behavior of desktop applications.
|
||||
|
||||
WORKAROUND: None.
|
||||
|
||||
@ -85,7 +85,7 @@ WORKAROUND: Use folder redirection or some other technology to ensure that any f
|
||||
|
||||
### Long Settings Storage Paths could cause an error
|
||||
|
||||
Keep settings storage paths as short as possible. Long paths could prevent resolution or synchronization. UE-V uses the Settings storage path as part of the calculated path to store settings. That path is calculated in the following way: settings storage path + “settingspackages” + package dir (template ID) + package name (template ID) + .pkgx. If that calculated path exceeds 260 characters, package storage will fail and generate the following error message in the UE-V operational event log:
|
||||
Keep settings storage paths as short as possible. Long paths could prevent resolution or synchronization. UE-V uses the Settings storage path as part of the calculated path to store settings. That path is calculated in the following way: settings storage path + "settingspackages" + package dir (template ID) + package name (template ID) + .pkgx. If that calculated path exceeds 260 characters, package storage will fail and generate the following error message in the UE-V operational event log:
|
||||
|
||||
\[boost::filesystem::copy\_file: The system cannot find the path specified\]
|
||||
|
||||
@ -95,7 +95,7 @@ WORKAROUND: None.
|
||||
|
||||
### Some operating system settings only roam between like operating system versions
|
||||
|
||||
Operating system settings for Narrator and currency characters specific to the locale (i.e. language and regional settings) will only roam across like operating system versions of Windows. For example, currency characters will not roam between Windows 7 and Windows 8.
|
||||
Operating system settings for Narrator and currency characters specific to the locale (that is, language and regional settings) will only roam across like operating system versions of Windows. For example, currency characters will not roam between Windows 7 and Windows 8.
|
||||
|
||||
WORKAROUND: None
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ Specifies the settings you can configure when joining a device to a domain, incl
|
||||
| --- | --- | --- |
|
||||
| Account | string | Account to use to join computer to domain |
|
||||
| AccountOU | Enter the full path for the organizational unit. For example: OU=testOU,DC=domain,DC=Domain,DC=com. | Name of organizational unit for the computer account |
|
||||
| ComputerName | Specify a unique name for the domain-joined computers using %RAND:x%, where x is an integer less than 15 digits long, or using %SERIAL% characters in the name.</br></br>ComputerName is a string with a maximum length of 15 bytes of content:</br></br>- ComputerName can use ASCII characters (1 byte each) and/or multi-byte characters such as Kanji, so long as you do not exceed 15 bytes of content.</br></br>- ComputerName cannot use spaces or any of the following characters: \{ | \} ~ \[ \\ \] ^ ' : ; < = > ? @ ! " \# $ % ` \( \) + / . , \* &, or contain any spaces.</br></br>- ComputerName cannot use some non-standard characters, such as emoji.</br></br>Computer names that cannot be validated through the DnsValidateName function cannot be used, for example, computer names that only contain numbers (0-9). For more information, see the [DnsValidateName function](https://go.microsoft.com/fwlink/?LinkId=257040). | Specifies the name of the Windows device (computer name on PCs) |
|
||||
| ComputerName | Specify a unique name for the domain-joined computers using %RAND:x%, where x is an integer that includes fewer than 15 digits, or using %SERIAL% characters in the name.</br></br>ComputerName is a string with a maximum length of 15 bytes of content:</br></br>- ComputerName can use ASCII characters (1 byte each) and/or multi-byte characters such as Kanji, so long as you do not exceed 15 bytes of content.</br></br>- ComputerName cannot use spaces or any of the following characters: \{ | \} ~ \[ \\ \] ^ ' : ; < = > ? @ ! " \# $ % ` \( \) + / . , \* &, or contain any spaces.</br></br>- ComputerName cannot use some non-standard characters, such as emoji.</br></br> Computer names that cannot be validated through the DnsValidateName function cannot be used, for example, computer names that only contain numbers (0-9). For more information, see the [DnsValidateName function](https://go.microsoft.com/fwlink/?LinkId=257040). | Specifies the name of the Windows device (computer name on PCs) |
|
||||
| DomainName | string (cannot be empty) | Specify the name of the domain that the device will join |
|
||||
| Password | string (cannot be empty) | Corresponds to the password of the user account that's authorized to join the computer account to the domain. |
|
||||
|
||||
@ -56,6 +56,6 @@ Use these settings to add local user accounts to the device.
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| UserName | string (cannot be empty) | Specify a name for the local user account |
|
||||
| HomeDir | string (cannot be ampty) | Specify the path of the home directory for the user |
|
||||
| HomeDir | string (cannot be empty) | Specify the path of the home directory for the user |
|
||||
| Password | string (cannot be empty) | Specify the password for the user account |
|
||||
| UserGroup | string (cannot be empty) | Specify the local user group for the user |
|
||||
|
||||
@ -27,7 +27,7 @@ Use for settings related to Maps.
|
||||
|
||||
## ChinaVariantWin10
|
||||
|
||||
Use **ChinaVariantWin10** to specify that the Windows device is intended to ship in China. When set to **True**, maps approved by the State Bureau of Surveying and Mapping in China are used, which are obtained from a server located in China.
|
||||
Use **ChinaVariantWin10** to specify that the Windows device is intended to ship in China. When set to **True**, maps approved by the State Bureau of Surveying and Mapping in China are used. These maps are obtained from a server located in China.
|
||||
|
||||
This customization may result in different maps, servers, or other configuration changes on the device.
|
||||
|
||||
@ -38,7 +38,7 @@ Use to store map data on an SD card.
|
||||
|
||||
Map data is used by the Maps application and the map control for third-party applications. This data can be store on an SD card, which provides the advantage of saving internal memory space for user data and allows the user to download more offline map data. Microsoft recommends enabling the **UseExternalStorage** setting on devices that have less than 8 GB of user storage and an SD card slot.
|
||||
|
||||
You can use **UseExternalStorage** whether or not you include an SD card with preloaded map data on the phone. If set to **True**, the OS only allows the user to download offline maps when an SD card is present. If an SD card is not present, users can still view and cache maps, but they will not be able to download a region of offline maps until an SD card is inserted.
|
||||
You can use **UseExternalStorage** whether or not you include an SD card with preloaded map data on the phone. If set to **True**, the OS only allows the user to download offline maps when an SD card is present. If no SD card is present, users can view and cache maps, but they can't download a region of offline maps until an SD card is inserted.
|
||||
|
||||
If set to **False**, map data will always be stored on the internal data partition of the device.
|
||||
|
||||
@ -47,4 +47,4 @@ If set to **False**, map data will always be stored on the internal data partiti
|
||||
|
||||
## UseSmallerCache
|
||||
|
||||
Do not use.
|
||||
Don't use this setting.
|
||||
|
||||
@ -27,20 +27,20 @@ Use to configure settings to personalize a PC.
|
||||
|
||||
## DeployDesktopImage
|
||||
|
||||
Deploy a jpg, jpeg or png image to the device to be used as desktop image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [DesktopImageUrl](#desktopimageurl).
|
||||
Deploy a .jpg, .jpeg, or .png image to the device to be used as a desktop image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [DesktopImageUrl](#desktopimageurl).
|
||||
|
||||
When using **DeployDesktopImage** and [DeployLockScreenImageFile](#deploylockscreenimage, the file names need to be different.
|
||||
|
||||
## DeployLockScreenImage
|
||||
|
||||
Deploy a jpg, jpeg or png image to the device to be used as lock screen image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [LockScreenImageUrl](#lockscreenimageurl).
|
||||
Deploy a .jpg, .jpeg, or .png image to the device to be used as lock screen image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [LockScreenImageUrl](#lockscreenimageurl).
|
||||
|
||||
When using [DeployDesktopImage](#deploydesktopimage) and **DeployLockScreenImageFile**, the file names need to be different.
|
||||
|
||||
## DesktopImageUrl
|
||||
|
||||
Specify a jpg, jpeg or png image to be used as desktop image. This setting can take a http or https url to a remote image to be downloaded or a file url to a local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployDesktopImage](#deploydesktopimage).
|
||||
Specify a .jpg, .jpeg, or .png image to be used as desktop image. This setting can take an HTTP or HTTPS URL to a remote image to be downloaded or a file URL to a local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployDesktopImage](#deploydesktopimage).
|
||||
|
||||
## LockScreenImageUrl
|
||||
|
||||
Specify a jpg, jpeg or png image to be used as Lock Screen Image. This setting can take a http or https Url to a remote image to be downloaded or a file Url to an existing local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployLockScreenImage](#deploylockscreenimage).
|
||||
Specify a .jpg, .jpeg, or .png image to be used as Lock Screen Image. This setting can take an HTTP or HTTPS URL to a remote image to be downloaded or a file URL to an existing local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployLockScreenImage](#deploylockscreenimage).
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Add Microsoft Store for Business applications to a Windows 10 image
|
||||
description: This topic describes how to add Microsoft Store for Business applications to a Windows 10 image.
|
||||
description: This article describes the correct way to add Microsoft Store for Business applications to a Windows 10 image.
|
||||
keywords: upgrade, update, windows, windows 10, deploy, store, image, wim
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,6 +13,7 @@ ms.author: greglin
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Add Microsoft Store for Business applications to a Windows 10 image
|
||||
|
||||
@ -13,6 +13,7 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Configure a PXE server to load Windows PE
|
||||
@ -21,8 +22,6 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
## Summary
|
||||
|
||||
This walkthrough describes how to configure a PXE server to load Windows PE by booting a client computer from the network. Using the Windows PE tools and a Windows 10 image file, you can install Windows 10 from the network.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -14,6 +14,7 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deploy Windows 10 with Microsoft 365
|
||||
|
||||
@ -13,6 +13,7 @@ ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# What's new in Windows 10 deployment
|
||||
@ -83,7 +84,7 @@ The following Delivery Optimization policies are removed in the Windows 10, vers
|
||||
- [**Windows Update for Business**](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523): There will now be a single, common start date for phased deployments (no more SAC-T designation). In addition, there will be a new notification and reboot scheduling experience for end users, the ability to enforce update installation and reboot deadlines, and the ability to provide end user control over reboots for a specific time period.
|
||||
- **Update rollback improvements**: You can now automatically recover from startup failures by removing updates if the startup failure was introduced after the installation of recent driver or quality updates. When a device is unable to start up properly after the recent installation of Quality of driver updates, Windows will now automatically uninstall the updates to get the device back up and running normally.
|
||||
- **Pause updates**: We have extended the ability to pause updates for both feature and monthly updates. This extension ability is for all editions of Windows 10, including Home. You can pause both feature and monthly updates for up to 35 days (seven days at a time, up to five times). Once the 35-day pause period is reached, you will need to update your device before pausing again.
|
||||
- **Improved update notifications**: When there’s an update requiring you to restart your device, you’ll see a colored dot on the Power button in the Start menu and on the Windows icon in your taskbar.
|
||||
- **Improved update notifications**: When there's an update requiring you to restart your device, you'll see a colored dot on the Power button in the Start menu and on the Windows icon in your taskbar.
|
||||
- **Intelligent active hours**: To further enhance active hours, users will now have the option to let Windows Update intelligently adjust active hours based on their device-specific usage patterns. You must enable the intelligent active hours feature for the system to predict device-specific usage patterns.
|
||||
- **Improved update orchestration to improve system responsiveness**: This feature will improve system performance by intelligently coordinating Windows updates and Microsoft Store updates, so they occur when users are away from their devices to minimize disruptions.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Add a Windows 10 operating system image using Configuration Manager (Windows 10)
|
||||
title: Add a Windows 10 operating system image using Configuration Manager
|
||||
description: Operating system images are typically the production image used for deployment throughout the organization.
|
||||
ms.assetid: 77f769cc-1a47-4f36-8082-201cd77b8d3b
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Add a Windows 10 operating system image using Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager (Windows 10)
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
description: Learn how to configure the Windows Preinstallation Environment (Windows PE) to include required network and storage drivers.
|
||||
ms.assetid: 97b3ea46-28d9-407e-8c42-ded2e45e8d5c
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
@ -51,10 +52,10 @@ On **CM01**:
|
||||
6. In the popup window that appears, click **Yes** to automatically update the distribution point.
|
||||
7. Click **Next**, wait for the image to be updated, and then click **Close**.
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
|
||||
Add drivers to Windows PE
|
||||
|
||||
@ -64,7 +65,7 @@ This section illustrates how to add drivers for Windows 10 using the HP EliteBoo
|
||||
|
||||
For the purposes of this section, we assume that you have downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the **D:\Sources$\OSD\DriverSources\Windows 10 x64\Hewlett-Packard\HP EliteBook 8560w** folder on CM01.
|
||||
|
||||
|
||||
|
||||
|
||||
Driver folder structure on CM01
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create a custom Windows PE boot image with Configuration Manager (Windows 10)
|
||||
description: In Microsoft Endpoint Configuration Manager, you can create custom Windows Preinstallation Environment (Windows PE) boot images that include extra components and features.
|
||||
description: Learn how to create custom Windows Preinstallation Environment (Windows PE) boot images in Microsoft Endpoint Configuration Manager.
|
||||
ms.assetid: b9e96974-324d-4fa4-b0ce-33cfc49c4809
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Create a custom Windows PE boot image with Configuration Manager
|
||||
@ -71,8 +72,8 @@ On **CM01**:
|
||||
8. In the Distribute Content Wizard, add the CM01 distribution point, and complete the wizard.
|
||||
9. Using Configuration Manager Trace, review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads **STATMSG: ID=2301**. You also can monitor Content Status in the Configuration Manager Console at **\Monitoring\Overview\Distribution Status\Content Status\Zero Touch WinPE x64**. See the following examples:
|
||||
|
||||
<br>
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
Content status for the Zero Touch WinPE x64 boot image
|
||||
|
||||
@ -81,8 +82,8 @@ On **CM01**:
|
||||
12. Using Configuration Manager Trace, review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for this text: **Expanding PS100009 to D:\\RemoteInstall\\SMSImages**.
|
||||
13. Review the **D:\\RemoteInstall\\SMSImages** folder. You should see three folders containing boot images. Two are from the default boot images, and the third folder (PS100009) is from your new boot image with DaRT. See the examples below:
|
||||
|
||||
<br>
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
>Note: Depending on your infrastructure and the number of packages and boot images present, the Image ID might be a different number than PS100009.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Finalize operating system configuration for Windows 10 deployment
|
||||
description: Follow this walk-through to finalize the configuration of your Windows 10 operating deployment.
|
||||
description: This article provides a walk-through to finalize the configuration of your Windows 10 operating deployment.
|
||||
ms.assetid: 38b55fa8-e717-4689-bd43-8348751d493e
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Finalize the operating system configuration for Windows 10 deployment with Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager (Windows 10)
|
||||
title: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
|
||||
description: Learn how to prepare a Zero Touch Installation of Windows 10 with Configuration Manager, by integrating Configuration Manager with Microsoft Deployment Toolkit.
|
||||
ms.assetid: 06e3a221-31ef-47a5-b4da-3b927cb50d08
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
|
||||
@ -240,7 +241,7 @@ On **CM01**:
|
||||
2. Right-click **PS1 - Primary Site 1**, point to **Configure Site Components**, and then select **Software Distribution**.
|
||||
3. On the **Network Access Account** tab, select **Specify the account that accesses network locations** and add the *New Account* **CONTOSO\\CM\_NAA** as the Network Access account (password: pass@word1). Use the new **Verify** option to verify that the account can connect to the **\\\\DC01\\sysvol** network share.
|
||||
|
||||
|
||||
|
||||
|
||||
Test the connection for the Network Access account.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
title: Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
description: Learn how to use Configuration Manager and Microsoft Deployment Toolkit (MDT) to refresh a Windows 7 SP1 client with Windows 10.
|
||||
ms.assetid: 57c81667-1019-4711-b3de-15ae9c5387c7
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
@ -57,9 +58,9 @@ On **PC0003**:
|
||||
|
||||
1. Open the Configuration Manager control panel (control smscfgrc).
|
||||
2. On the **Site** tab, click **Configure Settings**, then click **Find Site**.
|
||||
3. Verify that Configuration Manager has successfullyl found a site to manage this client is displayed. See the following example.
|
||||
3. Verify that Configuration Manager has successfully found a site to manage this client is displayed. See the following example.
|
||||
|
||||
|
||||
|
||||
|
||||
## Create a device collection and add the PC0003 computer
|
||||
|
||||
@ -123,16 +124,16 @@ On **PC0003**:
|
||||
2. In the **Software Center** warning dialog box, click **Install Operating System**.
|
||||
3. The client computer will run the Configuration Manager task sequence, boot into Windows PE, and install the new OS and applications. See the following examples:
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
|
||||
Next, see [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md).
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
title: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
description: In this topic, you will learn how to replacing a Windows 7 SP1 computer using Microsoft Endpoint Configuration Manager.
|
||||
ms.assetid: 3c8a2d53-8f08-475f-923a-bca79ca8ac36
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
@ -159,7 +160,7 @@ On **PC0004**:
|
||||
4. Confirm you want to upgrade the operating system on this computer by clicking **Install** again.
|
||||
5. Allow the Replace Task Sequence to complete. The PC0004 computer will gather user data, boot into Windows PE and gather more data, then boot back to the full OS. The entire process should only take a few minutes.
|
||||
|
||||
|
||||
|
||||
|
||||
Capturing the user state
|
||||
|
||||
@ -190,15 +191,15 @@ On **PC0006**:
|
||||
|
||||
When the process is complete, you will have a new Windows 10 computer in your domain with user data and settings restored. See the following examples:
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
|
||||
Next, see [Perform an in-place upgrade to Windows 10 using Configuration Manager](upgrade-to-windows-10-with-configuraton-manager.md).
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Perform in-place upgrade to Windows 10 via Configuration Manager
|
||||
description: In-place upgrades make upgrading Windows 7, Windows 8, and Windows 8.1 to Windows 10 easy -- you can even automate the whole process with a Microsoft Endpoint Configuration Manager task sequence.
|
||||
description: Learn how to perform an in-place upgrade to Windows 10 by automating the process with a Microsoft Endpoint Configuration Manager task sequence.
|
||||
ms.assetid: F8DF6191-0DB0-4EF5-A9B1-6A11D5DE4878
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -12,6 +12,7 @@ ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Perform an in-place upgrade to Windows 10 using Configuration Manager
|
||||
@ -126,13 +127,13 @@ On **PC0004**:
|
||||
4. Confirm you want to upgrade the operating system on this computer by clicking **Install** again.
|
||||
5. Allow the Upgrade Task Sequence to complete. The PC0004 computer will download the install.wim file, perform an in-place upgrade, and install your added applications. See the following examples:
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
|
||||
In-place upgrade with Configuration Manager
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Replace a Windows 7 computer with a Windows 10 computer (Windows 10)
|
||||
description: Learn how to replace a Windows 7 device with a Windows 10 device. Although the process is similar to performing a refresh, you'll need to backup data externally
|
||||
description: In this article, you will learn how to replace a Windows 7 device with a Windows 10 device.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.assetid: acf091c9-f8f4-4131-9845-625691c09a2a
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: 386e6713-5c20-4d2a-a220-a38d94671a38
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
description: Learn how to configure your environment for BitLocker, the disk volume encryption built into Windows 10 Enterprise and Windows 10 Pro, using MDT.
|
||||
keywords: disk, encryption, TPM, configure, secure, script
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,6 +14,7 @@ ms.pagetype: mdt
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Set up MDT for BitLocker
|
||||
|
||||
@ -14,6 +14,7 @@ ms.sitesec: library
|
||||
ms.pagetype: mobility
|
||||
audience: itpro
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deploy Windows To Go in your organization
|
||||
@ -113,7 +114,7 @@ The following Windows PowerShell cmdlet or cmdlets perform the same function as
|
||||
|
||||
$Disk = Get-Disk | Where-Object {$_.Path -match "USBSTOR" -and $_.Size -gt 20Gb -and -not $_.IsBoot }
|
||||
|
||||
#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with ‘New-Partition…) Validate that this is the correct disk that you want to completely erase.
|
||||
#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with 'New-Partition…) Validate that this is the correct disk that you want to completely erase.
|
||||
#
|
||||
# To skip the confirmation prompt, append –confirm:$False
|
||||
Clear-Disk –InputObject $Disk[0] -RemoveData
|
||||
@ -161,7 +162,7 @@ W:\Windows\System32\bcdboot W:\Windows /f ALL /s S:
|
||||
```
|
||||
~~~
|
||||
|
||||
5. Apply SAN policy—OFFLINE\_INTERNAL - “4” to prevent the operating system from automatically bringing online any internally connected disk. This is done by creating and saving a **san\_policy.xml** file on the disk. The following example illustrates this step:
|
||||
5. Apply SAN policy—OFFLINE\_INTERNAL - "4" to prevent the operating system from automatically bringing online any internally connected disk. This is done by creating and saving a **san\_policy.xml** file on the disk. The following example illustrates this step:
|
||||
|
||||
```
|
||||
<?xml version='1.0' encoding='utf-8' standalone='yes'?>
|
||||
@ -291,7 +292,7 @@ Making sure that Windows To Go workspaces are effective when used off premises i
|
||||
|
||||
- A domain-joined computer running Windows 8 or later and is configured as a Windows To Go host computer
|
||||
|
||||
- A Windows To Go drive that hasn’t been booted or joined to the domain using unattend settings.
|
||||
- A Windows To Go drive that hasn't been booted or joined to the domain using unattend settings.
|
||||
|
||||
- A domain user account with rights to add computer accounts to the domain and is a member of the Administrator group on the Windows To Go host computer
|
||||
|
||||
@ -319,7 +320,7 @@ Making sure that Windows To Go workspaces are effective when used off premises i
|
||||
|
||||
$Disk = Get-Disk | Where-Object {$_.Path -match "USBSTOR" -and $_.Size -gt 20Gb -and -not $_.IsBoot }
|
||||
|
||||
#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with ‘New-Partition…) Validate that this is the correct disk that you want to completely erase.
|
||||
#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with 'New-Partition…) Validate that this is the correct disk that you want to completely erase.
|
||||
#
|
||||
# To skip the confirmation prompt, append –confirm:$False
|
||||
Clear-Disk –InputObject $Disk[0] -RemoveData
|
||||
@ -414,7 +415,7 @@ dism /apply-image /imagefile:n:\imagefolder\deploymentimages\mywtgimage.wim /ind
|
||||
>[!NOTE]
|
||||
>Depending on your DirectAccess configuration you might be asked to insert your smart card to log on to the domain.
|
||||
|
||||
You should now be able to access your organization’s network resources and work from your Windows To Go workspace as you would normally work from your standard desktop computer on premises.
|
||||
You should now be able to access your organization's network resources and work from your Windows To Go workspace as you would normally work from your standard desktop computer on premises.
|
||||
|
||||
### Enable BitLocker protection for your Windows To Go drive
|
||||
|
||||
@ -467,7 +468,7 @@ BitLocker recovery keys are the keys that can be used to unlock a BitLocker prot
|
||||
|
||||
$Disk = Get-Disk | Where-Object {$_.Path -match "USBSTOR" -and $_.Size -gt 20Gb -and -not $_.IsBoot }
|
||||
|
||||
#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with ‘New-Partition…) Validate that this is the correct disk that you want to completely erase.
|
||||
#Clear the disk. This will delete any data on the disk. (and will fail if the disk is not yet initialized. If that happens, simply continue with 'New-Partition…) Validate that this is the correct disk that you want to completely erase.
|
||||
#
|
||||
# To skip the confirmation prompt, append –confirm:$False
|
||||
Clear-Disk –InputObject $Disk[0] -RemoveData
|
||||
@ -576,17 +577,17 @@ The sample script creates an unattend file that streamlines the deployment proce
|
||||
|
||||
* To run this sample script you must open a Windows PowerShell session as an administrator from a domain-joined computer using an account that has permission to create domain accounts.
|
||||
|
||||
* Using offline domain join is required by this script, since the script does not create a local administrator user account. However, domain membership will automatically put “Domain admins” into the local administrators group. Review your domain policies. If you are using DirectAccess you will need to modify the djoin.exe command to include the `policynames` and potentially the `certtemplate` parameters.
|
||||
* Using offline domain join is required by this script, since the script does not create a local administrator user account. However, domain membership will automatically put "Domain admins" into the local administrators group. Review your domain policies. If you are using DirectAccess you will need to modify the djoin.exe command to include the `policynames` and potentially the `certtemplate` parameters.
|
||||
|
||||
* The script needs to use drive letters, so you can only provision half as many drives as you have free drive letters.
|
||||
|
||||
#### To run the advanced deployment sample script
|
||||
|
||||
1. Copy entire the code sample titled “Windows To Go multiple drive provisioning sample script” into a PowerShell script (.ps1) file.
|
||||
1. Copy entire the code sample titled "Windows To Go multiple drive provisioning sample script" into a PowerShell script (.ps1) file.
|
||||
|
||||
2. Make the modifications necessary for it to be appropriate to your deployment and save the file.
|
||||
|
||||
3. Configure the PowerShell execution policy. By default PowerShell’s execution policy is set to Restricted; that means that scripts won’t run until you have explicitly given them permission to. To configure PowerShell’s execution policy to allow the script to run, use the following command from an elevated PowerShell prompt:
|
||||
3. Configure the PowerShell execution policy. By default PowerShell's execution policy is set to Restricted; that means that scripts won't run until you have explicitly given them permission to. To configure PowerShell's execution policy to allow the script to run, use the following command from an elevated PowerShell prompt:
|
||||
|
||||
```
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
audience: itpro
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deploy Windows 10
|
||||
|
||||
@ -15,6 +15,7 @@ manager: laurawi
|
||||
ms.audience: itpro
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# MBR2GPT.EXE
|
||||
@ -22,8 +23,6 @@ ms.topic: article
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
## Summary
|
||||
|
||||
**MBR2GPT.EXE** converts a disk from the Master Boot Record (MBR) to the GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. The tool is designed to be run from a Windows Preinstallation Environment (Windows PE) command prompt, but can also be run from the full Windows 10 operating system (OS) by using the **/allowFullOS** option.
|
||||
|
||||
>MBR2GPT.EXE is located in the **Windows\\System32** directory on a computer running Windows 10 version 1703 (also known as the Creator's Update) or later.
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: 0ce05f66-9009-4739-a789-60f3ce380e76
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
description: The Compatibility Administrator tool helps you resolve potential application-compatibility issues before deploying a new version of Windows.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
@ -12,6 +12,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Compatibility Administrator User's Guide
|
||||
|
||||
@ -4,7 +4,7 @@ ms.assetid: fdfbf02f-c4c4-4739-a400-782204fd3c6c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description:
|
||||
description: Learn about deploying your compatibility fixes as part of an application-installation package or through a centralized compatibility-fix database.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
@ -13,6 +13,7 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
---
|
||||
|
||||
# Compatibility Fix Database Management Strategies and Deployment
|
||||
@ -88,7 +89,7 @@ This approach tends to work best for organizations that have a well-developed de
|
||||
|
||||
### Merging Centralized Compatibility-Fix Databases
|
||||
|
||||
If you decide to use the centralized compatibility-fix database deployment strategy, you can merge any of your individual compatibility-fix databases. This enables you to create a single custom compatibility-fix database that can be used to search for and determine whether Windows® should apply a fix to a specific executable (.exe) file. We recommend merging your databases based on the following process.
|
||||
If you decide to use the centralized compatibility-fix database deployment strategy, you can merge any of your individual compatibility-fix databases. This enables you to create a single custom compatibility-fix database that can be used to search for and determine whether Windows® should apply a fix to a specific executable (.exe) file. We recommend merging your databases based on the following process.
|
||||
|
||||
**To merge your custom-compatibility databases**
|
||||
|
||||
@ -113,7 +114,7 @@ If you decide to use the centralized compatibility-fix database deployment strat
|
||||
|
||||
Deploying your custom compatibility-fix database into your organization requires you to perform the following actions:
|
||||
|
||||
1. Store your custom compatibility-fix database (.sdb file) in a location that is accessible to all of your organization’s computers.
|
||||
1. Store your custom compatibility-fix database (.sdb file) in a location that is accessible to all of your organization's computers.
|
||||
|
||||
2. Use the Sdbinst.exe command-line tool to install the custom compatibility-fix database locally.
|
||||
|
||||
@ -124,7 +125,7 @@ In order to meet the two requirements above, we recommend that you use one of th
|
||||
You can package your .sdb file and a custom deployment script into an .msi file, and then deploy the .msi file into your organization.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You must ensure that you mark your custom script so that it does not impersonate the calling user. For example, if you use Microsoft® Visual Basic® Scripting Edition (VBScript), the custom action type would be:
|
||||
> You must ensure that you mark your custom script so that it does not impersonate the calling user. For example, if you use Microsoft® Visual Basic® Scripting Edition (VBScript), the custom action type would be:
|
||||
>`msidbCustomActionTypeVBScript + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 0x0006 + 0x0400 + 0x0800 = 0x0C06 = 3078 decimal)`
|
||||
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista (Windows 10)
|
||||
title: Compatibility Fixes for Windows 10, Windows 8, Windows 7, & Windows Vista
|
||||
description: Find compatibility fixes for all Windows operating systems that have been released from Windows Vista through Windows 10.
|
||||
ms.assetid: cd51c824-557f-462a-83bb-54b0771b7dff
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista
|
||||
@ -75,7 +76,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>BIOSRead</p></td>
|
||||
<td align="left"><p>This problem is indicated when an application cannot access the <strong>Device\PhysicalMemory</strong> object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems.</p>
|
||||
<td align="left"><p>This problem is indicated when an application cannot access the <strong>Device\PhysicalMemory</strong> object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems.</p>
|
||||
<p>The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the <strong>\Device\Physical</strong> memory information..</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -92,7 +93,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="even">
|
||||
<td align="left"><p>ChangeFolderPathToXPStyle</p></td>
|
||||
<td align="left"><p>This fix is required when an application cannot return shell folder paths when it uses the <strong>SHGetFolder</strong> API.</p>
|
||||
<p>The fix intercepts the <strong>SHGetFolder</strong> path request to the common <strong>appdata</strong> file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.</p></td>
|
||||
<p>The fix intercepts the <strong>SHGetFolder</strong> path request to the common <strong>appdata</strong> file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ClearLastErrorStatusonIntializeCriticalSection</p></td>
|
||||
@ -188,7 +189,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>DirectXVersionLie</p></td>
|
||||
<td align="left"><p>This problem occurs when an application fails because it does not find the correct version number for DirectX®.</p>
|
||||
<td align="left"><p>This problem occurs when an application fails because it does not find the correct version number for DirectX®.</p>
|
||||
<p>The fix modifies the DXDIAGN GetProp function call to return the correct DirectX version.</p>
|
||||
<p>You can control this fix further by typing the following command at the command prompt:</p>
|
||||
<p>MAJORVERSION.MINORVERSION.LETTER</p>
|
||||
@ -456,7 +457,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IgnoreMSOXMLMF</p></td>
|
||||
<td align="left"><p>The problem is indicated by an error message that states that the operating system cannot locate the MSVCR80D.DLL file.</p>
|
||||
<p>The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID.</p></td>
|
||||
<p>The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>IgnoreSetROP2</p></td>
|
||||
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deployment considerations for Windows To Go
|
||||
@ -51,7 +52,7 @@ When a Windows To Go workspace is first used at the workplace, the Windows To Go
|
||||
|
||||
|
||||
|
||||
When the Windows To Go workspace is going to be used first on an off-premises computer, such as one at the employee’s home, then the IT professional preparing the Windows To Go drives should configure the drive to be able to connect to organizational resources and to maintain the security of the workspace. In this situation, the Windows To Go workspace needs to be configured for offline domain join and BitLocker needs to be enabled before the workspace has been initialized.
|
||||
When the Windows To Go workspace is going to be used first on an off-premises computer, such as one at the employee's home, then the IT professional preparing the Windows To Go drives should configure the drive to be able to connect to organizational resources and to maintain the security of the workspace. In this situation, the Windows To Go workspace needs to be configured for offline domain join and BitLocker needs to be enabled before the workspace has been initialized.
|
||||
|
||||
> [!TIP]
|
||||
> Applying BitLocker Drive Encryption to the drives before provisioning is a much faster process than encrypting the drives after data has already been stored on them due to a new feature called used-disk space only encryption. For more information, see [What's New in BitLocker](https://go.microsoft.com/fwlink/p/?LinkId=619076).
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Enabling and Disabling Compatibility Fixes in Compatibility Administrator (Windows 10)
|
||||
title: Enabling and Disabling Compatibility Fixes in Compatibility Administrator
|
||||
description: You can disable and enable individual compatibility fixes in your customized databases for testing and troubleshooting purposes.
|
||||
ms.assetid: 6bd4a7c5-0ed9-4a35-948c-c438aa4d6cb6
|
||||
ms.reviewer:
|
||||
@ -12,6 +12,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Enabling and Disabling Compatibility Fixes in Compatibility Administrator
|
||||
|
||||
@ -10,6 +10,7 @@ author: greg-lindsay
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
# Windows 10 features lifecycle
|
||||
|
||||
@ -21,7 +22,7 @@ Each release of Windows 10 contains many new and improved features. Occasionally
|
||||
|
||||
The following topic lists features that are no longer being developed. These features might be removed in a future release.
|
||||
|
||||
[Windows 10 features we’re no longer developing](windows-10-deprecated-features.md)
|
||||
[Windows 10 features we're no longer developing](windows-10-deprecated-features.md)
|
||||
|
||||
## Features removed
|
||||
|
||||
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Prepare your organization for Windows To Go
|
||||
@ -25,7 +26,7 @@ ms.topic: article
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
The following information is provided to help you plan and design a new deployment of a Windows To Go in your production environment. It provides answers to the “what”, “why”, and “when” questions an IT professional might have when planning to deploy Windows To Go.
|
||||
The following information is provided to help you plan and design a new deployment of a Windows To Go in your production environment. It provides answers to the "what", "why", and "when" questions an IT professional might have when planning to deploy Windows To Go.
|
||||
|
||||
## What is Windows To Go?
|
||||
|
||||
@ -51,16 +52,16 @@ The following scenarios are examples of situations in which Windows To Go worksp
|
||||
|
||||
- **Continuance of operations (COO).** In this scenario, selected employees receive a USB drive with a Windows To Go workspace, which includes all of the applications that the employees use at work. The employees can keep the device at home, in a briefcase, or wherever they want to store it until needed. When the users boot their home computer from the USB drive, it will create a corporate desktop experience so that they can quickly start working. On the very first boot, the employee sees that Windows is installing devices; after that one time, the Windows To Go drive boots like a normal computer. If they have enterprise network access, employees can use a virtual private network (VPN) connection or DirectAccess to access corporate resources. If the enterprise network is available, the Windows To Go workspace will automatically be updated using your standard client management processes.
|
||||
|
||||
- **Contractors and temporary workers.** In this situation, an enterprise IT pro or manager would distribute the Windows To Go drive directly to the worker where they can be assisted with any necessary additional user education needs or address any possible compatibility issues. While the worker is on assignment, they can boot their computer exclusively from the Windows To Go drive and run all applications in that environment until the end of the assignment when the device is returned. No installation of software is required on the worker’s personal computer.
|
||||
- **Contractors and temporary workers.** In this situation, an enterprise IT pro or manager would distribute the Windows To Go drive directly to the worker where they can be assisted with any necessary additional user education needs or address any possible compatibility issues. While the worker is on assignment, they can boot their computer exclusively from the Windows To Go drive and run all applications in that environment until the end of the assignment when the device is returned. No installation of software is required on the worker's personal computer.
|
||||
|
||||
- **Managed free seating.** The employee is issued a Windows To Go drive that is then used with the host computer assigned to that employee for a given session (this could be a vehicle, workspace, or standalone laptop). When the employee leaves the session, the next time they return they use the same USB flash drive but use a different host computer.
|
||||
|
||||
- **Work from home.** In this situation, the Windows To Go drive can be provisioned for employees using various methods including Microsoft Endpoint Configuration Manager or other deployment tools and then distributed to employees. The employee is instructed to boot the Windows To Go drive initially at work, which caches the employee’s credentials on the Windows To Go workspace and allows the initial data synchronization between the enterprise network and the Windows To Go workspace. The user can then bring the Windows To Go drive home where it can be used with their home computer, with or without enterprise network connectivity.
|
||||
- **Work from home.** In this situation, the Windows To Go drive can be provisioned for employees using various methods including Microsoft Endpoint Configuration Manager or other deployment tools and then distributed to employees. The employee is instructed to boot the Windows To Go drive initially at work, which caches the employee's credentials on the Windows To Go workspace and allows the initial data synchronization between the enterprise network and the Windows To Go workspace. The user can then bring the Windows To Go drive home where it can be used with their home computer, with or without enterprise network connectivity.
|
||||
|
||||
- **Travel lightly.** In this situation you have employees who are moving from site to site, but who always will have access to a compatible host computer on site. Using Windows To Go workspaces allows them to travel without the need to pack their PC.
|
||||
|
||||
> [!NOTE]
|
||||
> If the employee wants to work offline for the majority of the time, but still maintain the ability to use the drive on the enterprise network, they should be informed of how often the Windows To Go workspace needs to be connected to the enterprise network. Doing so will ensure that the drive retains its access privileges and the workspace’s computer object is not potentially deleted from Active Directory Domain Services (AD DS).
|
||||
> If the employee wants to work offline for the majority of the time, but still maintain the ability to use the drive on the enterprise network, they should be informed of how often the Windows To Go workspace needs to be connected to the enterprise network. Doing so will ensure that the drive retains its access privileges and the workspace's computer object is not potentially deleted from Active Directory Domain Services (AD DS).
|
||||
|
||||
|
||||
|
||||
@ -76,7 +77,7 @@ Windows To Go uses volume activation. You can use either Active Directory-based
|
||||
|
||||
Microsoft software, such as Microsoft Office, distributed to a Windows To Go workspace must also be activated. Office deployment is fully supported on Windows To Go. Please note, due to the retail subscription activation method associated with Microsoft 365 Apps for enterprise, Microsoft 365 Apps for enterprise subscribers are provided volume licensing activation rights for Office Professional Plus 2013 MSI for local installation on the Windows To Go drive. This is available to organizations who purchase Microsoft 365 Apps for enterprise or Office 365 Enterprise SKUs containing Microsoft 365 Apps for enterprise via volume licensing channels. For more information about activating Microsoft Office, see [Volume activation methods in Office 2013](https://go.microsoft.com/fwlink/p/?LinkId=618922).
|
||||
|
||||
You should investigate other software manufacturer’s licensing requirements to ensure they are compatible with roaming usage before deploying them to a Windows To Go workspace.
|
||||
You should investigate other software manufacturer's licensing requirements to ensure they are compatible with roaming usage before deploying them to a Windows To Go workspace.
|
||||
|
||||
> [!NOTE]
|
||||
> Using Multiple Activation Key (MAK) activation is not a supported activation method for Windows To Go as each different PC-host would require separate activation. MAK activation should not be used for activating Windows, Office, or any other application on a Windows To Go drive.
|
||||
@ -102,7 +103,7 @@ If you configure Windows To Go drives for scenarios where drives may remain unus
|
||||
## User account and data management
|
||||
|
||||
|
||||
People use computers to work with data and consume content - that is their core function. The data must be stored and retrievable for it to be useful. When users are working in a Windows To Go workspace, they need to have the ability to get to the data that they work with and to keep it accessible when the workspace is not being used. For this reason we recommend that you use folder redirection and offline files to redirect the path of local folders (such as the Documents folder) to a network location, while caching the contents locally for increased speed and availability. We also recommend that you use roaming user profiles to synchronize user specific settings so that users receive the same operating system and application settings when using their Windows To Go workspace and their desktop computer. When a user signs in using a domain account that is set up with a file share as the profile path, the user’s profile is downloaded to the local computer and merged with the local profile (if present). When the user logs off the computer, the local copy of their profile, including any changes, is merged with the server copy of the profile. For more information, see [Folder Redirection, Offline Files, and Roaming User Profiles overview](https://go.microsoft.com/fwlink/p/?LinkId=618924).
|
||||
People use computers to work with data and consume content - that is their core function. The data must be stored and retrievable for it to be useful. When users are working in a Windows To Go workspace, they need to have the ability to get to the data that they work with and to keep it accessible when the workspace is not being used. For this reason we recommend that you use folder redirection and offline files to redirect the path of local folders (such as the Documents folder) to a network location, while caching the contents locally for increased speed and availability. We also recommend that you use roaming user profiles to synchronize user specific settings so that users receive the same operating system and application settings when using their Windows To Go workspace and their desktop computer. When a user signs in using a domain account that is set up with a file share as the profile path, the user's profile is downloaded to the local computer and merged with the local profile (if present). When the user logs off the computer, the local copy of their profile, including any changes, is merged with the server copy of the profile. For more information, see [Folder Redirection, Offline Files, and Roaming User Profiles overview](https://go.microsoft.com/fwlink/p/?LinkId=618924).
|
||||
|
||||
Windows To Go is fully integrated with your Microsoft account. Setting synchronization is accomplished by connecting a Microsoft account to a user account. Windows To Go devices fully support this feature and can be managed by Group Policy so that the customization and configurations you prefer will be applied to your Windows To Go workspace.
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: SUA User's Guide (Windows 10)
|
||||
description: Standard User Analyzer (SUA) can test your apps and monitor API calls to detect compatibility issues related to Windows' User Account Control (UAC) feature.
|
||||
description: Learn how to use Standard User Analyzer (SUA). SUA can test your apps and monitor API calls to detect compatibility issues related to the Windows User Account Control (UAC) feature.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.assetid: ea525c25-b557-4ed4-b042-3e4d0e543e10
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -67,4 +68,3 @@ You can use SUA in either of the following ways:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ author: greg-lindsay
|
||||
ms.author: greglin
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Features and functionality removed in Windows 10
|
||||
@ -44,7 +45,7 @@ The following features and functionalities have been removed from the installed
|
||||
|Future updates through [Windows Embedded Developer Update](https://docs.microsoft.com/previous-versions/windows/embedded/ff770079\(v=winembedded.60\)) for Windows Embedded Standard 7-SP1 (WES7-SP1) and Windows Embedded Standard 8 (WES8)|We’re no longer publishing new updates to the WEDU server. Instead, you may secure any new updates from the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx). [Learn how](https://techcommunity.microsoft.com/t5/Windows-Embedded/Change-to-the-Windows-Embedded-Developer-Update/ba-p/285704) to get updates from the catalog.| 1809 |
|
||||
|Groove Music Pass|[We ended the Groove streaming music service and music track sales through the Microsoft Store in 2017](https://support.microsoft.com/help/4046109/groove-music-and-spotify-faq). The Groove app is being updated to reflect this change. You can still use Groove Music to play the music on your PC. You can use Spotify or other music services to stream music on Windows 10, or to buy music to own.| 1803 |
|
||||
|People - Suggestions will no longer include unsaved contacts for non-Microsoft accounts|Manually save the contact details for people you send mail to or get mail from.| 1803 |
|
||||
|Language control in the Control Panel| Use the Settings app to change your language settings.| 1803 |
|
||||
|Language control in the Control Panel| Use the Settings app to change your language settings.| 1803 |
|
||||
|HomeGroup|We are removing [HomeGroup](https://support.microsoft.com/help/17145) but not your ability to share printers, files, and folders.<br><br>When you update to Windows 10, version 1803, you won't see HomeGroup in File Explorer, the Control Panel, or Troubleshoot (**Settings > Update & Security > Troubleshoot**). Any printers, files, and folders that you shared using HomeGroup **will continue to be shared**.<br><br>Instead of using HomeGroup, you can now share printers, files and folders by using features that are built into Windows 10: <br>- [Share your network printer](https://www.bing.com/search?q=share+printer+windows+10) <br>- [Share files in File Explorer](https://support.microsoft.com/help/4027674/windows-10-share-files-in-file-explorer) | 1803 |
|
||||
|**Connect to suggested open hotspots** option in Wi-Fi settings |We previously [disabled the **Connect to suggested open hotspots** option](https://privacy.microsoft.com/windows-10-open-wi-fi-hotspots) and are now removing it from the Wi-Fi settings page. You can manually connect to free wireless hotspots with **Network & Internet** settings, from the taskbar or Control Panel, or by using Wi-Fi Settings (for mobile devices).| 1803 |
|
||||
|XPS Viewer|We're changing the way you get XPS Viewer. In Windows 10, version 1709 and earlier versions, the app is included in the installation image. If you have XPS Viewer and you update to Windows 10, version 1803, there's no action required. You'll still have XPS Viewer. <br><br>However, if you install Windows 10, version 1803, on a new device (or as a clean installation), you may need to [install XPS Viewer from **Apps and Features** in the Settings app](https://docs.microsoft.com/windows/application-management/add-apps-and-features) or through [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities). If you had XPS Viewer in Windows 10, version 1709, but manually removed it before updating, you'll need to manually reinstall it.| 1803 |
|
||||
|
||||
@ -49,13 +49,13 @@ The following list identifies some commonly asked questions about Windows To Go.
|
||||
|
||||
- [How do I make my computer boot from USB?](#wtf-faq-startup)
|
||||
|
||||
- [Why isn’t my computer booting from USB?](#wtg-faq-noboot)
|
||||
- [Why isn't my computer booting from USB?](#wtg-faq-noboot)
|
||||
|
||||
- [What happens if I remove my Windows To Go drive while it is running?](#wtg-faq-surprise)
|
||||
|
||||
- [Can I use BitLocker to protect my Windows To Go drive?](#wtg-faq-bitlocker)
|
||||
|
||||
- [Why can’t I enable BitLocker from Windows To Go Creator?](#wtg-faq-blfail)
|
||||
- [Why can't I enable BitLocker from Windows To Go Creator?](#wtg-faq-blfail)
|
||||
|
||||
- [What power states does Windows To Go support?](#wtg-faq-power)
|
||||
|
||||
@ -63,11 +63,11 @@ The following list identifies some commonly asked questions about Windows To Go.
|
||||
|
||||
- [Does Windows To Go support crash dump analysis?](#wtg-faq-crashdump)
|
||||
|
||||
- [Do “Windows To Go Startup Options” work with dual boot computers?](#wtg-faq-dualboot)
|
||||
- [Do "Windows To Go Startup Options" work with dual boot computers?](#wtg-faq-dualboot)
|
||||
|
||||
- [I plugged my Windows To Go drive into a running computer and I can’t see the partitions on the drive. Why not?](#wtg-faq-diskpart)
|
||||
- [I plugged my Windows To Go drive into a running computer and I can't see the partitions on the drive. Why not?](#wtg-faq-diskpart)
|
||||
|
||||
- [I’m booted into Windows To Go, but I can’t browse to the internal hard drive of the host computer. Why not?](#wtg-faq-san4)
|
||||
- [I'm booted into Windows To Go, but I can't browse to the internal hard drive of the host computer. Why not?](#wtg-faq-san4)
|
||||
|
||||
- [Why does my Windows To Go drive have an MBR disk format with a FAT32 system partition?](#wtg-faq-fatmbr)
|
||||
|
||||
@ -95,17 +95,17 @@ The following list identifies some commonly asked questions about Windows To Go.
|
||||
|
||||
- [How is Windows To Go licensed?](#wtg-faq-lic)
|
||||
|
||||
- [Does Windows Recovery Environment work with Windows To Go? What’s the guidance for recovering a Windows To Go drive?](#wtg-faq-recovery)
|
||||
- [Does Windows Recovery Environment work with Windows To Go? What's the guidance for recovering a Windows To Go drive?](#wtg-faq-recovery)
|
||||
|
||||
- [Why won’t Windows To Go work on a computer running Windows XP or Windows Vista?](#wtg-faq-oldos)
|
||||
- [Why won't Windows To Go work on a computer running Windows XP or Windows Vista?](#wtg-faq-oldos)
|
||||
|
||||
- [Why does the operating system on the host computer matter?](#wtg-faq-oldos2)
|
||||
|
||||
- [My host computer running Windows 7 is protected by BitLocker Drive Encryption. Why did I need to use the recovery key to unlock and reboot my host computer after using Windows To Go?](#wtg-faq-blreckey)
|
||||
|
||||
- [I decided to stop using a drive for Windows To Go and reformatted it – why doesn’t it have a drive letter assigned and how can I fix it?](#wtg-faq-reformat)
|
||||
- [I decided to stop using a drive for Windows To Go and reformatted it – why doesn't it have a drive letter assigned and how can I fix it?](#wtg-faq-reformat)
|
||||
|
||||
- [Why do I keep on getting the message “Installing devices…” when I boot Windows To Go?](#bkmk-roamconflict)
|
||||
- [Why do I keep on getting the message "Installing devices…" when I boot Windows To Go?](#bkmk-roamconflict)
|
||||
|
||||
- [How do I upgrade the operating system on my Windows To Go drive?](#bkmk-upgradewtg)
|
||||
|
||||
@ -188,7 +188,7 @@ In the **Windows To Go Startup Options** dialog box select **Yes** and then clic
|
||||
|
||||
If the host computer is running an earlier version of the Windows operating system need to configure the computer to boot from USB manually.
|
||||
|
||||
To do this, early during boot time (usually when you see the manufacturer’s logo), enter your firmware/BIOS setup. (This method to enter firmware/BIOS setup differs with different computer manufacturers, but is usually entered by pressing one of the function keys, such as F12, F2, F1, Esc, and so forth. You should check the manufacturer’s site to be sure if you do not know which key to use to enter firmware setup.)
|
||||
To do this, early during boot time (usually when you see the manufacturer's logo), enter your firmware/BIOS setup. (This method to enter firmware/BIOS setup differs with different computer manufacturers, but is usually entered by pressing one of the function keys, such as F12, F2, F1, Esc, and so forth. You should check the manufacturer's site to be sure if you do not know which key to use to enter firmware setup.)
|
||||
|
||||
After you have entered firmware setup, make sure that boot from USB is enabled. Then change the boot order to boot from USB drives first.
|
||||
|
||||
@ -201,14 +201,14 @@ Configuring a computer to boot from USB will cause your computer to attempt to b
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-noboot"></a>Why isn’t my computer booting from USB?
|
||||
## <a href="" id="wtg-faq-noboot"></a>Why isn't my computer booting from USB?
|
||||
|
||||
|
||||
Computers certified for Windows 7 and later are required to have support for USB boot. Check to see if any of the following items apply to your situation:
|
||||
|
||||
1. Ensure that your computer has the latest BIOS installed and the BIOS is configured to boot from a USB device.
|
||||
|
||||
2. Ensure that the Windows To Go drive is connected directly to a USB port on the computer. Many computers don’t support booting from a device connected to a USB 3 PCI add-on card or external USB hubs.
|
||||
2. Ensure that the Windows To Go drive is connected directly to a USB port on the computer. Many computers don't support booting from a device connected to a USB 3 PCI add-on card or external USB hubs.
|
||||
|
||||
3. If the computer is not booting from a USB 3.0 port, try to boot from a USB 2.0 port.
|
||||
|
||||
@ -229,7 +229,7 @@ You should never remove your Windows To Go drive when your workspace is running.
|
||||
|
||||
Yes. In Windows 8 and later, BitLocker has added support for using a password to protect operating system drives. This means that you can use a password to secure your Windows To Go workspace and you will be prompted to enter this password every time you use the Windows To Go workspace.
|
||||
|
||||
## <a href="" id="wtg-faq-blfail"></a>Why can’t I enable BitLocker from Windows To Go Creator?
|
||||
## <a href="" id="wtg-faq-blfail"></a>Why can't I enable BitLocker from Windows To Go Creator?
|
||||
|
||||
|
||||
Several different Group Policies control the use of BitLocker on your organizations computers. These policies are located in the **Computer Configuration\\Policies\\Administrative Templates\\Windows Components\\BitLocker Drive Encryption** folder of the local Group Policy editor. The folder contains three sub-folders for fixed, operating system and removable data drive types.
|
||||
@ -265,27 +265,27 @@ When a Windows To Go workspace is hibernated, it will only successfully resume o
|
||||
|
||||
Yes. Windows 8 and later support crash dump stack analysis for both USB 2.0 and 3.0.
|
||||
|
||||
## <a href="" id="wtg-faq-dualboot"></a>Do “Windows To Go Startup Options” work with dual boot computers?
|
||||
## <a href="" id="wtg-faq-dualboot"></a>Do "Windows To Go Startup Options" work with dual boot computers?
|
||||
|
||||
|
||||
Yes, if both operating systems are running the Windows 8 operating system. Enabling “Windows To Go Startup Options” should cause the computer to boot from the Windows To Go workspace when the drive is plugged in before the computer is turned on.
|
||||
Yes, if both operating systems are running the Windows 8 operating system. Enabling "Windows To Go Startup Options" should cause the computer to boot from the Windows To Go workspace when the drive is plugged in before the computer is turned on.
|
||||
|
||||
If you have configured a dual boot computer with a Windows operating system and another operating system it might work occasionally and fail occasionally. Using this configuration is unsupported.
|
||||
|
||||
## <a href="" id="wtg-faq-diskpart"></a>I plugged my Windows To Go drive into a running computer and I can’t see the partitions on the drive. Why not?
|
||||
## <a href="" id="wtg-faq-diskpart"></a>I plugged my Windows To Go drive into a running computer and I can't see the partitions on the drive. Why not?
|
||||
|
||||
|
||||
Windows To Go Creator and the recommended deployment steps for Windows To Go set the NO\_DEFAULT\_DRIVE\_LETTER flag on the Windows To Go drive. This flag prevents Windows from automatically assigning drive letters to the partitions on the Windows To Go drive. That’s why you can’t see the partitions on the drive when you plug your Windows To Go drive into a running computer. This helps prevent accidental data leakage between the Windows To Go drive and the host computer. If you really need to access the files on the Windows To Go drive from a running computer, you can use diskmgmt.msc or diskpart to assign a drive letter.
|
||||
Windows To Go Creator and the recommended deployment steps for Windows To Go set the NO\_DEFAULT\_DRIVE\_LETTER flag on the Windows To Go drive. This flag prevents Windows from automatically assigning drive letters to the partitions on the Windows To Go drive. That's why you can't see the partitions on the drive when you plug your Windows To Go drive into a running computer. This helps prevent accidental data leakage between the Windows To Go drive and the host computer. If you really need to access the files on the Windows To Go drive from a running computer, you can use diskmgmt.msc or diskpart to assign a drive letter.
|
||||
|
||||
**Warning**
|
||||
It is strongly recommended that you do not plug your Windows To Go drive into a running computer. If the computer is compromised, your Windows To Go workspace can also be compromised.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-san4"></a>I’m booted into Windows To Go, but I can’t browse to the internal hard drive of the host computer. Why not?
|
||||
## <a href="" id="wtg-faq-san4"></a>I'm booted into Windows To Go, but I can't browse to the internal hard drive of the host computer. Why not?
|
||||
|
||||
|
||||
Windows To Go Creator and the recommended deployment steps for Windows To Go set SAN Policy 4 on Windows To Go drive. This policy prevents Windows from automatically mounting internal disk drives. That’s why you can’t see the internal hard drives of the host computer when you are booted into Windows To Go. This is done to prevent accidental data leakage between Windows To Go and the host system. This policy also prevents potential corruption on the host drives or data loss if the host operating system is in a hibernation state. If you really need to access the files on the internal hard drive, you can use diskmgmt.msc to mount the internal drive.
|
||||
Windows To Go Creator and the recommended deployment steps for Windows To Go set SAN Policy 4 on Windows To Go drive. This policy prevents Windows from automatically mounting internal disk drives. That's why you can't see the internal hard drives of the host computer when you are booted into Windows To Go. This is done to prevent accidental data leakage between Windows To Go and the host system. This policy also prevents potential corruption on the host drives or data loss if the host operating system is in a hibernation state. If you really need to access the files on the internal hard drive, you can use diskmgmt.msc to mount the internal drive.
|
||||
|
||||
**Warning**
|
||||
It is strongly recommended that you do not mount internal hard drives when booted into the Windows To Go workspace. If the internal drive contains a hibernated Windows 8 or later operating system, mounting the drive will lead to loss of hibernation state and therefor user state or any unsaved user data when the host operating system is booted. If the internal drive contains a hibernated Windows 7 or earlier operating system, mounting the drive will lead to corruption when the host operating system is booted.
|
||||
@ -340,7 +340,7 @@ If you are using a USB 3.0 port and a Windows To Go certified device, there shou
|
||||
## <a href="" id="wtg-faq-safeloss"></a>If I lose my Windows To Go drive, will my data be safe?
|
||||
|
||||
|
||||
Yes! If you enable BitLocker on your Windows To Go drive, all your data will be encrypted and protected and a malicious user will not be able to access your data without your password. If you don’t enable BitLocker, your data will be vulnerable if you lose your Windows To Go drive.
|
||||
Yes! If you enable BitLocker on your Windows To Go drive, all your data will be encrypted and protected and a malicious user will not be able to access your data without your password. If you don't enable BitLocker, your data will be vulnerable if you lose your Windows To Go drive.
|
||||
|
||||
## <a href="" id="wtg-faq-mac"></a>Can I boot Windows To Go on a Mac?
|
||||
|
||||
@ -361,12 +361,12 @@ For more information, see the MSDN article on the [Win32\_OperatingSystem class]
|
||||
|
||||
Windows To Go allows organization to support the use of privately owned PCs at the home or office with more secure access to their organizational resources. With Windows To Go use rights under [Software Assurance](https://go.microsoft.com/fwlink/p/?LinkId=619062), an employee will be able to use Windows To Go on any company PC licensed with Software Assurance as well as from their home PC.
|
||||
|
||||
## <a href="" id="wtg-faq-recovery"></a>Does Windows Recovery Environment work with Windows To Go? What’s the guidance for recovering a Windows To Go drive?
|
||||
## <a href="" id="wtg-faq-recovery"></a>Does Windows Recovery Environment work with Windows To Go? What's the guidance for recovering a Windows To Go drive?
|
||||
|
||||
|
||||
No, use of Windows Recovery Environment is not supported on Windows To Go. It is recommended that you implement user state virtualization technologies like Folder Redirection to centralize and back up user data in the data center. If any corruption occurs on a Windows To Go drive, you should re-provision the workspace.
|
||||
|
||||
## <a href="" id="wtg-faq-oldos"></a>Why won’t Windows To Go work on a computer running Windows XP or Windows Vista?
|
||||
## <a href="" id="wtg-faq-oldos"></a>Why won't Windows To Go work on a computer running Windows XP or Windows Vista?
|
||||
|
||||
|
||||
Actually it might. If you have purchased a computer certified for Windows 7 or later and then installed an older operating system, Windows To Go will boot and run as expected as long as you have configured the firmware to boot from USB. However, if the computer was certified for Windows XP or Windows Vista, it might not meet the hardware requirements for Windows To Go to run. Typically computers certified for Windows Vista and earlier operating systems have less memory, less processing power, reduced video rendering, and slower USB ports.
|
||||
@ -374,7 +374,7 @@ Actually it might. If you have purchased a computer certified for Windows 7 or
|
||||
## <a href="" id="wtg-faq-oldos2"></a>Why does the operating system on the host computer matter?
|
||||
|
||||
|
||||
It doesn’t other than to help visually identify if the PC has compatible hardware. For a PC to be certified for Windows 7 or later it had to support booting from USB. If a computer cannot boot from USB there is no way that it can be used with Windows To Go. The Windows To Go workspace is a full Windows 10 environment, so all of the hardware requirements of Windows 10 with respect to processing speed, memory usage, and graphics rendering need to be supported to be assured that it will work as expected.
|
||||
It doesn't other than to help visually identify if the PC has compatible hardware. For a PC to be certified for Windows 7 or later it had to support booting from USB. If a computer cannot boot from USB there is no way that it can be used with Windows To Go. The Windows To Go workspace is a full Windows 10 environment, so all of the hardware requirements of Windows 10 with respect to processing speed, memory usage, and graphics rendering need to be supported to be assured that it will work as expected.
|
||||
|
||||
## <a href="" id="wtg-faq-blreckey"></a>My host computer running Windows 7 is protected by BitLocker Drive Encryption. Why did I need to use the recovery key to unlock and reboot my host computer after using Windows To Go?
|
||||
|
||||
@ -406,10 +406,10 @@ The host computer will now be able to be booted from a USB drive without trigger
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-reformat"></a>I decided to stop using a drive for Windows To Go and reformatted it – why doesn’t it have a drive letter assigned and how can I fix it?
|
||||
## <a href="" id="wtg-faq-reformat"></a>I decided to stop using a drive for Windows To Go and reformatted it – why doesn't it have a drive letter assigned and how can I fix it?
|
||||
|
||||
|
||||
Reformatting the drive erases the data on the drive, but doesn’t reconfigure the volume attributes. When a drive is provisioned for use as a Windows To Go drive the NODEFAULTDRIVELETTER attribute is set on the volume. To remove this attribute, use the following steps:
|
||||
Reformatting the drive erases the data on the drive, but doesn't reconfigure the volume attributes. When a drive is provisioned for use as a Windows To Go drive the NODEFAULTDRIVELETTER attribute is set on the volume. To remove this attribute, use the following steps:
|
||||
|
||||
1. Open a command prompt with full administrator permissions.
|
||||
|
||||
@ -424,14 +424,14 @@ Reformatting the drive erases the data on the drive, but doesn’t reconfigure t
|
||||
|
||||
4. After selecting the disk, run the `clean` command to remove all data, formatting, and initialization information from the drive.
|
||||
|
||||
## <a href="" id="bkmk-roamconflict"></a>Why do I keep on getting the message “Installing devices…” when I boot Windows To Go?
|
||||
## <a href="" id="bkmk-roamconflict"></a>Why do I keep on getting the message "Installing devices…" when I boot Windows To Go?
|
||||
|
||||
|
||||
One of the challenges involved in moving the Windows To Go drive between PCs while seamlessly booting Windows with access to all of their applications and data is that for Windows to be fully functional, specific drivers need to be installed for the hardware in each machine that runs Windows. Windows 8 or later has a process called respecialize which will identify new drivers that need to be loaded for the new PC and disable drivers which are not present on the new configuration. In general this feature is reliable and efficient when roaming between PCs of widely varying hardware configurations.
|
||||
|
||||
In certain cases, third party drivers for different hardware models or versions can reuse device ID’s, driver file names, registry keys (or any other operating system constructs which do not support side-by-side storage) for similar hardware. For example, Touchpad drivers on different laptops often reuse the same device ID’s, and video cards from the same manufacturer may often reuse service names. Windows handles these situations by marking the non-present device node with a flag that indicates the existing driver needs to be reinstalled before continuing to install the new driver.
|
||||
In certain cases, third party drivers for different hardware models or versions can reuse device ID's, driver file names, registry keys (or any other operating system constructs which do not support side-by-side storage) for similar hardware. For example, Touchpad drivers on different laptops often reuse the same device ID's, and video cards from the same manufacturer may often reuse service names. Windows handles these situations by marking the non-present device node with a flag that indicates the existing driver needs to be reinstalled before continuing to install the new driver.
|
||||
|
||||
This process will occur on any boot that a new driver is found and a driver conflict is detected. In some cases that will result in a respecialize progress message “Installing devices…” displaying every time that a Windows to Go drive is roamed between two PCs which require conflicting drivers.
|
||||
This process will occur on any boot that a new driver is found and a driver conflict is detected. In some cases that will result in a respecialize progress message "Installing devices…" displaying every time that a Windows to Go drive is roamed between two PCs which require conflicting drivers.
|
||||
|
||||
## <a href="" id="bkmk-upgradewtg"></a>How do I upgrade the operating system on my Windows To Go drive?
|
||||
|
||||
|
||||
@ -14,6 +14,7 @@ author: greg-lindsay
|
||||
ms.author: greglin
|
||||
audience: itpro
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Windows 10 in S mode - What is it?
|
||||
|
||||
@ -12,6 +12,7 @@ ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Windows Updates using forward and reverse differentials
|
||||
@ -37,8 +38,6 @@ The following general terms apply throughout this document:
|
||||
- *Revision*: Minor releases in between the major version releases, such as KB4464330 (Windows 10 Build 17763.55)
|
||||
- *Baseless Patch Storage Files (Baseless PSF)*: Patch storage files that contain full binaries or files
|
||||
|
||||
## Introduction
|
||||
|
||||
In this paper, we introduce a new technique that can produce compact software
|
||||
updates optimized for any origin/destination revision pair. It does this by
|
||||
calculating forward the differential of a changed file from the base version and
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
title: Introduction to the Windows Insider Program for Business
|
||||
description: Introduction to the Windows Insider Program for Business and why IT Pros should join
|
||||
description: In this article, you'll learn about the Windows Insider Program for Business and why IT Pros should join.
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -12,6 +12,7 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Conclusion
|
||||
|
||||
@ -11,6 +11,7 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deploy feature updates during maintenance windows
|
||||
@ -33,7 +34,7 @@ Use the following information to deploy feature updates during a maintenance win
|
||||
|
||||
### Step 2: Review computer restart device settings
|
||||
|
||||
If you’re not suppressing computer restarts and the feature update will be installed when no users are present, consider deploying a custom client settings policy to your feature update target collection to shorten the settings below or consider the total duration of these settings when defining your maintenance window duration.
|
||||
If you're not suppressing computer restarts and the feature update will be installed when no users are present, consider deploying a custom client settings policy to your feature update target collection to shorten the settings below or consider the total duration of these settings when defining your maintenance window duration.
|
||||
|
||||
For example, by default, 90 minutes will be honored before the system is rebooted after the feature update install. If users will not be impacted by the user logoff or restart, there is no need to wait a full 90 minutes before rebooting the computer. If a delay and notification is needed, ensure that the maintenance window takes this into account along with the total time needed to install the feature update.
|
||||
|
||||
@ -50,7 +51,7 @@ Use **Peer Cache** to help manage deployment of content to clients in remote loc
|
||||
|
||||
### Step 4: Override the default Windows setup priority (Windows 10, version 1709 and later)
|
||||
|
||||
If you’re deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
|
||||
If you're deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
|
||||
|
||||
%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
|
||||
|
||||
|
||||
@ -12,13 +12,14 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Best practices and recommendations for deploying Windows 10 Feature updates to mission critical devices
|
||||
|
||||
**Applies to**: Windows 10
|
||||
|
||||
Managing an environment with devices that provide mission critical services 24 hours a day, 7 days a week, can present challenges in keeping these devices current with Windows 10 feature updates. The processes that you use to keep regular devices current with Windows 10 feature updates, often aren’t the most effective to service mission critical devices. This whitepaper will focus on the recommended approach of using the Microsoft Endpoint Configuration Manager (current branch) software updates feature to deploy Windows 10 semi-annual feature updates.
|
||||
Managing an environment with devices that provide mission critical services 24 hours a day, 7 days a week, can present challenges in keeping these devices current with Windows 10 feature updates. The processes that you use to keep regular devices current with Windows 10 feature updates, often aren't the most effective to service mission critical devices. This whitepaper will focus on the recommended approach of using the Microsoft Endpoint Configuration Manager (current branch) software updates feature to deploy Windows 10 semi-annual feature updates.
|
||||
|
||||
For simplicity, we will outline the steps to deploy a feature update manually. If you prefer an automated approach, see [Manage Windows as a service using Configuration Manager](https://docs.microsoft.com/configmgr/osd/deploy-use/manage-windows-as-a-service).
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Deploy feature updates for user-initiated installations (during a fixed service window)
|
||||
@ -29,7 +30,7 @@ Use **Peer Cache** to help manage deployment of content to clients in remote loc
|
||||
|
||||
### Step 2: Override the default Windows setup priority (Windows 10, version 1709 and later)
|
||||
|
||||
If you’re deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
|
||||
If you're deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
|
||||
|
||||
%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
|
||||
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
---
|
||||
title: Windows 10 - How to make FoD and language packs available when you're using WSUS or Configuration Manager
|
||||
description: Learn how to make FoD and language packs available when you're using WSUS or Configuration Manager
|
||||
title: Make FoD and language packs available for WSUS/Configuration Manager
|
||||
description: Learn how to make FoD and language packs available when you're using WSUS/Configuration Manager.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
ms.pagetype: article
|
||||
ms.author: jaimeo
|
||||
audience: itpro
|
||||
@ -13,6 +12,7 @@ ms.date: 03/13/2019
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
# How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager
|
||||
|
||||
@ -20,11 +20,11 @@ ms.topic: article
|
||||
|
||||
As of Windows 10 version 1709, you can't use Windows Server Update Services (WSUS) to host [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (FODs) locally. Starting with Windows 10 version 1803, language packs can no longer be hosted on WSUS.
|
||||
|
||||
The **Specify settings for optional component installation and component repair** policy, located under `Computer Configuration\Administrative Templates\System` in the Group Policy Editor, can be used to specify alternate ways to acquire FOD packages, language packages, and content for corruption repair. However, it’s important to note this policy only allows specifying one alternate location and behaves differently across OS versions.
|
||||
The **Specify settings for optional component installation and component repair** policy, located under `Computer Configuration\Administrative Templates\System` in the Group Policy Editor, can be used to specify alternate ways to acquire FOD packages, language packages, and content for corruption repair. However, it's important to note this policy only allows specifying one alternate location and behaves differently across OS versions.
|
||||
|
||||
In Windows 10 version 1709 and 1803, changing the **Specify settings for optional component installation and component repair** policy to download content from Windows Update enables acquisition of FOD packages while also enabling corruption repair. Specifying a network location works for either, depending on the content is found at that location. Changing this policy on these OS versions does not influence how language packs are acquired.
|
||||
|
||||
In Windows 10 version 1809 and beyond, changing the **Specify settings for optional component installation and component repair** policy also influences how language packs are acquired, however language packs can only be acquired directly from Windows Update. It’s currently not possible to acquire them from a network share. Specifying a network location works for FOD packages or corruption repair, depending on the content at that location.
|
||||
In Windows 10 version 1809 and beyond, changing the **Specify settings for optional component installation and component repair** policy also influences how language packs are acquired, however language packs can only be acquired directly from Windows Update. It's currently not possible to acquire them from a network share. Specifying a network location works for FOD packages or corruption repair, depending on the content at that location.
|
||||
|
||||
For all OS versions, changing the **Specify settings for optional component installation and component repair** policy does not affect how OS updates are distributed. They continue to come from WSUS, Configuration Manager, or other sources as you have scheduled them, even while optional content is sourced from Windows Update or a network location.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Update works
|
||||
description: Learn how Windows Update works, including architecture and troubleshooting.
|
||||
description: In this article, learn about the process Windows Update uses to download and install updates on a Windows 10 devices.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
audience: itpro
|
||||
@ -12,6 +12,7 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# How does Windows Update work?
|
||||
@ -45,7 +46,7 @@ The Windows Update workflow has four core areas of functionality:
|
||||
|
||||
|
||||
## How updating works
|
||||
During the updating process, the Windows Update Orchestrator operates in the background to scan, download, and install updates. It does this automatically, according to your settings, and in a silent manner that doesn’t disrupt your computer usage.
|
||||
During the updating process, the Windows Update Orchestrator operates in the background to scan, download, and install updates. It does this automatically, according to your settings, and in a silent manner that doesn't disrupt your computer usage.
|
||||
|
||||
## Scanning updates
|
||||
|
||||
@ -127,7 +128,7 @@ Common update failure is caused due to network issues. To find the root of the i
|
||||
|
||||
Once the Windows Update Orchestrator determines which updates apply to your computer, it will begin downloading the updates, if you have selected the option to automatically download updates. It does this in the background without interrupting your normal use of the computer.
|
||||
|
||||
To ensure that your other downloads aren’t affected or slowed down because updates are downloading, Windows Update uses the Delivery Optimization (DO) technology which downloads updates and reduces bandwidth consumption.
|
||||
To ensure that your other downloads aren't affected or slowed down because updates are downloading, Windows Update uses the Delivery Optimization technology which downloads updates and reduces bandwidth consumption.
|
||||
|
||||
For more information see [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md).
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
keywords: insider, trial, enterprise, lab, corporation, test
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Olympia Corp
|
||||
@ -60,7 +61,7 @@ This is the Bring Your Own Device (BYOD) method--your device will receive Olympi
|
||||
|
||||
3. Click **Connect** and enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
@ -96,10 +97,10 @@ This is the Bring Your Own Device (BYOD) method--your device will receive Olympi
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
|
||||
3. Click **Connect**, then click **Join this device to Azure Active Directory**.
|
||||
|
||||
|
||||
![Joining device to Azure AD]](images/2-3.png)
|
||||
|
||||
4. Enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
@ -110,7 +111,7 @@ This is the Bring Your Own Device (BYOD) method--your device will receive Olympi
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
|
||||
6. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Servicing stack updates (Windows 10)
|
||||
description: Servicing stack updates improve the code that installs the other updates.
|
||||
description: In this article, learn how servicing stack updates improve the code that installs the other updates.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
@ -12,6 +12,7 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Servicing stack updates
|
||||
|
||||
@ -13,6 +13,7 @@ keywords: oms, operations management suite, optimization, downloads, updates, lo
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Delivery Optimization in Update Compliance
|
||||
@ -41,5 +42,5 @@ The table breaks down the number of bytes from each download source into specifi
|
||||
|
||||
The download sources that could be included are:
|
||||
- LAN Bytes: Bytes downloaded from LAN Peers which are other devices on the same local network
|
||||
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the “Group” download mode is used)
|
||||
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the "Group" download mode is used)
|
||||
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an SCCM Distribution Point for Express Updates.
|
||||
|
||||
@ -12,6 +12,7 @@ author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Feature Update Status
|
||||
|
||||
@ -13,6 +13,7 @@ ms.author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Monitor Windows Updates with Update Compliance
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Update Compliance - Need Attention! report
|
||||
manager: laurawi
|
||||
description: Learn how the Needs attention! section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance.
|
||||
description: Learn how the Need attention! section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance.
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
|
||||
@ -10,6 +10,7 @@ author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Security Update Status
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Using Update Compliance (Windows 10)
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Learn how to use Update Compliance to monitor your device's Windows updates and Microsoft Defender Antivirus status.
|
||||
description: Learn how to use Update Compliance to monitor your device's Windows updates.
|
||||
keywords: oms, operations management suite, wdav, updates, upgrades, antivirus, antimalware, signature, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,6 +13,7 @@ ms.author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Use Update Compliance
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configure BranchCache for Windows 10 updates (Windows 10)
|
||||
description: Use BranchCache to optimize network bandwidth during update deployment.
|
||||
description: In this article, learn how to use BranchCache to optimize network bandwidth during update deployment.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
@ -9,6 +9,7 @@ ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Configure BranchCache for Windows 10 updates
|
||||
@ -20,7 +21,7 @@ ms.topic: article
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
BranchCache is a bandwidth-optimization feature that has been available since the Windows Server 2008 R2 and Windows 7 operating systems. Each client has a cache and acts as an alternate source for content that devices on its own network request. Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager can use BranchCache to optimize network bandwidth during update deployment, and it’s easy to configure for either of them. BranchCache has two operating modes: Distributed Cache mode and Hosted Cache mode.
|
||||
BranchCache is a bandwidth-optimization feature that has been available since the Windows Server 2008 R2 and Windows 7 operating systems. Each client has a cache and acts as an alternate source for content that devices on its own network request. Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager can use BranchCache to optimize network bandwidth during update deployment, and it's easy to configure for either of them. BranchCache has two operating modes: Distributed Cache mode and Hosted Cache mode.
|
||||
|
||||
- Distributed Cache mode operates like the [Delivery Optimization](waas-delivery-optimization.md) feature in Windows 10: each client contains a cached version of the BranchCache-enabled files it requests and acts as a distributed cache for other clients requesting that same file.
|
||||
|
||||
@ -33,7 +34,7 @@ For detailed information about how Distributed Cache mode and Hosted Cache mode
|
||||
|
||||
## Configure clients for BranchCache
|
||||
|
||||
Whether you use BranchCache with Configuration Manager or WSUS, each client that uses BranchCache must be configured to do so. You typically make your configurations through Group Policy. For step-by-step instructions on how to use Group Policy to configure BranchCache for Windows clients, see [Client Configuration](https://technet.microsoft.com/library/dd637820%28v=ws.10%29.aspx) in the [BranchCache Early Adopter’s Guide](https://technet.microsoft.com/library/dd637762(v=ws.10).aspx).
|
||||
Whether you use BranchCache with Configuration Manager or WSUS, each client that uses BranchCache must be configured to do so. You typically make your configurations through Group Policy. For step-by-step instructions on how to use Group Policy to configure BranchCache for Windows clients, see [Client Configuration](https://technet.microsoft.com/library/dd637820%28v=ws.10%29.aspx) in the [BranchCache Early Adopter's Guide](https://technet.microsoft.com/library/dd637762(v=ws.10).aspx).
|
||||
|
||||
In Windows 10, version 1607, the Windows Update Agent uses Delivery Optimization by default, even when the updates are retrieved from WSUS. When using BranchCache with Windows 10, simply set the Delivery Optimization mode to Bypass to allow clients to use the Background Intelligent Transfer Service (BITS) protocol with BranchCache instead. For instructions on how to use BranchCache in Distributed Cache mode with WSUS, see the section WSUS and Configuration Manager with BranchCache in Distributed Cache mode.
|
||||
|
||||
|
||||
@ -2,17 +2,17 @@
|
||||
title: Delivery Optimization reference
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Reference of all Delivery Optimization settings and descriptions of same
|
||||
description: This article provides a summary of references and descriptions for all of the Delivery Optimization settings.
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
audience: itpro
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Delivery Optimization reference
|
||||
@ -111,7 +111,7 @@ Download mode dictates which download sources clients are allowed to use when do
|
||||
| --- | --- |
|
||||
| HTTP Only (0) | This setting disables peer-to-peer caching but still allows Delivery Optimization to download content over HTTP from the download's original source. This mode uses additional metadata provided by the Delivery Optimization cloud services for a peerless reliable and efficient download experience. |
|
||||
| LAN (1 – Default) | This default operating mode for Delivery Optimization enables peer sharing on the same network. The Delivery Optimization cloud service finds other clients that connect to the Internet using the same public IP as the target client. These clients then attempts to connect to other peers on the same network by using their private subnet IP.|
|
||||
| Group (2) | When group mode is set, the group is automatically selected based on the device’s Active Directory Domain Services (AD DS) site (Windows 10, version 1607) or the domain the device is authenticated to (Windows 10, version 1511). In group mode, peering occurs across internal subnets, between devices that belong to the same group, including devices in remote offices. You can use GroupID option to create your own custom group independently of domains and AD DS sites. Starting with Windows 10, version 1803, you can use the GroupIDSource parameter to take advantage of other method to create groups dynamically. Group download mode is the recommended option for most organizations looking to achieve the best bandwidth optimization with Delivery Optimization. |
|
||||
| Group (2) | When group mode is set, the group is automatically selected based on the device's Active Directory Domain Services (AD DS) site (Windows 10, version 1607) or the domain the device is authenticated to (Windows 10, version 1511). In group mode, peering occurs across internal subnets, between devices that belong to the same group, including devices in remote offices. You can use GroupID option to create your own custom group independently of domains and AD DS sites. Starting with Windows 10, version 1803, you can use the GroupIDSource parameter to take advantage of other method to create groups dynamically. Group download mode is the recommended option for most organizations looking to achieve the best bandwidth optimization with Delivery Optimization. |
|
||||
| Internet (3) | Enable Internet peer sources for Delivery Optimization. |
|
||||
| Simple (99) | Simple mode disables the use of Delivery Optimization cloud services completely (for offline environments). Delivery Optimization switches to this mode automatically when the Delivery Optimization cloud services are unavailable, unreachable or when the content file size is less than 10 MB. In this mode, Delivery Optimization provides a reliable download experience, with no peer-to-peer caching. |
|
||||
|Bypass (100) | Bypass Delivery Optimization and use BITS, instead. You should only select this mode if you use WSUS and prefer to use BranchCache. You do not need to set this option if you are using Configuration Manager. If you want to disable peer-to-peer functionality, it's best to set **DownloadMode** to **0** or **99**. |
|
||||
@ -156,7 +156,7 @@ This setting specifies the required minimum disk size (capacity in GB) for the d
|
||||
|
||||
### Max Cache Age
|
||||
|
||||
In environments configured for Delivery Optimization, you might want to set an expiration on cached updates and Windows application installation files. If so, this setting defines the maximum number of seconds each file can be held in the Delivery Optimization cache on each Windows 10 client device. The default Max Cache Age value is 259,200 seconds (3 days). Alternatively, organizations might choose to set this value to “0” which means “unlimited” to avoid peers re-downloading content. When “Unlimited” value is set, Delivery Optimization will hold the files in the cache longer and will clean up the cache as needed (for example when the cache size exceeded the maximum space allowed).
|
||||
In environments configured for Delivery Optimization, you might want to set an expiration on cached updates and Windows application installation files. If so, this setting defines the maximum number of seconds each file can be held in the Delivery Optimization cache on each Windows 10 client device. The default Max Cache Age value is 259,200 seconds (3 days). Alternatively, organizations might choose to set this value to "0" which means "unlimited" to avoid peers re-downloading content. When "Unlimited" value is set, Delivery Optimization will hold the files in the cache longer and will clean up the cache as needed (for example when the cache size exceeded the maximum space allowed).
|
||||
|
||||
### Max Cache Size
|
||||
|
||||
@ -188,7 +188,7 @@ This setting specifies the maximum download bandwidth that Delivery Optimization
|
||||
|
||||
### Max Upload Bandwidth
|
||||
|
||||
This setting allows you to limit the amount of upload bandwidth individual clients can use for Delivery Optimization. Consider this setting when clients are providing content to requesting peers on the network. This option is set in kilobytes per second (KB/s). The default setting is 0, or “unlimited” which means Delivery Optimization dynamically optimizes for minimal usage of upload bandwidth; however it does not cap the upload bandwidth rate at a set rate.
|
||||
This setting allows you to limit the amount of upload bandwidth individual clients can use for Delivery Optimization. Consider this setting when clients are providing content to requesting peers on the network. This option is set in kilobytes per second (KB/s). The default setting is 0, or "unlimited" which means Delivery Optimization dynamically optimizes for minimal usage of upload bandwidth; however it does not cap the upload bandwidth rate at a set rate.
|
||||
|
||||
### Set Business Hours to Limit Background Download Bandwidth
|
||||
Starting in Windows 10, version 1803, specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Set up Delivery Optimization
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Delivery Optimization is a new peer-to-peer distribution method in Windows 10
|
||||
description: In this article, learn how to set up Delivery Optimization, a new peer-to-peer distribution method in Windows 10.
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -12,6 +12,7 @@ ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Set up Delivery Optimization for Windows 10 updates
|
||||
@ -50,7 +51,7 @@ Quick-reference table:
|
||||
|
||||
### Hybrid WAN scenario
|
||||
|
||||
For this scenario, grouping devices by domain allows devices to be included in peer downloads and uploads across VLANs. **Set Download Mode to 2 - Group**. The default group is the authenticated domain or Active Directory site. If your domain-based group is too wide, or your Active Directory sites aren’t aligned with your site network topology, then you should consider additional options for dynamically creating groups, for example by using the GroupIDSrc parameter.
|
||||
For this scenario, grouping devices by domain allows devices to be included in peer downloads and uploads across VLANs. **Set Download Mode to 2 - Group**. The default group is the authenticated domain or Active Directory site. If your domain-based group is too wide, or your Active Directory sites aren't aligned with your site network topology, then you should consider additional options for dynamically creating groups, for example by using the GroupIDSrc parameter.
|
||||
|
||||
|
||||
|
||||
@ -103,7 +104,7 @@ To do this with MDM, go to **.Vendor/MSFT/Policy/Config/DeliveryOptimization/**
|
||||
|
||||
|
||||
## Monitor Delivery Optimization
|
||||
[//]: # (How to tell if it’s working? What values are reasonable; which are not? If not, which way to adjust and how? -- check PercentPeerCaching for files > minimum >= 50%)
|
||||
[//]: # (How to tell if it's working? What values are reasonable; which are not? If not, which way to adjust and how? -- check PercentPeerCaching for files > minimum >= 50%)
|
||||
|
||||
### Windows PowerShell cmdlets
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Delivery Optimization for Windows 10 updates
|
||||
manager: laurawi
|
||||
description: Delivery Optimization is a peer-to-peer distribution method in Windows 10
|
||||
description: This article provides information about Delivery Optimization, a peer-to-peer distribution method in Windows 10.
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,6 +13,7 @@ ms.collection:
|
||||
- M365-modern-desktop
|
||||
- m365initiative-coredeploy
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Delivery Optimization for Windows 10 updates
|
||||
@ -120,7 +121,7 @@ For complete list of every possible Delivery Optimization setting, see [Delivery
|
||||
|
||||
|
||||
## How Microsoft uses Delivery Optimization
|
||||
At Microsoft, to help ensure that ongoing deployments weren’t affecting our network and taking away bandwidth for other services, Microsoft IT used a couple of different bandwidth management strategies. Delivery Optimization, peer-to-peer caching enabled through Group Policy, was piloted and then deployed to all managed devices using Group Policy. Based on recommendations from the Delivery Optimization team, we used the "group" configuration to limit sharing of content to only the devices that are members of the same Active Directory domain. The content is cached for 24 hours. More than 76 percent of content came from peer devices versus the Internet.
|
||||
At Microsoft, to help ensure that ongoing deployments weren't affecting our network and taking away bandwidth for other services, Microsoft IT used a couple of different bandwidth management strategies. Delivery Optimization, peer-to-peer caching enabled through Group Policy, was piloted and then deployed to all managed devices using Group Policy. Based on recommendations from the Delivery Optimization team, we used the "group" configuration to limit sharing of content to only the devices that are members of the same Active Directory domain. The content is cached for 24 hours. More than 76 percent of content came from peer devices versus the Internet.
|
||||
|
||||
For more details, check out the [Adopting Windows as a Service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft) technical case study.
|
||||
|
||||
@ -188,7 +189,7 @@ This section summarizes common problems and some solutions to try.
|
||||
|
||||
### If you don't see any bytes from peers
|
||||
|
||||
If you don’t see any bytes coming from peers the cause might be one of the following issues:
|
||||
If you don't see any bytes coming from peers the cause might be one of the following issues:
|
||||
|
||||
- Clients aren’t able to reach the Delivery Optimization cloud services.
|
||||
- The cloud service doesn’t see other peers on the network.
|
||||
|
||||
@ -2,13 +2,14 @@
|
||||
title: Windows Update for Business (Windows 10)
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Update for Business lets you manage when devices received updates from Windows Update.
|
||||
description: Learn how Windows Update for Business lets you manage when devices receive updates from Windows Update.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# What is Windows Update for Business?
|
||||
@ -187,16 +188,16 @@ The branch readiness level enables administrators to specify which channel of fe
|
||||
- Windows Insider Release Preview
|
||||
- Semi-annual Channel for released updates
|
||||
|
||||
Prior to Windows 10, version 1903, there are two channels for released updates: Semi-annual Channel and Semi-annual Channel (Targeted). Deferral days are calculated against the release date of the chosen channel. Starting with Windows 10, version 1903 there is only the one release channel: Semi-annual Channel. All deferral days will be calculated against a release’s Semi-annual Channel release date. To see release dates, visit [Windows Release Information](https://docs.microsoft.com/windows/release-information/). You can set the branch readiness level by using the **Select when Preview Builds and Feature Updates are Received** policy. In order to use this to manage pre-release builds, first enable preview builds by using the **Manage preview Builds** policy.
|
||||
Prior to Windows 10, version 1903, there are two channels for released updates: Semi-annual Channel and Semi-annual Channel (Targeted). Deferral days are calculated against the release date of the chosen channel. Starting with Windows 10, version 1903 there is only the one release channel: Semi-annual Channel. All deferral days will be calculated against a release's Semi-annual Channel release date. To see release dates, visit [Windows Release Information](https://docs.microsoft.com/windows/release-information/). You can set the branch readiness level by using the **Select when Preview Builds and Feature Updates are Received** policy. In order to use this to manage pre-release builds, first enable preview builds by using the **Manage preview Builds** policy.
|
||||
|
||||
### Recommendations
|
||||
|
||||
For the best experience with Windows Update, follow these guidelines:
|
||||
|
||||
- Use devices for at least 6 hours per month, including at least 2 hours of continuous use.
|
||||
- Keep devices regularly charged. Plugging in devices overnight enables them to automatically update outside of active hours.
|
||||
- Make sure that devices have at least 10 GB of free space.
|
||||
- Give devices unobstructed access to the Windows Update service.
|
||||
- Use devices for at least 6 hours per month, including at least 2 hours of continuous use.
|
||||
- Keep devices regularly charged. Plugging in devices overnight enables them to automatically update outside of active hours.
|
||||
- Make sure that devices have at least 10 GB of free space.
|
||||
- Give devices unobstructed access to the Windows Update service.
|
||||
|
||||
|
||||
## Monitor Windows Updates by using Update Compliance
|
||||
|
||||
@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Windows as a service news & resources
|
||||
description: The latest news for Windows as a service with resources to help you learn more about them.
|
||||
ms.prod: w10
|
||||
ms.topic: article
|
||||
ms.manager: elizapo
|
||||
@ -17,8 +18,8 @@ Here's more news about [Windows as a service](windows-as-a-service.md):
|
||||
<ul>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-Enterprise-vs-Windows-10-Pro-Modern-management/ba-p/720445">Windows 10 Enterprise vs. Windows 10 Pro: Modern management considerations for your organization </a> - June 25, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Updating-Windows-10-version-1903-using-Configuration-Manager-or/ba-p/639100">Updating Windows 10, version 1903 using Configuration Manager or WSUS</a> - May 23, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-in-Windows-Update-for-Business-in-Windows-10-version/ba-p/622064">What’s new in Windows Update for Business in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1903/ba-p/622024">What’s new for IT pros in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-in-Windows-Update-for-Business-in-Windows-10-version/ba-p/622064">What's new in Windows Update for Business in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1903/ba-p/622024">What's new for IT pros in Windows 10, version 1903</a> - May 21, 2019</li>
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/05/21/how-to-get-the-windows-10-may-2019-update">How to get the Windows 10 May 2019 Update</a> - May 21, 2019</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/The-benefits-of-Windows-10-Dynamic-Update/ba-p/467847">The benefits of Windows 10 Dynamic Update</a> - April 17, 2019</li>
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2019/04/04/improving-the-windows-10-update-experience-with-control-quality-and-transparency">Improving the Windows 10 update experience with control, quality and transparency</a> - April 4, 2019</li>
|
||||
|
||||
@ -3,13 +3,14 @@ title: Manage device restarts after updates (Windows 10)
|
||||
description: Use Group Policy settings, mobile device management (MDM) or Registry to configure when devices will restart after a Windows 10 update is installed.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
- seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Manage device restarts after updates
|
||||
|
||||
@ -3,13 +3,14 @@ title: Assign devices to servicing channels for Windows 10 updates (Windows 10)
|
||||
description: Learn how to assign devices to servicing channels for Windows 10 updates locally, by using Group Policy, and by using MDM .
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
- seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Assign devices to servicing channels for Windows 10 updates
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Servicing differences between Windows 10 and older operating systems
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Learn the differences between servicing Windows 10 and servicing older operating systems.
|
||||
description: In this article, learn the differences between servicing Windows 10 and servicing older operating systems.
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -12,6 +12,7 @@ ms.audience: itpro
|
||||
author: jaimeo
|
||||
ms.topic: article
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
# Understanding the differences between servicing Windows 10-era and legacy Windows operating systems
|
||||
|
||||
@ -31,7 +32,7 @@ Prior to Windows 10, all updates to operating system (OS) components were publis
|
||||
|
||||
As a result, each environment within the global Windows ecosystem that had only a subset of security and non-security fixes installed had a different set of binaries and behaviors than those that consistently installed every available update as tested by Microsoft.
|
||||
|
||||
This resulted in a fragmented ecosystem that created diverse challenges in predictively testing interoperability, resulting in high update failure rates - which were subsequently mitigated by customers removing individual updates that were causing issues. Each customer that selectively removed individual updates amplified this fragmentation by creating more diverse environment permutations across the ecosystem. As an IT Administrator once quipped, "If you’ve seen one Windows 7 PC, you have seen one Windows 7 PC," suggesting no consistency or predictability across more than 250M commercial devices at the time.
|
||||
This resulted in a fragmented ecosystem that created diverse challenges in predictively testing interoperability, resulting in high update failure rates - which were subsequently mitigated by customers removing individual updates that were causing issues. Each customer that selectively removed individual updates amplified this fragmentation by creating more diverse environment permutations across the ecosystem. As an IT Administrator once quipped, "If you've seen one Windows 7 PC, you have seen one Windows 7 PC," suggesting no consistency or predictability across more than 250M commercial devices at the time.
|
||||
|
||||
## Windows 10 – Next generation
|
||||
Windows 10 provided an opportunity to end the era of infinite fragmentation. With Windows 10 and the Windows as a service model, updates came rolled together in the "latest cumulative update" (LCU) packages for both client and server. Every new update published includes all changes from previous updates, as well as new fixes. Since Windows client and server share the same code base, these LCUs allow the same update to be installed on the same client and server OS family, further reducing fragmentation.
|
||||
@ -64,12 +65,12 @@ While Windows 10 updates could have been controlled as cumulative from "Day 1,"
|
||||
|
||||
Customers saw the LCU model used for Windows 10 as having packages that were too large and represented too much of a change for legacy operating systems, so a different model was implemented. Windows instead offered one cumulative package (Monthly Rollup) and one individual package (Security Only) for all legacy operating systems.
|
||||
|
||||
The Monthly Rollup includes new non-security (if appropriate), security updates, Internet Explorer (IE) updates, and all updates from the previous month similar to the Windows 10 model. The Security-only package includes only new security updates for the month. This means that any security updates from any previous month are not included in current month’s Security-Only Package. If a Security-Only update is missed, it is missed. Those updates will not appear in a future Security-Only update. Additionally, a cumulative package is offered for IE, which can be tested and installed separately, reducing the total update package size. The IE cumulative update includes both security and non-security fixes following the same model as Windows 10.
|
||||
The Monthly Rollup includes new non-security (if appropriate), security updates, Internet Explorer (IE) updates, and all updates from the previous month similar to the Windows 10 model. The Security-only package includes only new security updates for the month. This means that any security updates from any previous month are not included in current month's Security-Only Package. If a Security-Only update is missed, it is missed. Those updates will not appear in a future Security-Only update. Additionally, a cumulative package is offered for IE, which can be tested and installed separately, reducing the total update package size. The IE cumulative update includes both security and non-security fixes following the same model as Windows 10.
|
||||
|
||||
|
||||
*Figure 2.0 - Legacy OS security-only update model*
|
||||
|
||||
Moving to the cumulative model for legacy OS versions continues to improve predictability of update quality. The Windows legacy environments which have fully updated machines with Monthly Rollups are running the same baseline against which all legacy OS version updates are tested. These include all of the updates (security and non-security) prior to and after October 2016. Many customer environments do not have all updates prior to this change installed, which leaves some continued fragmentation in the ecosystem. Further, customers who are installing Security-Only Updates and potentially doing so inconsistently are also more fragmented than Microsoft’s test environments for legacy OS version. This remaining fragmentation results in issues like those seen when the September 2016 Servicing Stack Update (SSU) was needed for smooth installation of the August 2018 security update. These environments did not have the SSU applied previously.
|
||||
Moving to the cumulative model for legacy OS versions continues to improve predictability of update quality. The Windows legacy environments which have fully updated machines with Monthly Rollups are running the same baseline against which all legacy OS version updates are tested. These include all of the updates (security and non-security) prior to and after October 2016. Many customer environments do not have all updates prior to this change installed, which leaves some continued fragmentation in the ecosystem. Further, customers who are installing Security-Only Updates and potentially doing so inconsistently are also more fragmented than Microsoft's test environments for legacy OS version. This remaining fragmentation results in issues like those seen when the September 2016 Servicing Stack Update (SSU) was needed for smooth installation of the August 2018 security update. These environments did not have the SSU applied previously.
|
||||
|
||||
### Points to consider
|
||||
- Windows 7 and Windows 8 legacy operating system updates [moved from individual to cumulative in October 2016](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/More-on-Windows-7-and-Windows-8-1-servicing-changes/ba-p/166783). Devices with updates missing prior to that point are still missing those updates, as they were not included in the subsequent cumulative packages.
|
||||
@ -83,7 +84,7 @@ Moving to the cumulative model for legacy OS versions continues to improve predi
|
||||
- For [Windows Server 2008 SP2](https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/), cumulative updates began in October 2018, and follow the same model as Windows 7. Updates for IE9 are included in those packages, as the last supported version of Internet Explorer for that Legacy OS version.
|
||||
|
||||
## Public preview releases
|
||||
Lastly, the cumulative update model directly impacts the public Preview releases offered in the 3rd and/or 4th weeks of the month. Update Tuesday, also referred to as the "B" week release occurs on the second Tuesday of the month. It is always a required security update across all operating systems. In addition to this monthly release, Windows also releases non-security update "previews" targeting the 3rd (C) and the 4th (D) weeks of the month. These preview releases include that month’s B-release plus a set of non-security updates for testing and validation as a cumulative package. We recommend IT Administrators uses the C/D previews to test the update in their environments. Any issues identified with the updates in the C/D releases are identified and then fixed or removed, prior to being rolled up in to the next month’s B release package together with new security updates. Security-only Packages are not part of the C/D preview program.
|
||||
Lastly, the cumulative update model directly impacts the public Preview releases offered in the 3rd and/or 4th weeks of the month. Update Tuesday, also referred to as the "B" week release occurs on the second Tuesday of the month. It is always a required security update across all operating systems. In addition to this monthly release, Windows also releases non-security update "previews" targeting the 3rd (C) and the 4th (D) weeks of the month. These preview releases include that month's B-release plus a set of non-security updates for testing and validation as a cumulative package. We recommend IT Administrators uses the C/D previews to test the update in their environments. Any issues identified with the updates in the C/D releases are identified and then fixed or removed, prior to being rolled up in to the next month's B release package together with new security updates. Security-only Packages are not part of the C/D preview program.
|
||||
|
||||
> [!NOTE]
|
||||
> Only preview updates for the most recent release of Windows 10 are published to Windows Server Update Services (WSUS). For customers using the WSUS channel, and products such as Microsoft Endpoint Configuration Manager that rely on it, will not see preview updates for older versions of Windows 10.
|
||||
@ -102,9 +103,9 @@ All of these updates are cumulative and build on each other for Windows 10. This
|
||||
*Figure 3.0 - Preview releases within the Windows 10 LCU model*
|
||||
|
||||
## Previews vs. on-demand releases
|
||||
In 2018, we experienced incidents which required urgent remediation that didn’t map to the monthly update release cadence. These incidents were situations that required an immediate fix to an Update Tuesday release. While Windows engineering worked aggressively to respond within a week of the B-release, these "on-demand" releases created confusion with the C Preview releases.
|
||||
In 2018, we experienced incidents which required urgent remediation that didn't map to the monthly update release cadence. These incidents were situations that required an immediate fix to an Update Tuesday release. While Windows engineering worked aggressively to respond within a week of the B-release, these "on-demand" releases created confusion with the C Preview releases.
|
||||
|
||||
As a general policy, if a Security-Only package has a regression, which is defined as an unintentional error in the code of an update, then the fix for that regression will be added to the next month’s Security-Only Update. The fix for that regression may also be offered as part an On-Demand release and will be rolled into the next Monthly Update. (Note: Exceptions do exist to this policy, based on timing.)
|
||||
As a general policy, if a Security-Only package has a regression, which is defined as an unintentional error in the code of an update, then the fix for that regression will be added to the next month's Security-Only Update. The fix for that regression may also be offered as part an On-Demand release and will be rolled into the next Monthly Update. (Note: Exceptions do exist to this policy, based on timing.)
|
||||
|
||||
### Point to consider
|
||||
- When Windows identifies an issue with a Update Tuesday release, engineering teams work to remediate or fix the issue as quickly as possible. The outcome is often a new update which may be released at any time, including during the 3rd or 4th week of the month. Such updates are independent of the regularly scheduled "C" and "D" update previews. These updates are created on-demand to remediate a customer impacting issue. In most cases they are qualified as a "non-security" update, and do not require a system reboot.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Manage additional Windows Update settings (Windows 10)
|
||||
description: Additional settings to control the behavior of Windows Update (WU) in Windows 10
|
||||
description: In this article, learn about additional settings to control the behavior of Windows Update in Windows 10.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
@ -10,6 +10,7 @@ author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Manage additional Windows Update settings
|
||||
@ -61,7 +62,7 @@ This setting lets you specify a server on your network to function as an interna
|
||||
|
||||
To use this setting in Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows Update\Specify Intranet Microsoft update service location**. You must set two server name values: the server from which the Automatic Updates client detects and downloads updates, and the server to which updated workstations upload statistics. You can set both values to be the same server. An optional server name value can be specified to configure Windows Update Agent to download updates from an alternate download server instead of the intranet update service.
|
||||
|
||||
If the setting is set to **Enabled**, the Automatic Updates client connects to the specified intranet Microsoft update service (or alternate download server), instead of Windows Update, to search for and download updates. Enabling this setting means that end users in your organization don’t have to go through a firewall to get updates, and it gives you the opportunity to test updates after deploying them.
|
||||
If the setting is set to **Enabled**, the Automatic Updates client connects to the specified intranet Microsoft update service (or alternate download server), instead of Windows Update, to search for and download updates. Enabling this setting means that end users in your organization don't have to go through a firewall to get updates, and it gives you the opportunity to test updates after deploying them.
|
||||
If the setting is set to **Disabled** or **Not Configured**, and if Automatic Updates is not disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.
|
||||
|
||||
The alternate download server configures the Windows Update Agent to download files from an alternative download server instead of the intranet update service.
|
||||
@ -86,9 +87,9 @@ If the setting is set to **Enabled**, Windows will check for available updates a
|
||||
If the setting is set to **Disabled** or **Not Configured**, Windows will check for available updates at the default interval of 22 hours.
|
||||
|
||||
>[!NOTE]
|
||||
>The “Specify intranet Microsoft update service location” setting must be enabled for this policy to have effect.
|
||||
>The "Specify intranet Microsoft update service location" setting must be enabled for this policy to have effect.
|
||||
>
|
||||
>If the “Configure Automatic Updates” policy is disabled, this policy has no effect.
|
||||
>If the "Configure Automatic Updates" policy is disabled, this policy has no effect.
|
||||
|
||||
To configure this policy with MDM, use [DetectionFrequency](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#update-detectionfrequency).
|
||||
|
||||
@ -116,7 +117,7 @@ If the setting is set to **Disabled** or **Not Configured**, no target group inf
|
||||
If the intranet Microsoft update service supports multiple target groups, this policy can specify multiple group names separated by semicolons. Otherwise, a single group must be specified.
|
||||
|
||||
>[!NOTE]
|
||||
>This policy applies only when the intranet Microsoft update service the device is directed to is configured to support client-side targeting. If the “Specify intranet Microsoft update service location” policy is disabled or not configured, this policy has no effect.
|
||||
>This policy applies only when the intranet Microsoft update service the device is directed to is configured to support client-side targeting. If the "Specify intranet Microsoft update service location" policy is disabled or not configured, this policy has no effect.
|
||||
|
||||
### Allow signed updates from an intranet Microsoft update service location
|
||||
|
||||
@ -124,7 +125,7 @@ This policy setting allows you to manage whether Automatic Updates accepts updat
|
||||
|
||||
To configure this setting in Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows update\Allow signed updates from an intranet Microsoft update service location**.
|
||||
|
||||
If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, as specified by [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location), if they are signed by a certificate found in the “Trusted Publishers” certificate store of the local computer.
|
||||
If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, as specified by [Specify Intranet Microsoft update service location](#specify-intranet-microsoft-update-service-location), if they are signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
|
||||
If you disable or do not configure this policy setting, updates from an intranet Microsoft update service location must be signed by Microsoft.
|
||||
|
||||
>[!NOTE]
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Walkthrough use Intune to configure Windows Update for Business (Windows 10)
|
||||
description: Configure Windows Update for Business settings using Microsoft Intune.
|
||||
description: In this article, learn how to configure Windows Update for Business settings using Microsoft Intune.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
@ -29,7 +29,7 @@ author: jaimeo
|
||||
>
|
||||
>In the following settings CB refers to Semi-Annual Channel (Targeted), while CBB refers to Semi-Annual Channel.
|
||||
|
||||
You can use Intune to configure Windows Update for Business even if you don’t have on-premises infrastructure when you use Intune in conjunction with Azure AD. Before configuring Windows Update for Business, consider a [deployment strategy](waas-servicing-strategy-windows-10-updates.md) for updates and feature updates in your environment.
|
||||
You can use Intune to configure Windows Update for Business even if you don't have on-premises infrastructure when you use Intune in conjunction with Azure AD. Before configuring Windows Update for Business, consider a [deployment strategy](waas-servicing-strategy-windows-10-updates.md) for updates and feature updates in your environment.
|
||||
|
||||
Windows Update for Business in Windows 10 version 1511 allows you to delay quality updates up to 4 weeks and feature updates up to an additional 8 months after Microsoft releases builds to the Current Branch for Business (CBB) servicing branch. In Windows 10 version 1607 and later, you can delay quality updates for up to 30 days and feature updates up to an additional 180 days after the release of either a Current Branch (CB) or CBB build.
|
||||
|
||||
@ -42,7 +42,7 @@ To use Intune to manage quality and feature updates in your environment, you mus
|
||||
|
||||
In this example, you use two security groups to manage your updates: **Ring 4 Broad business users** and **Ring 5 Broad business users #2** from Table 1 in [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md).
|
||||
|
||||
- The **Ring 4 Broad business users** group contains PCs of IT members who test the updates as soon as they’re released for Windows clients in the Current Branch for Business (CBB) servicing branch. This phase typically occurs after testing on Current Branch (CB) devices.
|
||||
- The **Ring 4 Broad business users** group contains PCs of IT members who test the updates as soon as they're released for Windows clients in the Current Branch for Business (CBB) servicing branch. This phase typically occurs after testing on Current Branch (CB) devices.
|
||||
- The **Ring 5 Broad business users #2** group consists of the first line-of-business (LOB) users, who consume quality updates after 1 week and feature updates 1 month after the CBB release.
|
||||
|
||||
>[!NOTE]
|
||||
@ -69,9 +69,9 @@ In this example, you use two security groups to manage your updates: **Ring 4 Br
|
||||
>[!NOTE]
|
||||
>The OMA-URI settings are case sensitive, so be sure to review [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) for the proper syntax.
|
||||
|
||||
|
||||
|
||||
|
||||
8. For this deployment ring, you’re required to enable only CBB, so click **Save Policy**.
|
||||
8. For this deployment ring, you're required to enable only CBB, so click **Save Policy**.
|
||||
|
||||
9. In the **Deploy Policy: Windows Update for Business – CBB1** dialog box, click **Yes**.
|
||||
|
||||
@ -156,7 +156,7 @@ In this example, you use three security groups from Table 1 in [Build deployment
|
||||
>[!NOTE]
|
||||
>The OMA-URI settings are case sensitive, so be sure to review [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) for the proper syntax.
|
||||
|
||||
|
||||
|
||||
|
||||
8. Because the **Ring 2 Pilot Business Users** deployment ring receives the CB feature updates after 28 days, in the **OMA-URI Settings** section, click **Add** to add another OMA-URI setting.
|
||||
|
||||
@ -164,7 +164,7 @@ In this example, you use three security groups from Table 1 in [Build deployment
|
||||
10. In the **OMA-URI** box, type **./Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays**.
|
||||
11. In the **Value** box, type **28**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
9. Click **Save Policy**.
|
||||
|
||||
@ -175,7 +175,7 @@ In this example, you use three security groups from Table 1 in [Build deployment
|
||||
|
||||
10. In the **Manage Deployment: Windows Update for Business – CB2** dialog box, select the **Ring 2 Pilot Business Users** group, click **Add**, and then click **OK**.
|
||||
|
||||
You have now configured the **Ring 2 Pilot Business Users** deployment ring to enable CB feature update deferment for 14 days. Now, you must configure **Ring 4 Broad business users** to receive CBB features updates as soon as they’re available.
|
||||
You have now configured the **Ring 2 Pilot Business Users** deployment ring to enable CB feature update deferment for 14 days. Now, you must configure **Ring 4 Broad business users** to receive CBB features updates as soon as they're available.
|
||||
|
||||
### Configure Ring 4 Broad business users policy
|
||||
|
||||
@ -205,7 +205,7 @@ You have now configured the **Ring 2 Pilot Business Users** deployment ring to e
|
||||
|
||||
11. In the **Value** box, type **0**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
12. Click **Save Policy**.
|
||||
|
||||
@ -216,7 +216,7 @@ You have now configured the **Ring 2 Pilot Business Users** deployment ring to e
|
||||
|
||||
14. In the **Manage Deployment: Windows Update for Business – CBB1** dialog box, select the **Ring 4 Broad business users** group, click **Add**, and then click **OK**.
|
||||
|
||||
You have now configured the **Ring 4 Broad business users** deployment ring to receive CBB feature updates as soon as they’re available. Finally, configure **Ring 5 Broad business users #2** to accommodate a 7-day delay for quality updates and a 14-day delay for feature updates.
|
||||
You have now configured the **Ring 4 Broad business users** deployment ring to receive CBB feature updates as soon as they're available. Finally, configure **Ring 5 Broad business users #2** to accommodate a 7-day delay for quality updates and a 14-day delay for feature updates.
|
||||
|
||||
|
||||
### Configure Ring 5 Broad business users \#2 policy
|
||||
@ -255,7 +255,7 @@ You have now configured the **Ring 4 Broad business users** deployment ring to r
|
||||
|
||||
15. In the **Value** box, type **14**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
16. Click **Save Policy**.
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ms.date: 09/18/2018
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Windows Update error codes by component
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Update common errors and mitigation
|
||||
description: Learn about some common issues you might experience with Windows Update
|
||||
description: In this article, learn about some common issues you might experience with Windows Update, as well as steps to resolve them.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
audience: itpro
|
||||
@ -11,6 +11,7 @@ ms.date: 09/18/2018
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Windows Update common errors and mitigation
|
||||
|
||||
@ -11,6 +11,7 @@ ms.date: 09/18/2018
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Windows Update log files
|
||||
@ -28,7 +29,7 @@ The following table describes the log files created by Windows Update.
|
||||
|CBS.log|%systemroot%\Logs\CBS|This logs provides insight on the update installation part in the servicing stack.|To troubleshoot the issues related to WU installation.|
|
||||
|
||||
## Generating WindowsUpdate.log
|
||||
To merge and convert WU trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](https://docs.microsoft.com/powershell/module/windowsupdate/get-windowsupdatelog?view=win10-ps).
|
||||
To merge and convert WU trace files (.etl files) into a single readable WindowsUpdate.log file, see [Get-WindowsUpdateLog](https://docs.microsoft.com/powershell/module/windowsupdate/get-windowsupdatelog?view=win10-ps&preserve-view=tru).
|
||||
|
||||
>[!NOTE]
|
||||
>When you run the **Get-WindowsUpdateLog** cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpate.log unless you run **Get-WindowsUpdateLog** again.
|
||||
@ -64,7 +65,7 @@ The WU engine has different component names. The following are some of the most
|
||||
- IdleTimer - Tracking active calls, stopping a service
|
||||
|
||||
>[!NOTE]
|
||||
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what’s important.
|
||||
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what's important.
|
||||
|
||||
### Windows Update log structure
|
||||
The Windows update log structure is separated into four main identities:
|
||||
@ -112,7 +113,7 @@ Search for and identify the components that are associated with the IDs. Differe
|
||||
#### Update identifiers
|
||||
|
||||
##### Update ID and revision number
|
||||
There are different identifiers for the same update in different contexts. It’s important to know the identifier schemes.
|
||||
There are different identifiers for the same update in different contexts. It's important to know the identifier schemes.
|
||||
- Update ID: A GUID (indicated in the previous screen shot) that's assigned to a given update at publication time
|
||||
- Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service
|
||||
- Revision numbers are reused from one update to another (not a unique identifier).
|
||||
@ -121,8 +122,8 @@ There are different identifiers for the same update in different contexts. It’
|
||||
|
||||
|
||||
##### Revision ID
|
||||
- A Revision ID (do no confuse this with “revision number”) is a serial number that's issued when an update is initially published or revised on a given service.
|
||||
- An existing update that’s revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a completely new revision ID that is not related to the previous ID.
|
||||
- A Revision ID (do no confuse this with "revision number") is a serial number that's issued when an update is initially published or revised on a given service.
|
||||
- An existing update that's revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a completely new revision ID that is not related to the previous ID.
|
||||
- Revision IDs are unique on a given update source, but not across multiple sources.
|
||||
- The same update revision may have completely different revision IDs on WU and WSUS.
|
||||
- The same revision ID may represent different updates on WU and WSUS.
|
||||
@ -131,7 +132,7 @@ There are different identifiers for the same update in different contexts. It’
|
||||
- Local ID is a serial number issued when an update is received from a service by a given WU client
|
||||
- Usually seen in debug logs, especially involving the local cache for update info (Datastore)
|
||||
- Different client PCs will assign different Local IDs to the same update
|
||||
- You can find the local IDs that a client is using by getting the client’s %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb file
|
||||
- You can find the local IDs that a client is using by getting the client's %WINDIR%\SoftwareDistribution\Datastore\Datastore.edb file
|
||||
|
||||
##### Inconsistent terminology
|
||||
- Sometimes the logs use terms inconsistently. For example, the InstalledNonLeafUpdateIDs list actually contains revision IDs, not update IDs.
|
||||
|
||||
@ -10,6 +10,7 @@ author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Windows Update troubleshooting
|
||||
|
||||
@ -1,12 +1,13 @@
|
||||
---
|
||||
title: Configure the Basic group policy for Windows Update for Business
|
||||
description: Learn how to get started using the Basic GPO in Windows Update for Business.
|
||||
description: In this article, you will learn how to configure the basic group policy for Windows Update for Business.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
itproauthor: jaimeo
|
||||
author: jaimeo
|
||||
ms.localizationprioauthor: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Enforce compliance deadlines with policies in Windows Update for Business (Windows 10)
|
||||
description: Learn how to enforce compliance deadlines using Windows Update for Business.
|
||||
description: This article contains information on how to enforce compliance deadlines using Windows Update for Business.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
@ -151,17 +152,17 @@ Before the deadline the device will be in two states: auto-restart period and en
|
||||
|
||||
Notification users get for quality update engaged deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update engaged deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Onboarding to Windows Update for Business (Windows 10)
|
||||
description: Get started using Windows Update for Business, a tool that enables IT pros and power users to manage content they want to receive from Windows Update Service.
|
||||
description: Get started using Windows Update for Business, a tool that enables IT pros and power users to manage content they want to receive from Windows Update.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -1,10 +1,11 @@
|
||||
---
|
||||
title: Log files - Windows IT Pro
|
||||
title: Log files and resolving upgrade errors
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn how to interpret the log files generated during the Windows 10 upgrade process.
|
||||
description: Learn how to interpret and analyze the log files that are generated during the Windows 10 upgrade process.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -5,6 +5,7 @@ manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn how to quickly resolve many problems, which may come up during a Windows 10 upgrade.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -5,6 +5,7 @@ manager: laurawi
|
||||
ms.author: greglin
|
||||
description: SetupDiag works by examining Windows Setup log files. This article shows how to use the SetupDiag tool to diagnose Windows Setup errors.
|
||||
keywords: deploy, troubleshoot, windows, 10, upgrade, update, setup, diagnose
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
@ -552,7 +553,7 @@ Refer to "https://docs.microsoft.com/windows/desktop/Debug/system-error-codes" f
|
||||
|
||||
## Sample registry key
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ ms.topic: article
|
||||
# Getting Started with the User State Migration Tool (USMT)
|
||||
This topic outlines the general process that you should follow to migrate files and settings.
|
||||
|
||||
## In this Topic
|
||||
## In this topic
|
||||
- [Step 1: Plan Your Migration](#step-1-plan-your-migration)
|
||||
|
||||
- [Step 2: Collect files and settings from the source computer](#step-2-collect-files-and-settings-from-the-source-computer)
|
||||
@ -48,7 +48,7 @@ This topic outlines the general process that you should follow to migrate files
|
||||
## Step 2: Collect files and settings from the source computer
|
||||
1. Back up the source computer.
|
||||
|
||||
2. Close all applications. If some applications are running when you run the **ScanState** command, USMT might not migrate all of the specified data. For example, if Microsoft® Office Outlook® is open, USMT might not migrate PST files.
|
||||
2. Close all applications. If some applications are running when you run the **ScanState** command, USMT might not migrate all of the specified data. For example, if Microsoft® Office Outlook® is open, USMT might not migrate PST files.
|
||||
|
||||
**Note**
|
||||
USMT will fail if it cannot migrate a file or setting unless you specify the **/C** option. When you specify the **/C** option, USMT will ignore the errors, and log an error every time that it encounters a file that is being used that USMT did not migrate. You can use the **<ErrorControl>** section in the Config.xml file to specify which errors should be ignored, and which should cause the migration to fail.
|
||||
@ -68,7 +68,7 @@ This topic outlines the general process that you should follow to migrate files
|
||||
2. Install all applications that were on the source computer. Although it is not always required, we recommend installing all applications on the destination computer before you restore the user state. This makes sure that migrated settings are preserved.
|
||||
|
||||
**Note**
|
||||
The application version that is installed on the destination computer should be the same version as the one on the source computer. USMT does not support migrating the settings for an older version of an application to a newer version. The exception to this is Microsoft® Office, which USMT can migrate from an older version to a newer version.
|
||||
The application version that is installed on the destination computer should be the same version as the one on the source computer. USMT does not support migrating the settings for an older version of an application to a newer version. The exception to this is Microsoft® Office, which USMT can migrate from an older version to a newer version.
|
||||
|
||||
3. Close all applications. If some applications are running when you run the **LoadState** command, USMT might not migrate all of the specified data. For example, if Microsoft Office Outlook is open, USMT might not migrate PST files.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ ms.topic: article
|
||||
# Offline Migration Reference
|
||||
|
||||
|
||||
Offline migration enables the ScanState tool to run inside a different Windows® operating system than the Windows operating system from which ScanState is gathering files and settings. There are two primary offline scenarios:
|
||||
Offline migration enables the ScanState tool to run inside a different Windows® operating system than the Windows operating system from which ScanState is gathering files and settings. There are two primary offline scenarios:
|
||||
|
||||
- **Windows PE.** The ScanState tool can be run from within Windows PE, gathering files and settings from the offline Windows operating system on that machine.
|
||||
|
||||
@ -31,7 +31,7 @@ When you use User State Migration Tool (USMT) 10.0 to gather and restore user s
|
||||
|
||||
- **New recovery scenario.** In scenarios where a machine no longer restarts properly, it might be possible to gather user state with the ScanState tool from within WinPE.
|
||||
|
||||
## In This Topic
|
||||
## In This topic
|
||||
|
||||
|
||||
- [What Will Migrate Offline?](#bkmk-whatwillmigrate)
|
||||
@ -61,7 +61,7 @@ The following user data and settings migrate offline, similar to an online migra
|
||||
|
||||
- EFS files
|
||||
|
||||
- Internet Explorer® Favorites
|
||||
- Internet Explorer® Favorites
|
||||
|
||||
For exceptions to what you can migrate offline, see [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)
|
||||
|
||||
@ -192,7 +192,7 @@ The following system environment variables are necessary in the scenarios outlin
|
||||
<tr class="even">
|
||||
<td align="left"><p>MIG_OFFLINE_PLATFORM_ARCH</p></td>
|
||||
<td align="left"><p>32 or 64</p></td>
|
||||
<td align="left"><p>While operating offline, this environment variable defines the architecture of the offline system, if the system does not match the WinPE and Scanstate.exe architecture. This environment variable enables the 32-bit ScanState application to gather data from a computer with 64-bit architecture, or the 64-bit ScanState application to gather data from a computer with 32-bit architecture. This is required when auto-detection of the offline architecture doesn’t function properly, for example, when the source system is running a 64-bit version of Windows XP. For example, to set this system environment variable for a 32-bit architecture, at a command prompt type the following:</p>
|
||||
<td align="left"><p>While operating offline, this environment variable defines the architecture of the offline system, if the system does not match the WinPE and Scanstate.exe architecture. This environment variable enables the 32-bit ScanState application to gather data from a computer with 64-bit architecture, or the 64-bit ScanState application to gather data from a computer with 32-bit architecture. This is required when auto-detection of the offline architecture doesn't function properly, for example, when the source system is running a 64-bit version of Windows XP. For example, to set this system environment variable for a 32-bit architecture, at a command prompt type the following:</p>
|
||||
<pre class="syntax" space="preserve"><code>Set MIG_OFFLINE_PLATFORM_ARCH=32</code></pre></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -219,7 +219,7 @@ Syntax: < winDir > </ winDir >
|
||||
|
||||
### <a href="" id="-path-"></a><path>
|
||||
|
||||
This element is a required child of **<winDir>** and contains a file path pointing to a valid Windows directory. Relative paths are interpreted from the ScanState tool’s working directory.
|
||||
This element is a required child of **<winDir>** and contains a file path pointing to a valid Windows directory. Relative paths are interpreted from the ScanState tool's working directory.
|
||||
|
||||
Syntax: <path> c:\\windows </path>
|
||||
|
||||
@ -235,7 +235,7 @@ Syntax: <mappings> </mappings>
|
||||
|
||||
### <a href="" id="-failonmultiplewindir-"></a><failOnMultipleWinDir>
|
||||
|
||||
This element is an optional child of **<offline>**. The **<failOnMultipleWinDir>** element allows the user to specify that the migration should fail when USMT detects that there are multiple instances of Windows installed on the source machine. When the **<failOnMultipleWinDir>** element isn’t present, the default behavior is that the migration does not fail.
|
||||
This element is an optional child of **<offline>**. The **<failOnMultipleWinDir>** element allows the user to specify that the migration should fail when USMT detects that there are multiple instances of Windows installed on the source machine. When the **<failOnMultipleWinDir>** element isn't present, the default behavior is that the migration does not fail.
|
||||
|
||||
Syntax: <failOnMultipleWinDir>1</failOnMultipleWinDir> or Syntax: <failOnMultipleWinDir>0</failOnMultipleWinDir>
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ You can modify the behavior of a basic User State Migration Tool (USMT)10.0 migr
|
||||
|
||||
This topic provides an overview of the default and custom migration XML files and includes guidelines for creating and editing a customized version of the MigDocs.xml file. The MigDocs.xml file uses the new **GenerateDocPatterns** function available in USMT to automatically find user documents on a source computer.
|
||||
|
||||
## In This Topic
|
||||
## In This topic
|
||||
|
||||
|
||||
[Overview of the Config.xml file](#bkmk-config)
|
||||
@ -435,7 +435,7 @@ In the examples below, the source computer has a .txt file called "new text docu
|
||||
|
||||
|
||||
|
||||
To exclude the new text document.txt file as well as any .txt files in “new folder”, you can do the following:
|
||||
To exclude the new text document.txt file as well as any .txt files in "new folder", you can do the following:
|
||||
|
||||
**Example 1: Exclude all .txt files in a folder**
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: USMT Best Practices (Windows 10)
|
||||
description: Learn about general and security-related best practices when using User State Migration Tool (USMT) 10.0.
|
||||
description: This article discusses general and security-related best practices when using User State Migration Tool (USMT) 10.0.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.assetid: e3cb1e78-4230-4eae-b179-e6e9160542d2
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -21,7 +21,7 @@ You use the User State Migration Tool (USMT) 10.0 when hardware and/or operatin
|
||||
|
||||
One common scenario when only the operating system, and not the hardware, is being upgraded is referred to as *PC refresh*. A second common scenario is known as *PC replacement*, where one piece of hardware is being replaced, typically by newer hardware and a newer operating system.
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
[PC Refresh](#bkmk-pcrefresh)
|
||||
@ -59,7 +59,7 @@ A company has just received funds to update the operating system on all of its c
|
||||
|
||||
1. On each computer, the administrator boots the machine into WinPE and runs the ScanState command-line tool, specifying the **/hardlink /nocompress** command-line options. ScanState saves the user state to a hard-link migration store on each computer, improving performance by minimizing network traffic as well as minimizing migration failures on computers with very limited space available on the hard drive.
|
||||
|
||||
2. On each computer, the administrator installs the company’s standard operating environment (SOE) which includes Windows 10 and other company applications.
|
||||
2. On each computer, the administrator installs the company's standard operating environment (SOE) which includes Windows 10 and other company applications.
|
||||
|
||||
3. The administrator runs the LoadState command-line tool on each computer. LoadState restores each user state back to each computer.
|
||||
|
||||
@ -89,7 +89,7 @@ A company has decided to update the operating system on all of its computers to
|
||||
|
||||
1. The administrator clean installs Windows 10 on each computer, making sure that the Windows.old directory is created by installing Windows 10 without formatting or repartitioning and by selecting a partition that contains the previous version of Windows.
|
||||
|
||||
2. On each computer, the administrator installs the company’s SOE which includes company applications.
|
||||
2. On each computer, the administrator installs the company's SOE which includes company applications.
|
||||
|
||||
3. The administrator runs the ScanState and LoadState command-line tools successively on each computer while specifying the **/hardlink /nocompress** command-line options.
|
||||
|
||||
@ -118,13 +118,13 @@ A company is allocating 20 new computers to users in the accounting department.
|
||||
|
||||
A company receives 50 new laptops for their managers and needs to reallocate 50 older laptops to new employees. In this scenario, an administrator runs the ScanState tool from the cmd prompt on each computer to collect the user states and save them to a server in a compressed migration store.
|
||||
|
||||
1. The administrator runs the ScanState tool on each of the manager’s old laptops, and saves each user state to a server.
|
||||
1. The administrator runs the ScanState tool on each of the manager's old laptops, and saves each user state to a server.
|
||||
|
||||
2. On the new laptops, the administrator installs the company's SOE, which includes Windows 10 and other company applications.
|
||||
|
||||
3. The administrator runs the LoadState tool on the new laptops to migrate the managers’ user states to the appropriate computer. The new laptops are now ready for the managers to use.
|
||||
3. The administrator runs the LoadState tool on the new laptops to migrate the managers' user states to the appropriate computer. The new laptops are now ready for the managers to use.
|
||||
|
||||
4. On the old computers, the administrator installs the company’s SOE, which includes Windows 10, Microsoft Office, and other company applications. The old computers are now ready for the new employees to use.
|
||||
4. On the old computers, the administrator installs the company's SOE, which includes Windows 10, Microsoft Office, and other company applications. The old computers are now ready for the new employees to use.
|
||||
|
||||
### <a href="" id="bkmk-threepcreplace"></a>Scenario Three: Managed network migration
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ To exclude a component from the Config.xml file, set the **migrate** value to **
|
||||
|
||||
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
In USMT there are new migration policies that can be configured in the Config.xml file. For example, you can configure additional **<ErrorControl>**, **<ProfileControl>**, and **<HardLinkStoreControl>** options. The following elements and parameters are for use in the Config.xml file only.
|
||||
|
||||
@ -31,7 +31,7 @@ When you include, exclude, and reroute files and settings, it is important to kn
|
||||
|
||||
- **You can use the <unconditionalExclude> element to globally exclude data.** This element excludes objects, regardless of any other <include> rules that are in the .xml files. For example, you can use the <unconditionalExclude> element to exclude all MP3 files on the computer or to exclude all files from C:\\UserData.
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
**General**
|
||||
|
||||
@ -19,7 +19,7 @@ ms.topic: article
|
||||
|
||||
A *hard-link migration store* enables you to perform an in-place migration where all user state is maintained on the computer while the old operating system is removed and the new operating system is installed; this is why it is best suited for the computer-refresh scenario. Use of a hard-link migration store for a computer-refresh scenario drastically improves migration performance and significantly reduces hard-disk utilization, reduces deployment costs and enables entirely new migration scenarios.
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
[When to Use a Hard-Link Migration](#bkmk-when)
|
||||
@ -75,7 +75,7 @@ A hard link can only be created for a file on the same volume. If you copy a har
|
||||
|
||||
For more information about hard links, please see [Hard Links and Junctions](https://go.microsoft.com/fwlink/p/?LinkId=132934)
|
||||
|
||||
In most aspects, a hard-link migration store is identical to an uncompressed migration store. It is located where specified by the Scanstate command-line tool and you can view the contents of the store by using Windows® Explorer. Once created, it can be deleted or copied to another location without changing user state. Restoring a hard-link migration store is similar to restoring any other migration store; however, as with creating the store, the same hard-link functionality is used to keep files in-place.
|
||||
In most aspects, a hard-link migration store is identical to an uncompressed migration store. It is located where specified by the Scanstate command-line tool and you can view the contents of the store by using Windows® Explorer. Once created, it can be deleted or copied to another location without changing user state. Restoring a hard-link migration store is similar to restoring any other migration store; however, as with creating the store, the same hard-link functionality is used to keep files in-place.
|
||||
|
||||
As a best practice, we recommend that you delete the hard-link migration store after you confirm that the Loadstate tool has successfully migrated the files. Since Loadstate has created new paths to the files on your new installation of a Windows operating system, deleting the hard links in the migration store will only delete one path to the files and will not delete the actual files or the paths to them from your new operating system.
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ ms.localizationpriority: medium
|
||||
|
||||
It is important to carefully consider how you plan to migrate users. By default, all users are migrated by User State Migration Tool (USMT) 5.0. You must specify which users to include by using the command line. You cannot specify users in the .xml files. For instructions on how to migrate users, see [Migrate User Accounts](usmt-migrate-user-accounts.md).
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
- [Migrating Local Accounts](#bkmk-8)
|
||||
- [Migrating Domain Accounts](#bkmk-9)
|
||||
|
||||
@ -17,9 +17,9 @@ ms.topic: article
|
||||
# LoadState Syntax
|
||||
|
||||
|
||||
This topic discusses the **LoadState** command syntax and options.
|
||||
This topic discusses the **LoadState** command syntax and options available with it.
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
[Before You Begin](#before)
|
||||
@ -462,7 +462,7 @@ You can use the **/uel**, **/ue** and **/ui** options together to migrate only t
|
||||
|
||||
**The /ui option has precedence over the /ue and /uel options.** If a user is specified to be included using the **/ui** option, and also specified to be excluded using either the **/ue** or **/uel** options, the user will be included in the migration. For example, if you specify `/ui:contoso\* /ue:contoso\user1`, then User1 will be migrated, because the **/ui** option takes precedence over the **/ue** option.
|
||||
|
||||
**The /uel option takes precedence over the /ue option.** If a user has logged on within the specified time period set by the **/uel** option, that user’s profile will be migrated even if they are excluded by using the **/ue** option. For example, if you specify `/ue:contoso\user1 /uel:14`, the User1 will be migrated if they have logged on to the computer within the last 14 days.
|
||||
**The /uel option takes precedence over the /ue option.** If a user has logged on within the specified time period set by the **/uel** option, that user's profile will be migrated even if they are excluded by using the **/ue** option. For example, if you specify `/ue:contoso\user1 /uel:14`, the User1 will be migrated if they have logged on to the computer within the last 14 days.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
|
||||
@ -251,7 +251,7 @@ The following examples describe common scenarios in which you can use the diagno
|
||||
|
||||
**Why is this file not migrating when I authored an "include" rule for it?**
|
||||
|
||||
Let’s imagine that we have the following directory structure and that we want the “data” directory to be included in the migration along with the “New Text Document.txt” file in the “New Folder.” The directory of **C:\\data** contains:
|
||||
Let's imagine that we have the following directory structure and that we want the "data" directory to be included in the migration along with the "New Text Document.txt" file in the "New Folder." The directory of **C:\\data** contains:
|
||||
|
||||
```
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
@ -293,7 +293,7 @@ To migrate these files you author the following migration XML:
|
||||
</migration>
|
||||
```
|
||||
|
||||
However, upon testing the migration you notice that the “New Text Document.txt” file isn’t included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable MIG\_ENABLE\_DIAG set such that the diagnostic log is generated. Upon searching the diagnostic log for the component “DATA1”, the following XML section is discovered:
|
||||
However, upon testing the migration you notice that the "New Text Document.txt" file isn't included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable MIG\_ENABLE\_DIAG set such that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered:
|
||||
|
||||
``` xml
|
||||
<MigUnitList>
|
||||
@ -312,7 +312,7 @@ However, upon testing the migration you notice that the “New Text Document.txt
|
||||
</Perform>
|
||||
```
|
||||
|
||||
Analysis of this XML section reveals the migunit that was created when the migration rule was processed. The <Perform> section details the actual files that were scheduled for gathering and the result of the gathering operation. The “New Text Document.txt” file doesn’t appear in this section, which confirms that the migration rule was not correctly authored.
|
||||
Analysis of this XML section reveals the migunit that was created when the migration rule was processed. The <Perform> section details the actual files that were scheduled for gathering and the result of the gathering operation. The "New Text Document.txt" file doesn't appear in this section, which confirms that the migration rule was not correctly authored.
|
||||
|
||||
An analysis of the XML elements reference topic reveals that the <pattern> tag needs to be modified as follows:
|
||||
|
||||
@ -345,7 +345,7 @@ This diagnostic log confirms that the modified <pattern> value enables the
|
||||
|
||||
**Why is this file migrating when I authored an exclude rule excluding it?**
|
||||
|
||||
In this scenario, you have the following directory structure and you want all files in the “data” directory to migrate, except for text files. The **C:\\Data** folder contains:
|
||||
In this scenario, you have the following directory structure and you want all files in the "data" directory to migrate, except for text files. The **C:\\Data** folder contains:
|
||||
|
||||
```
|
||||
Directory of C:\Data
|
||||
@ -395,7 +395,7 @@ You author the following migration XML:
|
||||
</component>
|
||||
```
|
||||
|
||||
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable MIG\_ENABLE\_DIAG set so that the diagnostic log is generated. Upon searching the diagnostic log for the component “DATA1”, the following XML section is discovered:
|
||||
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable MIG\_ENABLE\_DIAG set so that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered:
|
||||
|
||||
``` xml
|
||||
<MigUnitList>
|
||||
|
||||
@ -51,11 +51,3 @@ There are some scenarios in which the use of USMT is not recommended. These incl
|
||||
|
||||
## Related topics
|
||||
- [User State Migration Tool (USMT) Technical Reference](usmt-technical-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# User State Migration Tool (USMT) Technical Reference
|
||||
@ -37,12 +38,12 @@ USMT also includes a set of three modifiable .xml files:
|
||||
|
||||
Additionally, you can create custom .xml files to support your migration needs. You can also create a Config.xml file to specify files or settings to exclude from the migration.
|
||||
|
||||
USMT tools can be used on several versions of Windows operating systems, for more information, see [USMT Requirements](usmt-requirements.md). For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](https://go.microsoft.com/fwlink/p/?LinkId=246564).
|
||||
USMT tools can be used on several versions of Windows operating systems, for more information, see [USMT Requirements](usmt-requirements.md). For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User's Guide](https://go.microsoft.com/fwlink/p/?LinkId=246564).
|
||||
|
||||
## In This Section
|
||||
## In this section
|
||||
|Topic |Description|
|
||||
|------|-----------|
|
||||
|[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)|Describes what’s new in USMT, how to get started with USMT, and the benefits and limitations of using USMT.|
|
||||
|[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)|Describes what's new in USMT, how to get started with USMT, and the benefits and limitations of using USMT.|
|
||||
|[User State Migration Tool (USMT) How-to topics](usmt-how-to.md)|Includes step-by-step instructions for using USMT, as well as how-to topics for conducting tasks in USMT.|
|
||||
|[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)|Provides answers to frequently asked questions and common issues in USMT, as well as a reference for return codes used in USMT.|
|
||||
|[User State Migration Toolkit (USMT) Reference](usmt-reference.md)|Includes reference information for migration planning, migration best practices, command-line syntax, using XML, and requirements for using USMT.|
|
||||
|
||||
@ -43,12 +43,3 @@ For testing purposes, you can create an uncompressed store using the **/hardlink
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
|
||||
[Log Files](usmt-log-files.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -17,12 +17,10 @@ ms.topic: article
|
||||
# XML Elements Library
|
||||
|
||||
|
||||
## Overview
|
||||
|
||||
|
||||
This topic describes the XML elements and helper functions that you can employ to author migration .xml files to use with User State Migration Tool (USMT). It is assumed that you understand the basics of XML. .
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
In addition to XML elements and helper functions, this topic describes how to specify encoded locations and locations patterns, functions that are for internal USMT use only, and the version tags that you can use with helper functions.
|
||||
@ -326,7 +324,7 @@ Syntax:
|
||||
## <a href="" id="component"></a><component>
|
||||
|
||||
|
||||
The <component> element is required in a custom .xml file. This element defines the most basic construct of a migration .xml file. For example, in the MigApp.xml file, "Microsoft® Office 2003" is a component that contains another component, "Microsoft Office Access® 2003". You can use the child elements to define the component.
|
||||
The <component> element is required in a custom .xml file. This element defines the most basic construct of a migration .xml file. For example, in the MigApp.xml file, "Microsoft® Office 2003" is a component that contains another component, "Microsoft Office Access® 2003". You can use the child elements to define the component.
|
||||
|
||||
A component can be nested inside another component; that is, the <component> element can be a child of the <role> element within the <component> element in two cases: 1) when the parent <component> element is a container or 2) if the child <component> element has the same role as the parent <component> element.
|
||||
|
||||
@ -365,7 +363,7 @@ hidden="Yes|No">
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>You can use the following to group settings, and define the type of the component.</p>
|
||||
<ul>
|
||||
<li><p><strong>System:</strong> Operating system settings. All Windows® components are defined by this type.</p>
|
||||
<li><p><strong>System:</strong> Operating system settings. All Windows® components are defined by this type.</p>
|
||||
<p>When type="System" and defaultSupported="FALSE" the settings will not migrate unless there is an equivalent component in the .xml files that is specified on the LoadState command line. For example, the default MigSys.xml file contains components with type="System" and defaultSupported="FALSE". If you specify this file on the ScanState command line, you must also specify the file on the LoadState command line for the settings to migrate. This is because the LoadState tool must detect an equivalent component. That is, the component must have the same migration urlid of the .xml file and an identical display name. Otherwise, the LoadState tool will not migrate those settings from the store. This is helpful when the source computer is running Windows XP, and you are migrating to both Windows Vista and Windows XP because you can use the same store for both destination computers.</p></li>
|
||||
<li><p><strong>Application:</strong> Settings for an application.</p></li>
|
||||
<li><p><strong>Device:</strong> Settings for a device.</p></li>
|
||||
@ -556,7 +554,7 @@ For example:
|
||||
<tr class="odd">
|
||||
<td align="left"><p><em>OSType</em></p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Can be <strong>9x</strong> or <strong>NT</strong>. If <em>OSType</em> does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and <em>OSType</em> is “9x”, the result will be FALSE.</p></td>
|
||||
<td align="left"><p>Can be <strong>9x</strong> or <strong>NT</strong>. If <em>OSType</em> does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and <em>OSType</em> is "9x", the result will be FALSE.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><em>OSVersion</em></p></td>
|
||||
@ -598,7 +596,7 @@ For example:
|
||||
<tr class="odd">
|
||||
<td align="left"><p><em>OSType</em></p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Can be <strong>9x</strong> or <strong>NT</strong>. If <em>OSType</em> does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and <em>OSType</em> is “9x” the result will be FALSE.</p></td>
|
||||
<td align="left"><p>Can be <strong>9x</strong> or <strong>NT</strong>. If <em>OSType</em> does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and <em>OSType</em> is "9x" the result will be FALSE.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><em>OSVersion</em></p></td>
|
||||
@ -3131,8 +3129,8 @@ This filter helper function can be used to filter the migration of files based o
|
||||
<tr class="odd">
|
||||
<td align="left"><p>valueToCompare</p></td>
|
||||
<td align="left"><p>The value we are comparing. For example:</p>
|
||||
<p>Date: “2008/05/15-2005/05/17”, “2008/05/15”</p>
|
||||
<p>Size: A numeral with B, KB, MB, or GB at the end. “5GB”, “1KB-1MB”</p></td>
|
||||
<p>Date: "2008/05/15-2005/05/17", "2008/05/15"</p>
|
||||
<p>Size: A numeral with B, KB, MB, or GB at the end. "5GB", "1KB-1MB"</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -3464,8 +3462,8 @@ Syntax:
|
||||
</ul>
|
||||
<p>You can either:</p>
|
||||
<ol>
|
||||
<li><p>Specify up to three <role> elements within a <component> — one “Binaries” role element, one “Settings” role element and one “Data” role element. These parameters do not change the migration behavior — their only purpose is to help you categorize the settings that you are migrating. You can nest these <role> elements, but each nested element must be of the same role parameter.</p></li>
|
||||
<li><p>Specify one “Container” <role> element within a <component> element. In this case, you cannot specify any child <rules> elements, only other <component> elements. And each child <component> element must have the same type as that of parent <component> element. For example:</p></li>
|
||||
<li><p>Specify up to three <role> elements within a <component> — one "Binaries" role element, one "Settings" role element and one "Data" role element. These parameters do not change the migration behavior — their only purpose is to help you categorize the settings that you are migrating. You can nest these <role> elements, but each nested element must be of the same role parameter.</p></li>
|
||||
<li><p>Specify one "Container" <role> element within a <component> element. In this case, you cannot specify any child <rules> elements, only other <component> elements. And each child <component> element must have the same type as that of parent <component> element. For example:</p></li>
|
||||
</ol>
|
||||
<pre class="syntax" space="preserve"><code><component context="UserAndSystem" type="Application">
|
||||
<displayName _locID="migapp.msoffice2003">Microsoft Office 2003</displayName>
|
||||
@ -3846,7 +3844,7 @@ See the last component in the MigUser.xml file for an example of this element.
|
||||
~~~
|
||||
**Example:**
|
||||
|
||||
If GenerateUserPattens('File','%userprofile% \[\*.doc\]','FALSE') is called while USMT is processing user A, then this function will only generate patterns for users B and C. You can use this helper function to build complex rules. For example, to migrate all .doc files from the source computer — but if user X is not migrated, then do not migrate any of the .doc files from user X’s profile.
|
||||
If GenerateUserPattens('File','%userprofile% \[\*.doc\]','FALSE') is called while USMT is processing user A, then this function will only generate patterns for users B and C. You can use this helper function to build complex rules. For example, to migrate all .doc files from the source computer — but if user X is not migrated, then do not migrate any of the .doc files from user X's profile.
|
||||
|
||||
The following is example code for this scenario. The first <rules> element migrates all.doc files on the source computer with the exception of those inside C:\\Documents and Settings. The second <rules> elements will migrate all .doc files from C:\\Documents and Settings with the exception of the .doc files in the profiles of the other users. Because the second <rules> element will be processed in each migrated user context, the end result will be the desired behavior. The end result is the one we expected.
|
||||
|
||||
@ -4103,12 +4101,12 @@ Syntax:
|
||||
<tr class="odd">
|
||||
<td align="left"><p>name</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p><em>ID</em> is a string value that is the name used to reference the environment variable. We recommend that <em>ID</em> start with the component’s name to avoid namespace collisions. For example, if your component’s name is MyComponent, and you want a variable that is your component’s install path, you could specify <code>MyComponent.InstallPath</code>.</p></td>
|
||||
<td align="left"><p><em>ID</em> is a string value that is the name used to reference the environment variable. We recommend that <em>ID</em> start with the component's name to avoid namespace collisions. For example, if your component's name is MyComponent, and you want a variable that is your component's install path, you could specify <code>MyComponent.InstallPath</code>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>remap</p></td>
|
||||
<td align="left"><p>No, default = FALSE</p></td>
|
||||
<td align="left"><p>Specifies whether to evaluate this environment variable as a remapping environment variable. Objects that are located in a path that is underneath this environment variable’s value are automatically moved to where the environment variable points on the destination computer.</p></td>
|
||||
<td align="left"><p>Specifies whether to evaluate this environment variable as a remapping environment variable. Objects that are located in a path that is underneath this environment variable's value are automatically moved to where the environment variable points on the destination computer.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -4227,27 +4225,27 @@ The following functions are for internal USMT use only. Do not use them in an .x
|
||||
|
||||
You can use the following version tags with various helper functions:
|
||||
|
||||
- “CompanyName”
|
||||
- "CompanyName"
|
||||
|
||||
- “FileDescription”
|
||||
- "FileDescription"
|
||||
|
||||
- “FileVersion”
|
||||
- "FileVersion"
|
||||
|
||||
- “InternalName”
|
||||
- "InternalName"
|
||||
|
||||
- “LegalCopyright”
|
||||
- "LegalCopyright"
|
||||
|
||||
- “OriginalFilename”
|
||||
- "OriginalFilename"
|
||||
|
||||
- “ProductName”
|
||||
- "ProductName"
|
||||
|
||||
- “ProductVersion”
|
||||
- "ProductVersion"
|
||||
|
||||
The following version tags contain values that can be compared:
|
||||
|
||||
- “FileVersion”
|
||||
- "FileVersion"
|
||||
|
||||
- “ProductVersion”
|
||||
- "ProductVersion"
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -7,6 +7,7 @@ ms.author: greglin
|
||||
author: greg-lindsay
|
||||
description: Learn how to configure virtual machines (VMs) to enable Windows 10 Subscription Activation in a Windows Virtual Desktop Access (VDA) scenario.
|
||||
keywords: upgrade, update, task sequence, deploy
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Activate using Active Directory-based activation (Windows 10)
|
||||
description: Active Directory-based activation is implemented as a role service that relies on AD DS to store activation objects.
|
||||
description: Learn how active directory-based activation is implemented as a role service that relies on AD DS to store activation objects.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.assetid: 08cce6b7-7b5b-42cf-b100-66c363a846af
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -24,8 +24,8 @@ To enable the Volume Activation Management Tool (VAMT) to function correctly, ce
|
||||
|
||||
Organizations where the VAMT will be widely used may benefit from making these changes inside the master image for Windows.
|
||||
|
||||
> [IMPORTANT]
|
||||
> This procedure only applies to clients running Windows Vista or later. For clients running Windows XP Service Pack 1, see [Connecting Through Windows Firewall](https://docs.microsoft.com/windows/win32/wmisdk/connecting-to-wmi-remotely-with-vbscript).
|
||||
> [IMPORTANT]
|
||||
> This procedure only applies to clients running Windows Vista or later. For clients running Windows XP Service Pack 1, see [Connecting Through Windows Firewall](https://docs.microsoft.com/windows/win32/wmisdk/connecting-to-wmi-remotely-with-vbscript).
|
||||
|
||||
## Configuring the Windows Firewall to allow VAMT access
|
||||
|
||||
|
||||
@ -13,13 +13,14 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Volume Activation Management Tool (VAMT) Technical Reference
|
||||
|
||||
The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office, and select other Microsoft products volume and retail-activation process.
|
||||
The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office, and select other Microsoft products volume and retail-activation process.
|
||||
VAMT can manage volume activation using Multiple Activation Keys (MAKs) or the Windows Key Management Service (KMS). VAMT is a standard Microsoft Management Console (MMC) snap-in that requires the Microsoft Management Console (MMC) 3.0. VAMT can be installed on any computer that has one of the following Windows operating systems:
|
||||
- Windows® 7 or above
|
||||
- Windows® 7 or above
|
||||
- Windows Server 2008 R2 or above
|
||||
|
||||
|
||||
@ -28,7 +29,7 @@ VAMT is designed to manage volume activation for: Windows 7, Windows 8, Window
|
||||
|
||||
VAMT is only available in an EN-US (x86) package.
|
||||
|
||||
## In this Section
|
||||
## In this section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|
||||
@ -26,5 +26,5 @@ Learn about the tools available to deploy Windows 10.
|
||||
|[Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) |This guide describes how to configure a PXE server to load Windows PE by booting a client computer from the network. |
|
||||
|[Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) |The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. |
|
||||
|[Deploy Windows To Go in your organization](deploy-windows-to-go.md) |This topic helps you to deploy Windows To Go in your organization. Before you begin deployment, make sure that you have reviewed the topics [Windows To Go: feature overview](planning/windows-to-go-overview.md) and [Prepare your organization for Windows To Go](planning/prepare-your-organization-for-windows-to-go.md) to ensure that you have the correct hardware and are prepared to complete the deployment. You can then use the steps in this topic to start your Windows To Go deployment. |
|
||||
|[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation/volume-activation-management-tool.md) |The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office, and select other Microsoft products volume and retail-activation process. |
|
||||
|[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation/volume-activation-management-tool.md) |The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office, and select other Microsoft products volume and retail-activation process. |
|
||||
|[User State Migration Tool (USMT) Technical Reference](usmt/usmt-technical-reference.md) |The User State Migration Tool (USMT) 10.0 is included with the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10. USMT provides a highly customizable user-profile migration experience for IT professionals |
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user