Even THAT has failed at the exact same point, where it was no issue for the other one. I went ahead and attempted to image this thing the same way as the other unit- Join domain, add to collection, push TS to unit. Another kicker, I was able to bring the trouble unit back to the factory image using the recovery USB media created earlier. Update: I found this article, that is basically pointing out the same problem, sadly no solution though. Find low everyday prices and buy online for delivery or in-store pick-up. Has anyone run into or seen anything this before? Shop Microsoft Surface Pro 7 12.3' Touch Screen Intel Core i3 4GB Memory 128GB SSD Device Only Platinum at Best Buy. trying a new USB stick had no change as well. Other than that, I cannot figure out a reason as to why this is happening. Being it's a hard drive, the storage drivers should be the same for boot image being the chipset is the same, and vendor should not matter being the same sata protocol. From what we have seen, the majority of the surface units have a Samsung SSD, whereas the RMA units have a Hynix based SSD built in. The one thing that does stick out, is the internal hard drive vendor. I left one of the RMA'd devices stock, joined the domain, loaded client, added to a collection and pushed the task sequence for testing/troubleshooting, and I took another Surface we've had on hand for a while, and ran the offline USB image through n through with no issues. This problem remains true if I attempt to image via Offline media, with RMA units only. SP3 starts and loads files to boot into WinPEįormat and Partition Disk (UEFI) - Hangs and eventually fails out stating that it cannot format the disk (log file attached). Secure Erase SSD (via surface data eraser tool provided by MS) Model: 256GB Surface Pro 3 back from service

Note: There have been 0 changes to the Task sequence for sometime, and we are able to image new units.

We recently however had to warranty a few surface pro 3 devices for our users, and we are having alot of trouble getting these to format correctly, before failing the task sequence. We having been deploying Surface devices for sometime now using SCCM R2 SP1 CU3, followed the guides posted here, and have had good luck with these for sometime now.

Surface pro 3 windows7