Achieve better patch compliance with Update Connectivity data

Some very good questions asked, thank you.

To utilize this information with Configuration Manager you can use Update Compliance.  Because the data that drives the InsufficientUpdateConnectivity alert is pulled from online Microsoft services, we don’t currently have any plans to add this for on-prem servicing.

The 2 continuous hours mentioned above are included in the 6 hours total (in other words, it’s not 8 total hours).  This criteria allows for devices that intermittently are on, or intermittently connected to the internet.  Some parts of the update process can restart where they left off, like the downloads.  Others need to restart from the beginning if the device shuts down.  So these are both taken into account in the criteria.  Often, devices finish in less than this bar, so a good way to think of this is that devices that have more than this min bar have high confidence had enough update connectivity to be successful.

pembertronics ,  exactly right! Updating the default power settings can really help enabling overnight updates.  This whitepaper has some recommendations for power settings for achieving great update adoption (go to this link, select the download button, and choose the “Optimizing Windows 10 Update Adoption.pdf”:  http://aka.ms/updatevelocity