From e0264bde6ef88635d9c32a40850b6d2f9b3a2cf6 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 12:59:00 -0700 Subject: [PATCH 01/42] fixing link issues, reformatting table --- windows/deployment/TOC.md | 1 - ...windows-upgrades-with-upgrade-readiness.md | 6 ++-- .../upgrade/upgrade-readiness-architecture.md | 6 ++-- .../upgrade-readiness-deployment-script.md | 29 +++++++------------ .../upgrade/upgrade-readiness-get-started.md | 6 ++-- .../upgrade/upgrade-readiness-requirements.md | 4 +-- 6 files changed, 22 insertions(+), 30 deletions(-) diff --git a/windows/deployment/TOC.md b/windows/deployment/TOC.md index 33c1697c0f..73fce9589a 100644 --- a/windows/deployment/TOC.md +++ b/windows/deployment/TOC.md @@ -46,7 +46,6 @@ ### [Manage Windows upgrades with Upgrade Readiness](upgrade/manage-windows-upgrades-with-upgrade-readiness.md) #### [Upgrade Readiness architecture](upgrade/upgrade-readiness-architecture.md) #### [Upgrade Readiness requirements](upgrade/upgrade-readiness-requirements.md) -#### [Upgrade Readiness release notes](upgrade/upgrade-readiness-release-notes.md) #### [Get started with Upgrade Readiness](upgrade/upgrade-readiness-get-started.md) ##### [Upgrade Readiness deployment script](upgrade/upgrade-readiness-deployment-script.md) #### [Use Upgrade Readiness to manage Windows upgrades](upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md) diff --git a/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md b/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md index de269889bf..c2744bd544 100644 --- a/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md +++ b/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness.md @@ -29,15 +29,15 @@ The Upgrade Readiness workflow steps you through the discovery and rationalizati **Important** For system, application, and driver data to be shared with Microsoft, you must configure user computers to send data. For information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see: -- [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization) -- [Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services) +- [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization) +- [Manage connections from Windows operating system components to Microsoft services](/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services) - [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) ##**Related topics** [Upgrade Readiness architecture](upgrade-readiness-architecture.md)
[Upgrade Readiness requirements](upgrade-readiness-requirements.md)
-[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
+[Upgrade Readiness release notes](upgrade-readiness-requirements.md#important-information-about-this-release)
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)
[Use Upgrade Readiness to manage Windows upgrades](use-upgrade-readiness-to-manage-windows-upgrades.md)
[Troubleshoot Upgrade Readiness](troubleshoot-upgrade-readiness.md)
diff --git a/windows/deployment/upgrade/upgrade-readiness-architecture.md b/windows/deployment/upgrade/upgrade-readiness-architecture.md index 6bc7492d37..ae5949405f 100644 --- a/windows/deployment/upgrade/upgrade-readiness-architecture.md +++ b/windows/deployment/upgrade/upgrade-readiness-architecture.md @@ -19,12 +19,12 @@ After you enable Windows telemetry on user computers and install the compatibili For more information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see: -[Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization)
-[Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services)
+[Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization)
+[Manage connections from Windows operating system components to Microsoft services](/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services)
[Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965)
##**Related topics** [Upgrade Readiness requirements](upgrade-readiness-requirements.md)
-[Upgrade Readiness release notes](upgrade-readiness-release-notes.md)
+[Upgrade Readiness release notes](upgrade-readiness-requirements.md#important-information-about-this-release)
[Get started with Upgrade Readiness](upgrade-readiness-get-started.md)
diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 43870037ce..b3dcdf790a 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,11 +70,11 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. -
+ - +
Exit code
Exit code Meaning Suggested fix @@ -105,7 +105,7 @@ The deployment script displays the following exit codes to let you know if it wa
6 The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value. 		The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace. -
See [Generate your Commercial ID key](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. +
See [Generate your Commercial ID key](upgrade-readiness-get-started.md#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace.
8 Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
@@ -130,21 +130,21 @@ The deployment script displays the following exit codes to let you know if it wa 		**Http Get** on the end points did not return a success exit code.
For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive. -
If there is an error verifying connectivity, this will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). +
If there is an error verifying connectivity, this will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing).
13 Can’t connect to Microsoft - setting. -An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). +An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing).
14 Can’t connect to Microsoft - compatexchange. -An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). +An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing).
15 Function CheckVortexConnectivity failed with an unexpected exception. -This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). Check the logs for the exception message and the HResult. +This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing). Check the logs for the exception message and the HResult.
16 The computer requires a reboot before running the script. @@ -156,7 +156,7 @@ For previous operating systems, connectivity is verified by connecting to https:
18 Appraiser KBs not installed or **appraiser.dll** not found. -Either the Appraiser KBs are not installed, or the **appraiser.dll** file was not found. For more information, see appraiser telemetry events and fields information in the [Data collection](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#data-collection-and-privacy) and privacy topic. +Either the Appraiser KBs are not installed, or the **appraiser.dll** file was not found. For more information, see appraiser telemetry events and fields information in the [Data collection](upgrade-readiness-get-started.md#data-collection-and-privacy) and privacy topic.
19 Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception. @@ -217,7 +217,7 @@ For previous operating systems, connectivity is verified by connecting to https:
32 Appraiser version on the machine is outdated. -The configuration script detected a version of the compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Readiness solution. Use the latest version of the [compatibility update](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1. +The configuration script detected a version of the compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Readiness solution. Use the latest version of the [compatibility update](upgrade-readiness-get-started.md#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1.
33 **CompatTelRunner.exe** exited with an exit code @@ -246,7 +246,7 @@ For previous operating systems, connectivity is verified by connecting to https:
39 For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
-		For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization). +For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization).
40 Function **CheckTelemetryOptIn** failed with an unexpected exception. @@ -284,11 +284,4 @@ or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersio
The **CommercialID** referenced in RunConfig.bat must be a GUID. The **CommercialID** that is entered in RunConfig.bat must be a GUID. Copy the commercial ID from your workspace. To find the commercialID on the OMS portal, view Upgrade Readiness > Settings. You will find the commercial ID on the settings page. -
- -
- - - - - + \ No newline at end of file diff --git a/windows/deployment/upgrade/upgrade-readiness-get-started.md b/windows/deployment/upgrade/upgrade-readiness-get-started.md index 102fb76463..bb6ce8f949 100644 --- a/windows/deployment/upgrade/upgrade-readiness-get-started.md +++ b/windows/deployment/upgrade/upgrade-readiness-get-started.md @@ -32,8 +32,8 @@ When you are ready to begin using Upgrade Readiness, perform the following steps To enable system, application, and driver data to be shared with Microsoft, you must configure user computers to send data. For information about what telemetry data Microsoft collects and how that data is used and protected by Microsoft, see the following topics: -- [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization) -- [Manage connections from Windows operating system components to Microsoft services](https://technet.microsoft.com/itpro/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services) +- [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization) +- [Manage connections from Windows operating system components to Microsoft services](/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services) - [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) ## Add Upgrade Readiness to Operations Management Suite @@ -113,7 +113,7 @@ If you are planning to enable IE Site Discovery, you will need to install a few | **Site discovery** | **KB** | |----------------------|-----------------------------------------------------------------------------| -| [Review site discovery](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-additional-insights#site-discovery) | [KB3080149](http://www.catalog.update.microsoft.com/Search.aspx?q=3080149)
Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices.
For more information about this KB, see

Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update. | +| [Review site discovery](upgrade-readiness-additional-insights.md#site-discovery) | [KB3080149](http://www.catalog.update.microsoft.com/Search.aspx?q=3080149)
Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices.
For more information about this KB, see

Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update. | ### Deploy the Upgrade Readiness deployment script diff --git a/windows/deployment/upgrade/upgrade-readiness-requirements.md b/windows/deployment/upgrade/upgrade-readiness-requirements.md index 5593a4eb72..5643e2df81 100644 --- a/windows/deployment/upgrade/upgrade-readiness-requirements.md +++ b/windows/deployment/upgrade/upgrade-readiness-requirements.md @@ -30,7 +30,7 @@ See [Windows 10 Specifications](http://www.microsoft.com/en-US/windows/windows-1 Keeping Windows 10 up to date involves deploying a feature update, and Upgrade Readiness tools help you prepare and plan for these Windows updates. The latest cumulative updates must be installed on Windows 10 computers to make sure that the required compatibility KBs are installed. You can find the latest cumulative update on the [Microsoft Update Catalog](https://catalog.update.microsoft.com). -Windows 10 LTSB is not supported by Upgrade Readiness. The LTSB (long term servicing branch) of Windows 10 is not intended for general deployment, and does not receive feature updates, therefore it is not compatible with Upgrade Readiness. See [Windows as a service overview](https://technet.microsoft.com/en-us/itpro/windows/manage/waas-overview#long-term-servicing-branch) to understand more about LTSB. +Windows 10 LTSB is not supported by Upgrade Readiness. The LTSB (long term servicing branch) of Windows 10 is not intended for general deployment, and does not receive feature updates, therefore it is not compatible with Upgrade Readiness. See [Windows as a service overview](../update/waas-overview.md#long-term-servicing-branch) to understand more about LTSB. ## Operations Management Suite @@ -50,7 +50,7 @@ Upgrade Readiness can be integrated with your installation of Configuration Mana After you’ve signed in to Operations Management Suite and added the Upgrade Readiness solution to your workspace, you’ll need to complete the following tasks to allow user computer data to be shared with and assessed by Upgrade Readiness. -See [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) for more information about what user computer data Upgrade Readiness collects and assesses. See [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data. +See [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) for more information about what user computer data Upgrade Readiness collects and assesses. See [Configure Windows telemetry in your organization](windows/configuration/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data. **Whitelist telemetry endpoints.** To enable telemetry data to be sent to Microsoft, you’ll need to whitelist the following Microsoft telemetry endpoints on your proxy server or firewall. You may need to get approval from your security group to do this. From 8418877c9bca12240b51161885bbeb198c966fff Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:10:17 -0700 Subject: [PATCH 02/42] fixing table width --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- windows/deployment/upgrade/upgrade-readiness-requirements.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index b3dcdf790a..e44324588d 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
Exit code Meaning diff --git a/windows/deployment/upgrade/upgrade-readiness-requirements.md b/windows/deployment/upgrade/upgrade-readiness-requirements.md index 5643e2df81..eb98ebd2cf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-requirements.md +++ b/windows/deployment/upgrade/upgrade-readiness-requirements.md @@ -50,7 +50,7 @@ Upgrade Readiness can be integrated with your installation of Configuration Mana After you’ve signed in to Operations Management Suite and added the Upgrade Readiness solution to your workspace, you’ll need to complete the following tasks to allow user computer data to be shared with and assessed by Upgrade Readiness. -See [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) for more information about what user computer data Upgrade Readiness collects and assesses. See [Configure Windows telemetry in your organization](windows/configuration/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data. +See [Windows 7, Windows 8, and Windows 8.1 appraiser telemetry events and fields](https://go.microsoft.com/fwlink/?LinkID=822965) for more information about what user computer data Upgrade Readiness collects and assesses. See [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization) for more information about how Microsoft uses Windows telemetry data. **Whitelist telemetry endpoints.** To enable telemetry data to be sent to Microsoft, you’ll need to whitelist the following Microsoft telemetry endpoints on your proxy server or firewall. You may need to get approval from your security group to do this. From 775f74f6a25be6263068e8542f6756e7061fa831 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:21:44 -0700 Subject: [PATCH 03/42] table formatting --- .../upgrade/upgrade-readiness-deployment-script.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index e44324588d..cb0b03011c 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -74,9 +74,9 @@ The deployment script displays the following exit codes to let you know if it wa - - + + - + @@ -304,4 +304,16 @@ The deployment script displays the following exit codes to let you know if it wa
Exit codeMeaning -Suggested fix +
Exit codeMeaningSuggested fix
0 Success From 75fb00db33f91a16b706897542c703abd956094a Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:32:03 -0700 Subject: [PATCH 04/42] table formatting --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index cb0b03011c..896111f8b3 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
From fa2475afcd4d0565a5281b3ef8b33bd4721d5e21 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:40:16 -0700 Subject: [PATCH 05/42] table formatting --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 896111f8b3..1c10d4acaf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -76,7 +76,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
Exit code Meaning
Exit code MeaningSuggested fix
Suggested fix
0 Success From 42386a5239595660346cd48dadac9eb2526fbd43 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 13:55:32 -0700 Subject: [PATCH 06/42] table formatting --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 1c10d4acaf..f643327a10 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa - +
From b013e7cf58ffa4c26979bc8b5e24cde0e9fcbe2d Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 14:08:35 -0700 Subject: [PATCH 07/42] removed divs from tables --- .../upgrade-readiness-deployment-script.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index f643327a10..58802e85bf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -108,22 +108,22 @@ The deployment script displays the following exit codes to let you know if it wa
See [Generate your Commercial ID key](upgrade-readiness-get-started.md#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. - - - @@ -179,7 +179,7 @@ For previous operating systems, connectivity is verified by connecting to https: - @@ -244,8 +244,8 @@ For previous operating systems, connectivity is verified by connecting to https: - From 7a6c57fb9d110fde1fd02445af2c05466202c0c6 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 14:20:15 -0700 Subject: [PATCH 08/42] still playing with table size --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 58802e85bf..9256cab8df 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -72,7 +72,7 @@ The deployment script displays the following exit codes to let you know if it wa -
Exit code Meaning
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
-		The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** +The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception. -The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location. +		The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12 Can’t connect to Microsoft - Vortex. Check your network/proxy settings. @@ -163,7 +163,7 @@ For previous operating systems, connectivity is verified by connecting to https: Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
+		An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
21Verify that this environment variable is configured on the computer.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
25Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
-or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+		For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** +or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization).
40
+
From 9a6eff268802287045db524a7a514c5775feff2f Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Tue, 25 Apr 2017 14:32:55 -0700 Subject: [PATCH 09/42] still playing with table size --- .../upgrade/upgrade-readiness-deployment-script.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 9256cab8df..62768524f5 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -74,9 +74,9 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code Meaning
- - - + + + - - + - + - + @@ -180,7 +180,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +200,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - - or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ + or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** From ec3ad288ef4b8cc38fc6c0d38e3d514f4387acf8 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:15:13 -0700 Subject: [PATCH 12/42] trying smaller font for the whole table --- .../upgrade/upgrade-readiness-deployment-script.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index e5ee92c1bf..6174cfc954 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. - +
Exit codeMeaningSuggested fix
Exit codeMeaningSuggested fix
0 Success From 2939c6a5002395e3ff9ae19f29af16d84cc31971 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 10:32:27 -0700 Subject: [PATCH 10/42] fixing table --- .../upgrade-readiness-deployment-script.md | 447 +++++++++--------- 1 file changed, 233 insertions(+), 214 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 62768524f5..22ab8bc418 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -71,217 +71,236 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Exit codeMeaningSuggested fix
0Success -N/A - -
1Unexpected error occurred while executing the script. - The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again. - -
2Error when logging to console. $logMode = 0.
(console only) -		Try changing the $logMode value to **1** and try again.
$logMode value 1 logs to both console and file. - -
3Error when logging to console and file. $logMode = 1. -Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. - -
4Error when logging to file. $logMode = 2. -Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. - -
5Error when logging to console and file. $logMode = unknown. -Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. - -
6The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value. -		The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace. -
See [Generate your Commercial ID key](upgrade-readiness-get-started.md#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. - -
8Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -
Verify that the context under which the script in running has access to the registry key. - -
9The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -		Verify that the context under which the script in running has access to the registry key. - -
10Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -Verify that the deployment script is running in a context that has access to the registry key. - -
11Function **SetupCommercialId** failed with an unexpected exception. -The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location. - -
12Can’t connect to Microsoft - Vortex. Check your network/proxy settings. -**Http Get** on the end points did not return a success exit code.
-For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
-For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive. -
If there is an error verifying connectivity, this will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing). - - -
13Can’t connect to Microsoft - setting. -An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing). - - -
14Can’t connect to Microsoft - compatexchange. -An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing). - -
15Function CheckVortexConnectivity failed with an unexpected exception. -This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](upgrade-readiness-get-started.md#enable-data-sharing). Check the logs for the exception message and the HResult. - -
16The computer requires a reboot before running the script. -A reboot is required to complete the installation of the compatibility update and related KBs. Reboot the computer before running the Upgrade Readiness deployment script. - -
17Function **CheckRebootRequired** failed with an unexpected exception. -A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult. - -
18Appraiser KBs not installed or **appraiser.dll** not found. -Either the Appraiser KBs are not installed, or the **appraiser.dll** file was not found. For more information, see appraiser telemetry events and fields information in the [Data collection](upgrade-readiness-get-started.md#data-collection-and-privacy) and privacy topic. - -
19Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception. -Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed. - -
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** -The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key. - -
21Function **SetRequestAllAppraiserVersions** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
22**RunAppraiser** failed with unexpected exception. -Check the logs for the exception message and HResult. Check the **%windir%\System32*8 directory for the file **CompatTelRunner.exe**. If the file does not exist, reinstall the required compatibility updates which include this file, and check your organization's Group Policy to verify it does not remove this file. - -
23Error finding system variable **%WINDIR%**. -Verify that this environment variable is configured on the computer. - -
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult. - -
25The function **SetIEDataOptIn** failed with unexpected exception. -Check the logs for the exception message and HResult. - -
26The operating system is Server or LTSB SKU. - The script does not support Server or LTSB SKUs. - -
27The script is not running under **System** account. -The Upgrade Readiness configuration script must be run as **System**. - -
28Could not create log file at the specified **logPath**. - Make sure the deployment script has access to the location specified in the **logPath** parameter. - -
29Connectivity check failed for proxy authentication. -Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting. -
The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. -
For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled). -
For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688). - -
30Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled. -The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. -
For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled). -
For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688). - -
31There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. -Use the Windows Task Manager to check if **CompatTelRunner.exe** is running, and wait until it has completed to rerun the script. The Upgrade Readiness task is scheduled to run daily at 3 a.m. - -
32Appraiser version on the machine is outdated. -The configuration script detected a version of the compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Readiness solution. Use the latest version of the [compatibility update](upgrade-readiness-get-started.md#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1. - -
33**CompatTelRunner.exe** exited with an exit code -**CompatTelRunner.exe** runs the appraise task on the machine. If it fails, it will provide a specific exit code. The script will return exit code 33 when **CompatTelRunner.exe** itself exits with an exit code. Please check the logs for more details. - -
34Function **CheckProxySettings** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
35Function **CheckAuthProxy** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
36Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
37**Diagnose_internal.cmd** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
38Function **Get-SqmID** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** -or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** -For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization). - -
40Function **CheckTelemetryOptIn** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
41The script failed to impersonate the currently logged on user. -The script mimics the UTC client to collect upgrade readiness data. When auth proxy is set, the UTC client impersonates the logged on user. The script also tries to mimic this, but the process failed. - -
42Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
43Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. -Check the logs for the exception message and HResult. - -
44Function **Diagtrack.dll** version is old and so Auth Proxy will not work. -Update the computer using Windows Update or WSUS. - -
45**Diagtrack.dll** not found. -Update the computer using Windows Update or WSUS. - -
46**DisableEnterpriseAuthProxy** property should be set to 1 for ClientProxy=Telemetry to work. -The ClientProxy=Telemetry scenario requires the **DisableEnterpriseAuthProxy** registry key to be set to 1 at registry path: **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. - -
47**TelemetryProxyServer** property is not present in the Windows registry at **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. -ClientProxy selected is Telemetry. The **TelemetryProxyServer** key is not present at Windows registry path: **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. - -
48The **CommercialID** referenced in RunConfig.bat must be a GUID. -The **CommercialID** that is entered in RunConfig.bat must be a GUID. Copy the commercial ID from your workspace. To find the commercialID on the OMS portal, view Upgrade Readiness > Settings. You will find the commercial ID on the settings page. - -
\ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ + + + + + + + + + + + + + + + + + + + + +
Exit codeMeaningSuggested fix
0SuccessN/A
1Unexpected error occurred while executing the script. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again.
2Error when logging to console. $logMode = 0.
(console only)		Try changing the $logMode value to **1** and try again.
$logMode value 1 logs to both console and file.
3Error when logging to console and file. $logMode = 1.Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
4Error when logging to file. $logMode = 2.Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
5Error when logging to console and file. $logMode = unknown.Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
6The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value.		The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace. +
See [Generate your Commercial ID key](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace.
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Verify that the context under which the script in running has access to the registry key.
9The script failed to write Commercial Id to registry. +
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the deployment script is running in a context that has access to the registry key.
11Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.
12Can’t connect to Microsoft - Vortex. Check your network/proxy settings.**Http Get** on the end points did not return a success exit code.
+ For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
+ For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive. +
If there is an error verifying connectivity, this will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
13Can’t connect to Microsoft - setting. An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
14Can’t connect to Microsoft - compatexchange.An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
15Function CheckVortexConnectivity failed with an unexpected exception.This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). Check the logs for the exception message and the HResult.
16The computer requires a reboot before running the script.A reboot is required to complete the installation of the compatibility update and related KBs. Reboot the computer before running the Upgrade Readiness deployment script.
17Function **CheckRebootRequired** failed with an unexpected exception.A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult.
18Appraiser KBs not installed or **appraiser.dll** not found.Either the Appraiser KBs are not installed, or the **appraiser.dll** file was not found. For more information, see appraiser telemetry events and fields information in the [Data collection](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#data-collection-and-privacy) and privacy topic.
19Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception.Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
21Function **SetRequestAllAppraiserVersions** failed with an unexpected exception.Check the logs for the exception message and HResult.
22**RunAppraiser** failed with unexpected exception.Check the logs for the exception message and HResult. Check the **%windir%\System32*8 directory for the file **CompatTelRunner.exe**. If the file does not exist, reinstall the required compatibility updates which include this file, and check your organization's Group Policy to verify it does not remove this file.
23Error finding system variable **%WINDIR%**.Verify that this environment variable is configured on the computer.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
25The function **SetIEDataOptIn** failed with unexpected exception.Check the logs for the exception message and HResult.
26The operating system is Server or LTSB SKU. The script does not support Server or LTSB SKUs.
27The script is not running under **System** account.The Upgrade Readiness configuration script must be run as **System**.
28Could not create log file at the specified **logPath**. Make sure the deployment script has access to the location specified in the **logPath** parameter.
29Connectivity check failed for proxy authentication. Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting. +
The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. +
For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled). +
For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
30Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled.The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7. +
For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled). +
For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
31There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. Use the Windows Task Manager to check if **CompatTelRunner.exe** is running, and wait until it has completed to rerun the script. The Upgrade Readiness task is scheduled to run daily at 3 a.m.
32Appraiser version on the machine is outdated. The configuration script detected a version of the compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Readiness solution. Use the latest version of the [compatibility update](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1.
33**CompatTelRunner.exe** exited with an exit code **CompatTelRunner.exe** runs the appraise task on the machine. If it fails, it will provide a specific exit code. The script will return exit code 33 when **CompatTelRunner.exe** itself exits with an exit code. Please check the logs for more details.
34Function **CheckProxySettings** failed with an unexpected exception. Check the logs for the exception message and HResult.>
35Function **CheckAuthProxy** failed with an unexpected exception.Check the logs for the exception message and HResult.
36Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception.Check the logs for the exception message and HResult.
37**Diagnose_internal.cmd** failed with an unexpected exception.Check the logs for the exception message and HResult.
38Function **Get-SqmID** failed with an unexpected exception. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
40Function **CheckTelemetryOptIn** failed with an unexpected exception. Check the logs for the exception message and HResult.
41The script failed to impersonate the currently logged on user. The script mimics the UTC client to collect upgrade readiness data. When auth proxy is set, the UTC client impersonates the logged on user. The script also tries to mimic this, but the process failed.
42Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
43Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception.Check the logs for the exception message and HResult.
\ No newline at end of file From 7ba635949471d21edef301527f531716e0141cb4 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:01:08 -0700 Subject: [PATCH 11/42] changing font size for reg keys --- .../upgrade-readiness-deployment-script.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 22ab8bc418..e5ee92c1bf 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -114,26 +114,26 @@ The deployment script displays the following exit codes to let you know if it wa
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ 		Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
@@ -303,4 +303,5 @@ The deployment script displays the following exit codes to let you know if it wa -
Exit code43 Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
\ No newline at end of file +
+ \ No newline at end of file From 0ea38f35a6e61ed4c3bdceac99244d65617ef7f3 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:29:08 -0700 Subject: [PATCH 13/42] font size --- .../upgrade/upgrade-readiness-deployment-script.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 6174cfc954..9fd126d7ab 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. - +
@@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - - or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** + @@ -304,4 +304,4 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** + or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- \ No newline at end of file +
\ No newline at end of file From e5a85a93b59a3c716794e6af871ad5ad82a24365 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 11:38:43 -0700 Subject: [PATCH 14/42] trying md table --- .../upgrade-readiness-deployment-script.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 9fd126d7ab..11e09d889a 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -83,7 +83,7 @@ The deployment script displays the following exit codes to let you know if it wa
1Unexpected error occurred while executing the script.Unexpected error occurred while executiEng the script. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again.
Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- \ No newline at end of file + + +| Exit code | Meaning | Suggested fix | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Success | N/A | +| 1 | Unexpected error occurred while executing the script. | The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again. | +| 2 | Error when logging to console. | Try changing the $logMode value to **1** and try again.$logMode value 1 logs to both console and file. | +| 3 | Error when logging to console and file. $logMode = 1. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. | +| 4 | Error when logging to file. $logMode = 2. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. | +| 5 | Error when logging to console and file. $logMode = unknown. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.< | +| 6 | The commercialID parameter is set to unknown. Modify the runConfig.bat file to set the CommercialID value. | See [Generate your Commercial ID key](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. | +| 8 | Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**,Verify that the context under which the script in running has access to the registry key. | +| 9 | The script failed to write Commercial Id to registry.,Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | Verify that the context under which the script in running has access to the registry key.| From 072406c9bbc75173451a89745f59d4125050059a Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Wed, 26 Apr 2017 14:24:45 -0700 Subject: [PATCH 15/42] new topic --- devices/surface-hub/TOC.md | 1 + ...e-and-test-a-device-account-surface-hub.md | 1 + devices/surface-hub/skype-hybrid-voice.md | 19 +++++++++++++++++++ ...se-room-control-system-with-surface-hub.md | 2 +- 4 files changed, 22 insertions(+), 1 deletion(-) create mode 100644 devices/surface-hub/skype-hybrid-voice.md diff --git a/devices/surface-hub/TOC.md b/devices/surface-hub/TOC.md index a9cde81f15..742423081c 100644 --- a/devices/surface-hub/TOC.md +++ b/devices/surface-hub/TOC.md @@ -8,6 +8,7 @@ ##### [On-premises deployment (single forest)](on-premises-deployment-surface-hub-device-accounts.md) ##### [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) ##### [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) +##### [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md) ##### [Create a device account using UI](create-a-device-account-using-office-365.md) ##### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) ##### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md) diff --git a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md index 9930a748e3..c01273b24e 100644 --- a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md +++ b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md @@ -49,6 +49,7 @@ For detailed steps using PowerShell to provision a device account, choose an opt | [On-premises deployment (single-forest)](on-premises-deployment-surface-hub-device-accounts.md) | Your organization has servers that it controls and uses to host Active Directory, Exchange, and Skype for Business (or Lync) in a single-forest environment. | | [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) | Your organization has servers that it controls and uses to host Active Directory, Exchange, and Skype for Business (or Lync) in a multi-forest environment. | | [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Your organization has a mix of services, with some hosted on-premises and some hosted online through Office 365. | +| [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md) | Your organization has Skype for Business home pools and Exchange servers in the cloud, and uses an on-premises pool of Skype for Business 2015 or Cloud Connector edition connected via Public Switched Telephone Network (PSTN). | If you prefer to use a graphical user interface, some steps can be done using UI instead of PowerShell. For more information, see [Creating a device account using UI](create-a-device-account-using-office-365.md). diff --git a/devices/surface-hub/skype-hybrid-voice.md b/devices/surface-hub/skype-hybrid-voice.md new file mode 100644 index 0000000000..d930924045 --- /dev/null +++ b/devices/surface-hub/skype-hybrid-voice.md @@ -0,0 +1,19 @@ +--- +title: Online or hybrid deployment using Skype Hybrid Voice environment (Surface Hub) +description: A Skype Hybrid Voice deployment requires special processing to set up a device account for your Microsoft Surface Hub. +keywords: hybrid deployment, Skype Hybrid Voice, Skype for Business Cloud PBX +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: surfacehub +author: jdeckerms +localizationpriority: medium +--- + +# Online or hybrid deployment using Skype Hybrid Voice environment (Surface Hub) + +This topic explains how to enable Skype for Business Cloud PBX with on premises PSTN connectivity via Cloud Connector Edition or Skype for Business 2015 pool. In this option your Skype for Business home pools and Exchange servers are in the Cloud, however PSTN connected via on premises pool of Skype for Business 2015 or via a Cloud Connector edition. More about different Cloud PBX options is here https://technet.microsoft.com/en-us/library/mt612869.aspx + +If you deployed Skype for Business Cloud PBX with one of the hybrid voice options, please follow the steps below to enable the room account. It is important to create a regular user account first, assign all hybrid voice options and phone numbers and only after this convert the account to a room account. If you do not follow this order you will not be able to assign a hybrid phone number. + + diff --git a/devices/surface-hub/use-room-control-system-with-surface-hub.md b/devices/surface-hub/use-room-control-system-with-surface-hub.md index 6b8805b229..056064b880 100644 --- a/devices/surface-hub/use-room-control-system-with-surface-hub.md +++ b/devices/surface-hub/use-room-control-system-with-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerms localizationpriority: medium --- From 5288121d4110043c78d2afebf0fb845fb4f8bc61 Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Wed, 26 Apr 2017 14:31:01 -0700 Subject: [PATCH 16/42] added new video in mbr-to-gpt and fixed a link --- windows/deployment/mbr-to-gpt.md | 2 ++ windows/whats-new/whats-new-windows-10-version-1703.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/deployment/mbr-to-gpt.md b/windows/deployment/mbr-to-gpt.md index 46c411919f..b01537fa06 100644 --- a/windows/deployment/mbr-to-gpt.md +++ b/windows/deployment/mbr-to-gpt.md @@ -36,6 +36,8 @@ Offline conversion of system disks with earlier versions of Windows installed, s >[!IMPORTANT] >After the disk has been converted to GPT partition style, the firmware must be reconfigured to boot in UEFI mode.
Make sure that your device supports UEFI before attempting to convert the disk. + + ## Syntax diff --git a/windows/whats-new/whats-new-windows-10-version-1703.md b/windows/whats-new/whats-new-windows-10-version-1703.md index 901e7a0a0c..6b9af04119 100644 --- a/windows/whats-new/whats-new-windows-10-version-1703.md +++ b/windows/whats-new/whats-new-windows-10-version-1703.md @@ -75,7 +75,7 @@ Cortana is Microsoft’s personal digital assistant, who helps busy people get t Using Azure AD also means that you can remove an employee’s profile (for example, when an employee leaves your organization) while respecting Windows Information Protection (WIP) policies and ignoring enterprise content, such as emails, calendar items, and people lists that are marked as enterprise data. -For more info about Cortana at work, see [Cortana integration in your business or enterprise](/windows/configuration/cortana-at-work/cortana-at-work-overview.md) +For more info about Cortana at work, see [Cortana integration in your business or enterprise](/windows/configuration/cortana-at-work/cortana-at-work-overview) ## Deployment From 89f7d62722d23e4ff92766bf899194ebc56ea5a1 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Wed, 26 Apr 2017 15:10:39 -0700 Subject: [PATCH 17/42] updating redirects for docs --- .openpublishing.redirection.json | 390 +++++++++++++++---------------- 1 file changed, 195 insertions(+), 195 deletions(-) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index df892ca516..bc0528dea6 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -7,57 +7,57 @@ }, { "source_path": "windows/keep-secure/configure-windows-defender-in-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/deploy-manage-report-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/enable-pua-windows-defender-for-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/detect-block-potentially-unwanted-apps-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/detect-block-potentially-unwanted-apps-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/get-started-with-windows-defender-for-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/deploy-manage-report-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus", "redirect_document_id": false }, { "source_path": "windows/keep-secure/run-cmd-scan-windows-defender-for-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/command-line-arguments-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/troubleshoot-windows-defender-in-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/troubleshoot-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/troubleshoot-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/use-powershell-cmdlets-windows-defender-for-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/use-powershell-cmdlets-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/use-powershell-cmdlets-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/windows-defender-block-at-first-sight.md", -"redirect_url": "/itpro/windows/keep-secure/configure-block-at-first-sight-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/configure-block-at-first-sight-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/windows-defender-in-windows-10.md", -"redirect_url": "/itpro/windows/keep-secure/windows-defender-antivirus-in-windows-10", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10", "redirect_document_id": true }, { "source_path": "windows/keep-secure/windows-defender-enhanced-notifications.md", -"redirect_url": "/itpro/windows/keep-secure/configure-notifications-windows-defender-antivirus", +"redirect_url": "/windows/threat-protection/windows-defender-antivirus/configure-notifications-windows-defender-antivirus", "redirect_document_id": true }, { "source_path": "windows/keep-secure/configure-aad-windows-defender-advanced-threat-protection.md", -"redirect_url": "/itpro/windows/keep-secure/enable-siem-integration-windows-defender-advanced-threat-protection", +"redirect_url": "/windows/threat-protection/windows-defender-atp/enable-siem-integration-windows-defender-advanced-threat-protection", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-7.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-7", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-7", "redirect_document_id": true }, { @@ -72,7 +72,7 @@ }, { "source_path": "windows/manage/waas-servicing-strategy-windows-10-updates.md", -"redirect_url": "windows/deployment/update/waas-servicing-strategy-windows-10-updates", +"redirect_url": "/windows/deployment/update/waas-servicing-strategy-windows-10-updates", "redirect_document_id": true }, { @@ -92,32 +92,32 @@ }, { "source_path": "windows/manage/update-compliance-get-started.md", -"redirect_url": "/itpro/windows/update/update-compliance-get-started", +"redirect_url": "/windows/deployment/update/update-compliance-get-started", "redirect_document_id": true }, { "source_path": "windows/manage/update-compliance-using.md", -"redirect_url": "/itpro/windows/update/update-compliance-using", +"redirect_url": "/windows/deployment/update/update-compliance-using", "redirect_document_id": true }, { "source_path": "windows/manage/waas-optimize-windows-10-updates.md", -"redirect_url": "/itpro/windows/update/waas-optimize-windows-10-updates", +"redirect_url": "/windows/deployment/update/waas-optimize-windows-10-updates", "redirect_document_id": true }, { "source_path": "windows/manage/waas-delivery-optimization.md", -"redirect_url": "/itpro/windows/update/waas-delivery-optimization", +"redirect_url": "/windows/deployment/update/waas-delivery-optimization", "redirect_document_id": true }, { "source_path": "windows/manage/waas-branchcache.md", -"redirect_url": "/itpro/windows/update/waas-branchcache", +"redirect_url": "/windows/deployment/update/waas-branchcache", "redirect_document_id": true }, { "source_path": "windows/manage/waas-mobile-updates.md", -"redirect_url": "/itpro/windows/update/waas-mobile-updates", +"redirect_url": "/windows/deployment/update/waas-mobile-updates", "redirect_document_id": true }, { @@ -127,32 +127,32 @@ }, { "source_path": "windows/manage/waas-configure-wufb.md", -"redirect_url": "/itpro/windows/update/waas-configure-wufb", +"redirect_url": "/windows/deployment/update/waas-configure-wufb", "redirect_document_id": true }, { "source_path": "windows/manage/waas-integrate-wufb.md", -"redirect_url": "/itpro/windows/update/waas-integrate-wufb", +"redirect_url": "/windows/deployment/update/waas-integrate-wufb", "redirect_document_id": true }, { "source_path": "windows/manage/waas-wufb-group-policy.md", -"redirect_url": "/itpro/windows/update/waas-wufb-group-policy", +"redirect_url": "/windows/deployment/update/waas-wufb-group-policy", "redirect_document_id": true }, { "source_path": "windows/manage/waas-wufb-intune.md", -"redirect_url": "/itpro/windows/update/waas-wufb-intune.md", +"redirect_url": "/windows/deployment/update/waas-wufb-intune.md", "redirect_document_id": true }, { "source_path": "windows/manage/waas-manage-updates-wsus.md", -"redirect_url": "/itpro/windows/update/waas-manage-updates-wsus", +"redirect_url": "/windows/deployment/update/waas-manage-updates-wsus", "redirect_document_id": true }, { "source_path": "windows/manage/waas-manage-updates-configuration-manager.md", -"redirect_url": "/itpro/windows/update/waas-manage-updates-configuration-manager", +"redirect_url": "/windows/deployment/update/waas-manage-updates-configuration-manager", "redirect_document_id": true }, { @@ -167,12 +167,12 @@ }, { "source_path": "windows/manage/configure-windows-telemetry-in-your-organization.md", -"redirect_url": "/itpro/windows/configure/configure-windows-telemetry-in-your-organization", +"redirect_url": "/windows/configuration/configure-windows-telemetry-in-your-organization", "redirect_document_id": true }, { "source_path": "windows/manage/lockdown-features-windows-10.md", -"redirect_url": "/itpro/windows/configure/lockdown-features-windows-10", +"redirect_url": "/windows/configuration/lockdown-features-windows-10", "redirect_document_id": true }, { @@ -182,7 +182,7 @@ }, { "source_path": "windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md", -"redirect_url": "/itpro/windows/configure/manage-connections-from-windows-operating-system-components-to-microsoft-services", +"redirect_url": "/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services", "redirect_document_id": false }, { @@ -192,12 +192,12 @@ }, { "source_path": "windows/manage/set-up-a-kiosk-for-windows-10-for-desktop-editions.md", -"redirect_url": "/itpro/windows/configure/set-up-a-kiosk-for-windows-10-for-desktop-editions", +"redirect_url": "/windows/configuration/set-up-a-kiosk-for-windows-10-for-desktop-editions", "redirect_document_id": true }, { "source_path": "windows/manage/guidelines-for-assigned-access-app.md", -"redirect_url": "/itpro/windows/configure/guidelines-for-assigned-access-app", +"redirect_url": "/windows/configuration/guidelines-for-assigned-access-app", "redirect_document_id": true }, { @@ -212,22 +212,22 @@ }, { "source_path": "windows/manage/lockdown-xml.md", -"redirect_url": "/itpro/windows/configure/lockdown-xml", +"redirect_url": "/windows/configuration/mobile-devices/lockdown-xml", "redirect_document_id": true }, { "source_path": "windows/manage/settings-that-can-be-locked-down.md", -"redirect_url": "/itpro/windows/configure/settings-that-can-be-locked-down", +"redirect_url": "/windows/configuration/mobile-devices/settings-that-can-be-locked-down", "redirect_document_id": true }, { "source_path": "windows/manage/product-ids-in-windows-10-mobile.md", -"redirect_url": "/itpro/windows/configure/product-ids-in-windows-10-mobile", +"redirect_url": "/windows/configuration/mobile-devices/product-ids-in-windows-10-mobile", "redirect_document_id": true }, { "source_path": "windows/manage/manage-tips-and-suggestions.md", -"redirect_url": "/itpro/windows/configure/manage-tips-and-suggestions", +"redirect_url": "/windows/configuration/manage-tips-and-suggestions", "redirect_document_id": true }, { @@ -237,27 +237,27 @@ }, { "source_path": "windows/manage/configure-windows-10-taskbar.md", -"redirect_url": "/itpro/windows/configure/configure-windows-10-taskbar", +"redirect_url": "/windows/configuration//configure-windows-10-taskbar", "redirect_document_id": true }, { "source_path": "windows/manage/customize-and-export-start-layout.md", -"redirect_url": "/itpro/windows/configure/customize-and-export-start-layout", +"redirect_url": "/windows/configuration//customize-and-export-start-layout", "redirect_document_id": true }, { "source_path": "windows/manage/start-layout-xml-desktop.md", -"redirect_url": "/itpro/windows/configure/start-layout-xml-desktop", +"redirect_url": "/windows/configuration/start-layout-xml-desktop", "redirect_document_id": true }, { "source_path": "windows/manage/start-layout-xml-mobile.md", -"redirect_url": "/itpro/windows/configure/start-layout-xml-mobile", +"redirect_url": "/windows/configuration/mobile-devices/start-layout-xml-mobile", "redirect_document_id": true }, { "source_path": "windows/manage/customize-windows-10-start-screens-by-using-group-policy.md", -"redirect_url": "/itpro/windows/configure/customize-windows-10-start-screens-by-using-group-policy", +"redirect_url": "/windows/configuration/customize-windows-10-start-screens-by-using-group-policy", "redirect_document_id": true }, { @@ -267,72 +267,72 @@ }, { "source_path": "windows/manage/customize-windows-10-start-screens-by-using-mobile-device-management.md", -"redirect_url": "/itpro/windows/configure/customize-windows-10-start-screens-by-using-mobile-device-management", +"redirect_url": "/windows/configuration/customize-windows-10-start-screens-by-using-mobile-device-management", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-testing-scenarios.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-testing-scenarios", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-testing-scenarios", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-1.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-1", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-1", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-2.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-2", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-2", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-3.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-3", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-3", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-4.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-4", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-4", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-5.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-5", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-5", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-scenario-6.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-scenario-6", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-scenario-6", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-o365.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-o365", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-o365", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-crm.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-crm", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-crm", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-powerbi.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-powerbi", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-powerbi", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-voice-commands.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-voice-commands", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-voice-commands", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-policy-settings.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-policy-settings", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-policy-settings", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-feedback.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-feedback", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-feedback", "redirect_document_id": true }, { @@ -347,17 +347,17 @@ }, { "source_path": "windows/manage/changes-to-start-policies-in-windows-10.md", -"redirect_url": "/itpro/windows/configure/changes-to-start-policies-in-windows-10", +"redirect_url": "/windows/configuration/changes-to-start-policies-in-windows-10", "redirect_document_id": true }, { "source_path": "windows/manage/how-it-pros-can-use-configuration-service-providers.md", -"redirect_url": "/itpro/windows/configure/how-it-pros-can-use-configuration-service-providers", +"redirect_url": "/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers", "redirect_document_id": true }, { "source_path": "windows/manage/lock-down-windows-10.md", -"redirect_url": "/itpro/windows/configure/index", +"redirect_url": "/windows/configuration/index", "redirect_document_id": true }, { @@ -372,112 +372,112 @@ }, { "source_path": "windows/deploy/provisioning-how-it-works.md", -"redirect_url": "/itpro/windows/configure/provisioning-how-it-works", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-how-it-works", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-install-icd.md", -"redirect_url": "/itpro/windows/configure/provisioning-install-icd", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-install-icd", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-create-package.md", -"redirect_url": "/itpro/windows/configure/provisioning-create-package", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-create-package", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-apply-package.md", -"redirect_url": "/itpro/windows/configure/provisioning-apply-package", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-apply-package", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-uninstall-package.md", -"redirect_url": "/itpro/windows/configure/provisioning-uninstall-package", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-uninstall-package", "redirect_document_id": true }, { "source_path": "windows/deploy/provision-pcs-for-initial-deployment.md", -"redirect_url": "/itpro/windows/configure/provision-pcs-for-initial-deployment", +"redirect_url": "/windows/configuration/provisioning-packages/provision-pcs-for-initial-deployment", "redirect_document_id": true }, { "source_path": "windows/deploy/provision-pcs-with-apps-and-certificates.md", -"redirect_url": "/itpro/windows/configure/provision-pcs-with-apps", +"redirect_url": "/windows/configuration/provisioning-packages/provision-pcs-with-apps", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-script-to-install-app.md", -"redirect_url": "/itpro/windows/configure/provisioning-script-to-install-app", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-script-to-install-app", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-nfc.md", -"redirect_url": "/itpro/windows/configure/provisioning-nfc", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-nfc", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-command-line.md", -"redirect_url": "/itpro/windows/configure/provisioning-command-line", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-command-line", "redirect_document_id": true }, { "source_path": "windows/deploy/provisioning-multivariant.md", -"redirect_url": "/itpro/windows/configure/provisioning-multivariant", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-multivariant", "redirect_document_id": true }, { "source_path": "windows/keep-secure/create-edp-policy-using-intune.md", -"redirect_url": "/itpro/windows/keep-secure/create-wip-policy-using-intune", +"redirect_url": "/windows/threat-protection/windows-information-protection/create-wip-policy-using-intune", "redirect_document_id": true }, { "source_path": "windows/keep-secure/create-edp-policy-using-sccm.md", -"redirect_url": "/itpro/windows/keep-secure/create-wip-policy-using-sccm", +"redirect_url": "/windows/threat-protection/windows-information-protection/create-wip-policy-using-sccm", "redirect_document_id": true }, { "source_path": "windows/keep-secure/create-vpn-and-edp-policy-using-intune.md", -"redirect_url": "/itpro/windows/keep-secure/create-vpn-and-wip-policy-using-intune", +"redirect_url": "/windows/threat-protection/windows-information-protection/create-vpn-and-wip-policy-using-intune", "redirect_document_id": true }, { "source_path": "windows/keep-secure/hello-enable-phone-signin.md", -"redirect_url": "/itpro/windows/keep-secure/hello-identity-verification", +"redirect_url": "/windows/access-protection/hello-for-business/hello-identity-verification", "redirect_document_id": false }, { "source_path": "windows/keep-secure/deploy-edp-policy-using-intune.md", -"redirect_url": "/itpro/windows/keep-secure/deploy-wip-policy-using-intune", +"redirect_url": "/windows/threat-protection/windows-information-protection/deploy-wip-policy-using-intune", "redirect_document_id": true }, { "source_path": "windows/keep-secure/guidance-and-best-practices-edp.md", -"redirect_url": "/itpro/windows/keep-secure/guidance-and-best-practices-wip", +"redirect_url": "/windows/threat-protection/windows-information-protection/guidance-and-best-practices-wip", "redirect_document_id": true }, { "source_path": "windows/keep-secure/overview-create-edp-policy.md", -"redirect_url": "/itpro/windows/keep-secure/overview-create-wip-policy", +"redirect_url": "/windows/threat-protection/windows-information-protection/overview-create-wip-policy", "redirect_document_id": true }, { "source_path": "windows/keep-secure/protect-enterprise-data-using-edp.md", -"redirect_url": "/itpro/windows/keep-secure/protect-enterprise-data-using-wip", +"redirect_url": "/windows/threat-protection/windows-information-protection/protect-enterprise-data-using-wip", "redirect_document_id": true }, { "source_path": "windows/keep-secure/testing-scenarios-for-edp.md", -"redirect_url": "/itpro/windows/keep-secure/testing-scenarios-for-wip", +"redirect_url": "/windows/threat-protection/windows-information-protection/testing-scenarios-for-wip", "redirect_document_id": true }, { "source_path": "windows/keep-secure/wip-enterprise-overview.md", -"redirect_url": "/itpro/windows/keep-secure/protect-enterprise-data-using-wip", +"redirect_url": "/windows/threat-protection/windows-information-protection/protect-enterprise-data-using-wip", "redirect_document_id": false }, { "source_path": "windows/keep-secure/enlightened-microsoft-apps-and-edp.md", -"redirect_url": "/itpro/windows/keep-secure/enlightened-microsoft-apps-and-wip", +"redirect_url": "/windows/threat-protection/windows-information-protection/enlightened-microsoft-apps-and-wip", "redirect_document_id": true }, { @@ -487,22 +487,22 @@ }, { "source_path": "windows/deploy/upgrade-analytics-prepare-your-environment.md", -"redirect_url": "/itpro/windows/deploy/upgrade-analytics-identify-apps", +"redirect_url": "/windows/deployment/upgrade/upgrade-analytics-identify-apps", "redirect_document_id": true }, { "source_path": "windows/deploy/upgrade-analytics-release-notes.md", -"redirect_url": "/itpro/windows/deploy/upgrade-analytics-requirements", +"redirect_url": "/windows/deployment/upgrade/upgrade-analytics-requirements", "redirect_document_id": true }, { "source_path": "windows/deploy/upgrade-analytics-review-site-discovery.md", -"redirect_url": "/itpro/windows/deploy/upgrade-analytics-additional-insights", +"redirect_url": "/windows/deployment/upgrade/upgrade-analytics-additional-insights", "redirect_document_id": true }, { "source_path": "windows/keep-secure/additional-configuration-windows-advanced-threat-protection.md", -"redirect_url": "/itpro/windows/keep-secure/configure-endpoints-windows-defender-advanced-threat-protection", +"redirect_url": "/windows/threat-protection/windows-defender-atp/configure-endpoints-windows-defender-advanced-threat-protection", "redirect_document_id": true }, { @@ -512,27 +512,27 @@ }, { "source_path": "windows/keep-secure/creating-a-device-guard-policy-for-signed-apps.md", -"redirect_url": "/itpro/windows/keep-secure/device-guard-deployment-guide", +"redirect_url": "/windows/device-security/device-guard/device-guard-deployment-guide", "redirect_document_id": true }, { "source_path": "windows/keep-secure/device-guard-certification-and-compliance.md", -"redirect_url": "/itpro/windows/keep-secure/device-guard-deployment-guide", +"redirect_url": "/windows/device-security/device-guard/device-guard-deployment-guide", "redirect_document_id": false }, { "source_path": "windows/keep-secure/enable-phone-signin-to-pc-and-vpn.md", -"redirect_url": "/itpro/windows/keep-secure/hello-enable-phone-signin", +"redirect_url": "/windows/access-protection/hello-for-business/hello-enable-phone-signin", "redirect_document_id": true }, { "source_path": "windows/keep-secure/getting-apps-to-run-on-device-guard-protected-devices.md", -"redirect_url": "/itpro/windows/keep-secure/device-guard-deployment-guide", +"redirect_url": "/windows/device-security/device-guard/device-guard-deployment-guide", "redirect_document_id": false }, { "source_path": "windows/keep-secure/implement-microsoft-passport-in-your-organization.md", -"redirect_url": "/itpro/windows/keep-secure/hello-manage-in-organization", +"redirect_url": "/windows/access-protection/hello-for-business/hello-manage-in-organization", "redirect_document_id": true }, { @@ -542,47 +542,47 @@ }, { "source_path": "windows/keep-secure/microsoft-passport-and-password-changes.md", -"redirect_url": "/itpro/windows/keep-secure/hello-and-password-changes", +"redirect_url": "/windows/access-protection/hello-for-business/hello-and-password-changes", "redirect_document_id": true }, { "source_path": "windows/keep-secure/microsoft-passport-errors-during-pin-creation.md", -"redirect_url": "/itpro/windows/keep-secure/hello-errors-during-pin-creation", +"redirect_url": "/windows/access-protection/hello-for-business/hello-errors-during-pin-creation", "redirect_document_id": true }, { "source_path": "windows/keep-secure/microsoft-passport-guide.md", -"redirect_url": "/itpro/windows/keep-secure/hello-identity-verification", +"redirect_url": "/windows/access-protection/hello-for-business/hello-identity-verification", "redirect_document_id": false }, { "source_path": "windows/keep-secure/monitor-onboarding-windows-advanced-threat-protection.md", -"redirect_url": "/itpro/windows/keep-secure/configure-endpoints-windows-defender-advanced-threat-protection", +"redirect_url": "/windows/threat-protection/windows-defender-atp/configure-endpoints-windows-defender-advanced-threat-protection", "redirect_document_id": false }, { "source_path": "windows/keep-secure/passport-event-300.md", -"redirect_url": "/itpro/windows/keep-secure/hello-event-300", +"redirect_url": "/windows/access-protection/hello-for-business/hello-event-300", "redirect_document_id": true }, { "source_path": "windows/keep-secure/prepare-people-to-use-microsoft-passport.md", -"redirect_url": "/itpro/windows/keep-secure/hello-prepare-people-to-use", +"redirect_url": "/windows/access-protection/hello-for-business/hello-prepare-people-to-use", "redirect_document_id": true }, { "source_path": "windows/keep-secure/why-a-pin-is-better-than-a-password.md", -"redirect_url": "/itpro/windows/keep-secure/hello-why-pin-is-better-than-password", +"redirect_url": "/windows/access-protection/hello-for-business/hello-why-pin-is-better-than-password", "redirect_document_id": true }, { "source_path": "windows/keep-secure/windows-hello-in-enterprise.md", -"redirect_url": "/itpro/windows/keep-secure/hello-biometrics-in-enterprise", +"redirect_url": "/windows/access-protection/hello-for-business/hello-biometrics-in-enterprise", "redirect_document_id": true }, { "source_path": "windows/manage/app-inventory-managemement-windows-store-for-business.md", -"redirect_url": "/itpro/windows/manage/app-inventory-management-windows-store-for-business", +"redirect_url": "/microsoft-store/app-inventory-management-windows-store-for-business", "redirect_document_id": true }, { @@ -592,37 +592,37 @@ }, { "source_path": "windows/manage/appv-accessibility.md", -"redirect_url": "/itpro/windows/manage/appv-getting-started", +"redirect_url": "/windows/application-management/app-v/appv-getting-started", "redirect_document_id": true }, { "source_path": "windows/manage/appv-accessing-the-client-management-console.md", -"redirect_url": "/itpro/windows/manage/appv-using-the-client-management-console", +"redirect_url": "/windows/application-management/app-v/appv-using-the-client-management-console", "redirect_document_id": true }, { "source_path": "windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md", -"redirect_url": "/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client", +"redirect_url": "/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client", "redirect_document_id": true }, { "source_path": "windows/manage/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md", -"redirect_url": "/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client", +"redirect_url": "/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client", "redirect_document_id": false }, { "source_path": "windows/manage/appv-planning-for-migrating-from-a-previous-version-of-appv.md", -"redirect_url": "/itpro/windows/manage/appv-migrating-to-appv-from-a-previous-version", +"redirect_url": "/windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version", "redirect_document_id": true }, { "source_path": "windows/manage/configure-windows-10-devices-to-stop-data-flow-to-microsoft.md", -"redirect_url": "/itpro/windows/configure/manage-connections-from-windows-operating-system-components-to-microsoft-services", +"redirect_url": "/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services", "redirect_document_id": true }, { "source_path": "windows/manage/disconnect-your-organization-from-microsoft.md", -"redirect_url": "/itpro/windows/configure/manage-connections-from-windows-operating-system-components-to-microsoft-services", +"redirect_url": "/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services", "redirect_document_id": false }, { @@ -632,132 +632,132 @@ }, { "source_path": "windows/manage/manage-cortana-in-enterprise.md", -"redirect_url": "/windows/configuration/cortana-at-work-overview", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-overview", "redirect_document_id": true }, { "source_path": "windows/manage/cortana-at-work-overview.md", -"redirect_url": "/itpro/windows/configure/cortana-at-work-overview", +"redirect_url": "/windows/configuration/cortana-at-work/cortana-at-work-overview", "redirect_document_id": false }, { "source_path": "windows/manage/manage-inventory-windows-store-for-business.md", -"redirect_url": "/itpro/windows/manage/app-inventory-managemement-windows-store-for-business", +"redirect_url": "/microsoft-store/app-inventory-managemement-windows-store-for-business", "redirect_document_id": true }, { "source_path": "windows/manage/uev-accessibility.md", -"redirect_url": "/itpro/windows/manage/uev-for-windows", +"redirect_url": "/windows/configuration/ue-v/uev-for-windows", "redirect_document_id": true }, { "source_path": "windows/manage/uev-privacy-statement.md", -"redirect_url": "/itpro/windows/manage/uev-security-considerations", +"redirect_url": "/windows/configuration/ue-v/uev-security-considerations", "redirect_document_id": true }, { "source_path": "windows/plan/act-community-ratings-and-process.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": true }, { "source_path": "windows/plan/act-database-configuration.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-database-migration.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-deployment-options.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-glossary.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/activating-and-closing-windows-in-acm.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-lps-share-permissions.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-operatingsystem-application-report.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-operatingsystem-computer-report.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-operatingsystem-device-report.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-product-and-documentation-resources.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-settings-dialog-box-preferences-tab.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-settings-dialog-box-settings-tab.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-toolbar-icons-in-acm.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-tools-packages-and-services.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/act-user-interface-reference.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/adding-or-editing-an-issue.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/adding-or-editing-a-solution.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/analyzing-your-compatibility-data.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/application-dialog-box.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/categorizing-your-compatibility-data.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { @@ -767,77 +767,77 @@ }, { "source_path": "windows/plan/common-compatibility-issues.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/compatibility-monitor-users-guide.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/computer-dialog-box.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/configuring-act.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/creating-and-editing-issues-and-solutions.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/creating-an-enterprise-environment-for-compatibility-testing.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/creating-an-inventory-collector-package.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/creating-a-runtime-analysis-package.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/customizing-your-report-views.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/data-sent-through-the-microsoft-compatibility-exchange.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/deciding-whether-to-fix-an-application-or-deploy-a-workaround.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/deciding-which-applications-to-test.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/deleting-a-data-collection-package.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/deploying-an-inventory-collector-package.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/deploying-a-runtime-analysis-package.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { @@ -847,27 +847,27 @@ }, { "source_path": "windows/plan/example-filter-queries.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/exporting-a-data-collection-package.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/filtering-your-compatibility-data.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/fixing-compatibility-issues.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/identifying-computers-for-inventory-collection.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { @@ -877,77 +877,77 @@ }, { "source_path": "windows/plan/internet-explorer-web-site-report.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/labeling-data-in-acm.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/log-file-locations-for-data-collection-packages.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/managing-your-data-collection-packages.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/organizational-tasks-for-each-report-type.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/organizing-your-compatibility-data.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/prioritizing-your-compatibility-data.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/ratings-icons-in-acm.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/resolving-an-issue.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/saving-opening-and-exporting-reports.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/selecting-the-send-and-receive-status-for-an-application.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/selecting-your-compatibility-rating.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/selecting-your-deployment-status.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/sending-and-receiving-compatibility-data.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/settings-for-acm.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { @@ -957,72 +957,72 @@ }, { "source_path": "windows/plan/software-requirements-for-act.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/software-requirements-for-rap.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/taking-inventory-of-your-organization.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/testing-compatibility-on-the-target-platform.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/troubleshooting-act.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/troubleshooting-act-database-issues.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/troubleshooting-the-act-configuration-wizard.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/troubleshooting-the-act-log-processing-service.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/using-act.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/using-compatibility-monitor-to-send-feedback.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/viewing-your-compatibility-reports.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/websiteurl-dialog-box.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/welcome-to-act.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { "source_path": "windows/plan/whats-new-in-act-60.md", -"redirect_url": "/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-readiness", +"redirect_url": "/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness", "redirect_document_id": false }, { @@ -1042,87 +1042,87 @@ }, { "source_path": "windows/whats-new/applocker.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": true }, { "source_path": "windows/whats-new/bitlocker.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": false }, { "source_path": "windows/whats-new/change-history-for-what-s-new-in-windows-10.md", -"redirect_url": "/itpro/windows/whats-new/index", +"redirect_url": "/windows/whats-new/index", "redirect_document_id": true }, { "source_path": "windows/whats-new/credential-guard.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": false }, { "source_path": "windows/whats-new/device-guard-overview.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": false }, { "source_path": "windows/whats-new/device-management.md", -"redirect_url": "/itpro/windows/manage/index", +"redirect_url": "/windows/client-management/index", "redirect_document_id": false }, { "source_path": "windows/whats-new/edge-ie11-whats-new-overview.md", -"redirect_url": "/itpro/microsoft-edge/enterprise-guidance-using-microsoft-edge-and-ie11", +"redirect_url": "/microsoft-edge/deploy/enterprise-guidance-using-microsoft-edge-and-ie11", "redirect_document_id": true }, { "source_path": "windows/whats-new/edp-whats-new-overview.md", -"redirect_url": "/itpro/windows/keep-secure/protect-enterprise-data-using-wip", +"redirect_url": "/windows/threat-protection/windows-information-protection/protect-enterprise-data-using-wip", "redirect_document_id": false }, { "source_path": "windows/whats-new/lockdown-features-windows-10.md", -"redirect_url": "/itpro/windows/configure/lockdown-features-windows-10", +"redirect_url": "/windows/configuration/lockdown-features-windows-10", "redirect_document_id": false }, { "source_path": "windows/whats-new/microsoft-passport.md", -"redirect_url": "/itpro/windows/keep-secure/hello-identity-verification", +"redirect_url": "/windows/access-protection/hello-for-business/hello-identity-verification", "redirect_document_id": false }, { "source_path": "windows/whats-new/new-provisioning-packages.md", -"redirect_url": "/itpro/windows/configuration/provisioning-packages/provisioning-packages", +"redirect_url": "/windows/configuration/provisioning-packages/provisioning-packages", "redirect_document_id": false }, { "source_path": "windows/whats-new/security-auditing.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": false }, { "source_path": "windows/whats-new/trusted-platform-module.md", -"redirect_url": "/itpro/windows/keep-secure/trusted-platform-module-overview", +"redirect_url": "/windows/device-security/tpm/trusted-platform-module-overview", "redirect_document_id": true }, { "source_path": "windows/whats-new/user-account-control.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": false }, { "source_path": "windows/whats-new/windows-spotlight.md", -"redirect_url": "/itpro/windows/configure/windows-spotlight", +"redirect_url": "/windows/configuration/windows-spotlight", "redirect_document_id": true }, { "source_path": "windows/whats-new/windows-store-for-business-overview.md", -"redirect_url": "/itpro/windows/manage/windows-store-for-business-overview", +"redirect_url": "/microsoft-store/windows-store-for-business-overview", "redirect_document_id": true }, { "source_path": "windows/whats-new/windows-update-for-business.md", -"redirect_url": "/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511", +"redirect_url": "/windows/whats-new/whats-new-windows-10-version-1507-and-1511", "redirect_document_id": false }, { @@ -1132,7 +1132,7 @@ }, { "source_path": "windows/whats-new/security.md", -"redirect_url": "/itpro/windows/keep-secure/overview-of-threat-mitigations-in-windows-10", +"redirect_url": "/windows/threat-protection/overview-of-threat-mitigations-in-windows-10", "redirect_document_id": false }, { From 755b8c2b8ceceb5b605950e675ab350b84cd0f3f Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 15:37:44 -0700 Subject: [PATCH 18/42] replaced font with style:font-size --- .../upgrade-readiness-deployment-script.md | 30 ++++++------------- 1 file changed, 9 insertions(+), 21 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 11e09d889a..97c8f28afa 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -114,26 +114,26 @@ The deployment script displays the following exit codes to let you know if it wa - - + - + - + @@ -180,7 +180,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +200,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -305,15 +305,3 @@ The deployment script displays the following exit codes to let you know if it wa
8Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** + Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** +
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
> 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		 Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>
Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
> 		The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		 This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** - or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
> + or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		 For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
Check the logs for the exception message and HResult.
- -| Exit code | Meaning | Suggested fix | -|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 0 | Success | N/A | -| 1 | Unexpected error occurred while executing the script. | The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again. | -| 2 | Error when logging to console. | Try changing the $logMode value to **1** and try again.$logMode value 1 logs to both console and file. | -| 3 | Error when logging to console and file. $logMode = 1. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. | -| 4 | Error when logging to file. $logMode = 2. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. | -| 5 | Error when logging to console and file. $logMode = unknown. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.< | -| 6 | The commercialID parameter is set to unknown. Modify the runConfig.bat file to set the CommercialID value. | See [Generate your Commercial ID key](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace. | -| 8 | Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**,Verify that the context under which the script in running has access to the registry key. | -| 9 | The script failed to write Commercial Id to registry.,Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** | Verify that the context under which the script in running has access to the registry key.| From 8f1741f9bf41b00192a7d7986acb4fe7488ffd97 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 15:49:35 -0700 Subject: [PATCH 19/42] trying font size xxsmall --- .../upgrade-readiness-deployment-script.md | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 97c8f28afa..f9206c5c0a 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,8 +70,8 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. -
- +
+
@@ -114,26 +114,26 @@ The deployment script displays the following exit codes to let you know if it wa - - + - + - + @@ -180,7 +180,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +200,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +280,8 @@ The deployment script displays the following exit codes to let you know if it wa - + From bce245227f01c72753fee2a4a32cd5fca15c0394 Mon Sep 17 00:00:00 2001 From: John Tobin Date: Wed, 26 Apr 2017 16:06:02 -0700 Subject: [PATCH 20/42] Add new topic:Credential Guard Known Issues --- windows/access-protection/TOC.md | 2 +- .../credential-guard-known-issues.md | 34 +++++++++++++++++++ .../credential-guard-manage.md | 3 +- 3 files changed, 36 insertions(+), 3 deletions(-) create mode 100644 windows/access-protection/credential-guard/credential-guard-known-issues.md diff --git a/windows/access-protection/TOC.md b/windows/access-protection/TOC.md index 47adc1005f..57dc050f50 100644 --- a/windows/access-protection/TOC.md +++ b/windows/access-protection/TOC.md @@ -24,7 +24,7 @@ ### [Credential Guard protection limits](credential-guard/credential-guard-protection-limits.md) ### [Considerations when using Credential Guard](credential-guard/credential-guard-considerations.md) ### [Credential Guard: Additional mitigations](credential-guard/additional-mitigations.md) - +### [Credential Guard: Known issues](credential-manager-known-issues.md) ## [Protect Remote Desktop credentials with Remote Credential Guard](remote-credential-guard.md) diff --git a/windows/access-protection/credential-guard/credential-guard-known-issues.md b/windows/access-protection/credential-guard/credential-guard-known-issues.md new file mode 100644 index 0000000000..5499b6cfdd --- /dev/null +++ b/windows/access-protection/credential-guard/credential-guard-known-issues.md @@ -0,0 +1,34 @@ +--- +title: Credential Guard Known issues (Windows 10) +description: Credential Guard - Known issues in Windows 10 Enterprise +ms.prod: w10 +ms.mktglfcycl: explore +ms.sitesec: library +ms.pagetype: security +localizationpriority: high +author: brianlic-msft +--- + +# Credential Guard: Known issues + +**Applies to** +- Windows 10 +- Windows Server 2016 + +Credential Guard has certain requirements for applications. Credential Guard blocks specific authentication capabilities. Therefore applications that require such capabilities will not function when Credential Guard is enabled. For further information, see [Application requirements](https://docs.microsoft.com/en-us/windows/access-protection/credential-guard/credential-guard-requirements#application-requirements). + +The following known issues have been fixed by servicing releases made available in the Cumulative Security Updates for April 2017: + +• KB4015217: [Credential Guard generates double bad password count on Active Directory domain-joined Windows 10 machines](https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217) + +This issue can potentially lead to unexpected account lockouts. +See also Knowledge Base articles [KB4015219](https://support.microsoft.com/en-us/help/4015219/windows-10-update-kb4015219) and +[KB4015221](https://support.microsoft.com/en-us/help/4015221/windows-10-update-kb4015221). + +In addition, products that connect to Virtualization Based Security (VBS) protected processes can cause Credential Guard-enabled Windows 10 clients to exhibit high CPU utilization. For further information, see the following Knowledge Base articles: + +• KB88869: [Windows 10 machines exhibit high CPU usage with McAfee Application and Change Control (MACC) installed when Credential Guard is enabled](https://kc.mcafee.com/corporate/index?page=content&id=KB88869) + +• [Installing AppSense Environment Manager on Windows 10 machines causes LsaIso.exe to exhibit high CPU usage when Credential Guard is enabled](http://www.appsense.com/kb/160525073917945) * + + *Registration required to access this article. diff --git a/windows/access-protection/credential-guard/credential-guard-manage.md b/windows/access-protection/credential-guard/credential-guard-manage.md index 44be2404c6..9396f2dd47 100644 --- a/windows/access-protection/credential-guard/credential-guard-manage.md +++ b/windows/access-protection/credential-guard/credential-guard-manage.md @@ -15,8 +15,7 @@ author: brianlic-msft - Windows 10 - Windows Server 2016 -Prefer video? See [Protecting privileged users with Credential Guard](https://mva.microsoft.com/en-us/training-courses/deep-dive-into-credential-guard-16651?l=JNbjYMJyC_8104300474) -in the Deep Dive into Credential Guard video series. +Prefer video? See [Credential Guard Deployment](https://mva.microsoft.com/en-us/training-courses/deep-dive-into-credential-guard-16651?l=sRcyvLJyC_3304300474) in the Deep Dive into Credential Guard video series. ## Enable Credential Guard Credential Guard can be enabled either by using [Group Policy](#enable-credential-guard-by-using-group-policy), the [registry](#enable-credential-guard-by-using-the-registry), or the Device Guard and Credential Guard [hardware readiness tool](#hardware-readiness-tool). Credential Guard can also protect secrets in a Hyper-V virtual machine, just as it would on a physical machine. From 5d9f0530b051beb35f1a377b4a78cfa43f8f4503 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 16:35:38 -0700 Subject: [PATCH 21/42] fixed font size in table --- .../upgrade-readiness-deployment-script.md | 25 +++++++++---------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index f9206c5c0a..2d803f1012 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -68,9 +68,8 @@ To run the Upgrade Readiness deployment script: 5. After you finish editing the parameters in RunConfig.bat, you are ready to run the script. If you are using the Pilot version, run RunConfig.bat from an elevated command prompt. If you are using the Deployment version, use ConfigMgr or other software deployment service to run RunConfig.bat as system. -The deployment script displays the following exit codes to let you know if it was successful, or if an error was encountered. +The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. -
Exit code Meaning
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
> + 		Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
> +
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>
Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
> 		An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
 The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
> - or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
>		For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
+ or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
 For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
@@ -84,7 +83,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -114,26 +113,26 @@ The deployment script displays the following exit codes to let you know if it wa - - + - + - + @@ -180,7 +179,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -200,7 +199,7 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -280,8 +279,8 @@ The deployment script displays the following exit codes to let you know if it wa - + @@ -304,4 +303,4 @@ The deployment script displays the following exit codes to let you know if it wa
Exit code
1 Unexpected error occurred while executiEng the script. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409) from the download center and try again. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966) from the download center and try again.
2
8Failure to create registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The Commercial Id property is set at the following registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+ 		Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9 The script failed to write Commercial Id to registry. -
Error creating or updating registry key: **CommercialId** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
+
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11 Function **SetupCommercialId** failed with an unexpected exception.The **SetupCommercialId** function updates the Commercial Id at the registry key path:
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**

Verify that the configuration script has access to this location.		The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at
**HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser**
An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path
**HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**
- or
**HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** + or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
-
+ From d34ac0bef086ea31977651c7a4dde455dc93b4ff Mon Sep 17 00:00:00 2001 From: John Tobin Date: Wed, 26 Apr 2017 16:41:19 -0700 Subject: [PATCH 22/42] Fix TOC file name discrepancy --- windows/access-protection/TOC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/access-protection/TOC.md b/windows/access-protection/TOC.md index 57dc050f50..4691b7553c 100644 --- a/windows/access-protection/TOC.md +++ b/windows/access-protection/TOC.md @@ -24,7 +24,7 @@ ### [Credential Guard protection limits](credential-guard/credential-guard-protection-limits.md) ### [Considerations when using Credential Guard](credential-guard/credential-guard-considerations.md) ### [Credential Guard: Additional mitigations](credential-guard/additional-mitigations.md) -### [Credential Guard: Known issues](credential-manager-known-issues.md) +### [Credential Guard: Known issues](credential-guard-known-issues.md) ## [Protect Remote Desktop credentials with Remote Credential Guard](remote-credential-guard.md) From 81a4d4db2809f7ad773008456a2bc1f6633048a3 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 16:49:01 -0700 Subject: [PATCH 23/42] added font size around the table to try to make text smaller --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 2d803f1012..dbee3d45e1 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,6 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. + @@ -303,4 +304,4 @@ The deployment script displays the following exit codes to let ddfyou know if it
Exit codeFunction **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- + From 7bbd6813fbf51144f1f2d4403d07727efe853cc1 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Wed, 26 Apr 2017 16:50:45 -0700 Subject: [PATCH 24/42] Update TOC.md --- windows/access-protection/TOC.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/access-protection/TOC.md b/windows/access-protection/TOC.md index 4691b7553c..a07a391e84 100644 --- a/windows/access-protection/TOC.md +++ b/windows/access-protection/TOC.md @@ -1,4 +1,4 @@ -# [Access protection](access-control/access-control.md) +credential-guard# [Access protection](access-control/access-control.md) ## [Access Control Overview](access-control/access-control.md) ### [Dynamic Access Control Overview](access-control/dynamic-access-control.md) @@ -24,7 +24,7 @@ ### [Credential Guard protection limits](credential-guard/credential-guard-protection-limits.md) ### [Considerations when using Credential Guard](credential-guard/credential-guard-considerations.md) ### [Credential Guard: Additional mitigations](credential-guard/additional-mitigations.md) -### [Credential Guard: Known issues](credential-guard-known-issues.md) +### [Credential Guard: Known issues](credential-guard/credential-guard-known-issues.md) ## [Protect Remote Desktop credentials with Remote Credential Guard](remote-credential-guard.md) From 79ae15f447c16e1285f50386ad0e43beb7e1bef2 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Wed, 26 Apr 2017 17:02:44 -0700 Subject: [PATCH 25/42] Update TOC.md --- windows/access-protection/TOC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/access-protection/TOC.md b/windows/access-protection/TOC.md index a07a391e84..16b848c11f 100644 --- a/windows/access-protection/TOC.md +++ b/windows/access-protection/TOC.md @@ -1,4 +1,4 @@ -credential-guard# [Access protection](access-control/access-control.md) +# [Access protection](access-control/access-control.md) ## [Access Control Overview](access-control/access-control.md) ### [Dynamic Access Control Overview](access-control/dynamic-access-control.md) From ed6822497e30a1f9d6ba5c957da7e28c7a2c5a40 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 17:06:24 -0700 Subject: [PATCH 26/42] wrapping table in div tag to try to get smaller font --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index dbee3d45e1..c62727df3e 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. - +
@@ -304,4 +304,4 @@ The deployment script displays the following exit codes to let ddfyou know if it
Exit codeFunction **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
- +
From c27b6aeb936f67002088dcf96970d90014d192c8 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 17:38:27 -0700 Subject: [PATCH 27/42] fixed typo in div --- .../deployment/upgrade/upgrade-readiness-deployment-script.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index c62727df3e..2b9e9ed18b 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -70,7 +70,7 @@ To run the Upgrade Readiness deployment script: The deployment script displays the following exit codes to let ddfyou know if it was successful, or if an error was encountered. -
+
From 54af9e6347fc39ce9009c34b5d15a8dd63f42737 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 26 Apr 2017 18:07:07 -0700 Subject: [PATCH 28/42] collapsed three column table into 2 --- .../upgrade-readiness-deployment-script.md | 134 ++++++------------ 1 file changed, 45 insertions(+), 89 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md index 2b9e9ed18b..2e289b8a5b 100644 --- a/windows/deployment/upgrade/upgrade-readiness-deployment-script.md +++ b/windows/deployment/upgrade/upgrade-readiness-deployment-script.md @@ -73,235 +73,191 @@ The deployment script displays the following exit codes to let ddfyou know if it
Exit code
- - + - - + - - + - - + - - + - - + - - + - - + - - + - - - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - - - + - - + - - + - - +
Exit codeMeaningExit code and meaning Suggested fix
0Success
0 - Success N/A
1Unexpected error occurred while executiEng the script.1 - Unexpected error occurred while executiEng the script. The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966) from the download center and try again.
2Error when logging to console. $logMode = 0.
(console only)		2 - Error when logging to console. $logMode = 0.
(console only)		 Try changing the $logMode value to **1** and try again.
$logMode value 1 logs to both console and file.
3Error when logging to console and file. $logMode = 1.3 - Error when logging to console and file. $logMode = 1. Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
4Error when logging to file. $logMode = 2.4 - Error when logging to file. $logMode = 2. Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
5Error when logging to console and file. $logMode = unknown.5 - Error when logging to console and file. $logMode = unknown. Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location.
6The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value.		6 - The commercialID parameter is set to unknown.
Modify the runConfig.bat file to set the CommercialID value.		 The value for parameter in the runconfig.bat file should match the Commercial ID key for your workspace.
See [Generate your Commercial ID key](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#generate-your-commercial-id-key) for instructions on generating a Commercial ID key for your workspace.
8Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**8 - Failure to create registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** The Commercial Id property is set at the following registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the context under which the script in running has access to the registry key.
9The script failed to write Commercial Id to registry. + 9 - The script failed to write Commercial Id to registry.
Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** 		Verify that the context under which the script in running has access to the registry key.
10Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**10 - Error when writing **CommercialDataOptIn** to the registry at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** Verify that the deployment script is running in a context that has access to the registry key.
11Function **SetupCommercialId** failed with an unexpected exception.11 - Function **SetupCommercialId** failed with an unexpected exception. The **SetupCommercialId** function updates the Commercial Id at the registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**
Verify that the configuration script has access to this location.
12Can’t connect to Microsoft - Vortex. Check your network/proxy settings.12 - Can’t connect to Microsoft - Vortex. Check your network/proxy settings. **Http Get** on the end points did not return a success exit code.
For Windows 10, connectivity is verified by connecting to https://v10.vortex-win.data.microsoft.com/health/keepalive.
For previous operating systems, connectivity is verified by connecting to https://vortex-win.data.microsoft.com/health/keepalive.
If there is an error verifying connectivity, this will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
13Can’t connect to Microsoft - setting. 13 - Can’t connect to Microsoft - setting. An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
14Can’t connect to Microsoft - compatexchange.14 - Can’t connect to Microsoft - compatexchange. An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).
15Function CheckVortexConnectivity failed with an unexpected exception.15 - Function CheckVortexConnectivity failed with an unexpected exception. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). Check the logs for the exception message and the HResult.
16The computer requires a reboot before running the script.16 - The computer requires a reboot before running the script. A reboot is required to complete the installation of the compatibility update and related KBs. Reboot the computer before running the Upgrade Readiness deployment script.
17Function **CheckRebootRequired** failed with an unexpected exception.17 - Function **CheckRebootRequired** failed with an unexpected exception. A reboot is required to complete installation of the compatibility update and related KBs. Check the logs for the exception message and the HResult.
18Appraiser KBs not installed or **appraiser.dll** not found.18 - Appraiser KBs not installed or **appraiser.dll** not found. Either the Appraiser KBs are not installed, or the **appraiser.dll** file was not found. For more information, see appraiser telemetry events and fields information in the [Data collection](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-get-started#data-collection-and-privacy) and privacy topic.
19Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception.19 - Function **CheckAppraiserKB**, which checks the compatibility update KBs, failed with unexpected exception. Check the logs for the Exception message and HResult. The script will not run further if this error is not fixed.
20An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** 20 - An error occurred when creating or updating the registry key **RequestAllAppraiserVersions** at **HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser** The registry key is required for data collection to work correctly. Verify that the script is running in a context that has access to the registry key.
21Function **SetRequestAllAppraiserVersions** failed with an unexpected exception.21 - Function **SetRequestAllAppraiserVersions** failed with an unexpected exception. Check the logs for the exception message and HResult.
22**RunAppraiser** failed with unexpected exception.22 - **RunAppraiser** failed with unexpected exception. Check the logs for the exception message and HResult. Check the **%windir%\System32*8 directory for the file **CompatTelRunner.exe**. If the file does not exist, reinstall the required compatibility updates which include this file, and check your organization's Group Policy to verify it does not remove this file.
23Error finding system variable **%WINDIR%**.23 - Error finding system variable **%WINDIR%**. Verify that this environment variable is configured on the computer.
24The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**24 - The script failed when writing **IEDataOptIn** to the registry. An error occurred when creating registry key **IEOptInLevel** at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** This is a required registry key for IE data collection to work correctly. Verify that the deployment script in running in a context that has access to the registry key. Check the logs for the exception message and HResult.
25The function **SetIEDataOptIn** failed with unexpected exception.25 - The function **SetIEDataOptIn** failed with unexpected exception. Check the logs for the exception message and HResult.
26The operating system is Server or LTSB SKU.26 - The operating system is Server or LTSB SKU. The script does not support Server or LTSB SKUs.
27The script is not running under **System** account.27 - The script is not running under **System** account. The Upgrade Readiness configuration script must be run as **System**.
28Could not create log file at the specified **logPath**.28 - Could not create log file at the specified **logPath**. Make sure the deployment script has access to the location specified in the **logPath** parameter.
29Connectivity check failed for proxy authentication. 29 - Connectivity check failed for proxy authentication. Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting.
The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled).
For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
30Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled.30 - Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled. The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled).
For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).
31There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. 31 - There is more than one instance of the Upgrade Readiness data collector running at the same time on this computer. Use the Windows Task Manager to check if **CompatTelRunner.exe** is running, and wait until it has completed to rerun the script. The Upgrade Readiness task is scheduled to run daily at 3 a.m.
32Appraiser version on the machine is outdated. 32 - Appraiser version on the machine is outdated. The configuration script detected a version of the compatibility update module that is older than the minimum required to correctly collect the data required by Upgrade Readiness solution. Use the latest version of the [compatibility update](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#deploy-the-compatibility-update-and-related-kbs) for Windows 7 SP1/Windows 8.1.
33**CompatTelRunner.exe** exited with an exit code 33 - **CompatTelRunner.exe** exited with an exit code **CompatTelRunner.exe** runs the appraise task on the machine. If it fails, it will provide a specific exit code. The script will return exit code 33 when **CompatTelRunner.exe** itself exits with an exit code. Please check the logs for more details.
34Function **CheckProxySettings** failed with an unexpected exception. 34 - Function **CheckProxySettings** failed with an unexpected exception. Check the logs for the exception message and HResult.>
35Function **CheckAuthProxy** failed with an unexpected exception.35 - Function **CheckAuthProxy** failed with an unexpected exception. Check the logs for the exception message and HResult.
36Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception.36 - Function **CheckAppraiserEndPointsConnectivity** failed with an unexpected exception. Check the logs for the exception message and HResult.
37**Diagnose_internal.cmd** failed with an unexpected exception.37 - **Diagnose_internal.cmd** failed with an unexpected exception. Check the logs for the exception message and HResult.
38Function **Get-SqmID** failed with an unexpected exception. 38 - Function **Get-SqmID** failed with an unexpected exception. Check the logs for the exception message and HResult.
39For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** + 39 - For Windows 10: AllowTelemetry property is not set to 1 or higher at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** or **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** For Windows 10 machines, the **AllowTelemetry** property should be set to 1 or greater to enable data collection. The script will throw an error if this is not true. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
40Function **CheckTelemetryOptIn** failed with an unexpected exception. 40 - Function **CheckTelemetryOptIn** failed with an unexpected exception. Check the logs for the exception message and HResult.
41The script failed to impersonate the currently logged on user. 41 - The script failed to impersonate the currently logged on user. The script mimics the UTC client to collect upgrade readiness data. When auth proxy is set, the UTC client impersonates the logged on user. The script also tries to mimic this, but the process failed.
42Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. 42 - Function **StartImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
43Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception.43 - Function **EndImpersonatingLoggedOnUser** failed with an unexpected exception. Check the logs for the exception message and HResult.
-
+ From 50ce65ade4c289b7078ca10207bbbe0ef8538ab5 Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Thu, 27 Apr 2017 07:09:01 -0700 Subject: [PATCH 29/42] sync --- devices/surface-hub/skype-hybrid-voice.md | 1 + 1 file changed, 1 insertion(+) diff --git a/devices/surface-hub/skype-hybrid-voice.md b/devices/surface-hub/skype-hybrid-voice.md index d930924045..82a57d1aee 100644 --- a/devices/surface-hub/skype-hybrid-voice.md +++ b/devices/surface-hub/skype-hybrid-voice.md @@ -17,3 +17,4 @@ This topic explains how to enable Skype for Business Cloud PBX with on premises If you deployed Skype for Business Cloud PBX with one of the hybrid voice options, please follow the steps below to enable the room account. It is important to create a regular user account first, assign all hybrid voice options and phone numbers and only after this convert the account to a room account. If you do not follow this order you will not be able to assign a hybrid phone number. +1. Create a new user account for Surface Hub. In this example, I will use surfacehub2@adatum.biz account. The account can be created in local active directory and synchronized to the cloud or created directly in the cloud. \ No newline at end of file From 165d57579b6a083ea040e46d44b0e9ad34d8c538 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rodolfo=20Castelo=20M=C3=A9ndez?= Date: Thu, 27 Apr 2017 09:46:12 -0500 Subject: [PATCH 30/42] Update overview-of-threat-mitigations-in-windows-10.md --- .../overview-of-threat-mitigations-in-windows-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/threat-protection/overview-of-threat-mitigations-in-windows-10.md b/windows/threat-protection/overview-of-threat-mitigations-in-windows-10.md index 0f50719dce..a23616e9a6 100644 --- a/windows/threat-protection/overview-of-threat-mitigations-in-windows-10.md +++ b/windows/threat-protection/overview-of-threat-mitigations-in-windows-10.md @@ -56,7 +56,7 @@ Windows 10 mitigations that you can configure are listed in the following two ta | **Windows Defender SmartScreen**
helps prevent
malicious applications
from being downloaded | Windows Defender SmartScreen can check the reputation of a downloaded application by using a service that Microsoft maintains. The first time a user runs an app that originates from the Internet (even if the user copied it from another PC), SmartScreen checks to see if the app lacks a reputation or is known to be malicious, and responds accordingly.

**More information**: [Windows Defender SmartScreen](#windows-defender-smartscreen), later in this topic | | **Credential Guard**
helps keep attackers
from gaining access through
Pass-the-Hash or
Pass-the-Ticket attacks | Credential Guard uses virtualization-based security to isolate secrets, such as NTLM password hashes and Kerberos Ticket Granting Tickets, so that only privileged system software can access them.
Credential Guard is included in Windows 10 Enterprise and Windows Server 2016.

**More information**: [Protect derived domain credentials with Credential Guard](/windows/access-protection/credential-guard/credential-guard) | | **Enterprise certificate pinning**
helps prevent
man-in-the-middle attacks
that leverage PKI | Enterprise certificate pinning enables you to protect your internal domain names from chaining to unwanted certificates or to fraudulently issued certificates. With enterprise certificate pinning, you can “pin” (associate) an X.509 certificate and its public key to its Certification Authority, either root or leaf.

**More information**: [Enterprise Certificate Pinning](/windows/access-protection/enterprise-certificate-pinning) | -| **Device Guard**
helps keep a device
from running malware or
other untrusted apps | Device Guard includes a Code Integrity policy that you create; a whitelist of trusted apps—the only apps allowed to run in your organization. Device Guard also includes a powerful system mitigation called hypervisor-protected code integrity (HVCI), which leverages virtualization-based security (VBS) to protect Windows’ kernel-mode code integrity validation process. HVCI has specific hardware requirements, and works with Code Integrity policies to help stop attacks even if they gain access to the kernel.
Device Guard is included in Windows 10 Enterprise and Windows Server 2016.

**More information**: [Introduction to Device Guard](/windows/access-protection/device-guard/introduction-to-device-guard-virtualization-based-security-and-code-integrity-policies. | +| **Device Guard**
helps keep a device
from running malware or
other untrusted apps | Device Guard includes a Code Integrity policy that you create; a whitelist of trusted apps—the only apps allowed to run in your organization. Device Guard also includes a powerful system mitigation called hypervisor-protected code integrity (HVCI), which leverages virtualization-based security (VBS) to protect Windows’ kernel-mode code integrity validation process. HVCI has specific hardware requirements, and works with Code Integrity policies to help stop attacks even if they gain access to the kernel.
Device Guard is included in Windows 10 Enterprise and Windows Server 2016.

**More information**: [Introduction to Device Guard](/windows/device-security/device-guard/introduction-to-device-guard-virtualization-based-security-and-code-integrity-policies) | | **Windows Defender Antivirus**,
which helps keep devices
free of viruses and other
malware | Windows 10 includes Windows Defender Antivirus, a robust inbox antimalware solution. Windows Defender Antivirus has been significantly improved since it was introduced in Windows 8.

**More information**: [Windows Defender Antivirus](#windows-defender-antivirus), later in this topic | | **Blocking of untrusted fonts**
helps prevent fonts
from being used in
elevation-of-privilege attacks | Block Untrusted Fonts is a setting that allows you to prevent users from loading fonts that are "untrusted" onto your network, which can mitigate elevation-of-privilege attacks associated with the parsing of font files. However, as of Windows 10, version 1703, this mitigation is less important, because font parsing is isolated in an [AppContainer sandbox](https://msdn.microsoft.com/library/windows/desktop/mt595898(v=vs.85).aspx) (for a list describing this and other kernel pool protections, see [Kernel pool protections](#kernel-pool-protections), later in this topic).

**More information**: [Block untrusted fonts in an enterprise](/windows/threat-protection/block-untrusted-fonts-in-enterprise) | | **Memory protections**
help prevent malware
from using memory manipulation
techniques such as buffer
overruns | These mitigations, listed in [Table 2](#table-2), help to protect against memory-based attacks, where malware or other code manipulates memory to gain control of a system (for example, malware that attempts to use buffer overruns to inject malicious executable code into memory. Note:
A subset of apps will not be able to run if some of these mitigations are set to their most restrictive settings. Testing can help you maximize protection while still allowing these apps to run.

**More information**: [Table 2](#table-2), later in this topic | From 3ba5fb49fa905a4991e29eeff6c8f402cf9a2c29 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Thu, 27 Apr 2017 09:40:10 -0700 Subject: [PATCH 31/42] updating breadcrumbs --- education/breadcrumb/toc.yml | 6 +++--- store-for-business/breadcrumb/toc.yml | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/education/breadcrumb/toc.yml b/education/breadcrumb/toc.yml index 84a37555a8..acc2508932 100644 --- a/education/breadcrumb/toc.yml +++ b/education/breadcrumb/toc.yml @@ -2,6 +2,6 @@ tocHref: / topicHref: / items: - - name: Education - tocHref: /education - topicHref: /education/index \ No newline at end of file + - name: Windows + tocHref: /education/windows + topicHref: /education/windows/index \ No newline at end of file diff --git a/store-for-business/breadcrumb/toc.yml b/store-for-business/breadcrumb/toc.yml index 456f809e33..104d0bb7a6 100644 --- a/store-for-business/breadcrumb/toc.yml +++ b/store-for-business/breadcrumb/toc.yml @@ -2,6 +2,6 @@ tocHref: / topicHref: / items: - - name: Windows - tocHref: /windows - topicHref: /windows/windows-10 \ No newline at end of file + - name: Windows Store for Business + tocHref: /microsoft-store + topicHref: /microsoft-store/index \ No newline at end of file From d310e24f4f49a8a7fd84dd0fc47a575955023a4b Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Thu, 27 Apr 2017 09:56:19 -0700 Subject: [PATCH 32/42] put admin tools in TOC --- windows/client-management/TOC.md | 1 + windows/client-management/index.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/client-management/TOC.md b/windows/client-management/TOC.md index 82de2c56b1..f1ecdab931 100644 --- a/windows/client-management/TOC.md +++ b/windows/client-management/TOC.md @@ -1,4 +1,5 @@ # [Manage clients in Windows 10](index.md) +## [Administrative Tools in Windows 10](administrative-tools-in-windows-10.md) ## [Create mandatory user profiles](mandatory-user-profile.md) ## [Connect to remote Azure Active Directory-joined PC](connect-to-remote-aadj-pc.md) ## [Join Windows 10 Mobile to Azure Active Directory](join-windows-10-mobile-to-azure-active-directory.md) diff --git a/windows/client-management/index.md b/windows/client-management/index.md index b26f244d6c..7f532e30a4 100644 --- a/windows/client-management/index.md +++ b/windows/client-management/index.md @@ -17,7 +17,7 @@ Learn about the administrative tools, tasks and best practices for managing Wind | Topic | Description | |---|---| -|[Administrative tools in Windows 10](administrative-tools-in-windows-10.md)| Listing of administrative tools useful for ITPros and advanced users in managing Windows client.| +|[Administrative tools in Windows 10](administrative-tools-in-windows-10.md)| Listing of administrative tools useful for IT pros and advanced users in managing Windows client.| |[Connect to remote AADJ PCs](connect-to-remote-aadj-pc.md)| Instructions for connecting to a remote PC joined to Azure Active Directory (Azure AD)| |[Group policies for enterprise and education editions](group-policies-for-enterprise-and-education-editions.md)| Listing of all group policy settings that apply specifically to Windows 10 Enterprise and Education editions| |[Join Windows 10 Mobile to AAD](join-windows-10-mobile-to-azure-active-directory.md)| Describes the considerations and options for using Windows 10 Mobile with Azure AD in your organization.| From 43f688c3214b0c3e80a48368b4bf6f1ec30d99a9 Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Thu, 27 Apr 2017 10:15:35 -0700 Subject: [PATCH 33/42] fix index description --- windows/client-management/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/index.md b/windows/client-management/index.md index 7f532e30a4..5ee8fc4e71 100644 --- a/windows/client-management/index.md +++ b/windows/client-management/index.md @@ -17,7 +17,7 @@ Learn about the administrative tools, tasks and best practices for managing Wind | Topic | Description | |---|---| -|[Administrative tools in Windows 10](administrative-tools-in-windows-10.md)| Listing of administrative tools useful for IT pros and advanced users in managing Windows client.| +|[Administrative Tools in Windows 10](administrative-tools-in-windows-10.md)| Links to documentation for tools for IT pros and advanced users in the Administrative Tools folder.| |[Connect to remote AADJ PCs](connect-to-remote-aadj-pc.md)| Instructions for connecting to a remote PC joined to Azure Active Directory (Azure AD)| |[Group policies for enterprise and education editions](group-policies-for-enterprise-and-education-editions.md)| Listing of all group policy settings that apply specifically to Windows 10 Enterprise and Education editions| |[Join Windows 10 Mobile to AAD](join-windows-10-mobile-to-azure-active-directory.md)| Describes the considerations and options for using Windows 10 Mobile with Azure AD in your organization.| From e4bf22b5634b63e469ba3bbbef333bf3836bd5cd Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Thu, 27 Apr 2017 11:27:54 -0700 Subject: [PATCH 34/42] remove hybrid voice --- devices/surface-hub/TOC.md | 1 - ...e-and-test-a-device-account-surface-hub.md | 2 +- devices/surface-hub/skype-hybrid-voice.md | 20 ------------------- 3 files changed, 1 insertion(+), 22 deletions(-) delete mode 100644 devices/surface-hub/skype-hybrid-voice.md diff --git a/devices/surface-hub/TOC.md b/devices/surface-hub/TOC.md index 742423081c..a9cde81f15 100644 --- a/devices/surface-hub/TOC.md +++ b/devices/surface-hub/TOC.md @@ -8,7 +8,6 @@ ##### [On-premises deployment (single forest)](on-premises-deployment-surface-hub-device-accounts.md) ##### [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) ##### [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) -##### [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md) ##### [Create a device account using UI](create-a-device-account-using-office-365.md) ##### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) ##### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md) diff --git a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md index c01273b24e..353d6cf6fd 100644 --- a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md +++ b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md @@ -49,7 +49,7 @@ For detailed steps using PowerShell to provision a device account, choose an opt | [On-premises deployment (single-forest)](on-premises-deployment-surface-hub-device-accounts.md) | Your organization has servers that it controls and uses to host Active Directory, Exchange, and Skype for Business (or Lync) in a single-forest environment. | | [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) | Your organization has servers that it controls and uses to host Active Directory, Exchange, and Skype for Business (or Lync) in a multi-forest environment. | | [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Your organization has a mix of services, with some hosted on-premises and some hosted online through Office 365. | -| [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md) | Your organization has Skype for Business home pools and Exchange servers in the cloud, and uses an on-premises pool of Skype for Business 2015 or Cloud Connector edition connected via Public Switched Telephone Network (PSTN). | + If you prefer to use a graphical user interface, some steps can be done using UI instead of PowerShell. For more information, see [Creating a device account using UI](create-a-device-account-using-office-365.md). diff --git a/devices/surface-hub/skype-hybrid-voice.md b/devices/surface-hub/skype-hybrid-voice.md deleted file mode 100644 index 82a57d1aee..0000000000 --- a/devices/surface-hub/skype-hybrid-voice.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Online or hybrid deployment using Skype Hybrid Voice environment (Surface Hub) -description: A Skype Hybrid Voice deployment requires special processing to set up a device account for your Microsoft Surface Hub. -keywords: hybrid deployment, Skype Hybrid Voice, Skype for Business Cloud PBX -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: surfacehub -author: jdeckerms -localizationpriority: medium ---- - -# Online or hybrid deployment using Skype Hybrid Voice environment (Surface Hub) - -This topic explains how to enable Skype for Business Cloud PBX with on premises PSTN connectivity via Cloud Connector Edition or Skype for Business 2015 pool. In this option your Skype for Business home pools and Exchange servers are in the Cloud, however PSTN connected via on premises pool of Skype for Business 2015 or via a Cloud Connector edition. More about different Cloud PBX options is here https://technet.microsoft.com/en-us/library/mt612869.aspx - -If you deployed Skype for Business Cloud PBX with one of the hybrid voice options, please follow the steps below to enable the room account. It is important to create a regular user account first, assign all hybrid voice options and phone numbers and only after this convert the account to a room account. If you do not follow this order you will not be able to assign a hybrid phone number. - - -1. Create a new user account for Surface Hub. In this example, I will use surfacehub2@adatum.biz account. The account can be created in local active directory and synchronized to the cloud or created directly in the cloud. \ No newline at end of file From 0bcee57418036da8bf3bf90e387785c59b2550dc Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Thu, 27 Apr 2017 11:31:05 -0700 Subject: [PATCH 35/42] add link to edu topic --- windows/configuration/set-up-shared-or-guest-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/set-up-shared-or-guest-pc.md b/windows/configuration/set-up-shared-or-guest-pc.md index e93bdd976e..d89c6c3063 100644 --- a/windows/configuration/set-up-shared-or-guest-pc.md +++ b/windows/configuration/set-up-shared-or-guest-pc.md @@ -69,7 +69,7 @@ Shared PC mode exposes a set of customizations to tailor the behavior to your re | Customization: MaintenanceStartTime | By default, the maintenance start time (which is when automatic maintenance tasks run, such as Windows Update) is midnight. You can adjust the start time in this setting by entering a new start time in minutes from midnight. For example, if you want maintenance to begin at 2 AM, enter `120` as the value. | | Customization: MaxPageFileSizeMB | Adjusts the maximum page file size in MB. This can be used to fine-tune page file behavior, especially on low end PCs. | | Customization: RestrictLocalStorage | Set as **True** to restrict the user from saving or viewing local storage when using File Explorer. This setting controls this API: [ShouldAvoidLocalStorage](https://docs.microsoft.com/uwp/api/windows.system.profile.sharedmodesettings) | -| Customization: SetEduPolicies | Set to **True** for PCs that will be used in a school. This setting controls this API: [IsEducationEnvironment](https://docs.microsoft.com/uwp/api/windows.system.profile.educationsettings) | +| Customization: SetEduPolicies | Set to **True** for PCs that will be used in a school. For more information, see [Windows 10 configuration recommendations for education customers](https://docs.microsoft.com/education/windows/configure-windows-for-education). This setting controls this API: [IsEducationEnvironment](https://docs.microsoft.com/uwp/api/windows.system.profile.educationsettings) | | Customization: SetPowerPolicies | When set as **True**:
- Prevents users from changing power settings
- Turns off hibernate
- Overrides all power state transitions to sleep (e.g. lid close) | | Customization: SignInOnResume | This setting specifies if the user is required to sign in with a password when the PC wakes from sleep. | | Customization: SleepTimeout | Specifies all timeouts for when the PC should sleep. Enter the amount of idle time in seconds. If you don't set sleep timeout, the default of 1 hour applies. | From 98e1dcb845a3576da79ed0c7dc69499fe2669e16 Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Thu, 27 Apr 2017 12:11:54 -0700 Subject: [PATCH 36/42] sync --- .../surface-hub/create-and-test-a-device-account-surface-hub.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md index 353d6cf6fd..b06c909230 100644 --- a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md +++ b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md @@ -51,7 +51,7 @@ For detailed steps using PowerShell to provision a device account, choose an opt | [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Your organization has a mix of services, with some hosted on-premises and some hosted online through Office 365. | -If you prefer to use a graphical user interface, some steps can be done using UI instead of PowerShell. +If you prefer to use a graphical user interface (UI), some steps can be done using UI instead of PowerShell. For more information, see [Creating a device account using UI](create-a-device-account-using-office-365.md). From 8ba888ef74a14c1320718fef387622a63b5abb6b Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Thu, 27 Apr 2017 13:50:19 -0700 Subject: [PATCH 37/42] updating MDM policy --- ...windows-operating-system-components-to-microsoft-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index f844b54aa3..e81b1db45a 100644 --- a/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -1288,7 +1288,7 @@ To change the level of diagnostic and usage data sent when you **Send your devic -or- -- Create a REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\Policies\\Microsoft\\Windows\\DataCollection!AllowTelemetry**, with a value of 0 (zero). +- Create a REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DataCollection\\AllowTelemetry**, with a value of 0 (zero). -or- From ad01735e7fbeecad139a852ec50a1b696c1cb864 Mon Sep 17 00:00:00 2001 From: Michael Niehaus Date: Thu, 27 Apr 2017 14:18:15 -0700 Subject: [PATCH 38/42] Update waas-quick-start.md Changes to reflect new terminology, timelines. --- windows/deployment/update/waas-quick-start.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/deployment/update/waas-quick-start.md b/windows/deployment/update/waas-quick-start.md index 917f902b1c..8b7414fd7d 100644 --- a/windows/deployment/update/waas-quick-start.md +++ b/windows/deployment/update/waas-quick-start.md @@ -22,19 +22,19 @@ Windows as a service is a new concept, introduced with the release of Windows 10 ## Definitions Some new terms have been introduced as part of Windows as a service, so you should know what these terms mean. -- **Feature updates** will be released two to three times per year. As the name suggests, these will add new features to Windows 10, delivered in bite-sized chunks compared to the previous practice of Windows releases every 3-5 years. +- **Feature updates** will be released twice per year, around March and September. As the name suggests, these will add new features to Windows 10, delivered in bite-sized chunks compared to the previous practice of Windows releases every 3-5 years. - **Quality updates** are released monthly, delivering both security and non-security fixes. These are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. - **Insider Preview** builds are made available during the development of the features that will be shipped in the next feature update, enabling organizations to validate new features as well as compatibility with existing apps and infrastructure, providing feedback to Microsoft on any issues encountered. -- **Servicing branches** allow organizations to choose when to deploy new features. Current Branch (CB) deploys the fastest, soon after a feature update is released. Current Branch for Business (CBB) defers the installation of the same feature update by about four months, until that feature update is considered ready for broad deployment. Long Term Servicing Branch (LTSB) is different, used only for specialized devices (which typically don’t run Office) such as those that control medical equipment or ATM machines that need to be kept stable and secure. +- **Servicing channels** allow organizations to choose when to deploy new features. The Semi-Annual Channel receives feature updates twice per year. The Long Term Servicing Channel, which is designed to be used only for specialized devices (which typically don't run Office) such as those that control medical equipment or ATM machines, receives new feature releases about every three years. - **Deployment rings** are groups of devices used to initially pilot, and then to broadly deploy, each feature update in an organization. See [Overview of Windows as a service](waas-overview.md) for more information. ## Key Concepts -New feature update releases are initially considered **Current Branch (CB) releases**; organizations will use these for pilot deployments to ensure compatibility with existing apps and infrastructure. After about four months, the feature update will be declared as **Current Branch for Business (CBB)**, indicating that it is ready for broad deployment. +Windows 10 gains new functionality with twice-per-year feature update releases. Initially, organizations will use these feature update releases for pilot deployments to ensure compatibility with existing apps and infrastructure. After a period of time, typically about four months after the feature update release, broad deployment throughout the organization can begin. The exact timeframe is determined by feedback from customers, ISVs, OEMs, and others, with an explicit "ready for broad deployment" declaration signaling this to customers. -Each Windows 10 feature update (which initially begins as CB and then is declared as CBB) will be serviced with quality updates for a minimum of 18 months after it is released. The total length of time can be longer, as there will be two CBB releases serviced at all times. There will be a minimum of 60 days advanced notice (a grace period) after a CBB declaration occurs before an older feature update is no longer serviced. +Each Windows 10 feature update will be serviced with quality updates for 18 months from the date of the feature update release. Windows 10 Enterprise LTSB is a separate **Long Term Servicing Branch (LTSB)** version. Each release is supported for a total of 10 years (five years standard support, five years extended support). New releases are expected about every three years. @@ -44,9 +44,9 @@ See [Assign devices to servicing branches for Windows 10 updates](waas-servicing The process for keeping Windows 10 up to date involves deploying a feature update, at an appropriate time after its release. A variety of tools management and patching tools such as Windows Update, Windows Update for Business, Windows Server Update Services, System Center Configuration Manager, and third-party products) can be used to help with this process. [Windows Analytics Upgrade Readiness](https://www.microsoft.com/en-us/WindowsForBusiness/windows-analytics), a free tool to streamline Windows upgrade projects, is another important tool to help. -Because app compatibility, both for desktop apps and web apps, is outstanding with Windows 10, extensive advanced testing isn’t required. Instead, only business-critical apps need to be tested, with the remaining apps validated through a series of pilot deployment rings. Once these pilot deployments have validated most apps and CBB has been declared, broad deployment can begin. +Because app compatibility, both for desktop apps and web apps, is outstanding with Windows 10, extensive advanced testing isn’t required. Instead, only business-critical apps need to be tested, with the remaining apps validated through a series of pilot deployment rings. Once these pilot deployments have validated most apps, broad deployment can begin. -This process repeats with each new feature update, two to three times per year. These are small deployment projects, compared to the big projects that were necessary with the old three-to-five-year Windows release cycles. +This process repeats with each new feature update, twice per year. These are small deployment projects, compared to the big projects that were necessary with the old three-to-five-year Windows release cycles. Additional technologies such as BranchCache and Delivery Optimization, both peer-to-peer distribution tools, can help with the distribution of the feature update installation files. From e3f521d99556327786b0943b5771bfeefa33f7d6 Mon Sep 17 00:00:00 2001 From: John Tobin Date: Thu, 27 Apr 2017 16:51:42 -0700 Subject: [PATCH 39/42] Added new Vendor Support section --- .../credential-guard-known-issues.md | 52 ++++++++++++++++--- 1 file changed, 44 insertions(+), 8 deletions(-) diff --git a/windows/access-protection/credential-guard/credential-guard-known-issues.md b/windows/access-protection/credential-guard/credential-guard-known-issues.md index 5499b6cfdd..b9cacf0bc7 100644 --- a/windows/access-protection/credential-guard/credential-guard-known-issues.md +++ b/windows/access-protection/credential-guard/credential-guard-known-issues.md @@ -15,20 +15,56 @@ author: brianlic-msft - Windows 10 - Windows Server 2016 -Credential Guard has certain requirements for applications. Credential Guard blocks specific authentication capabilities. Therefore applications that require such capabilities will not function when Credential Guard is enabled. For further information, see [Application requirements](https://docs.microsoft.com/en-us/windows/access-protection/credential-guard/credential-guard-requirements#application-requirements). +Credential Guard has certain application requirements. Credential Guard blocks specific authentication capabilities. Therefore applications that require such capabilities will not function when Credential Guard is enabled. For further information, see [Application requirements](https://docs.microsoft.com/en-us/windows/access-protection/credential-guard/credential-guard-requirements#application-requirements). The following known issues have been fixed by servicing releases made available in the Cumulative Security Updates for April 2017: -• KB4015217: [Credential Guard generates double bad password count on Active Directory domain-joined Windows 10 machines](https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217) +- KB4015217: [Credential Guard generates double bad password count on Active Directory domain-joined Windows 10 machines](https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217) -This issue can potentially lead to unexpected account lockouts. + This issue can potentially lead to unexpected account lockouts. See also Knowledge Base articles [KB4015219](https://support.microsoft.com/en-us/help/4015219/windows-10-update-kb4015219) and -[KB4015221](https://support.microsoft.com/en-us/help/4015221/windows-10-update-kb4015221). +[KB4015221](https://support.microsoft.com/en-us/help/4015221/windows-10-update-kb4015221) -In addition, products that connect to Virtualization Based Security (VBS) protected processes can cause Credential Guard-enabled Windows 10 clients to exhibit high CPU utilization. For further information, see the following Knowledge Base articles: +The following issue is under investigation. For available workarounds, see the following Knowledge Base article: +- [Installing AppSense Environment Manager on Windows 10 machines causes LsaIso.exe to exhibit high CPU usage when Credential Guard is enabled](http://www.appsense.com/kb/160525073917945) * -• KB88869: [Windows 10 machines exhibit high CPU usage with McAfee Application and Change Control (MACC) installed when Credential Guard is enabled](https://kc.mcafee.com/corporate/index?page=content&id=KB88869) + *Registration required to access this article. -• [Installing AppSense Environment Manager on Windows 10 machines causes LsaIso.exe to exhibit high CPU usage when Credential Guard is enabled](http://www.appsense.com/kb/160525073917945) * +- [Blue screen on Windows 10 computers running Device Guard and Credential Guard with Cisco Anyconnect 4.3.04027](https://quickview.cloudapps.cisco.com/quickview/bug/CSCvc66692)** - *Registration required to access this article. + **Registration required to access this article. + +Products that connect to Virtualization Based Security (VBS) protected processes can cause Credential Guard-enabled Windows 10 clients to exhibit high CPU usage. For further information, see the following Knowledge Base articles: + +- KB88869: [Windows 10 machines exhibit high CPU usage with McAfee Application and Change Control (MACC) installed when Credential Guard is enabled](https://kc.mcafee.com/corporate/index?page=content&id=KB88869) + + +- Windows 10 machines exhibit high CPU usage with Citrix applications installed when Credential Guard is enabled. + + Microsoft is currently working with Citrix to investigate this issue. + + +## Vendor support + +- [Citrix Support for Secure Boot](https://www.citrix.com/blogs/2016/12/08/windows-server-2016-hyper-v-secure-boot-support-now-available-in-xenapp-7-12/) + +Credential Guard is not supported by either these products, products versions, computer systems, or Windows 10 versions: + +- For Credential Guard on Windows 10 with McAfee Encryption products, see: +[Support for Device Guard and Credential Guard on Windows 10 with McAfee encryption products](https://kc.mcafee.com/corporate/index?page=content&id=KB86009) + +- For Credential Guard on Windows 10 with Check Point Endpoint Security Client, see: +[Check Point Endpoint Security Client support for Microsoft Windows 10 Credential Guard and Device Guard features](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk113912) + +- For Credential Guard on Windows 10 with VMWare Workstation +[Windows 10 host fails when running VMWare Workstation when Credential Guard is enabled](https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2146361) + +- For Credential Guard on Windows 10 with specific versions of the Lenovo ThinkPad +[ThinkPad support for Device Guard and Credential Guard in Microsoft Windows 10 – ThinkPad](https://support.lenovo.com/in/en/solutions/ht503039) + +- For Credential Guard on Windows 10 with Symantec Endpoint Protection +[Windows 10 with Credential Guard and Symantec Endpoint Protection 12.1](https://www.symantec.com/connect/forums/windows-10-device-guard-credentials-guard-and-sep-121) + + This is not a comprehensive list. Check whether your product vendor, product version, or computer system, supports Credential guard on systems that run Windows 10 or specific versions of Windows 10. Specific computer system models may be incompatible with Credential Guard. + + Microsoft encourages third-party vendors to contribute to this page by providing relevant product support information and by adding links to their own product support statements. \ No newline at end of file From 5d4c5ff733c47a76659aca818dd2b0e04f409e78 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Thu, 27 Apr 2017 17:14:32 -0700 Subject: [PATCH 40/42] revised section about disabling firewall --- ...-administration-with-windows-powershell.md | 20 ++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md b/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md index fc03f88ce9..4acd498a40 100644 --- a/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md +++ b/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md @@ -86,21 +86,27 @@ Set-NetFirewallProfile -DefaultInboundAction Block -DefaultOutboundAction Allow ### Disable Windows Firewall -Disabling Windows Firewall with Advanced Security can cause the following problems: +Microsoft recommends that you do not disable Windows Firewall because you lose other benefits provided by the service, such as the ability to use Internet Protocol security (IPsec) connection security rules, network protection from attacks that employ network fingerprinting, [Windows Service Hardening](http://go.microsoft.com/fwlink/?linkid=104976), and [boot time filters](https://blogs.technet.microsoft.com/networking/2009/03/24/stopping-the-windows-authenticating-firewall-service-and-the-boot-time-policy/). + +Disabling Windows Firewall with Advanced Security can also cause problems, including: - Start menu can stop working - Modern applications can fail to install or update - Activation of Windows via phone fails - Application or OS incompatibilities that depend on Windows Firewall -Do not disable Windows Firewall with Advanced Security service by stopping the service. -The proper method to disable the Windows Firewall is to disable the Windows Firewall Profiles and leave the service running. -Use the following procedure to turn the firewall off, or disable the Group Policy setting **Computer Configuration|Administrative Templates|Network|Network Connections|Windows Firewall|Domain Prolfile|Windows Firewall:Protect all network connections**. -For more information, see [Windows firewall with advanced security deployment guide](windows-firewall-with-advanced-security-deployment-guide.md). -If you turn off the Windows Firewall with Advanced Security service, you lose other benefits provided by the service, such as the ability to use Internet Protocol security (IPsec) connection security rules, network protection from attacks that employ network fingerprinting, [Windows Service Hardening](http://go.microsoft.com/fwlink/?linkid=104976), and [boot time filters](https://blogs.technet.microsoft.com/networking/2009/03/24/stopping-the-windows-authenticating-firewall-service-and-the-boot-time-policy/). +Microsoft recommends disabling Windows Firewall with Advanced Security only when installing a third-party firewall, and resetting Windows Firewall back to defaults when the third-party software is disabled or removed. + +If disabling Windows Firewall with Advanced Security is required, do not disable it by stopping the Windows Firewall service. +Stopping the Windows Firewall service is not supported by Microsoft. + Non-Microsoft firewall software can programmatically disable only the parts of Windows Firewall with Advanced Security that need to be disabled for compatibility. You should not disable the firewall yourself for this purpose. -Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. + +The proper method to disable the Windows Firewall is to disable the Windows Firewall Profiles and leave the service running. + +Use the following procedure to turn the firewall off, or disable the Group Policy setting **Computer Configuration|Administrative Templates|Network|Network Connections|Windows Firewall|Domain Prolfile|Windows Firewall:Protect all network connections**. +For more information, see [Windows firewall with advanced security deployment guide](windows-firewall-with-advanced-security-deployment-guide.md). The following example disables Windows Firewall with Advanced Security for all profiles. From fb0b368b40ff8c87a8f1e632c0143140b55d933f Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Thu, 27 Apr 2017 17:27:05 -0700 Subject: [PATCH 41/42] added service name --- ...-advanced-security-administration-with-windows-powershell.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md b/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md index 4acd498a40..498b42fa47 100644 --- a/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md +++ b/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md @@ -97,7 +97,7 @@ Disabling Windows Firewall with Advanced Security can also cause problems, inclu Microsoft recommends disabling Windows Firewall with Advanced Security only when installing a third-party firewall, and resetting Windows Firewall back to defaults when the third-party software is disabled or removed. -If disabling Windows Firewall with Advanced Security is required, do not disable it by stopping the Windows Firewall service. +If disabling Windows Firewall with Advanced Security is required, do not disable it by stopping the Windows Firewall service (in the **Services** snap-in, the display name is Windows Firewall and the service name is MpsSvc). Stopping the Windows Firewall service is not supported by Microsoft. Non-Microsoft firewall software can programmatically disable only the parts of Windows Firewall with Advanced Security that need to be disabled for compatibility. From f1305173c929e5a22851bffd5d07d0752e7dd5a5 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Fri, 28 Apr 2017 08:12:24 -0700 Subject: [PATCH 42/42] fixing link --- windows/deployment/change-history-for-deploy-windows-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/change-history-for-deploy-windows-10.md b/windows/deployment/change-history-for-deploy-windows-10.md index 1fa15b38c4..56563526b0 100644 --- a/windows/deployment/change-history-for-deploy-windows-10.md +++ b/windows/deployment/change-history-for-deploy-windows-10.md @@ -21,7 +21,7 @@ This topic lists new and updated topics in the [Deploy Windows 10](index.md) doc ## RELEASE: Windows 10, version 1703 -The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). The provisioning topics have been moved to [Configure Windows 10](/windows/configuration/index.md). +The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). The provisioning topics have been moved to [Configure Windows 10](/windows/configuration/index). ## March 2017