SMSTS log file does not persist after deployment completion RRS feed

  • Question

  • I have a Windows 10 upgrade task sequence which works just fine, however, I started noticing that the SMSTS log file does not get retained when MDT does its environment cleanup at the end of the sequence.

    I checked all the standard locations and even wrote a script to search the system for it thinking maybe it got shunted to a folder I wasn't looking in, but it could never find it.

    I then decided to dump all of the variables to a log file at various points to see if the _SMSTSLogPath existed and what it was set to. I noticed that throughout the entire sequence it's set to null/empty.

    This is the first time I've built an upgrade task sequence and have never seen that variable not get a path value, so I'm not really sure what to think about it.

    I guess my question is, should I be able to set that variable to a path in the task sequence (say at the beginning) and have it persist so I can have this log at the end of the deployment?

    Saturday, December 23, 2017 5:14 AM