How can I deploy Windows 10 x64 to the Microsoft Surface Pro 4 using MDT 2013 Update 1

[anyweb]

Introduction

In a previous post I've shown you how you can deploy Windows 10 x64 to the Surface Pro 3 with MDT 2013 Update 1 using a PowerShell script. Now that the Surface Pro 4 is released it's time to automate that installation also, so here we go !

 

 

The PowerShell script is to be run on your soon-to-be MDT server and it will create everything for you, all you have to do is supply it with an OS (Windows 10 x64) and optionally some apps, drivers or even the Windows ADK 10. Fear not, if you don't have the Surface Pro 4 drivers or Windows ADK 10 then the script will download them for you.

 

Download the script

You can download the script here, then unzip it.

 

Deploy Microsoft Surface Pro 4 with MDT 2013 Update 1- October 2015.zip

 

To use the script simply adjust the many variables within to suit your needs, the one you'll probably want to change first is

$SourcePath = "E:\Source"

followed by the CustomSettings.ini variables starting at line 310 as shown here...

 

 

then the BootStrap.ini variables on line 386 and onwards as shown here..

 

 

Once done, copy Windows 10 X64 Enterprise to the specified folder

 

 

and decide if you want the script to download the following:

 

• Windows ADK 10
• MDT 2013 Update 1
• Surface Pro 4 drivers
• Surface Ethernet adapter driver
• Surface Gigabit Ethernet adapter driver

 

If you do NOT want the script to automatically download the above content, then manually copy the files to the location specified in the script

 

 

If you place the files listed above in the wrong folder or use a different name than specified in the script, then the script will attempt to download them again.

 

When you are ready to test the script, run it by starting Windows PowerShell ISE as Administrator.

 

 

The script will automatically configure Windows ADK 10 and MDT 2013 Update 1. In addition, it will install Windows Deployment Services and after configuring the MDT DeploymentShare it will import the x64 boot image into WDS.

 

The x64 boot image in MDT 2013 Update 1 will have both the Surface Pro 4 100mb and gigabit network drivers injected. If you want to remove with, simply rem out the line in the script.

 

The script will import all drivers for the Surface Pro 4 into the MDT 2013 Update 1 deployment workbench.

 

Once the script is complete you should see something like the following screenshot

 

 

you can go ahead and launch the MDT 2013 Update 1 deployment workbench to review what has happened. Here you can see the drivers imported for the Surface Pro 4.

 

 

Opening the task sequence reveals the Inject Drivers step for the Surface Pro 4 containing the WMI query needed

 

 

after you are done admiring what it's put in place, it's time to UEFI network boot your Surface Pro 4 and enjoy the show

 

 

Related Posts

• MDT 2013 Update 1 re-released - http://blogs.technet.com/b/msdeployment/archive/2015/09/15/mdt-2013-update-1-re-released-build-8298.aspx
• Where can I find the official drivers for the new Surface Pro 4 and Surface Book products ?
  http://www.niallbrady.com/2015/10/26/where-can-i-find-the-official-drivers-for-the-new-surface-pro-4-and-surface-book-products/
• CM12 in a Lab - How can I deploy Windows 10 Enterprise x64 with MDT 2013 Update 1 integrated with System Center 2012 R2 SP1 Configuration Manager ?
• CM12 in a Lab - How can I upgrade to System Center 2012 R2 SP1 with MDT 2013 update 1 integrated ?

Until next time, adios !

[chida]

How about pen pairing in Surface Pro 4 during deployment, is it the same as for Surface Pro 3 as descibed in your article

 

"https://www.windows-noob.com/forums/topic/11508-how-can-i-add-support-for-pen-pairing-during-oobe-on-a-surface-pro-3-using-system-center-2012-r2-configuration-manager/"

[anyweb]

yup it works the same, it just looks different in windows 10 (more polished)

[alou]

Hi anyweb,

 

