ConfigMgr Frontline

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

Where the heck is the #($*@(*#$# panther logs? Logfile location Description $windows.~bt\Sources\Panther Log location before Setup can access the drive. $windows.~bt\Sources\Rollback Log location when Setup rolls back in the event of a fatal error. %WINDIR%\Panther Log location of Setup actions after disk configuration. %WINDIR%\Inf\Setupapi .log Used to log Plug and Play device installations. %WINDIR%\Memory.dmp Location of memory dump from bug checks. %WINDIR%\Minidump.dmp Location of log minidumps from bug checks. %WINDIR%\System32\Sysprep\Panther Location of Sysprep logs.

This one was a real head scratcher. After upgrading from Windows 7 to Windows 10 1809, you could not open the Start Menu. When you would click on it, nothing would happen. You could also not perform a search. I saw in the System event log: "The server Microsoft.Windows.ShellExperienceHost _10.0.17763.1_neutral_neutral_cw5n1h2txyewy! App did not register with DCOM within the required timeout." about every 30 seconds. I noticed the same thing with Cortana. and "The server Microsoft.Windows.Cortana _1.11.6.17763_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca did not register with DCOM within the required timeout." I captured a procmon trace and found: Both ShellExperienceHost.exe and SearchUI.exe exit with an error (-1073741790 which is Access Denied) as soon as they try to load sysfer.dll (part of Symantec Endpoint Protection). See https://support.symantec.com/us/en/article.TECH252314.html Evidently, sysf...

If you go here on a Windows box: C:\Windows\System32\DriverStore\FileRepository You will see a ton of folders…each folder corresponds to a driver. Inside each folder is the inf file and any other required files for the driver. You can sort them by date to see which drivers were just installed. Windows saves all drivers you add here. Find the folder that contains the driver you need and copy that folder to your driver repository… name it something descriptive and include it in your driver package. Windows will find and use that driver during its plug n play search. You can effectively decrease your driver packages size by 90%!