ConfigMgr Frontline

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 Window...

Be sure to re-install the inbox apps if you want them to be translated on the first launch. See: https://www.powershellgallery.com/packages/Windows365LanguagesInstaller/1.0.0.2/Content/Windows365LanguagesInstaller.ps1 If using a Task Sequence, the following results in a machine that is fully translated on the first use (you don’t need to use both LP and LXP). Install LP: dism.exe /Image:%OSDTargetSystemDrive%\ /ScratchDir:%OSDTargetSystemDrive%\Windows\Temp /Add-Package /PackagePath:".\Microsoft-Windows-Client-Language-Pack_x64_%Language%.cab"  Install LXP: powershell.exe -executionpolicy bypass -command "Add-AppxProvisionedPackage -Path %OSDTargetSystemDrive%\ -PackagePath .\LanguageExperiencePack.%Language%.Neutral.appx" -LicensePath ".\License.xml" Install FoD: powershell.exe -executionpolicy bypass -command $cabs = Get-ChildItem -Filter "*.cab"; foreach ($cab in $cabs) { Add-WindowsPackage -PackagePath "$($cab.FullName)" -NoRestar...

Happy Monday, fellow ConfigMgr administrators! I ran across a pretty difficult Task Sequence last week that had me scratching my head. It involved a pretty complex Task Sequence that contained over 50 applications. The Task Sequence would fail within 5 seconds upon launch from the Software Center with an message of  “The software could not be found on any servers at this time.” No error code was given. I ended up removing all the apps from the TS and adding them back one at a time. Many of the applications had at least one supersedence, dependencies and dependency chaining. It turned out there was one particular superseded application that  was missing its content!! Yeah, that would do it. Unfortunately, ConfigMgr did not log what application or package ID had its content missing so it was a crap shoot trying to find it.  I really feel like there should have been a log somewhere that gave this information. This is the only log info...