Jump to content


crakeador

WDS and UEFI deployment

Recommended Posts

Hallo WDS experts,

 

I would like to share with all one problem that I have. Last year I have configured WDS under WS2012 that helps me a lot in my job. Now all installations are complete unattended includind software and some customizations. Now I am starting to receive new computers with windows 8. These computers are using UEFI BIOS instead LEGACY BIOS. When I try to install windows using WDS, the installation fails. I would like to ask if somebody has experience in this field using WDS.

Share this post


Link to post
Share on other sites


Hi,

Which OS are you trying to install? Windows 7? Windows 7 x86 doesn't support UEFI at all and x64 has some limitations as well.

 

Regards,
jörgen

Share this post


Link to post
Share on other sites

Thanks for helping me Jörgen.

 

Currently I can deploy Windows 7 and Windows 8 if machines are running in legacy mode. But new models come now under UEFI mode with GPT partition. When this machine connect to WDS and you try to install Windows 7 or Windows 8 you receive an error about digital signature directly. If you swap in each new machine UEFI mode to LEGACY mode, then this new machine can connect correctly and you can install systems perfectly.

Share this post


Link to post
Share on other sites

Hi

I'm trying to deploy Windows 8.1 x64 to HP Machines with uefi.

WDS and DHCP are in the same network and I am using DHCP options 66 and 67, which ist working perfectly with BIOS Computers.

My Bootloader is boot\x64\wdsmgfw.efi

 

When my client starts using wdsmgfw.efi, it loops for some minutes and stops showing error 0x102.

Share this post


Link to post
Share on other sites

don't use dhcp scope options for UEFI, use iphelpers instead.

Share this post


Link to post
Share on other sites

My understanding has been that a ip helper address can only be used if dhcp and wds are on the same box ...???

Share this post


Link to post
Share on other sites

Nope, you can always use IP helpers. Especially when you've got UEFI and legacy BIOS devices, you need to use IP helpers, because they need different boot files and with DHCP options you can only specify one file.

Share this post


Link to post
Share on other sites

Got DHCP options removed and ip helper address pointing to wds installed - boot.wim can now be downloaded. Thank you guys!

Share this post


Link to post
Share on other sites

My experience here is as follows:

 

I put an ip helper address in place and remove all the dhcp options: Immediately my uefi client starts booting from LAN, it downloads wdsmgfw.efi and starts downloading the boot.wim...

 

BUT

 

It keeps on working for one or two days and then, suddenly the happiness comes to an end: pxe-e16: No offer received.

 

Then I would put the dhcp options in place again in order to be able to set up my bios clients.

I would let 2 days go by before trying again to pxe an uefi-pc.

 

After the 2 days, I would re-remove the options and pxe boot with uefi clients would work again, as if nothing hat happened.

 

and on and on and on...

 

Sounds funny, but it is not.

Share this post


Link to post
Share on other sites

do you mean that UEFI network boot works fine for two days and then all of a sudden it fails with that error ? what does the smspxe.log file tell you when you receive that failure ?

Share this post


Link to post
Share on other sites

do you mean that UEFI network boot works fine for two days and then all of a sudden it fails with that error ? what does the smspxe.log file tell you when you receive that failure ?

yes. last night before I went home pxe-boot worked and now, 14 hrs later I get the error pxe-e16: No offer received.

I will do some wiresharking on the switch now.

Share this post


Link to post
Share on other sites

what about the smspxe.log like i mentioned, attach it here

Share this post


Link to post
Share on other sites

what about the smspxe.log like i mentioned, attach it here

I'm trying to find sth like that.. wds 2012 here

Share this post


Link to post
Share on other sites

oh right, no Configmgr... well forget about that then, why are you using WDS, no MDT ?

Share this post


Link to post
Share on other sites

cause wds has been working like a charm and I just can't believe that it can be that difficult to deploy to uefi with wds

Share this post


Link to post
Share on other sites
I tried the following:

I made a WinPE bootable USB-Stick with ADK 8.1, booted my PC from that stick in UEFI mode, and it worked.

Then I took the boot.wim from my WinPE Stick and loaded it as an additional boot image on WDS. When I pxe-boot my UEFI client from that boot.wim coming from adk, I get the unmountable_boot_volume error again.

Then I thought, maybe some drivers are missing, and I injected all the device drivers I could find into my boot.wim, but that would not make a difference.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...