Device don't report to Windows Update for Business reports
We start using Autopatch. I setup all thigs for this report. Create LA and setup it. https://learn.microsoft.com/en-us/windows/deployment/update/wufb-reports-overview But from 750 device i see only 42. I try creating new LA, and onboard it but number of computers is same. On my NB i try even script but nothing works https://learn.microsoft.com/en-us/windows/deployment/update/wufb-reports-configuration-script Any help?WufB Delivery Optimization Report Broken
Since some days, we have a problem with our Delivery-Optimization-Report in WufB-Workbook. We only see the following error in all Sections Query could not be parsed at 'datetime()' on line [2,21] Token: 'datetime()' Line: 2 Postion: 21 Is this a global Issue? Is anybode else faceing this problem. The Report used to work fine for several Weeks - no changes made.Windows 10 Report Feature Update failures
Hi I work in a co-managed enviroment where we have switched WUFB workload to Intune. The feature updates are working well but the reporting does not. We have 70% errors in the Windows 10 and later feature update report, all failures are: "Device Registration Invalid Azure AD Device Id". Now, the devices are Hybrid-AzureAD Joined and as mentioned Co-Managed with WUFB as Intune-managed workload. For what it's worth, I can see the Azure Device ID present in AzureAD. Anyone have any suggestions regarding how to solve this so we get that fancy piechart-report working? 🙂Update rings applied, but clients not updating from Intinue /Windows update for business
Recently I switched the Windows Update Policies co-management workload from Configmgr to Pilot Intune and created update rings in Intune assigned to my pilot group. The update ring is set to defer both quality and feature updates for 0 days, with deadlines of 2 and 28 days. The clients don't seem to be updating based on that schedule though. It's been more than the 28 days since I set this up, and none of the computers in the pilot ring have installed a feature update since the change was made. The computers in the pilot group are running a mix of Win10 1903, 1809, and 1803. They have received the January 2020 updates, but I think those still came from configmgr, not Intune / Windows Update for Business. What am I missing that would cause the clients to still get windows updates from Configmgr and not intune/WUfB?Best practice MDM / Windows Update for Business
Hey together, i just implemented in a pilot stage MDM for Windows 10 Devices and Windows Update for Business. Therefore i have some questions about your experiences. The current config looks like this: 1. Windows Update Ring: Win10 Insider Channel (Release) - e.g. for IT Workers 2. Windows Update Ring: Win10 Semi-Annual Channel (Targeted) - e.g. for some Key-users 3. Windows Update Ring: Win10 Semi-Annual Channel - for the rest of the company Are there any ideas to improve, or am i missed something? How do you manage the clients update status? In Intune i'm only able to see which client has applied which update ring, but i can't see (like in the old WSUS console) which client is needing which update or if everything is okay. What could be a best practice for this? Thank you in advance Patrick. :)Windows Update for Business & Channels
Hi, i'm asking myself if there is an option to see what update ring (SAC, Insider) a client has applied. (When looking at the client, not at intune.) And: Is it possible to change the update ring after the intune policy has been applied? (e.g. the machine has applied a policy pointing the device to SAC and some other update options. Now the device should apply the insider ring.) My first thought was looking at the advanced diagnistic report, which can be exported, but nope. Thanks in advance Patrick :)
