Last updated on September 25th, 2021 at 09:11 pm
We have recently been doing some big OSD projects and with testing for such big projects comes the point where some of your testing will fail, so to find out why a test sequence fails, the first thing you should look at is your log files.
However, ConfigMgr makes this an annoying process as the log files move about during different points in the task sequence. So, when it does fail, you have to look in different areas, then pull out the log files and then go through them to find the error.
Well, we knew that we could capture the log files upon failure during the task sequence and copy them to a network share so that we had one location to aim at. To do this, we found an excellent walk through guide over at System Center Guru so we thought that we would share this with you.
So, click the link below and see how you can capture your log files as part of a task sequence when you get a failure.
If you have any questions or comments on this, please feel free to use our comments method below.
If you want to be notified when we post more quality guides like this one, sign up to our free subscription service and you will receive an email when a new post is live.
No need to worry, we will not be filling your inbox with spam and you can unsubscribe anytime you like.