This happened to a friend of mine as well, witht he same model. I haven't
had a chance to test it myself, but you should be able to use a WQL query
to test, like so:
* If Surface Pro 5
* If index = 0
Regular partitioning step
* if index = 2
etc...
On Fri, Jul 28, 2017 at 2:44 PM, Keith Garner <[email protected]>
wrote:
> Sorry, I have not had a chance to try the latest Surface Pro [5] Model
> with MDT.
>
>
>
> But, yes, MDT Litetouch (for example), makes assumptions that the primary
> target disk is fixed, like “Disk 0”.
>
> If true, open a support case, or post the question on the Surface IT
> Forums, someone from Microsoft Surface should respond.
>
>
>
> (it’s possible that the storage controller has some weirdness, like the
> Surface Studio, which has 2 disks but is combined as one with the storage
> driver).
>
>
>
> -k
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *[email protected]
> *Sent:* Friday, July 28, 2017 10:39 AM
> *To:* [email protected]
> *Subject:* RE: [MDT-OSD] RE: Diskpart disk 0 does not show and internal
> disk shows as 2
>
>
>
> I'm glad I'm not they only one too. Unfortunately I knew we are getting
> more so now I definitely need to find a better solution so the guys doing
> the actual deployments don't have problems.
>
>
>
> I was already playing with a script to do diskpart /s and a txt file being
> built on the fly to do something else so I am hoping I can just modify that
> to do what I want. If I get it to work I'll let you know and send it over.
>
>
>
>
>
>
>
> Sent from my Verizon 4G LTE smartphone
>
>
>
> -------- Original message --------
> From: "Vann, Gerry" <[email protected]>
> Date: 7/28/17 1:27 PM (GMT-05:00)
> To: [email protected]
> Subject: [MDT-OSD] RE: Diskpart disk 0 does not show and internal disk
> shows as 2
>
> Thanks for the response, good to hear I’m not the only one who has seen
> this on the new Surface model. Like you, I will probably just copy and
> modify my task sequence to get it out the door.
>
>
>
> Still, I’m just wondering what happened to disk 0 and disk 1.
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *[email protected]
> *Sent:* Friday, July 28, 2017 12:26 PM
> *To:* [email protected]
> *Subject:* [MDT-OSD] RE: Diskpart disk 0 does not show and internal disk
> shows as 2
>
>
>
> We recently got two Surface Pros (2017 model) and saw the same thing. One
> of them had the physical drive as index 0, which is what you would expect,
> and the other was index 2. The one with index 2 would always fail the
> partition steps until I adjusted them to point to disk index 2 but with my
> time constraints I wasn’t able to find a way to variableize the disk the
> partition steps are trying to format. So to get the device out the door I
> just copied the task sequence then changed the steps to point to disk 2
> then used that task sequence to image the machine.
>
>
>
> Does anyone have a way to turn the disk index the partitioning steps point
> to into a variable? It could probably be done with a powershell script run
> in place of the built in steps.
>
>
>
> *Ben Smith*
>
> *Everest Technology Services*
>
> *Everest Global Services, Inc.*
>
> Westgate Corporate Center | 477 Martinsville Rd, P.O. Box 830 | Liberty
> Corner, NJ 07938-0830
>
> (O) +1 908-604-3167 <(908)%20604-3167> | [email protected]
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Vann, Gerry
> *Sent:* Friday, July 28, 2017 11:19 AM
> *To:* [email protected]
> *Subject:* [MDT-OSD] Diskpart disk 0 does not show and internal disk
> shows as 2
>
>
>
> Hello,
>
>
>
> We have a new Surface Pro 5 that I’m trying to image. When I boot to
> WinPE open a command prompt and run DISKPART then List Disk it does not
> show a disk 0 or disk 1. The internal drive shows as disk 3 and the USB
> drive I booted from shows as Disk 2. Likewise, if I PXE boot then the
> internal drive shows as disk 2 and again disk 0 and disk 1 do not show.
> When I attempt to select disk 0 or 1 it tells me they do not exist.
>
>
>
> I can see the internal drive so I’m confident the storage drivers are
> there. Since by default we autodeploy to disk 0 this causes issues with
> our default task sequence. I know I can change this and make a one off,
> but I’d rather figure out what’s up with this Surface Pro 5 and will they
> all ship this way.
>
>
>
> I was able to boot from a Windows 10 ISO and image it, I then downloaded
> the latest drivers and firmware then updated that….same issue. Disk
> management in the Windows 10 install that’s on there now lists the os drive
> as Disk 2.
>
>
>
> Any idea’s how I can get disk 0 to show up?
>
>
>
> Thanks,
>
> Gerry
>
>
> ------------------------------
>
>
> This e-mail is intended only for the person or entity to whom it is
> addressed and may contain information that is privileged, confidential, or
> otherwise protected from disclosure. If you are not the intended recipient,
> or an employee or agent responsible for delivering this message to the
> intended recipient, you are notified that any disclosure, copying,
> distribution, or the taking of any action in reliance on the contents of
> this message is prohibited. If you have received this e-mail in error,
> please contact the sender immediately and delete the original message and
> all copies from your system. Statements and representations made in this
> message are not necessarily that of the Company.
>
>
> ------------------------------
>
>
> This e-mail is intended only for the person or entity to whom it is
> addressed and may contain information that is privileged, confidential, or
> otherwise protected from disclosure. If you are not the intended recipient,
> or an employee or agent responsible for delivering this message to the
> intended recipient, you are notified that any disclosure, copying,
> distribution, or the taking of any action in reliance on the contents of
> this message is prohibited. If you have received this e-mail in error,
> please contact the sender immediately and delete the original message and
> all copies from your system. Statements and representations made in this
> message are not necessarily that of the Company.
>
