moob

I installed mdt on my wds server and made a lite touch boot image. Guess what. I pxe boot my uefi client, select the lite touch boot image and: bluescreen and unmountable_boot_volume.

Still trying to deploy windows 8.1 x64 to uefi client with wds 2012. I was advised to setup wds as a Standalone server, which I did. In my Standalone server console I see Prestaged Devices, containing nothing and Active Directory Prestaged Devices, containing all the computer accounts from AD When I deploy a known computer (=computer acct listed in Active Directory Prestaged Devices) the computer joins the Domain, but with a random (=wrong) name. When I add the same computer manually to "Prestaged Devices" prior to deploying, the computer joins the domain with the right name. How can I tell wds to make use of the "Active Directory Prestaged Devices"?

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.

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

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

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.

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.

It is a network boot and the bluescreen appers right after successful download of boot wim, video starts right after this ok, I'll look into mdt. but my guess is that also with mdt my uefi client would need to be able to boot from LAN...

because I know nothing about mdt and because wds has been running without any issues until I started playing around with uefi... here's the video

ok, I'll do the vid. I thougt the formatting would be done during Unattended Setup by the component Disk Configuration in WindowsPE???

boot.wim contains Win PE and Windows Setup, both x64 I have not added any drivers since the boot.wim works as soon as I switch back to legacy mode.

Hi experts When I try to boot my uefi client from LAN it successfully downloads boot.wim from my WDS 2012, shows the Windows Logo for some seconds, but then it crashes, showing BSOD and the message "UNMOUNTABLE_BOOT_VOLUME". I'm using the same x64 boot.wim as with the BIOS clients, but with the mbr clients it works. What is it, that makes my boot.wim unusable for uefi clients?

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

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

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.

I'm seeing the same thing here with x64-clients and WDS 2012 - error x102 after loading wdsmgfw.efi... Has this ever been solved anywhere?

Hi Every time I set up a new virtual wds server 2012 the following happens: Everything works perfectly until I restart my server. After the server's first reboot, clients behave as follows: When trying to pxe boot a client, it loads and launches wdsbnp.com 5 times: Downloaded WDSNBP from... WDSNBP started using DHCP referral. Contacting server... Architecture... Contacting server... TFTP download: boot\x86\wdsnbp.com Downloaded WDSNBP from ... Architecture... Contacting Server... TFTP download: boot\x86\wdsnbp.com Then it goes on 4 times in a row: "TFTP Download: Boot\x86\wdsnbp.com" With Option "Require the user to press the F12 key..." enabled, I have to press F12 4 times, which is 3 times too many. After the x-th download of wdsnbp.com the client continues the boot process normally and the rest works fine. We are using DHCP-Options here and we have an equally configured WDS on Server 2008 up and running without any problems. Any Ideas? Michael