SCCM HTA Front End User Variables to select Laptop and department SCCM OSD on Azure VM SCCM PXE Boot Issue SCCM PXE Pending Request ID: [Changing Everytime] SCCM Report for Server Roles and Features SCCM reports to get all active deployments SCCM SQL Query to get file name path and details...
The current package which was released 5/14/2013 contains the following: May2013SurfacePro.zip Surface Pro - Enterprise Deployment Quick Start Guide.pdfThe .pdf contains some general guidance around deploying to the Surface Pro using Microsoft Deployment Toolkit and SCCM. It also explains how ...
In the last month the Surface Pro team have started releasing driver and firmware packs that include all on the drivers and firmware required for Surface Pro. This pack is a simple zip file that contains all of the drivers as INF files that can be installed with out requiring an execu...
Step #3: Add the Surface Pro 3 Firmware and Driver pack drivers to MDTIn the Microsoft Deployment Toolkit Workbench create the following folder structure under Out-Of-Box DriversNote: The last folder must be called “Surface Pro 3” Right click Out-Of-Box Drivers\WindowsPEX64 ...
There is something different on the surface laptop. Anyone else deployed a surface laptop through SCCM - or even MDT for that matter? I had to the apply the boot image driver's to fix the keyboard issue, that works ok. I have even removed the answer file processing step after post insta...
Why would a surface laptop not like this? This answer file is a standard file produced by MDT integrated with SCCM. <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schema...
Step #3: Add the Surface Pro 3 Firmware and Driver pack drivers to MDTIn the Microsoft Deployment Toolkit Workbench create the following folder structure under Out-Of-Box DriversNote: The last folder must be called “Surface Pro 3” Right click Out-Of-Box Drivers\WindowsPEX64 fo...
So here's the scenario: Surface Pro 2, Surface Pro Ethernet Adapter or Dock SCCM 2012R2 w/PXE Hotfix PXE booting from the same VLAN as the SCCM Server (no forwarding or DHCP options configured) Verified that PXE Boot works for a laptop. Surface Pro 2 PXE boot, "PXE Booting from IPv4...
Why would a surface laptop not like this? This answer file is a standard file produced by MDT integrated with SCCM. <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas...
So here's the scenario: Surface Pro 2, Surface Pro Ethernet Adapter or Dock SCCM 2012R2 w/PXE Hotfix PXE booting from the same VLAN as the SCCM Server (no forwarding or DHCP options configured) Verified that PXE Boot works for a laptop. Surface Pro 2 PXE boot, "PXE Booting from IPv4...