here is a reply I received from Microsoft... Hey Team,
The issue is a bug that intel fixed in the iastor driver. This driver has a fix that’s been delivered in the latest drivers located here: http://www.microsoft.com/en-us/download/details.aspx?id=38826 but only in the MSI. We will be releasing the driver to the .zip file shortly. Until we release the driver, you can have a look at this guide - http://blogs.technet.com/b/askcore/archive/2014/07/15/deploy-windows-to-surface-pro-3-using-microsoft-deployment-toolkit.aspx Take the zip file on the site, and create a device specific driver pack and apply that in your task sequence. This will help you to continue to deploy. For machines where the issue has occurred, if you boot to UEFI and don’t see the SSD as an option, that device will have to be exchanged. jeff On Tue, May 5, 2015 at 11:53 AM, Richard Poole < [email protected]> wrote: > The one I had needed to be sent out to a user right away so I didn’t > have time to really beat it up, did learn the joys of creating a full > restore USD thumb drive. I have another SurPro3 being ordered and should > here shortly that is all mine to play with. I’ll get the info to you as > soon as possible, though I’m hoping the first one was just a fluke. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *keith garner > *Sent:* Thursday, April 30, 2015 11:40 PM > > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Surface Pro 3 disk goes AWOL during partition job > > > > I haven’t seen the disappearing disk 0 issue on a surface pro 3. Note > that this is not a MDT or SCCM issue, since winpe loses the disk, there is > nothing to do. My best guess is that this is a storage driver issue, a > WinPE issue or some faulty firmware. If you see the issue again, can you > grab the uEFI version firmware version, and the WinPE ‘revision’ number? I > can follow up internally. > > > > Additionally, check out the surface bare metal recovery bits, they contain > a WinPE boot wim built by surface. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Richard Poole > *Sent:* Thursday, April 30, 2015 10:12 AM > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Surface Pro 3 disk goes AWOL during partition job > > > > 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] <[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]> > 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]] *On Behalf Of *Richard Poole > *Sent:* Thursday, April 30, 2015 12:10 PM > *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 > > >