I am having this really odd issue with my deployment of Windows 10 (1511) x64 with MDT 2013 Update 1 and Update 2 as well.The deployment wizard windows size on the Surface Pro 4 are really small and I cant seem to make them any bigger except by resizing them. Also, audio drivers are not being injected in Windows. Once deployment is complete Surface Pro 4 is missing the audio drivers. Only way to get the audio drivers installed is to manually update them.

I am attaching pictures just to have a better view of the issues.

 

Any idea how to solve my issues?

 

Thanks!

[anyweb]

something is clearly not right, which drivers are you using and did you try my script ?

[alou]

Hi,

 

first of all thank you for approving and replying to my post.

I need to be honest, I haven't ran the script, but locking at you script I did follow all the instructions, just like I have been doing for years when building images using MDT.

Drivers have been added, selection profiles created and correctly assigned using WMI queries in the task sequence, but I am having the issues I described. For instance, image for Surface Pro 1 works great, just having issues with the Pro 4.

Any clue?

 

Thanks!!

[anyweb]

which driver pack are you using ?

[alou]

SurfacePro4_Win10_160128_0.zip - The one downloaded from MS: https://www.microsoft.com/en-us/download/details.aspx?id=49498

 

I can see all the drivers (including the sound ones) added to the deployment (out-of-box drivers).

 

Installing the driver manually once Windows 10 deployment finishes works, which I believe it means that there is nothing wrong with the hardware.

[jeffsolberg125]

Attempting to deploy Windows 10 to Surface Pro 4 using MDT 2013 SP1. I updated ADK to include Win 10 support on my Build Server. Using WDS and MDT combo.

 

I have had no issue deploying the Surface Pro 3 in my environment deploying Windows 8.1.

 

The issue i am running into is it appears that my WinPE boot images cannot find a storage driver for the SP4. I get all the way into the PXE sequence with no issue. I choose the task sequence I have created for SP4 which points to a selection profile containing the SP4 drivers I got from Microsoft. I imported them into the deployment share i have for the rest of my models i am deploying. I took the 2 network drivers from the SP4.zip and placed them into my WinPE boot image. I then ran an update to my deployment share and re-published the Boot images to the WDS server.

 

I get all the way through the task sequence selections and it starts the LiteTouch Deployment. As soon as it gets to the task that it formats the disk, the deployment fails with the following error:

 

#################################

## Disk(0) was not found. Unable to continue.

##Possible Cause: Missing Storage Driver.

##################################

Failure (7711 ) Disk OSDiskindex(0) can not be found!

Litetouch deployment failed: Return Code = 214767259 0x80004005

##################################

 

I believe the Surface Pro 4 model that comes with the 128 GIG Drive is a Samsumg MZFLV128 SSD. I have went out to Samsung's site and got the driver for this model and included it in my WinPE boot image along with the MS SP4 drivers and no resolution. I have spent the better part of today on this. I have seen others successfully deploy the SP4 using MDT but not many. I am hoping someone here can lend a hand. Thanks in advance.

 

-Jeff

[fluidmint]

Hi Anyweb,

 

Any chance this could be updated please? I wouldn't want your hard work to be wasted. The drivers/firmware link needs updating. Also I keep getting an error when the script tries to create the task sequence. Could you give me any advice please?

 

Import-MDTTaskSequence : Cannot bind parameter 'OperatingSystemPath' to the target. Exception setting "OperatingSystemPath": "Cannot find path

'DS001:\Operating Systems\Windows 10 x64\sources\install.wim' because it does not exist."

At E:\Deploy Microsoft Surface Pro 4.ps1:304 char:211

+ ... tingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullN ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : WriteError: ( [import-MDTTaskSequence], ParameterBindingExcept

[anyweb]

 

Hi Anyweb,

 

Any chance this could be updated please? I wouldn't want your hard work to be wasted. The drivers/firmware link needs updating. Also I keep getting an error when the script tries to create the task sequence. Could you give me any advice please?

 

Import-MDTTaskSequence : Cannot bind parameter 'OperatingSystemPath' to the target. Exception setting "OperatingSystemPath": "Cannot find path

'DS001:\Operating Systems\Windows 10 x64\sources\install.wim' because it does not exist."

At E:\Deploy Microsoft Surface Pro 4.ps1:304 char:211

+ ... tingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullN ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : WriteError: ( [import-MDTTaskSequence], ParameterBindingExcept

 

 

i'm updating it now and will post a new blog post shortly, but in the mean time look for the line that contains this string

 "$SourcePath\Operating Systems\$OStoDeploy"

and change it to

 "$SourcePath\Operating System Images\$OStoDeploy"

then run it again, should work

 

and depending on the version of Windows 10 you are deploying (1507 or 1511) read the change below, the above script was only tested with Windows 10 x64 - 1507, therefore if you use Windows 10 x64 - 1511 (original november release) it would fail, the below will resolve that.

# use this line for Windows 10 1507
# import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose
# Use this line for Windows 10 1511
import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise Technical Preview in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose

If however you are using the Windows 10 x64 - 1511 media that was updated to February 2016 (availabe on Microsofts volume license site) then use the first import statement and rem out the second, like so.

# use this line for Windows 10 1507, or updated Windows 10 1511 media from Feb 2016
import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose
# Use this line for original Windows 10 1511 media
# import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise Technical Preview in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose

[fluidmint]

 

 

i'm updating it now and will post a new blog post shortly, but in the mean time look for the line that contains this string

 "$SourcePath\Operating Systems\$OStoDeploy"

and change it to

 "$SourcePath\Operating System Images\$OStoDeploy"

then run it again, should work

 

and depending on the version of Windows 10 you are deploying (1507 or 1511) read the change below, the above script was only tested with Windows 10 x64 - 1507, therefore if you use Windows 10 x64 - 1511 (original november release) it would fail, the below will resolve that.

# use this line for Windows 10 1507
# import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose
# Use this line for Windows 10 1511
import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise Technical Preview in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose

If however you are using the Windows 10 x64 - 1511 media that was updated to February 2016 (availabe on Microsofts volume license site) then use the first import statement and rem out the second, like so.

# use this line for Windows 10 1507, or updated Windows 10 1511 media from Feb 2016
import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose
# Use this line for original Windows 10 1511 media
# import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise Technical Preview in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose

Still the same error message I'm afraid.

[anyweb]

did you see my new blog post here, as regards your current failure message i'd need to see the entire output from the script, can you post it please ? (copy/paste save as a txt file and attach)

[pk@ianz]

Hi Niall,

 

I am tryign to deploy an captured OS image to SP4 via MDT 2013 (Update 1). I am getting the below error:

 

FAILURE ( 5624 ): 1392: Run DISM: /Apply-Image /ImageFile:"\\WDS\SP4Sept2016$\Operating Systems\WIN10Ver1607x64\WIN10Ver1607x64.wim" /Index:1 /ApplyDir:E: LTIApply 28/09/2016 2:06:04 p.m. 0 (0x0000)
Event 41002 sent: FAILURE ( 5624 ): 1392: Run DISM: /Apply-Image /ImageFile:"\\WDS\SP4Sept2016$\Operating Systems\WIN10Ver1607x64\WIN10Ver1607x64.wim" /Index:1 /ApplyDir:E: LTIApply 28/09/2016 2:06:04 p.m. 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 28/09/2016 2:06:05 p.m. 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 28/09/2016 2:06:05 p.m. 0 (0x0000)
Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 28/09/2016 2:06:05 p.m. 0 (0x0000)

 

I can deploy Surface Pro 3 without any issues but only get the above error for Surface Pro 4. Any idea ?

 

[anyweb]

have you tried with MDT 2013 Update 2 ? and what version of ADK are you using ?