after updating windows and a few firmware updates it's now UEFI booting
just fine,

someone else has the same issue

http://social.technet.microsoft.com/Forums/en-US/d0c8822d-beb3-4a01-9da5-5ff5070c8f98/having-issues-with-surface-pro-3-downloading-boot-image-over-pxe?forum=configmanagerdeployment

On Mon, Sep 8, 2014 at 11:15 AM, Niall Brady <[email protected]> wrote:

> tried the same hardware in my home lab, still taking 3 hours, booted the
> device back into windows and it sees a firmware update for the surface3 ,
> i'll update it and try again.
>
> On Wed, Sep 3, 2014 at 5:03 AM, Joe Sestrich <[email protected]>
> wrote:
>
>> I think if it takes 3 hours you have something else going on, but the
>> original MS USB to Ethernet adapters are only 100mb. I boot a Dell 7440
>> with onboard nic and a Surface 2 with the 1st gen USB, and the 7440
>> finishes in half the time.
>>
>>
>>
>> *From:* [email protected] [mailto:
>> [email protected]] *On Behalf Of *Niall Brady
>> *Sent:* Tuesday, September 02, 2014 9:57 AM
>> *To:* [email protected]
>> *Subject:* Re: [mssms] UEFI network boot extremely slow on Surface Pro 3
>> with Microsoft USB nic.
>>
>>
>>
>> Have you tried uefi boot with the first gen nic, i think thats my issue
>>
>> Sent from my phone, please excuse any typo's as a result.
>>
>>
>>
>>
>> On 02 Sep 2014, at 15:31, Justin Chalfant <[email protected]>
>> wrote:
>>
>> Yes this would affect all devices. WDS would send larger chunks of the
>> boot.wim at once. 3 hours is definitely longer than it should be J.
>>
>>
>>
>> I would say without changing the TFTP size it took my SP1 and SP3 7 – 10
>> minutes with the TFTP size set like below maybe 2 – 3 minutes.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> *Justin Chalfant*
>>
>> Premier Field Engineer – Configuration Manager
>>
>> Public Sector
>>
>> Microsoft Services
>>
>>
>>
>> Tel : (303) 846-2701
>>
>> Email:     [email protected]
>>
>>
>>
>> If you have any feedback about my work, please let either myself or my
>> manager Ron Hill know at [email protected]
>>
>>
>>
>> *From:* [email protected] [
>> mailto:[email protected] <[email protected]>] *On
>> Behalf Of *Niall Brady
>> *Sent:* Tuesday, September 2, 2014 7:34 AM
>> *To:* [email protected]
>> *Subject:* Re: [mssms] UEFI network boot extremely slow on Surface Pro 3
>> with Microsoft USB nic.
>>
>>
>>
>> Wont that impact all devices that uefi/pxe boot on that dp ? This is the
>> only device that is slow, 3 hours to download boot.wim over uefi
>>
>> Sent from my phone, please excuse any typo's as a result.
>>
>>
>>
>>
>> On 02 Sep 2014, at 15:11, Justin Chalfant <[email protected]>
>> wrote:
>>
>> In my experience, Surface Pro’s take longer than PC’s with built in
>> NIC’s. Try this Created registry key RamDiskTFTPBlockSize under
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP with Hex value as 1456
>> should help a little.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> *Justin Chalfant*
>>
>> Premier Field Engineer – Configuration Manager
>>
>> Public Sector
>>
>> Microsoft Services
>>
>>
>>
>> Tel : (303) 846-2701
>>
>> Email:     [email protected]
>>
>>
>>
>> If you have any feedback about my work, please let either myself or my
>> manager Ron Hill know at [email protected]
>>
>>
>>
>> *From:* [email protected] [
>> mailto:[email protected] <[email protected]>] *On
>> Behalf Of *Niall Brady
>> *Sent:* Tuesday, September 2, 2014 3:37 AM
>> *To:* [email protected]
>> *Subject:* [mssms] UEFI network boot extremely slow on Surface Pro 3
>> with Microsoft USB nic.
>>
>>
>>
>> hi,
>> i'm testing a surface 3 with uefi network boot (cm12 r2 CU2) and the
>> download of the boot wim is extremely slow, like painfully slow,
>>
>> the usb nic is a microsoft nic which i got with my original surface and
>> i'm using that because it seems the usb3 lenovo nics wont work with the
>> Surface3 for UEFI network boot.
>>
>> so, is this supported or a known issue ? also is it a requirement to use
>> Microsoft branded usb nics with the surface brand for UEFI network boot ?
>> anyone know ?
>>
>> cheers
>> niall.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>



Reply via email to