From 643b1d7cc5b29e69ae1ee86733e12993297da062 Mon Sep 17 00:00:00 2001 From: Paul Fitzgerald Date: Tue, 15 Aug 2017 15:01:31 -0500 Subject: [PATCH 1/3] Updated list of target operating systems. Windows 10 version 1703 is now available as a targeted operating system. --- .../upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md b/windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md index 85acab5a0a..807cd59c14 100644 --- a/windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md +++ b/windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md @@ -41,7 +41,7 @@ As mentioned previously, the default target version in Upgrade Readiness is set The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target version. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Readiness is based on the target operating system version. -You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, and Windows version 1607. +You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, Windows 10 version 1607, and Windows 10 version 1703. To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution: From 478cc141729bc2fa2758fe83928fd1b157850b65 Mon Sep 17 00:00:00 2001 From: Paul Fitzgerald Date: Tue, 15 Aug 2017 15:33:23 -0500 Subject: [PATCH 2/3] Corrected link targets 1) The "target version" link was missing the section ID 2) The "related KBs" link was absolute rather than relative --- .../upgrade/upgrade-readiness-upgrade-overview.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/upgrade/upgrade-readiness-upgrade-overview.md b/windows/deployment/upgrade/upgrade-readiness-upgrade-overview.md index bbbb2a155d..860f86c5bb 100644 --- a/windows/deployment/upgrade/upgrade-readiness-upgrade-overview.md +++ b/windows/deployment/upgrade/upgrade-readiness-upgrade-overview.md @@ -9,7 +9,7 @@ author: greg-lindsay The first blade in the Upgrade Readiness solution is the upgrade overview blade. This blade displays the total count of computers sharing data with Microsoft, and the count of computers upgraded. As you successfully upgrade computers, the count of computers upgraded increases. -The upgrade overivew blade displays data refresh status, including the date and time of the most recent data update and whether user changes are reflected. The upgrade overview blade also displays the current target OS version. For more information about the target OS version, see [target version](use-upgrade-readiness-to-manage-windows-upgrades.md). +The upgrade overivew blade displays data refresh status, including the date and time of the most recent data update and whether user changes are reflected. The upgrade overview blade also displays the current target OS version. For more information about the target OS version, see [target version](use-upgrade-readiness-to-manage-windows-upgrades.md#target-version). The following color-coded status changes are reflected on the upgrade overview blade: @@ -32,7 +32,7 @@ The following color-coded status changes are reflected on the upgrade overview b - If the current value is an older OS version than the recommended value, but not deprecated, the version is displayed in amber. - If the current value is a deprecated OS version, the version is displayed in red. -Click on a row to drill down and see details about individual computers. If KBs are missing, see [Deploy the compatibility update and related KBs](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#deploy-the-compatibility-update-and-related-kbs) for information on required KBs. +Click on a row to drill down and see details about individual computers. If KBs are missing, see [Deploy the compatibility update and related KBs](upgrade-readiness-get-started.md#deploy-the-compatibility-update-and-related-kbs) for information on required KBs. In the following example, there is no delay in data processing, less than 4% of computers (6k\294k) have incomplete data, there are no pending user changes, and the currently selected target OS version is the same as the recommended version: @@ -65,4 +65,4 @@ Select **Total applications** for a list of applications discovered on user comp - Percentage of computers in your total computer inventory that opened the application in the past 30 days - Issues detected, if any - Upgrade assessment based on analysis of application data -- Rollup level \ No newline at end of file +- Rollup level From 88d6556397121795dcd80cc5d0c419f675507e11 Mon Sep 17 00:00:00 2001 From: Gerardo Saca Date: Tue, 15 Aug 2017 15:47:11 -0700 Subject: [PATCH 3/3] Add note on joining to Azure AD when device already setup Adding an important note to the section with instructions on joining a device to Azure AD when it has already been setup. Without that disclaimer, a user going through a rather common scenario will experience a silent error where clicking the button does NOTHING leaving the user at a loss as to why things aren't working. --- windows/deployment/deploy-enterprise-licenses.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 6881363aa1..40f279e10f 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -91,6 +91,9 @@ Now the device is Azure AD joined to the company’s subscription. **To join a device to Azure AD when the device already has Windows 10 Pro, version 1703 installed and set up** +>[!IMPORTANT] +>Make sure that the user you're signing in with is **not** a BUILTIN/Administrator. That user cannot use the `+ Connect` button to join a work or school account. + 1. Go to **Settings > Accounts > Access work or school**, as illustrated in **Figure 5**. Connect to work or school configuration