Jump to content


We use cookies to let you log in, for ads and for analytics. OK

Photo

How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using MDT 2013 ?





  • Please log in to reply
66 replies to this topic

#1 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 19 October 2014 - 08:29 PM

Introduction

In a previous post I showed you how you can deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager.
 

Surface-Pro-3.jpg

 

In this post I'll show you how to do the same thing with Microsoft Deployment Toolkit (MDT) 2013, except this is fully automated, all you have to provide is a server, the operating system files and change a few variables in the script.

 

Note: As this is fully automated, and as this does install a WDS server role hosting a boot image, you should test it in a lab first and modify the script accordingly.

 

There are many PowerShell scripts out there to create fully automated labs (hydration kits) from MDT gurus like Johan Arwidmark or Mikael Nystrom or upcoming cool dudes like Nickolaj Andersen, but this script is tailored for one thing only, deploying Windows 8.1 x64 to the Microsoft Surface Pro 3 with all drivers loaded.

 

You may want to download it and customize it to suit your needs for other hardware because what it does is pretty cool.

 

This script performs the following actions:-

  • Downloads and then Installs Windows ADK 8.1 (if you have not done so already)
  • Downloads and then Installs MDT 2013 (if you have not done so already)
  • Downloads all required drivers for Microsoft Surface Pro 3 (see screenshot below)

Downloading Surface Pro 3 drivers.png

  • Adds the Windows 8.1 x64 operating system into MDT
  • Adds the Microsoft Surface Pro 3 drivers into MDT (see screenshot below)

Surface Pro 3 drivers in the Deployment Workbench.png

  • Creates Selection Profiles for Microsoft Surface Pro 3 and WinPE x64 (see screenshot below)

selection profiles.png

  • Creates a Deploy Windows 8.1 x64 - Surface Pro 3 task sequence
  • Edits the Deploy Windows 8.1 x64 - Surface Pro 3 task sequence and adds an inject drivers step for Microsoft Surface Pro 3 (see screenshot below)

Surface Pro 3 drivers step.png

 

in addition, it sets the WMI query for the Surface Pro 3 on that step (see screenshot below)

 

wmi query.png

  • Injects the Microsoft Surface Pro 3 network drivers into the LiteTouchPE_x64.wim
  • Creates new CustomSettings.ini and BootStrap.ini files
  • Disables the X86 boot wim (not needed for Surface Pro 3)
  • Changes the Selection Profile for the X64 boot wim to use the WinPE x64 selection profile (see screenshot below)

winPE x64 selection profile.png

  • Installs the Windows Deployment Service role
  • Configures the WDS role and adds the previously created LiteTouchPE_x64.wim (see screenshot below)

wds with lite touch windows pe boot wim.png

  • Starts the WDS service so that you can PXE boot (UEFI network boot).

All you have to do is download the script below, then place some files in the right place, PXE boot a Microsoft Surface Pro 3 and sit back and enjoy the show. So let's get on with what you need to do...

 

Step 1. Download the script

 

This PowerShell script will do all the hard work for you, download it and place it on your server that is designated to be the MDT 2013 server. I've tested it on Server 2012R2 only, if you run it on a different operating system and have issues then post your results below.

 

Attached File  Setup MDT 2013 for Microsoft Surface Pro 3.zip   5.79KB   1001 downloads

 

Update: I've updated the script above to include the March 2015 drivers and updates and it's available here.

 

Step 2. Configure the variables in the script

 

