have you seen these ? I explain how to add the Surface Pro 3 drivers to the boot wim in these videos
- http://channel9.msdn.com/Series/Surface-Pro-3-Deployment/Mod2 - http://channel9.msdn.com/Series/Surface-Pro-3-Deployment/Mod5 also you can use dism to display what drivers are in your boot wim https://technet.microsoft.com/en-us/library/dd799258%28v=ws.10%29.aspx cheers niall On Wed, Mar 11, 2015 at 5:28 PM, Bradley, Matt <[email protected]> wrote: > When I image my Surface3’s, I have them on the dock to gain mouse and > keyboard control, but I still have to use the Microsoft Ethernet Adapter > plugged directly into the Surface3 to do PXE booting to SCCM. The > Microsoft Ethernet Adapter is the only USB Ethernet adapter that has worked > for me. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Timothy Ransom > *Sent:* Wednesday, March 11, 2015 10:51 AM > *To:* [email protected] > *Subject:* [External] RE: [mssms] RE: Surface Pro 3 dock boot from flash > fails > > > > Thanks for the replies. > > > > I have those two drivers injected and still not finding dock’s nic. > > > > May be hw, even from Windows 8.1 the dock is intermittently not found – > will try another dock. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Sean Pomeroy > *Sent:* Monday, March 09, 2015 4:16 PM > *To:* [email protected] > *Subject:* Re: [mssms] RE: Surface Pro 3 dock boot from flash fails > > > > With these two drives in my x64 boot image, I have successfully imaged > using a Surface Pro 2 and 3 dock. > > > > [image: Inline image 1] > > > > On Mon, Mar 9, 2015 at 4:07 PM <[email protected]> wrote: > > THIS!!! > > > > You need to have both injected. > > > > Once the machine has at least the November firmware, PXE is very reliable. > > > > Sent from Windows Mail > > > > *From:* Sean Pomeroy <[email protected]> > *Sent:* Monday, March 9, 2015 1:53 PM > *To:* [email protected] > > > > Did you add both "Surface Ethernet Adapters" to the boot image? > > > > On Mon, Mar 9, 2015 at 1:45 PM Timothy Ransom <[email protected]> > wrote: > > I applied all firmware updates before attempting boot from SCCM flash > drive and no changes made to power settings. > > > > Task sequencing Error – Failed to find valid network adapter. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Mears, Mark > *Sent:* Monday, March 09, 2015 9:06 AM > *To:* [email protected] > *Subject:* [mssms] RE: Surface Pro 3 dock boot from flash fails > > > > You may want to allow the Surface to connect to the WindowsUpdate to pull > the latest firmware before attempting to image it. At my last customer we > found a few units that needed this before we were able to get them to find > certain device drivers. Once you get the new firmware you should be fine. > > > > Thanks, > > > > *Mark A. Mears, Sr.* > > *MCSA, MCTS, MCITP, MCT* > > Microsoft Architect | En Pointe Technologies | www.enpointe.com > > HQ: 18701 S. Figueroa Street, Gardena, CA 90248-4506 | 310-337-5200 > Direct: (310) 337-4580 > > Office Ext: 4580 > > Mobile: (757) 945-2651 > > > > [image: cid:[email protected]] <http://www.enpointe.com/> > > [image: MS] <http://www.enpointe.com/microsoft> > > > > Systems Integrator Licensing Solution Provider (SI-LSP) > > > > Software Asset Mgmt Gold Partner > Volume Licensing Gold Partner > Server Platform Gold Partner > > > > Communications Gold Partner > Virtualization Gold Partner > Collaboration Gold Partner > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Timothy Ransom > *Sent:* Sunday, March 8, 2015 7:12 PM > *To:* [email protected] > *Subject:* [mssms] Surface Pro 3 dock boot from flash fails > > > > Hi, > > > > Surface Pro 3 dock boot from flash fails to find valid network adapter. I > am using SCCM 2012 R2 and have followed steps in > Surface-Pro-3-Deployment-Administration-Guide. > > > > Has anyone else resolved this issue? > > > > Not sure what I am missing, no problems importing (1) driver to boot image > – but guide mentions (3) drivers. > > > > Thanks, > > Tim > > > > > > > ********************************************************************************************** > GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential > information protected by state or federal law. The information is intended > only for use consistent with the state business discussed in this > transmission. If you are not the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or the taking of any > action based on the contents is strictly prohibited. If you have received > this transmission in error, please delete this email and notify the sender > immediately. Your cooperation is appreciated. > > ********************************************************************************************** > > > > > > > > > ********************************************************************************************** > GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential > information protected by state or federal law. The information is intended > only for use consistent with the state business discussed in this > transmission. If you are not the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or the taking of any > action based on the contents is strictly prohibited. If you have received > this transmission in error, please delete this email and notify the sender > immediately. Your cooperation is appreciated. > > ********************************************************************************************** > > > > > > > > > > > ********************************************************************************************** > GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential > information protected by state or federal law. The information is intended > only for use consistent with the state business discussed in this > transmission. If you are not the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or the taking of any > action based on the contents is strictly prohibited. If you have received > this transmission in error, please delete this email and notify the sender > immediately. Your cooperation is appreciated. > > ********************************************************************************************** > > > >
