Ztiwinre is a piece of junk and should be REMOVED from mdt. I have filed a bug against mdt. For now... Just disable the step.
Sent from my Verizon, Samsung Galaxy smartphone -------- Original message -------- From: ODONNELL Aaron M <[email protected]> Date: 4/7/17 1:59 PM (GMT-05:00) To: "'[email protected]'" <[email protected]> Subject: [MDT-OSD] Errors copying recovery partition We’ve been doing some Windows 10 1607 deployment tests and on some of the newer Dell hardware (seems to be the Kaby Lake chipset ones, this error is from a Latitude 7280) MDT is throwing errors saying it can’t copy the recovery partition .wim file. It’s working just fine on other Win10 deployments. Here’s the part from bdd.log: ---------------- Initialization ---------------- ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) Ensure boot drive has a Drive Letter. ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) Find the boot drive (if any) [False] [] [True] ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) New ZTIDiskPartition : \\MININT-LEFGNC8\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-LEFGNC8\root\cimv2:Win32_LogicalDisk.DeviceID="W:" ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) New ZTIDisk : \\MININT-LEFGNC8\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) Found bootable drive [ W: ]: \\MININT-LEFGNC8\root\cimv2:Win32_LogicalDisk.DeviceID="W:" ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) Target file: W:\Recovery\WindowsRE\WinRE.wim ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) FindFile: The file WinRE.wim could not be found in any standard locations. ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) Copy File: \\server\W10DEV$\Boot\LiteTouchPE_x64.wim to W:\Recovery\WindowsRE\WinRE.wim ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) FAILURE (Err): -2147024784 0x80070070: Copy File: \\server\W10DEV$\Boot\LiteTouchPE_x64.wim to W:\Recovery\WindowsRE\WinRE.wim - ZTIWinRE 4/7/2017 11:14:32 AM 0 (0x0000) FindFile: The file REAgentC.exe could not be found in any standard locations. ZTIWinRE 4/7/2017 11:14:33 AM 0 (0x0000) About to run command: D:\Windows\System32\REAgentC.exe /info /target D:\Windows ZTIWinRE 4/7/2017 11:14:33 AM 0 (0x0000) Command has been started (process ID 2116) ZTIWinRE 4/7/2017 11:14:33 AM 0 (0x0000) Everything else works just fine if you ignore the error. This problem isn’t happening on our non-Kabylake chipset hardware so I’m guessing it’s a driver but I’ve added the storage controller drivers and I would think the deployment wouldn’t work at all if that were missing. Using MDT 2013 Update 1. Thanks, Aaron O’Donnell