Once you have downloaded the script, you should configure the variables interspersed throughout the script, the most important of them is the $SourceFolder variable as this decides where to get the content from (if you've copied it already) and where to store it. This variable should point to a valid drive letter, the folder name will be created if it does not exist.

 

change the SourcePath variable.png

 

The $FolderPath variable will be the MDT Deployment share root folder eg: E:\DeploymentShare.

 

There are other variables to configure, scroll down through the script to find them, such as the ones below

 

configuring variables.png

 

You will also want to edit the CustomSettings.ini and BootStrap.ini settings within the script to suit your own environment.

 

Step 3. Copy the Windows 8.1 x64 operating system files

 

Mount a Microsoft Windows 8.1 x64 Enterprise ISO and copy the contents to $SourceFolder\Operating Systems\ as shown below

 

copy the Windows 81 iso contents.png

 

Step 4. Copy MDT 2013, ADK 8.1, Surface Pro 3 drivers (optional)

 

If you've already downloaded the above files then place them in the source folder, otherwise the script will download them for you. In the screenshot below you can see I'm manually copying the offline ADK 8.1 files, you do not have to do this as the script will download the content for you if it's not found.

 

copy the Windows ADK 81.png

 

Step 5. Copy your Applications to the respective folders (optional)

 

If you have apps like Office 2013, copy them to their respective folders as shown below

 

Office 2013 Pro Plus.png

 

If you do add apps, then you'll also need to change the following section of CustomSettings.ini

SkipApplications=YES

to

SkipApplications=NO

Step 6. Run the script

 

On the server that is to be your MDT server, start the script in PowerShell ISE or which method you prefer, below you can see the script in action, it has just created the selection profiles for the Surface Pro 3

 

the script in action.png

 

After the script is complete, you are ready to test deploying a Microsoft Surface Pro 3 installation.

 

script is all done.png

 

and below you can see the E:\Source folder after the script has run, it has downloaded a bunch of stuff !

 

source folder.png

 

Step 7. Sit back and watch the deployment

 

Take a properly shutdown Surface Pro 3, and power it on using the following sequence

 

Hold the down volume key and then press the power button while continuing to hold down the volume key, it should PXE boot

 

Press enter when prompted

 

PXE boot.png

 

and then it will load the MDT LitetouchPE_X64 boot wim.

 

LiteTouchPE_X64.png

 

before prompting you for a computername, note that it's currently set to SurfacePro3,

 

Windows Deployment Wizard shows the SurfacePro3 computername.png

 

you can change it in the UI itself or automate it via the many methods available such as those that Mikael describes here

 

click next and off it goes, inject the Surface Pro 3 drivers (oh and of course, you've got working network in WinPE as the network drivers were added to the boot wim already)

 

drivers injected.png

 

and after a wee while, it's done.

 

the finished product.png

 

Troubleshooting

 

If the script has issues starting WDS (and you see the error below)

 

An error occurred while trying to execute the command.
Error Code: 0x41D
Error Description: The service did not respond to the start or control request in a timely fashion.

 

 

then restart the server, as you were asked to do at the end of the script ;-).

 

For deployment issues, you can review the logs found in the following locations depending on what part of the OSD process you are in:-

 

In WinPE

 

  • X:\windows\temp\SMSTSLOG

 

In Windows

 

  • C:\Windows\Temp\DeploymentLogs
  • C:\MININT\SMSOSD\OSDLOGS
  • C:\Users\Administrator\Appdata\Local\temp\SMSTSLog

 

Summary

 

Automating the deployment of Windows 8.1 x64 Enterprise to the Microsoft Surface Pro 3 is not only possible but relatively easy with MDT 2013 and a custom powershell script like the one above. I must also say a big thanks to Nikolaj who helped me with some issues in the script, you are awesome !

 

Related Reading


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog



#2 ccatlett1984

ccatlett1984

    Newbie

  • Established Members
  • Pip
  • 1 posts
  • Gender:Male
  • Location:Detroit, MI

Posted 20 October 2014 - 05:11 AM

Depending on what firmware your Surface Pro 3 has loaded, you may not be able to PXE boot at all.

 

http://blogs.technet...urface-pro.aspx

 

If the device your trying to image still has the April firmware, you won't be able to PXE.

You can either use a usb boot drive to chain into MDT, or update the firmware while on the factory load, then PXE.



#3 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 20 October 2014 - 06:48 AM

that blog post was for the original Surface Pro surely based on the date (16th of May 2013...), this blog post is for the Surface Pro 3 which was released earlier this year

 

Surface Pro: February 9, 2013[3]
Surface Pro 2: October 22, 2013
Surface Pro 3: June 20, 2014

 

there were issues with older firmware on Surface Pro 3 causing slow UEFI boot but that's fixable by a variety of methods including those below

 


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#4 ricardou

ricardou

    Newbie

  • Established Members
  • Pip
  • 1 posts

Posted 22 October 2014 - 05:10 PM

Hey, have you released how to make a bootable MDT deployment for the UEFI Surface Pro 3.  I have tried to do it a couple of ways, and have failed.  I have been using an external usb hard drive, since it had a controller I could use to go between different partitions.  Any suggestions?



#5 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 22 October 2014 - 09:44 PM

assuming you've completed my guide above and have run the script, and everything finished successfully, then try expanding Advanced, select Media, right click and choose New Media

 

new media.png

 

point to a blank folder (such as E:\Media) for the Media Path step and select the Everything selection profile as shown below

 

media path.png

 

continue through that wizard until completion, here's the powershell to do the above

Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\DeploymentShare"
new-item -path "DS001:\Media" -enable "True" -Name "MEDIA001" -Comments "creating bootable media for the Surface Pro 3 (c) windows-noob.com October 2014" -Root "E:\Media" -SelectionProfile "Everything" -SupportX86 "True" -SupportX64 "True" -GenerateISO "True" -ISOName "LiteTouchMedia.iso" -Verbose
new-PSDrive -Name "MEDIA001" -PSProvider "MDTProvider" -Root "E:\Media\Content\Deploy" -Description "Embedded media deployment share" -Force -Verbose

Next, manually copy BootStrap.ini and CustomSettings.ini from E:\DeploymentShare\Control to E:\Media\Content\Deploy\Control and answer yes to the replace.

 

replace the files.png

 

Next, right click on the new Media, choose properties

 

media properties.png

 

remove support for the X86 boot wim as it's not needed for support Surface Pro 3

 

platforms supported.png

 

Select the Windows PE Tab, and choose the drop down for X64, then select Drivers and patches and make sure the WinPEx64 selection profile is selected

 

WinPE x64.png

 

close the wizard when done.

 

Finally, right click the Media001 and choose Update Media Content,

 

Update Media Content.png

 

continue through that wizard

 

Update Media Content done.png

 

or use this powershell script

Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\DeploymentShare"
Update-MDTMedia -path "DS001:\Media\MEDIA001" -Verbose

Once done, browse to your media folder, eg: E:\Media and use the ISO provided to image your Surface Pro 3.

 

LiteTouchMedia.png

 

alternatively, you can mount the ISO and copy the contents to a FAT32 formatted usb key/disc and boot from that instead,

 

you might need to use diskpart to make that partition (vol) active, the USB disc must be formatted as FAT32 as UEFI devices cannot boot from USB media formatted as NTFS.


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#6 chandrashekar

chandrashekar

    Newbie

  • Established Members
  • Pip
  • 5 posts

Posted 25 November 2014 - 10:37 AM

Dear Niall.

 

I am a big fan of you as many of your articles are real life savers. I am approaching now for a solution for Windows 8.1 custom image deplyment on surface pro 3 . I have an image which is around 10 Gigs and am unable to copy it in USB due to Fat 32 restriction as surface only supports fat32, I dont have an option of using WDS as BootP is not an option in my network. Only way out am thinking is boot using USB and install OS over the network using MDT 2013. am not successful in it,can you guide me in doing this and also any other ways of achieving this.desperately seeking  your reply.

 

Regards

Chan



#7 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 25 November 2014 - 10:55 AM

hi Chan
 

 

I am a big fan of you as many of your articles are real life savers

 

 

thanks !
 

 

I have an image which is around 10 Gigs and am unable to copy it in USB due to Fat 32 restriction as surface only supports fat32, I dont have an option of using WDS as BootP is not an option in my network. Only way out am thinking is boot using USB and install OS over the network using MDT 2013. am not successful in it,can you guide me in doing this and also any other ways of achieving this.desperately seeking  your reply.

 

 

Keith Garner explains how to work around that problem here


  • chandrashekar likes this
Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#8 chandrashekar

chandrashekar

    Newbie

  • Established Members
  • Pip
  • 5 posts

Posted 26 November 2014 - 04:37 AM

Thanks Niall, that worked ,but I am now stuck with deployment, not sure if any changes to be made to task sequence, I am getting command prompt with X:\ windows\system32 prompt after the installation completes, I exit out of it, system reboots and gets stuck in :Getting ready screen" for long time and then "Unattend.xml parse ..could not access panther etc.. failure" message  pops and another message says installation incomplete and asks to reinstall again, (IE welcome page - false) which was an issue is fixed in 2013,not sure what the issue with 2013.. kindly help



#9 chandrashekar

chandrashekar

    Newbie

  • Established Members
  • Pip
  • 5 posts

Posted 26 November 2014 - 05:09 AM

 

Am attaching the actual error message and also the "unattend.xml with oobe system" screenshot.Am unable to attach xml file for your reference to this post,kindly let me know if I have to email you if you want to have a look at it.

 

Kindly let me know if any more info required

 

Eagerly Waiting for your reply.

 



#10 chandrashekar

chandrashekar

    Newbie

  • Established Members
  • Pip
  • 5 posts

Posted 26 November 2014 - 05:49 AM

Thanks

Attached Files



#11 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 26 November 2014 - 10:01 AM

are you following my guide exactly ? are you using Windows 8.1x64 UPDATE, are you using a custom unattend.xml file (not needed)


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#12 chandrashekar

chandrashekar

    Newbie

  • Established Members
  • Pip
  • 5 posts

Posted 27 November 2014 - 10:21 AM

Hi Niall, I just used the steps, not the script. so the issue, but managed to get through by "disabling First Run Wizard" for IE

 

Thanks again for all your help...



#13 arjanv

arjanv

    Newbie

  • Established Members
  • Pip
  • 7 posts

Posted 01 December 2014 - 07:36 AM

hi,

 

great guide. thanks.

 

but what about the Surface Pro 2? I got MDT setup with the correct drivers and so on, but when i pxe boot the boot.wim takes about 6 ~8 minutes to load.

anyone has experienced the same?



#14 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 01 December 2014 - 07:40 AM

do all your computers take this long to pull down the boot wim ?


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#15 arjanv

arjanv

    Newbie

  • Established Members
  • Pip
  • 7 posts

Posted 01 December 2014 - 08:29 AM

do all your computers take this long to pull down the boot wim ?

 

Hi,

 

No only the Microsoft Surface pro 2..........at least for now.

Surface pro 3 and "normal" computers works fine.



#16 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 01 December 2014 - 10:09 AM

well have you tried to update the firmware on the SP2 via windows update, then once done, pxe boot and see is there any difference in speed ?


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#17 arjanv

arjanv

    Newbie

  • Established Members
  • Pip
  • 7 posts

Posted 01 December 2014 - 10:37 AM

well have you tried to update the firmware on the SP2 via windows update, then once done, pxe boot and see is there any difference in speed ?

Yes, makes no difference.



#18 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 01 December 2014 - 12:35 PM

is it only slow via PXE UEFI network boot, have you tried USB boot ?


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#19 takim

takim

    Newbie

  • Established Members
  • Pip
  • 1 posts

Posted 29 December 2014 - 08:15 PM

I'm trying to run this but it's not creating the task sequence. I'm getting an error during this part that says cannot find file but it's there so not sure why it's failing. Any ideas?

 

 

 

Edit: Well I got around it by manually creating the Task Sequence but I'd be curious to know what was causing the Import-MDTTaskSequence to fail though. Also thanks for this. Works great. I had tried setting one up using the technet article prior but it would boot to a recovery screen after the deployment completed. Couldn't figure out what was wrong.

Import-MDTTaskSequence : Cannot bind parameter 'OperatingSystemPath' to the target. Exception setting "OperatingSystemPath": "Cannot find path 
'DS001:\Operating Systems\Windows 8.1 x64\Windows 8.1 Enterprise in Windows 8.1 Enterprise x64 install.wim' because it does not exist."
At C:\Users\smsworkr\Desktop\Setup MDT 2013 for Microsoft Surface Pro 3.PS1:302 char:219
+ import-mdttasksequence -path "DS001:\Task Sequences\Windows 8.1 x64" -Name "Depl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [Import-MDTTaskSequence], ParameterBindingException
    + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.BDD.PSSnapIn.ImportTaskSequence


#20 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 7,251 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 30 December 2014 - 06:02 AM

well it's telling you it can't find the Install.WIM file for Windows 8.1, look at the ridiculous long file name though, that's obviously not right,

 

 

look at step 3 above and read it carefully, it should resolve your problem, let me know ok ?


Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users