Append Logging instead of overwriting

BatchPatch Forums Home Forums BatchPatch Support Forum Append Logging instead of overwriting

  • This topic has 2 replies, 2 voices, and was last updated 4 years ago by TomHuis.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #12624
    TomHuis
    Participant

    We use batchpatch to update golden image and create snapshot, clean, etc. This works as a charm. But we also want some more logging so we can see what happend on a image without having to turn it on. Most updates we have captured but we are missing the windows updates itself. They are captured in the Remote Agent Log and because we run the windows updates 2 times to be sure we have everything, it only shows the 2nd time, which most of the time shows, 0 updates. Anyway we can easily solve this?

    #12625
    doug
    Moderator

    This is not currently possible, but we will consider adding some kind of “append” option for a future build.

    In the meantime you would either have turn on the target computer to view the BatchPatch.log to see the history of what BatchPatch did with Windows Updates before the machine was shutdown, or you have two possible workarounds:

    1. One option is to use multiple rows per host in the BP grid. So if you put the same “host1” into two separate rows in the grid, and then each row executed a Windows Update action at a different time, you would be able to see the log of both actions in the ‘Remote Agent Log’ column for each row. In this case you would have to take care to ensure that the rows’ executions do not overlap. The ‘advanced multi-row queue sequence’ could be used to ensure that the two rows are executed sequentially. Or you could use scheduled tasks for each row, just making sure that they execute far apart enough in time that they would not ever overlap.

    2. Another option is to use “Save current-row HTML export” inside of the job queue. You can run that after each Windows Update action, and then on the BP computer you’ll have the details from the ‘Remote Agent Log’ column for each run saved in those HTML files that are created.

    #12629
    TomHuis
    Participant

    Thanks Doug, I already use the 2nd option now before we start the excercise but I can probably use another local command to write the information in the batchpatch logging to another logging file we already use for this excercise. Thanks for the suggestion.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.