We had this same issue, if I remember right it was something to do with how the disk was being labeled but I can’t remember for sure.
I just checked my boot image and I don’t have any storage drivers for the surface in it. I am running the surface Pro3 256 and 512. Thanks Jim Pogue Desktop Support | MiTek Industries Inc.<http://www.mitek-us.com/Default.aspx> Office: 314-851-7326 | Mobile: 314-412-5703 | 14515 North Outer Forty | Chesterfield, MO | 63017 From: [email protected] [mailto:[email protected]] On Behalf Of Richard Poole Sent: Thursday, April 30, 2015 11:10 AM To: [email protected] Subject: [MDT-OSD] Surface Pro 3 disk goes AWOL during partition job Hello everyone, I have a task sequence that handles both BIOS and UEFI imaging over PXE, and was excited when even the newer Lenovo Helix machines (strictly UEFI, can’t switch to legacy) were able to image with no problems. Now I’m doing some testing with a Surface Pro 3 and am encountering a very odd issue. The job during the task sequence that partitions the disk into a small EFI, small MSR, and large GPT partition (again, works on other UEFI devices so I know the job works) fails every time. Going into diskpart and listing disks, none are listed. Going into diskpart after a reboot, but before firing the task sequence off, shows the disk and partitions but keeps disappearing right after the partitioning job error (makes sense if it can’t find the disk to partition). Anyone else out there experiencing this or know what I can do to fix it? Possibly a mass storage driver I need to put into the boot image? Thanks, Richard Poole MiTek Holdings, Inc., 2011-2014, All Rights Reserved ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it.
