ConfigMgr Frontline

Why do my Windows 10 2004, 20H2, and 21H1, and 22H2 systems continue to show compliant even though I've deployed the Feature Update to 22H2, and they are clearly NOT 22H2!? Make sure you are also deploying the Windows 10 22H2 Enablement Package! Enablement package? Each time a monthly cumulative update gets installed, it includes files from the upcoming Feature Update. These files are stored on the drive and include the updates for the next Feature Update. In October 2022, all the pieces were in place for Windows 10 22H2. Microsoft then released "Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package". (One for each CPU architecture.) So, in ConfigMgr add the enablement package to your deployment (it is language agnostic) and let it fly. The enablement package is about 2mb and takes only a few minutes and a reboot. Here is some more information about the enablement package. Note: Any Windows 10 version prior to 2004 can't use the e

 While attempting to upgrade SSMS to version 18.11.1, it kept failing with a very odd error I'd never run across before.  "MainViewModel.OnBundleAction: Bundle action failed: Fatal error during installation (0x80070643)" After trying many of the tips on the web like updating Visual C++ Redistributable, running a .NET repair, etc., I finally found the solution. I fired up trusty old Procmon64 and let it capture while I attempted to install SSMS 18.11.1. Once it failed, I went to Tools \ Count Occurrences and chose "Result".  The count showed 222 "Access Denied" results. I double-clicked that line which took me to the list of "Access Denied". I found the ones that were the culprit. Evidently, SSMS 18.11.1 needs to install some help files and it couldn't access the HelpLibrary2 folder. My assumption was the permissions were incorrect, so I addressed that by running the following command from an elevated CMD prompt: icacls.exe C:\ProgramData\

New Report - Windows Build Counts This report will show a count of builds in a collection. Download below. Download  here .

Configuration Manager Software Update Classifications (according to SQL).

I threw this together and thought someone might be able to use it. Feedback welcome. If something doesn't work, let me know. Download here . 4/23/22 - Updated the report with some improvements.

Delivery Optimization can be a powerful tool to help manage your content. However, getting things configured can be confusing and daunting. Here I've broken out the steps to get you going. Client Settings 1.     BranchCache and PeerCache. a.    First, create a new Custom Device Settings and check the box for “Client Cache Settings” and “Delivery Optimization”. b.       BranchCache . To enable BranchCache on clients, set “Configure BranchCache” and “Enable BranchCache” to Yes and set the “Maximum BranchCache cache size (percentage of disk)”. (Default is 10). c.        PeerCache . To make the client a SuperPeer (PeerCache Source), set “Enable as peer cache source” to “Yes”. Note: SuperPeers should be clients that are newer (faster), always on devices, that are hard wired, and have plenty of hard drive space. Note: Build a WQL query to create and maintain a collection of SuperPeers. I.E., CPU, memory, free space, etc.   2.     Delivery Optimization and Microsoft Con

If you are trying to decide what Products to include in your WSUS settings, this is the article for you.  ConfigMgr and WSUS currently have a dozen Windows 10 “products” listed but the descriptions are lacking. Windows 10 and Later Drivers:  These are drivers that will be offered to all builds of Windows 10 all the time, excluding upgrade scenarios (i.e., via Orchestrator, DSM, or Device Manager). They will not download during a Dynamic Update (i.e., Windows 10 upgrading itself from build 1511 to 1607).    They should only include KBs for the current Win10 version. . Windows 10 and Later Upgrade & Servicing Drivers:  These are drivers that are offered in all Win10 scenarios (i.e., via Orchestrator, DSM, Device Manager, or during DU). They may include some KBs later win10 version and enable current win10 version to upgrade. . Windows 10 Anniversary Update and Later Servicing Drivers:   These drivers apply only to Windows 10 1607 Anniversary and will not contain later upgrade. It als