mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into rs3
# Conflicts: # windows/configuration/change-history-for-configure-windows-10.md
This commit is contained in:
jdeckerMS
commit
33f33f008f
@ -100,6 +100,6 @@
|
||||
#### [Viewing App-V Server Publishing Metadata](app-v/appv-viewing-appv-server-publishing-metadata.md)
|
||||
#### [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md)
|
||||
## [Service Host process refactoring](svchost-service-refactoring.md)
|
||||
## [Per User services in Windows](per-user-services-in-windows.md)
|
||||
## [Per-user services in Windows](per-user-services-in-windows.md)
|
||||
## [Deploy app upgrades on Windows 10 Mobile](deploy-app-upgrades-windows-10-mobile.md)
|
||||
## [Change history for Application management](change-history-for-application-management.md)
|
||||
|
||||
@ -14,6 +14,11 @@ author: jdeckerms
|
||||
|
||||
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
||||
|
||||
## September 2017
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
| [Per-user services in Windows](per-user-services-in-windows.md) | New |
|
||||
|
||||
## July 2017
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Per-user services in Windows 10 and Windows Server 2016
|
||||
title: Per-user services in Windows 10 and Windows Server
|
||||
description: Learn about per-user services introduced in Windows 10.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -10,7 +10,9 @@ author: lizap
|
||||
ms.date: 08/14/2017
|
||||
---
|
||||
|
||||
# Per-user services in Windows 10 and Windows Server 2016
|
||||
# Per-user services in Windows 10 and Windows Server
|
||||
|
||||
> Applies to: Windows 10, Windows Server
|
||||
|
||||
Per-user services are services that are created when a user signs into Windows or Windows Server and are stopped and deleted when that user signs out. These services run in the security context of the user account - this provides better resource management than the previous approach of running these kinds of services in Explorer, associated with a preconfigured account, or as tasks.
|
||||
|
||||
@ -29,6 +31,7 @@ Beginning with Windows 10, version 1709 and Windows Server, version 1709, there
|
||||
|
||||
|
||||
Use the following information to understand per-user services, change the template service Startup Type, and manage per-user services through Group Policy and security templates.
|
||||
For more information about disabling system services for Windows Server, see [Guidance on disabling system services on Windows Server with Desktop Experience](https://docs.microsoft.com/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server).
|
||||
|
||||
## Per-user services
|
||||
|
||||
|
||||
@ -1043,6 +1043,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
<li>Education/DefaultPrinterName</li>
|
||||
<li>Education/PreventAddingNewPrinters</li>
|
||||
<li>Education/PrinterNames</li>
|
||||
<li>Search/AllowCloudSearch</li>
|
||||
<li>Security/ClearTPMIfNotReady</li>
|
||||
<li>System/LimitEnhancedDiagnosticDataWindowsAnalytics</li>
|
||||
<li>Update/AllowAutoWindowsUpdateDownloadOverMeteredNetwork</li>
|
||||
|
||||
@ -2383,6 +2383,9 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
### Search policies
|
||||
|
||||
<dl>
|
||||
<dd>
|
||||
<a href="./policy-csp-search.md#search-allowcloudsearch" id="search-allowcloudsearch">Search/AllowCloudSearch</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-search.md#search-allowindexingencryptedstoresoritems" id="search-allowindexingencryptedstoresoritems">Search/AllowIndexingEncryptedStoresOrItems</a>
|
||||
</dd>
|
||||
|
||||
@ -19,6 +19,42 @@ ms.date: 08/30/2017
|
||||
|
||||
## Search policies
|
||||
|
||||
<!--StartPolicy-->
|
||||
<a href="" id="search-allowcloudsearch"></a>**Search/AllowCloudSearch**
|
||||
|
||||
<!--StartSKU-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
<th>Mobile Enterprise</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>3</sup></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<!--EndSKU-->
|
||||
<!--StartDescription-->
|
||||
<p style="margin-left: 20px">Added in Windows 10, version 1709. Allow search and Cortana to search cloud sources like OneDrive and SharePoint. This policy allows corporate administrators to control whether employees can turn off/on the search of these cloud sources. The default policy value is to allow employees access to the setting that controls search of cloud sources.
|
||||
|
||||
<p style="margin-left: 20px">The following list shows the supported values:
|
||||
|
||||
- 0 – Not allowed.
|
||||
- 1 (default) – Allowed.
|
||||
|
||||
<!--EndDescription-->
|
||||
<!--EndPolicy-->
|
||||
<!--StartPolicy-->
|
||||
<a href="" id="search-allowindexingencryptedstoresoritems"></a>**Search/AllowIndexingEncryptedStoresOrItems**
|
||||
|
||||
|
||||
@ -14,10 +14,18 @@ author: jdeckerms
|
||||
|
||||
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
||||
|
||||
|
||||
## RELEASE: Windows 10, version 1709
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1709 (also known as the Fall Creators Update).
|
||||
|
||||
## September 2017
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md) | Added that Windows Spotlight can be managed by the Experience/AllowWindowsSpotlight MDM policy.
|
||||
|
||||
|
||||
## August 2017
|
||||
|
||||
New or changed topic | Description
|
||||
|
||||
@ -113,7 +113,7 @@ See the following table for a summary of the management settings for Windows 10
|
||||
| [21. Wi-Fi Sense](#bkmk-wifisense) |  |  | |  | |
|
||||
| [22. Windows Defender](#bkmk-defender) | |  |  |  | |
|
||||
| [23. Windows Media Player](#bkmk-wmp) |  | | | |  |
|
||||
| [24. Windows spotlight](#bkmk-spotlight) |  |  | |  | |
|
||||
| [24. Windows Spotlight](#bkmk-spotlight) |  |  |  |  | |
|
||||
| [25. Microsoft Store](#bkmk-windowsstore) | |  | |  | |
|
||||
| [26. Windows Update Delivery Optimization](#bkmk-updates) |  |  |  |  | |
|
||||
| [27. Windows Update](#bkmk-wu) |  |  |  | | |
|
||||
@ -558,7 +558,7 @@ The following Microsoft Edge MDM policies are available in the [Policy CSP](http
|
||||
| Browser/FirstRunURL | Choose the home page for Microsoft Edge on Windows Mobile 10. <br /> Default: blank |
|
||||
|
||||
|
||||
For a complete list of the Microsoft Edge policies, see [Available policies for Microsoft Edge](http://technet.microsoft.com/library/mt270204.aspx).
|
||||
For a complete list of the Microsoft Edge policies, see [Available policies for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/available-policies).
|
||||
|
||||
### <a href="" id="bkmk-ncsi"></a>13. Network Connection Status Indicator
|
||||
|
||||
@ -1636,7 +1636,7 @@ You can stop sending file samples back to Microsoft.
|
||||
|
||||
-or-
|
||||
|
||||
- For Windows 10 only, apply the Defender/SubmitSamplesConsent MDM policy from the [Defender CSP](http://msdn.microsoft.com/library/windows/hardware/dn904962.aspx), where:
|
||||
- For Windows 10 only, apply the Defender/SubmitSamplesConsent MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender), where:
|
||||
|
||||
- **0**. Always prompt.
|
||||
|
||||
@ -1682,9 +1682,9 @@ To remove Windows Media Player on Windows Server 2016:
|
||||
|
||||
- Run the following DISM command from an elevated command prompt: **dism /online /Disable-Feature /FeatureName:WindowsMediaPlayer**
|
||||
|
||||
### <a href="" id="bkmk-spotlight"></a>24. Windows spotlight
|
||||
### <a href="" id="bkmk-spotlight"></a>24. Windows Spotlight
|
||||
|
||||
Windows spotlight provides features such as different background images and text on the lock screen, suggested apps, Microsoft account notifications, and Windows tips. You can control it by using the user interface or through Group Policy.
|
||||
Windows Spotlight provides features such as different background images and text on the lock screen, suggested apps, Microsoft account notifications, and Windows tips. You can control it by using the user interface, MDM policy, or through Group Policy.
|
||||
|
||||
If you're running Windows 10, version 1607 or later, you only need to enable the following Group Policy:
|
||||
|
||||
@ -1695,6 +1695,10 @@ If you're running Windows 10, version 1607 or later, you only need to enable the
|
||||
|
||||
-or-
|
||||
|
||||
- For Windows 10 only, apply the Experience/AllowWindowsSpotlight MDM policy from the [Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-experience), with a value of 0 (zero).
|
||||
|
||||
-or-
|
||||
|
||||
- Create a new REG\_DWORD registry setting in **HKEY\_CURRENT\_USER\\SOFTWARE\\Policies\\Microsoft\\Windows\\CloudContent!DisableWindowsSpotlightFeatures**, with a value of 1 (one).
|
||||
|
||||
If you're not running Windows 10, version 1607 or later, you can use the other options in this section.
|
||||
@ -1847,7 +1851,7 @@ You can turn off automatic updates by doing one of the following. This is not re
|
||||
|
||||
-or-
|
||||
|
||||
- For Windows 10 only, apply the Update/AllowAutoUpdate MDM policy from the [Policy CSP](http://msdn.microsoft.com/library/windows/hardware/dn904962.aspx), where:
|
||||
- For Windows 10 only, apply the Update/AllowAutoUpdate MDM policy from the [Policy CSP](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update), where:
|
||||
|
||||
- **0**. Notify the user before downloading the update.
|
||||
|
||||
|
||||
@ -15,8 +15,18 @@ author: greg-lindsay
|
||||
|
||||
This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md) or [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD).
|
||||
|
||||
>Note: Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.
|
||||
>Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.
|
||||
>Note: Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.<BR>
|
||||
>Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.<BR>
|
||||
|
||||
## Enabling Subscription Activation with an existing EA
|
||||
|
||||
If you are an EA customer with an existing Office 365 tenant, use the following steps to enable Windows 10 Subscription licenses on your existing tenant:
|
||||
|
||||
1. Work with your reseller to place an order for $0 SKU. There are two SKUs available, depending on their current Windows Enterprise SA license:<BR>
|
||||
a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3<BR>
|
||||
b. **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5<BR>
|
||||
2. After placing an order, the OLS admin on the agreement will receive a service activation email, indicating their subscription licenses have been provisioned on the tenant.
|
||||
3. The admin can now assign subscription licenses to users.
|
||||
|
||||
Also in this article:
|
||||
- [Explore the upgrade experience](#explore-the-upgrade-experience): How to upgrade devices using the deployed licenses.
|
||||
@ -196,4 +206,3 @@ Devices must be running Windows 10 Pro, version 1703, and be Azure Active Direct
|
||||
A popup window will display the Windows 10 version number and detailed OS build information.
|
||||
|
||||
If a device is running a previous version of Windows 10 Pro (for example, version 1511), it will not be upgraded to Windows 10 Enterprise when a user signs in, even if the user has been assigned a subscription in the CSP portal.
|
||||
|
||||
|
||||
@ -5,6 +5,7 @@ ms.assetid: 5a37e390-8617-4768-9eee-50397fbbb2e1
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.date: 09/07/2017
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
@ -28,6 +29,8 @@ The following sections discuss common issues that you might see when you run the
|
||||
|
||||
[Hard Link Migration Problems](#bkmk-hardlink)
|
||||
|
||||
[USMT does not migrate the Start layout](#usmt-does-not-migrate-the-start-layout)
|
||||
|
||||
## General Guidelines for Identifying Migration Problems
|
||||
|
||||
|
||||
@ -222,6 +225,26 @@ There are three typical causes for this issue.
|
||||
|
||||
**Resolution:** To migrate PST files that are not linked to Outlook profiles, you must create a separate migration rule to capture these files.
|
||||
|
||||
### USMT does not migrate the Start layout
|
||||
|
||||
**Description:** You are using USMT to migrate profiles from one installation of Windows 10 to another installation of Windows 10 on different hardware. After migration, the user signs in on the new device and does not have the Start menu layout they had previously configured.
|
||||
|
||||
**Cause:** A code change in the Start Menu with Windows 10 version 1607 is incompatible with this USMT function.
|
||||
|
||||
**Resolution:** The following workaround is available:
|
||||
|
||||
1. With the user signed in, back up the Start layout using the following Windows PowerShell command. You can specify a different path if desired:
|
||||
|
||||
```
|
||||
Export-StartLayout -Path "C:\Layout\user1.xml"
|
||||
```
|
||||
2. Migrate the user's profile with USMT.
|
||||
3. Before the user signs in on the new device, import the Start layout using the following Windows PowerShell command:
|
||||
|
||||
```
|
||||
Import-StartLayout –LayoutPath "C:\Layout\user1.xml" –MountPath %systemdrive%
|
||||
```
|
||||
|
||||
## <a href="" id="bkmk-offline"></a>Offline Migration Problems
|
||||
|
||||
|
||||
@ -286,6 +309,10 @@ USMTutils /rd <storedir>
|
||||
|
||||
You should also reboot the machine.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What Does USMT Migrate (Windows 10)
|
||||
description: What Does USMT Migrate
|
||||
title: What does USMT migrate (Windows 10)
|
||||
description: What does USMT migrate
|
||||
ms.assetid: f613987d-0f17-43fe-9717-6465865ceda7
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -8,23 +8,23 @@ ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# What Does USMT Migrate?
|
||||
# What does USMT migrate?
|
||||
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
- [Default Migration Scripts](#bkmk-defaultmigscripts)
|
||||
- [Default migration scripts](#bkmk-defaultmigscripts)
|
||||
|
||||
- [User Data](#bkmk-3)
|
||||
|
||||
- [Operating-System Components](#bkmk-4)
|
||||
- [Operating-system components](#bkmk-4)
|
||||
|
||||
- [Supported Applications](#bkmk-2)
|
||||
- [Supported applications](#bkmk-2)
|
||||
|
||||
- [What USMT Does Not Migrate](#no)
|
||||
- [What USMT does not migrate](#no)
|
||||
|
||||
## <a href="" id="bkmk-defaultmigscripts"></a>Default Migration Scripts
|
||||
## <a href="" id="bkmk-defaultmigscripts"></a>Default migration scripts
|
||||
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 is designed so that an IT engineer can precisely define migrations using the USMT .xml scripting language. USMT provides the following sample scripts:
|
||||
@ -43,7 +43,7 @@ The User State Migration Tool (USMT) 10.0 is designed so that an IT engineer ca
|
||||
|
||||
- Access control lists (ACLs) for folders outside the user profile.
|
||||
|
||||
## <a href="" id="bkmk-3"></a>User Data
|
||||
## <a href="" id="bkmk-3"></a>User data
|
||||
|
||||
|
||||
This section describes the user data that USMT migrates by default, using the MigUser.xml file. It also defines how to migrate ACLs.
|
||||
@ -52,6 +52,9 @@ This section describes the user data that USMT migrates by default, using the Mi
|
||||
|
||||
My Documents, My Video, My Music, My Pictures, desktop files, Start menu, Quick Launch settings, and Favorites.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Starting in Windows 10, version 1607 the USMT does not migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](https://docs.microsoft.com/windows/deployment/usmt/usmt-common-issues#usmt-does-not-migrate-the-start-layout).
|
||||
|
||||
- **Folders from the All Users and Public profiles.** When you specify the MigUser.xml file, USMT also migrates the following from the **All Users** profile in Windows® XP, or the **Public** profile in Windows Vista, Windows 7, or Windows 8:
|
||||
|
||||
- Shared Documents
|
||||
@ -84,7 +87,7 @@ To migrate ACLs, you must specify the directory to migrate in the MigUser.xml fi
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-4"></a>Operating-System Components
|
||||
## <a href="" id="bkmk-4"></a>Operating-system components
|
||||
|
||||
|
||||
USMT migrates operating-system components to a destination computer from computers running Windows 7 and Windows 8
|
||||
@ -151,7 +154,7 @@ Some settings, such as fonts, are not applied by the LoadState tool until after
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-2"></a>Supported Applications
|
||||
## <a href="" id="bkmk-2"></a>Supported applications
|
||||
|
||||
|
||||
Although it is not required for all applications, it is good practice to install all applications on the destination computer before restoring the user state. Installing applications before migrating settings helps to ensure that the migrated settings are not overwritten by the application installers.
|
||||
@ -361,12 +364,12 @@ When you specify the MigApp.xml file, USMT migrates the settings for the followi
|
||||
|
||||
|
||||
|
||||
## <a href="" id="no"></a>What USMT Does Not Migrate
|
||||
## <a href="" id="no"></a>What USMT does not migrate
|
||||
|
||||
|
||||
The following is a list of the settings that USMT does not migrate. If you are having a problem that is not listed here, see [Common Issues](usmt-common-issues.md).
|
||||
|
||||
### Application Settings
|
||||
### Application settings
|
||||
|
||||
USMT does not migrate the following application settings:
|
||||
|
||||
@ -382,7 +385,7 @@ USMT does not migrate the following application settings:
|
||||
|
||||
- You attempt to migrate from a 32-bit computer to a 64-bit computer. This is because the ICQ Pro default installation directory is different on the two types of computers. When you install ICQ Pro on a 32-bit computer, the default location is "C:\\Program Files\\...". The ICQ Pro default installation directory on an x64-based computer, however, is “C:\\Program Files (x86)\\...”.
|
||||
|
||||
### Operating-System Settings
|
||||
### Operating-System settings
|
||||
|
||||
USMT does not migrate the following operating-system settings.
|
||||
|
||||
@ -402,10 +405,14 @@ You should also note the following:
|
||||
|
||||
- You can use the /**localonly** option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify /**localonly**, see [ScanState Syntax](usmt-scanstate-syntax.md).
|
||||
|
||||
### Start menu layout
|
||||
|
||||
Starting in Windows 10, version 1607 the USMT does not migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](https://docs.microsoft.com/windows/deployment/usmt/usmt-common-issues#usmt-does-not-migrate-the-start-layout).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -79,7 +79,7 @@ You can create a custom dashboard in Power BI Desktop to create visualizations t
|
||||
|
||||
8. Select **New table and matrix visuals** and **Custom data connectors** and click **OK**.
|
||||
|
||||
>[NOTE]
|
||||
>[!NOTE]
|
||||
>If you are using Power BI Desktop July 2017 version (or later), you won't need to select **New table and matrix visuals**. You'll only need to select **Custom data connectors**.
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user