Enabling Surface Laptop keyboard during MDT deployment
Hi, my name is Scott McArthur and I am Supportability PM with commercial Surface. Today’s blog will discuss how to enable the keyboard on the new Surface Laptop during a Microsoft Deployment Toolkit deployment. The information in this blog could be used for other deployment methodologies also
On most devices, the keyboard should work while in Lite Touch. Surface Laptop requires some additional drivers to enable the keyboard. Use the following steps:
1. Download the latest Surface Laptop .MSI from https://www.microsoft.com/en-us/download/details.aspx?id=55489
2. Extract the contents to folder
Msiexec.exe /a SurfaceLaptop_Win10_15063_1703008_1.msi targetdir=c:\surface_laptop_drivers /qn
Best practice with MDT is to create a folder for WindowsPE and use selection profile to limit what drivers are injected into Lite Touch.
For example, the WindowsPEX64 folder below
You should import the following folders into the WindowsPEX64 folder.
- C:\surface_laptop_drivers\SurfacePlatformInstaller\Drivers\System\GPIO
- C:\surface_laptop_drivers\SurfacePlatformInstaller\Drivers\System\SurfaceHidMiniDriver
- C:\surface_laptop_drivers\SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
The following shows the 3 folders imported (5 drivers). It also contains the latest Surface Ethernet Driver .
Selection profile configuration
You should also have a selection profile configured for the folder
Configuration of Windows PE.
Then in the configuration of Windows PE you choose that selection profile, WindowsPEX64.
Notes
· Make sure you are choosing X64 architecture
· Make sure you choose “include all drivers from the selection profile” option.
Just as added note you should configure the rest of the Surface Laptop drivers using selection profile or DriverGroup001 variable. The model is Surface Laptop
When deploying a new image to Surface Laptop you should also be aware of the following issue:
4032347 "Your organization used Device Guard to block this app" error on Surface Laptop https://support.microsoft.com/en-US/help/4032347
Update 8/23/2017: My friend Frank Rojas from the Configuration Manager OSD Support Team blog was kind enough to test this in Configuration Manager 1702. He sent the following screenshots over which shows you what it looks like
Driver Properties
Hope this helps with your deployments.
Scott McArthur