A few months ago I published a blog post on the OMS Upgrade Analytics (now called Upgrade Readiness).

Recently I was asked to record a podcast based on content from my blog post. A big thank you goes out to fellow MVP Cameron Fuller, who put Adaptiva in contact with me. And so my first podcast was born.

You can find the Tweet about the recording here, and the recording itself on SoundCloud here.

I’m not going to give away all of the content, but here’s a sampling of some of the questions that were discussed during the podcast:

  • They’ve replaced the functionality in the Application Compatibility Toolkit (ACT) with Upgrade Analytics. So ACT is still available, or it’s dead now and not available?
  • With Upgrade Readiness, you have register every endpoint in your organization with the cloud, correct?
  • What’s that entail? Is there a client agent for Windows 7/8? How intrusive is it? How much information are you giving to the Azure cloud when you do that? What’s the network load?
  • Describe the process of installing Upgrade Readiness on all the machines in an enterprise. Is this process daunting? Are a lot of enterprises going to avoid it because they don’t want to give Microsoft telemetry data, or is that a non-issue since when they go to Windows 10 they’ll be doing that anyhow?
  • What is “Update Compliance”?
  • So, update compliance requires OMS, but it’s a “cloud” version of OMS, correct? So, while the upgrade readiness goes to the Azure cloud, and there is no charge, the “Update Compliance” goes to the cloud and charges you money, is that right?
  • How does Upgrade Readiness help you track your deployment? Will it tell you how many machines have been moved to Windows 10, and how many have yet to move?
  • There is no charge to use Upgrade Readiness, but what if you want to use Log Analytics to query it — does that require you to pay money?

If you like the recording and are interested in setting up something similar with me, please feel free to email me at Adin.Ermie@outlook.com.