Having 4 parts of the earlier investigation series, I was thinking how improve it, surely there must be something that can be improved. Looking back at the previous blogs, we are looking at on the spot log file troubleshooting.
While there is nothing wrong with that, an example of windows patches deployment, we take a look at UpdateDeployment.log to see if we have deployment issue. While there is nothing wrong with this approach, I was thinking why not me map out the end to end work flow.
Surely this will help us greatly in which log file. The below workflow is basically base on my understanding from reading the below technet article;
There was some sort of flowchart in SCCM 2007 but not for SCCM 2012. In this series, I will begin with Software Updates workflow:
You will see 2 grouped clusters, one cluster is from the server end while the other will be on the client end, in the future series I will map the process with all the necessary log files so that it will be easier for the administrator to jump into which log file to look. (More importantly, save time)
Don't forget my earlier log investigation series:
Happy reading! :)
SY
