Welcome back to part three in this series, first up was an introduction to OMS and Windows Analytics, second was installing the script on to older version of Windows Pro, and today we look at some of the different reporting options that are available once the device data has been processed. As mentioned. This will start off as a high level overview, and in upcoming posts we will dig further into some of the reporting categories.
Starting in the OMS Workspace you can see that Upgrade Readiness is reporting that our Windows 7 Pro and Windows 8.1 Pro PCs have been processed. Click on Upgrade Readiness to drill in to the solution.
Upgrade Overview tells
us what we would expect, some very high level details of computers and application counts. You can also see that Windows 10 Version 1709 has been chosen as the target, and tomorrow I will dig further into this and give some explanations as to why you may choose this option versus the other options.
Step 1: Identify important apps shows that from the two Windows machines that have been processed there are 36 apps we need to review. Because we are working with such a small sample size it can’t really list them as “Low install count”, because they would either be on 50% or 100% of the devices if they were detected.
Step 2: Resolve Issues is showing that there is 1potentially problematic app, but no driver issues. Because these PCs are Hyper-V VMs, seeing no issues with drivers should be expected.
Step 3: Deploy shows that our 2 PCs are currently in the review process, and that we can also create Computer Groups to more easily identify them.
Step 4: Monitor allows us to track update progress, and offers potential solutions when you do encounter driver issues.
Office add-ins allows us to identify
that are installed. Most organisations will find a variety of add-ins here, from those that were included with Office installs, to those that were installed standalone or as part of another software installation.
And finally, if you opted in to IE reporting, you will see information populated in Site discovery. If you have older line of business apps that have stronger IE dependencies this is going to be useful information, but if you are already accessing your web applications from a variety of platforms and devices this should be much less of an issue. The worst case scenario is that you might identify a few sites and ActiveX controls that weren’t considered for the migration.