Change Log question

While not critical, I think this would be a great improvement idea.   I wouldn't say to put it in the root of C, but there should already be a logs folder where scripted actions and similar will log to, seems a logical location.

But overall, seems like a simple thing that could be added to the tasking work, and shouldn't extend the time it takes to capture an image.  The latter part is what my only concern would be, don't make it noticeably longer. 

It would just have to copy the text from the current log to the text file before it starts the set as image process.

Michael Lenahan  - Indeed, I can't imagine this couldn't be accomplished with the existing custom script extension commands being executed, into a nicely formatted log file that appends that change onto previous.  Icing on the cake if it matches to the ACG's version for this image, though if the capture fails, now that could get out of alignment if not well thought out. 

As mentioned, I think it is an excellent idea.  Added value, is that when working on a session host troubleshooting user issues, this file would still exist (unless you explicitly wipe it) and could expose to an engineer troubleshooting, what was recently change, per the change log entry. 

I see a lot of potential value for what should be a fairly simple change.    This would be a great post in the feature request category.