<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Windows-Update-for-Business on Jon's Notes</title><link>https://4c4806b4.configjon-blog.pages.dev/category/windows-update-for-business/</link><description>Recent content in Windows-Update-for-Business on Jon's Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 10 Apr 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://4c4806b4.configjon-blog.pages.dev/category/windows-update-for-business/index.xml" rel="self" type="application/rss+xml"/><item><title>Update Compliance Log Analytics Queries</title><link>https://4c4806b4.configjon-blog.pages.dev/update-compliance-log-analytics-queries/</link><pubDate>Wed, 10 Apr 2019 00:00:00 +0000</pubDate><guid>https://4c4806b4.configjon-blog.pages.dev/update-compliance-log-analytics-queries/</guid><description>&lt;p&gt;Lately I have been helping many people with moving their update workloads from Configuration Manager and WSUS to Windows Update for Business. The one thing I get the most questions about with the move to Windows Update for Business is how to monitor update compliance. The computers are now pointing to the internet for updates, and as a result, no longer report update compliance information to Configuration Manager or WSUS. The answer to this is the &lt;strong&gt;&lt;a href="https://docs.microsoft.com/en-us/windows/deployment/update/update-compliance-monitor"&gt;Update Compliance&lt;/a&gt;&lt;/strong&gt; solution in Azure Log Analytics.&lt;/p&gt;</description></item></channel></rss>