diff --git a/windows/deploy/images/ua-cg-08.png b/windows/deploy/images/ua-cg-08.png index 4d7f924d76..f256b2f097 100644 Binary files a/windows/deploy/images/ua-cg-08.png and b/windows/deploy/images/ua-cg-08.png differ diff --git a/windows/deploy/images/ua-cg-09-old.png b/windows/deploy/images/ua-cg-09-old.png new file mode 100644 index 0000000000..b9aa1cea41 Binary files /dev/null and b/windows/deploy/images/ua-cg-09-old.png differ diff --git a/windows/deploy/images/ua-cg-09.png b/windows/deploy/images/ua-cg-09.png index b9aa1cea41..0150a24ee5 100644 Binary files a/windows/deploy/images/ua-cg-09.png and b/windows/deploy/images/ua-cg-09.png differ diff --git a/windows/deploy/images/ua-cg-15.png b/windows/deploy/images/ua-cg-15.png index 5362db66da..009315fc4a 100644 Binary files a/windows/deploy/images/ua-cg-15.png and b/windows/deploy/images/ua-cg-15.png differ diff --git a/windows/deploy/images/ur-overview.PNG b/windows/deploy/images/ur-overview.PNG new file mode 100644 index 0000000000..f1818d7073 Binary files /dev/null and b/windows/deploy/images/ur-overview.PNG differ diff --git a/windows/deploy/upgrade-readiness-deployment-script.md b/windows/deploy/upgrade-readiness-deployment-script.md index 14547ca3c4..af0612ef13 100644 --- a/windows/deploy/upgrade-readiness-deployment-script.md +++ b/windows/deploy/upgrade-readiness-deployment-script.md @@ -61,7 +61,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. -
+
diff --git a/windows/deploy/upgrade-readiness-get-started.md b/windows/deploy/upgrade-readiness-get-started.md index d5a0c20e31..86e9613548 100644 --- a/windows/deploy/upgrade-readiness-get-started.md +++ b/windows/deploy/upgrade-readiness-get-started.md @@ -15,7 +15,7 @@ This topic explains how to obtain and configure Upgrade Readiness for your organ You can use Upgrade Readiness to plan and manage your upgrade project end-to-end. Upgrade Readiness works by establishing communications between computers in your organization and Microsoft. Upgrade Readiness collects computer, application, and driver data for analysis. This data is used to identify compatibility issues that can block your upgrade and to suggest fixes that are known to Microsoft. Before you begin, consider reviewing the following helpful information:
- - [Upgrade Readiness requirements](https://technet.microsoft.com/itpro/windows/deploy/upgrade-readiness-requirements): Provides detailed requirements to use Upgrade Readiness.
+ - [Upgrade Readiness requirements](upgrade-readiness-requirements.md): Provides detailed requirements to use Upgrade Readiness.
- [Upgrade Readiness blog](https://blogs.technet.microsoft.com/UpgradeAnalytics): Contains announcements of new features and provides helpful tips for using Upgrade Readiness. >If you are using System Center Configuration Manager, also check out information about how to integrate Upgrade Readiness with Configuration Manager: [Integrate Upgrade Readiness with System Center Configuration Manager](https://docs.microsoft.com/sccm/core/clients/manage/upgrade/upgrade-analytics). diff --git a/windows/deploy/upgrade-readiness-requirements.md b/windows/deploy/upgrade-readiness-requirements.md index 6ef5fc19ff..3d0c2d0367 100644 --- a/windows/deploy/upgrade-readiness-requirements.md +++ b/windows/deploy/upgrade-readiness-requirements.md @@ -30,6 +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 https://technet.microsoft.com/en-us/itpro/windows/manage/waas-overview#long-term-servicing-branch to understand more about LTSB. ## Operations Management Suite diff --git a/windows/deploy/upgrade-readiness-upgrade-overview.md b/windows/deploy/upgrade-readiness-upgrade-overview.md index a7521e839f..bc3a495d98 100644 --- a/windows/deploy/upgrade-readiness-upgrade-overview.md +++ b/windows/deploy/upgrade-readiness-upgrade-overview.md @@ -9,19 +9,28 @@ 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 following status changes are reflected on the upgrade overview blade: +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 following color-coded status changes are reflected on the upgrade overview blade: + +- The "Last updated" banner: + - No delay in processing device inventory data = "Last updated" banner is displayed in green. + - Delay processing device inventory data = "Last updated" banner is displayed in amber. - Computers with incomplete data: - - Less than 4% = count is displayed in green. + - Less than 4% = Count is displayed in green. - 4% - 10% = Count is displayed in amber. - Greater than 10% = Count is displayed in red. -- Delay processing device inventory data = The "Last updated" banner is displayed in amber. -- Pending user changes = User changes count displays "Data refresh pending" in amber. -- No pending user changes = User changes count displays "Up to date" in green. +- User changes: + - Pending user changes = User changes count displays "Data refresh pending" in amber. + - No pending user changes = User changes count displays "Up to date" in green. +- Target version: + - If the current value matches the recommended value, the version is displayed in green. + - 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. -In the following example, less than 4% of (3k\355k) computers have incomplete data, and there are no pending user changes: +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: -![Upgrade overview](images/ua-cg-17.png) +![Upgrade overview](images/ur-overview.png)