none
MDT 2012 Image Deployment on Surface Pro RRS feed

  • Question

  • I am trying to deploy a win8 image on a new surface pro.  I currently have mdt2012 deploying win8 images using LTI deployment.  I have a fully automated task sequence (PXE or USB boot) that names computer, joins domain, WSUS updates, multicast, etc.  This works flawless on desktops/laptops.  Question is, can I incorporate this same procedure and boot from a USB on the Surface and run this same task sequence?  I have disabled secure boot on surface.  can I run an NTFS bootable USB stick on the Surface? or does it have to be FAT32?  any information to get me going would be great.  Thanks
    Wednesday, August 14, 2013 9:26 PM

Answers

  • no, I had the firmware and drivers already in place.  I had to add an IP helper to VLAN interface on the switchport I was connected to.  I thought the helper had to boot to the DHCP server, but no, has to point to the WDS.
    Wednesday, August 21, 2013 12:52 PM

All replies

  • Haven't tried it myself, but see if this gets you started:

    http://blogs.technet.com/b/deploymentguys/archive/2013/05/16/pxe-deployment-with-surface-pro.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, August 14, 2013 10:52 PM
  • Everything in the process will work except the boot USB must be FAT32 since the Surface Pro is UEFI based.  Also, make sure to grab the latest drivers for it: http://www.microsoft.com/en-us/download/details.aspx?id=38826

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Thursday, August 15, 2013 12:21 AM
    Answerer
  • Like David said make sure you format it as FAT32. Use "Media" in MDT to create a bootable/portable MDT. I'd recommend making good use of selection profiles and separate folders to keep your tablet apps, drivers, etcetera together. No point creating media that includes stuff you don't need. Make sure only x86 is selected as platforms supported so the correct UEFI files are used.
    Thursday, August 15, 2013 2:27 PM
  • I think my first step is to get PXE boot to work.  I have the latest firmware and the Surface Pro Ethernet Adapter.. all the drivers installed.  I hold down the volume button while powering up and get to the Start PXE over IPv4.  I never get the option to hit enter.  it then goes to Start PXE over IPv6 and then loads Windows.  I tried changing the DHCP option 067 Bootfile Name to Boot\x86\Bootmgfw.efi with no success (same exact results) and I also tried adding an IP Helper address to the vlan associated with the switch port I am connected to (and removed the bootfilename option).. same results.  am I doing something wrong?  
    Thursday, August 15, 2013 8:44 PM
  • Looking at the thread here: http://blogs.technet.com/b/deploymentguys/archive/2013/05/16/pxe-deployment-with-surface-pro.aspx

    1. You can't do this on a new out of the box Surface, you have to first boot it up and update the firmware.

    2. Look at this: http://support.microsoft.com/kb/2602043/EN-US as many of us will fall under the mix of UEFI and BIOS environments.

    Ben said "Essentially you will need to use IP Helpers rather than specifying a boot file via DHCP."

    Thursday, August 15, 2013 9:18 PM
  • Looking at the thread here: http://blogs.technet.com/b/deploymentguys/archive/2013/05/16/pxe-deployment-with-surface-pro.aspx

    1. You can't do this on a new out of the box Surface, you have to first boot it up and update the firmware.

    2. Look at this: http://support.microsoft.com/kb/2602043/EN-US as many of us will fall under the mix of UEFI and BIOS environments.

    Ben said "Essentially you will need to use IP Helpers rather than specifying a boot file via DHCP."

    Thanks, I did boot the surface up and install the correct firmware and have the correct dongle with driver and I also did follow that link and remove the DHCP boot file option and added an IP Helper on the switch.  I mentioned all this is my previous comment.

    Thursday, August 15, 2013 9:22 PM
  • Sorry I've had an absurdly busy day, it's driven me to having goldfish memory syndrome :P

    Thursday, August 15, 2013 9:25 PM
  • is there logs anyway that I can sift through to determine whats going on ?
    Friday, August 16, 2013 4:07 PM
  • Got it to work.  thanks all for your input.
    Tuesday, August 20, 2013 4:29 PM
  • Good work, can you post how you got it to work? Was it the firmware update?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, August 21, 2013 4:50 AM
  • no, I had the firmware and drivers already in place.  I had to add an IP helper to VLAN interface on the switchport I was connected to.  I thought the helper had to boot to the DHCP server, but no, has to point to the WDS.
    Wednesday, August 21, 2013 12:52 PM
  • Cool, so it was actually a PXE issue. Thanks for sharing the fix, much appreciated.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, August 21, 2013 1:25 PM