Windows 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_MSFTThird-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.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 suggestionsCloud Attach Your Future - Part I - ConfigMgr to AzureAD Groups
From the title, you may be wondering what the heck does Configuration Manager have to do with Azure Active Directory (AD) groups. Well, get ready for another lesson. As a Configuration Manager admin or an IT Manager, you may be wondering, “Why I should care about Azure AD groups? I have collections and collections are way better than Azure AD groups.” Azure AD groups become more important when you start to have conversations that include cloud context and dialogue.
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 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 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/wufbreports
