In today’s post we will focus on analysing the data that was collected previously from the Windows 7 Pro and Windows 8.1 Pro. What you will also see in this post is that PCs that have been upgraded to Windows 10 will also start appearing in Upgrade Readiness to help identify any issues that might arise with the next round of Windows upgrades you need to manage.
For this post I’ve switched over to using https://portal.azure.com rather than using the classic OMS portal, partly as a way of highlighting that this capability is now available, and to help wean myself off the old workspace. You can see in the image above that at 1 I have
customised the shortcuts, and brought Solutions in as an easily accessible link.
At 2 I have selected Compatibility Assessment from a filtered list of the Solutions I have enabled in this tenant. From here you can see the overview blade, and at 3 you can see that I have 3 computers sitting in Upgrade Readiness. Clicking on Upgrade Readiness takes
us to the following screen.
Focusing on the Upgrade Overview information, clicking on Total computers gives us a good overview of the current stage of PCs that have been processed.
You can see that we can type our own queries or use the inbuilt ones. What I want to focus on here are the three PCs that I’ve highlighted, each with UAComputer in the $table column. This indicates that these machines haven’t been upgraded to the required Windows version, which is identified as Windows 10 Version 1709 in the Upgrade Overview image.
Expanding this Windows 10 PC out, you can now see that it’s on RS2 aka version 1703, thus the reason for being flagged. Once this machine is updated to 1709 it will be moved over to UAUpgradedComputer rather than UAComputer.
We can filter out the Windows 10 devices pretty easily so that we can focus on the older clients.
You can find more details on Step 1: Identify important apps
here. Click on Not reviewed to see what applications have been detected.
Rather than looking at the applications that aren’t being reported as problematic, can group and filter, as seen in the next screenshot.
Filtering out No known
issues only leaves one result – Microsoft Security Esssentials.
Even though we are informed that that app will be removed during upgrade, but if it’s one that isn’t reporting such a requirement, following the ReadyForWindows link takes us to the following page.
Because we already know that Windows Defender will replace Security Essentials on Windows 10, we don’t really need to worry about the lack of support.
If we head back to the main Upgrade Readiness view and take a look at STEP2: Resolve Issues we see that in REVIEW APPLICATIONS WITH KNOWN ISSUES we see that single app that I had already identified by filtering, but presented in a more user friendly manner. In the next screenshot we will see what options we have with the detected app. These are all VMs so the REVIEW KNOWN DRIVER ISSUES isn’t listing any problems, as would be expected, REVIEW LOW-RISK APPS AND DRIVERS and PRIORITIZE APP AND DRIVER TESTING are designed to help identify some of the lower hanging fruit for getting devices across the line faster.
Here is that same app that was previously identified, but if I click on Bulk Edit after selecting Decide upgrade readiness I get the following.
The options we can set here are Importance, Upgrade decision, Test plan, Test result and App owner, so that we
can log what is required and assign an owner if needed.
I’ll leave it therefor today’s post, next up we will look at the different options for deploying Windows 10 Pro/Windows 10 Business based on what we have discovered.