ConfigMgr Frontline

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

Starting October 9, the Office Customization Tool now offers 11 standard deployment configurations. Administrators can now choose to use the standard configuration or build their own custom configuration. The announcement was made through a Tech Community blog post. Standard deployment configurations for Office deployment now available

Office Customization Tool for Click-to-Run follows the Office 365 Support policy guidelines for Office 365 ProPlus Subscriptions. Agents and Engineers familiar with how to troubleshoot the manual creation of Configuration.xml for use with the Office Deployment Tool will easily be able to transfer that knowledge to this new tool. https://techcommunity.microsoft.com/t5/Office-365-Blog/Customizing-Office-365-ProPlus-using-the-Office-Customization/ba-p/141932

Did you set Process Explorer 64 bit (procexp64.exe) to "Replace Task Manager" but then decided you wanted to go back but couldn't? Well then you've come to the right place. The fix is to delete procexp64.exe from off your PC and download procexp.exe from live.sysinternals.com (the 32 bit version) and run it. Within procexp.exe set "Replace Task Manager" from the Options menu and then set it again to deselect "Replace Task Manager". Voila! Back in business.

If you run across this error in the App-V Sequencer check the Event Log for AppV - Sequencer - Operational. You will probably find that the sequencer was not stopping a service (in my case it was the windows update service). It will show as "stopping". Set the service to disabled and then reboot. That should fix it.

1.) Login to the machine with the local administrator account or connect remotely from another server. 2.) Delete the profile for the user that's having the problem, i.e. C:\Users\User01 3.) Run Regedit, and remove the profile from HKLM>Software>Microsoft>Windows NT>CurrentVersion>Profile List>(SID) (you can right click on Profile List and do a search for the user name, i.e. User01. 4.) Once found delete the entire KEY for the user. 5.) Double check to ensure it's removed from System Properties>Advanced System Settings>Advanced TAB>User Profiles (Settings...) button> If you see the user in there, delete it too. 6.) Logoff as Local Admin and reboot. (Reboot not required but you may want to to be sure). 7.) Login with domain username.