anyweb Posted January 17, 2015 Report post Posted January 17, 2015 Introduction Microsoft released new updated drivers for the Surface Pro 3 yesterday and you can read about what those driver updates contained here. Here's a breakdown of what those driver versions are: Surface Pro UEFI update (v3.11.450.0) adds support for updated HD Graphics Family driver. HD Graphics Family driver update (v10.18.14.4029) enhances display stability and performance, improves user experience when using Miracast adapters. Improves compatibility with DisplayPort monitors and daisy chaining. Wireless Network Controller and Bluetooth driver update (v15.68.3073.151) addresses connectivity issues while Hyper-V is enabled. Adds an advanced feature to control the 2.4Ghz and 5Ghz band preference. Surface Home Button driver update (v2.0.1179.0) ensures compatibility with the Surface Hub app. Microsoft Docking Station Audio Device driver update (v1.31.35.7) improves the user experience while using the Surface Pro 3 Docking Station so that sound is available when a speaker is not connected to the docking station. Last year I blogged about automating the deployment of the Microsoft Surface Pro 3 using MDT 2013 and PowerShell, the original blogpost is here and I updated it in November with a newer version of the script here. Now that there are new drivers available, I've modified the PowerShell script to download and install them including the new MSI file. It creates the deployment share with a new name (MDTDeploy) instead of the default, you can always configure it as you wish. For those of you that don't know, this script is totally automated and builds a complete MDT 2013 deployment solution for deploying the Surface Pro 3 with all drivers included from Microsoft right up to January 2015, all you have to provide is Windows 8.1 x64 Update source files and optionally Office 365. Here's the new updated script. Setup MDT 2013 for Microsoft Surface Pro 3 - January 2015.zip This is what it looks like when running Once complete, it should look like this, scroll up to see if there are any errors in red, if so, fix them, The script will have downloaded several new drivers to your source path And those drivers are automatically imported into the Deployment Workbench. Below you can see the updated Intel HD Graphics driver is shown. and below is what you'll see when you UEFI network boot your Surface Pro 3 computers Prompted to change the name Prompted whether you want the optional Applications or not and off it goes with the automated deployment Please test this out and let me know how it went ! cheers niall Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 18, 2015 Report post Posted January 18, 2015 Great stuff Niall. Can I ask what does the msi file contain that the January 2015 driver folder doesn't? And if using SCCM to deploy this, does it be deployed via a standard package? Thanks Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted January 18, 2015 Report post Posted January 18, 2015 the msi is something called Surface Platform Support and it shows up in Programs and Features after being installed, but apart from that I'm not sure what it does and yes you can install it using a standard package method, it's just a msiexec /i bla.msi /q 1 Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 18, 2015 Report post Posted January 18, 2015 Good to know... didn't have this included in the deployment sequence, thanks again. Quote Share this post Link to post Share on other sites More sharing options...
Loran Posted February 23, 2015 Report post Posted February 23, 2015 Love your work! Thanks for looking out for all the IT folks that are still figuring out how to deploy hundreds of these things at a time. I've been playing around with your script since the first version, and they only thing I haven't been able to figure out is where you are getting the urls for the updates from. I've poked around on MS's download pages and haven't found any links that look like the ones you have been using each time you update the script. Where can I get the URL to manually update this next time an update is released? example: # Download Microsoft Surface Pro 3 drivers Write-Host "Downloading Surface Pro 3 January 2015 drivers.." -nonewline $clnt = New-Object System.Net.WebClient $url = "http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/SurfacePro 3 - January 2015.zip" $clnt.DownloadFile($url,$file3) Write-Host "done!" -ForegroundColor Green Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 23, 2015 Report post Posted February 23, 2015 Love your work! Thanks for looking out for all the IT folks that are still figuring out how to deploy hundreds of these things at a time. thank you ! Where can I get the URL to manually update this next time an update is released? it requires manual work, when i put together the new scripts i have to manually download the stuff and when i get to the download page after selecting one or more downloads and clicking next, i view the html source and pull the urls from there Quote Share this post Link to post Share on other sites More sharing options...
Loran Posted February 23, 2015 Report post Posted February 23, 2015 thank you ! it requires manual work, when i put together the new scripts i have to manually download the stuff and when i get to the download page after selecting one or more downloads and clicking next, i view the html source and pull the urls from there Thank you so much! Can't believe I overlooked that. Quote Share this post Link to post Share on other sites More sharing options...
drieswillems Posted March 11, 2015 Report post Posted March 11, 2015 Have you already tested how to change the UEFI Administrator Password with PowerShell? Quote Share this post Link to post Share on other sites More sharing options...
