ScrJeff Yes, we are monitoring and continually looking into ways to improve reporting responsiveness. It's an ongoing process where we are analyzing data issues and fixing them in an ongoing effort, so you'll most likley see gradual improvements rather than a big change. We recognize how important accuracy and timeliness are to reporting.
Thank you for your feedback, my follow-up thoughts:
* We are hoping to add later this year a view of the list of applicable devices, including the device manufacturer and model fields, to help with this.
* I think you have some good ideas around how to organize deployments across update types and organizations. What drivers has done is make it so that the traditional org based structure that you describe, like "finance last" that you'd use for quality or feature updates is not necessarily how you want to manage the hardware/driver updates. Some tools to help build or design the deployments would make sense and is something to think about.
* The overview is something we will be adding in the future.
* I would have expected those columns to be sortable, so I'll work with the engineering team to find out if there's a reason they are not, and otherwise log a bug to fix that. I noticed the same thing in Feature update reports.
* We are hoping to add the policy based report sometime later this year as well.
Henrikcj , Vern_Bateman There are no drivers specific log files or troubleshooting steps, so following existing approaches would be appropriate. Since you mentioned co-management, there is something else you can check... look into the DisableDualScan and/or https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourcefordriverupdates policy settings, to ensure the device is able to scan WU, rather than WSUS, for drivers. Next steps might be to use product support. Using that policy, you can use Drivers management in Intune while managing other software updates in Configuration Manager, you do not need to wait.
Thank you all for the great questions and feedback!
-David