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
Following on from the earlier posts on Microsoft 365 Business, it’s now on the price list and there are some additional resources that will help get you up to speed. One of the documents I strongly encourage you to take a look at is the FAQ, which covers a variety of topics, but also explains some of the capabilities versus some of the restrictions. I’ve copied some of these here, as they explain some of the pieces you need to
Following on from the last post on Azure Active Directory inclusions in Microsoft 365 Business, let’s take a look at the Windows AutoPilot pieces. For full details on Windows AutoPilot take a look at the official documentation. To start adding enrolling devices into Windows AutoPilot, sign in to the Microsoft Store for Business as an admin and clicking Manage. Click on Windows AutoPilot Deployment Program. I already have one device enrolled, but I need to add another device.
One of the scenarios I’m often asked about at the events I’m involved with is “why are my Windows 10 clients going to Windows Update instead of WSUS?”, and previously I’ve pointed people to the Demystifying “Dual Scan” post from the WSUS Product Team Blog. They’ve just put up a new post Improving Dual Scan on 1607 which is being released as part of the August cumulative update. This update is also being rolled into 1703, and is already part of 1709. Right