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.
Imagine my surprise when my Dell Latitude 5501 was able to be upgraded to 64GB of RAM when the specifications state it has a maximum of 32GB. My guess is marketing. They want to sell you a more expensive model that officially supports more RAM. Here is a link to the RAM that worked for me. Anyway, if you are looking to upgrade your 5501, go ahead and move to 64GB.
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...
Comments
Post a Comment