Mark, I have one job that creates all three partitions. Niall, I’m using SCCM. I’ll take a look at those videos and see if there’s anything I’m somehow missing. Thank you!
From: [email protected] [mailto:[email protected]] On Behalf Of Niall Brady Sent: Thursday, April 30, 2015 10:04 AM To: [email protected] Subject: Re: [MDT-OSD] Surface Pro 3 disk goes AWOL during partition job no mass storage driver is needed in your boot wim, are you deploying with mdt or SCCM ? have you seen these yet, they cover deploying the surface pro 3 with mdt and with sccm http://www.windows-noob.com/forums/index.php?/topic/11685-5-video-series-on-deploying-the-microsoft-surface-pro-3-available-now/ On Thu, Apr 30, 2015 at 6:55 PM, Kent, Mark <[email protected]<mailto:[email protected]>> wrote: Do you have three steps to create each partition. Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Richard Poole Sent: Thursday, April 30, 2015 12:10 PM To: [email protected]<mailto:[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
