I Am ReSpOnSiBlE fOr .........WhAt I aM...........wHaT i Do.....WhAt I hAvE

When running Configuration manager Task Sequence, it can be extremly frustrating trying to find ever moving log files if you get an error during OS. The log files locations on our hard disk depending on what stage of deployment your task sequence is at: To try and help you find where the log files are located please see the below table: Task Sequence Storage                                                                         Log location WinPE - Before HD Format                                                    x:\windows\temp\smstslog\smsts.log WindPE - After HD format                                                  x:\smstslog\smsts.log Windows no client installed                                              c:\_smstasksequence\logs\smstslog\smsts.log Windows - x86 client installed                               c:\windows\system32\ccm\logs\smstslog\smsts.log Windows - x64 client installed                            c:\windows\sysWOW64\ccm\logs\smstslog\smsts.log

Problem Description - Recently we come across very strange, shitty and crappy issue. We weren't able to distribute any of the packages or applications resulting work loss and productivity. Error -   I was  following in the ‘distmgr.log’ file and noticed TON of messages like the following. a t the outset, they weren't seems error, I've never seen such errors before and couldn't  find anywhere in the forums, not sure what these messages were referring to.  initially, we wait for one day , two days BUT these messages didn't disappear. Resolution -  We went through all the hierarchy settings and site settings , couldn't find anything useful. When i opened "SMS_DISTRIBUTION_MANAGER' component and checked the logs  surprisingly found that 'software update' package size to 25 GB was deleted from all 7 distribution points and considering it's size, it took 7 days to successfully removed the package from all