It’s probably faster to add the second image, due to single-instancing ☺
I do recall adding the logic that looks for an existing WIM and appends to it if one is found (designed to support capturing multiple images to the same WIM). There’s no override for that behavior, short of specifying your own file name (set BackupFile variable) or deleting the old file prior to running the backup step. Thanks, -Michael From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Hebbel Sent: Friday, February 10, 2017 3:55 PM To: mdtosd@lists.myitforum.com Subject: Re: [MDT-OSD] ZTIBackup adds instance to existing WIM According to the (potentially dated) document here it is expected. https://technet.microsoft.com/en-us/library/ee914607.aspx On mobile at the moment, but the creating a single WIM heading is where the reference info is located. Based on that I *assume* you'd need to back it up to a different location each time or maybe append a versioning number to whatever naming scheme you use for the WIM. Matt On Feb 10, 2017, 5:30 PM -0600, Miller, Todd <todd-mil...@uiowa.edu<mailto:todd-mil...@uiowa.edu>>, wrote: In MDT 2013u2 standalone, it is normal for ZTIBackup in the Build and Capture Task Sequence to add an instance to an existing WIM instead of overwriting the instance in the existing WIM? I did a build and capture last night and instead of the process replacing the existing WIM, the process added an Instance #2 to the existing WIM instead. Is the only solution to delete the existing WIM before doing a new capture or is there some way to tell ZTIBackup to always overwrite the existing instance in the WIM file provided? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521<tel:2510-2521> and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________