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?Third-Party Updates and Windows Update for Business
While using Windows Updates for Business (WUfB) is not for everyone, its simplicity and familiar end-user experience make it quite attractive to many organizations. One thing that WUfB does not provide today, though, is updates for third-party products. For that, you need to continue to use an on-premises solution like Microsoft Endpoint Manager Configuration Manager to complement WUfB.
WSUS - Why Windows target version GPO / registry setting is not working?
Hi, I would like to set my Windows 10 PC's target version to 22H2 and disable Windows 11 upgrade. I set a GPO to disable the upgrade, but it is not working, my test PC's still get the Windows 11 upgrade (and it fails with unsupported processor error). The registry settings set correctly on the Windows 10 PC, but it is still try to get the update from my WSUS server. What do I miss? How could I tell these PC's to not try this update? According to https://answers.microsoft.com/en-us/windows/forum/all/how-to-stop-or-block-windows-11-update/9f271456-51dd-4716-b69d-0834d552ca83, I did everything correctly, but still I face this problem.Microsoft Configuration Manager 2309 - Press release
This article provides information about Microsoft Configuration Manager 2309 release. To learn about the Configuration Manager, see Microsoft Configuration Manager FAQ. Microsoft Configuration Manager 2309 release is planned for October 2023. With this release we are bringing in new features and additional enhancements to the existing feature set. Configuration Manager 2305 Technical Preview had new enhancements, likewise, 2307 Technical Preview will bring additional capabilities to customers. Here is the list of features that are being introduced during Configuration Manager 2307 TP and 2309 Current Branch focusing on key customer value/asks and delivering high quality product updates. Some of the key additions are 1) Operating system deployment support for Windows 23H2; 2) Customers can perform Windows 11 edition upgrade like they did for Windows 10 edition upgrade from Professional to Enterprise Operating System; 3) a Windows 11 readiness dashboard for administrators or management to decide on how many devices are ready to upgrade to latest Windows 11 operating system, 4) Script runtime can be scheduled with simple steps, and customers can schedule the scripts to run on a particular time from the Primary Site time zone 5) Unified Service Orchestrator (USO) integration with Configuration Manager provides native windows update reboot experience( pre-release feature), and 6) Improvements in external notifications (Console Connectors). Furthermore we added critical customer asks such as, 1) Operating Systems Deployment (OSD) Preferred MP options which enables IT admins to choose a preferred Management point for PXE boot scenario; 2) Task Execution Status messages can now be deleted from primary servers which are older than 30 days, or any configured number of days; 3) CMG creation using third party app via console or PowerShell instead of the first party app; 4) Attack Surface Reduction (ASR) capability now marks server SKU as compliant only after enforcement is completed successfully; 5) Enable BitLocker through provisionTS task sequence option available on CM console to save the recovery key on CM database; 6) Client certificate state in console (self-signed) will now match state in control panel (PKI) applet; 7) Discrepancy in App Summarization report in console is corrected; 😎 Synchronization of collection memberships to Azure AD groups now optimized to show the entire set of members; 9) Patch downloader log size increased for troubleshooting purposes. We value your feedback on the upcoming functionalities to be released as it will contribute greatly to the enhancement of the product. Thanks, The Configuration Manager team Additional resources: What’s New in Configuration Manager Documentation for Configuration Manager Microsoft Configuration Manager announcement Microsoft Configuration Manager vision statement Evaluate Configuration Manager in a lab Upgrade to Configuration Manager Configuration Manager Forums Configuration Manager Support Report an issue Provide suggestionsWufB 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.Update Compliance is retiring
Update Compliance is retiring on March 31st, 2023. You must have enrolled to Windows Update for Business (WUfB) reports by February 14th to continue receiving reports. For more information about this transition, see http://aka.ms/wufbreportsGA and please enroll at http://aka.ms/wufbreportsWindows 10, version 21H2 announced!
Windows continues to play an important role in people’s lives as they continue to work, learn and have fun in hybrid and remote environments. Our goal is to provide new features and functionality via a fast and reliable update experience to help keep people and organizations protected and productive. Version 21H2 will continue the recent feature update trend of being delivered in an optimized way using servicing technology, like the way we delivered version 1909 to devices running version 1903 and the way we delivered version 21H1 to devices running versions 2004 and 20H2. Our launch approach for Windows 10, version 21H2 continues to fully leverage the Windows Insider Program to obtain user feedback and data insights on quality. Today, we begin releasing 21H2 builds to Windows Insiders who were moved to the Release Preview channel from the Beta channel because their specific devices did not meet the hardware requirements for Windows 11. For more information on Windows 10, version 21H2, its feature set, how it's being delivered, and the Windows Insider channels, please see John Cable's blog here: Introducing the next feature update to Windows 10: 21H2 | Windows Experience Blog. --Joe. Follow me on Twitter: @LURIE_MSFTWindows 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? 🙂WU / WuFB - Duplicate Download of Feature upgrades and DL of updates during Feature Upgrades
Dear Servicing Team, this is a repost because of a technical issue with the previous post. Thanks for heads-up Heather_Poulsen . Scenario: Windows 10 pro / Enterprise 1909 Using GPO for Update policies but effectively DL updates from WU no policy to limit the Feature Update version (all default) Issue 1: a computer using WU / WuFB does see two different feature upgrades in Settings and both seem be to be downloaded to SoftwareDistribution cache. Effectively the installation in windows.bt will fail because of the conflict starting another round of download. On "restart now" none of both updates would have been applied but cost bandwidth for the download. actual behaviour: both full installers are downloaded, non will be applied until restart, process starts over, eventually with only 2004 or 20H2. expected behaviour: in this scenario it should be expected that it either DL 2004 or 20H2, then using a enablement package to 20H2 or 21H1. proposed idea for a solution: When initiating Feature Update Downloads via WU / WuFB or even WSUS The USOclient / servicing stack should - recognize the latest FU version according to Server and/or Policy, if applied. - remove conflicting upgrades or updates (some have no supersedence marker by design). - should never download a CU or .net Update at the same time with a feature update*. Above measures should remove the issue to download outdated updates. In fact I have too little insights and knowledge about the internals of the process. *Issue 2: Especially this happens regularly. In practice this a very common and unwanted behaviour as the DL and install of a CU or .net update will cause pending restart even before the FU installation is ready. - causes a lot of unnecessary CPU time / system load as we install CUs that would go into Windows.old anyway. - it causes to install both the FU and CU one by another while all the time and ressources invested into the FU install will be canceled and reset on restart for the CU. It will start DL (cache) and install again after restart. Background: It feels like I have seen this more than once when I tested some behaviour for AriaUpdated evaluating how old and outdated version like 1507 or later would behave. Means would they directly download the latest release? No they do not. Mostly they picked some older releases from WU and would cause a 2 time upgrade. But also I have seen this behaviour above, where USOclient ist fetching 2 feature upgrades at a time. even though the softwaredistribution cache was clean.
