+ Post New Thread
Results 1 to 6 of 6
Windows Server 2012 Thread, HyperV Gen2 VMs - PXE Booting from WDS in Technical; Bit of an odd one this, I'm hoping someone can point me in the right direction. When I'm building my ...
  1. #1
    Norphy's Avatar
    Join Date
    Jan 2006
    Location
    Harpenden
    Posts
    2,319
    Thank Post
    54
    Thanked 294 Times in 230 Posts
    Blog Entries
    6
    Rep Power
    116

    HyperV Gen2 VMs - PXE Booting from WDS

    Bit of an odd one this, I'm hoping someone can point me in the right direction.

    When I'm building my PCs, I do so with SCCM. My PXE enabled DP is sitting on a Windows Server 2012 box so I can build SecureBoot UEFI machines from it. With physical UEFI PCs, this works as happy as can be as it does with physical BIOS PCs and Generation 1 Hyper-V VMs with legacy NICs. However, when I try to make a generation 2 VM and PXE boot with that, I get a PXE-E16 error, no offers were received.

    I've googled around and I've found sites that say changing your WDS server to standalone mode fixes this. However since it's an SCCM DP I don't want to do this.

    This isn't anything urgent or especially important but I would like to fix it!

  2. #2

    Join Date
    Jul 2014
    Location
    Eindhoven
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi Norphy,

    In case your issue isn't solved yet:
    1. check that you have installed the hotfix: http:///support.microsoft.com/kb/2905002
    2. restart your WDS service if you have the hotfix installed, sometimes it hangs without giving a error.

    If you have your SCCM DP in the same subnet all should be fine after this. If your DP is in a different subnet, make sure you have all the IP-Helpers in place.

  3. #3

    tmcd35's Avatar
    Join Date
    Jul 2005
    Location
    Norfolk
    Posts
    5,665
    Thank Post
    850
    Thanked 893 Times in 738 Posts
    Blog Entries
    9
    Rep Power
    328
    Are you building a base image in the VM and capturing the WIM to be distributed to physical UEFI clients later? If so, AFAIK, you can just use a legacy NIC and BIOS mode in the VM. The resulting WIM *should* install fine on a physical UEFI machine. I did this earlier today with no issues. All the formatting and driver issues should be taken care of in the SCCM Task Sequence, the image should be pretty generic. The capture process strips all drivers out as part of Sysprep anyway.

  4. #4

    Join Date
    Jul 2014
    Location
    Eindhoven
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    The install should go without any problems on a physical UEFI machine. Tho if you install the hotfix and check your WDS service, you can go ahead and build gen2 VM's in Hyper-V without any problem, as matter of fact that is what currently is happening on my machine as I'm typing up this post. Testing the tasksequences on a hyper-v gen 2 machine to catch the problems, then deploy it for the physical machines.

    But why would you actually go ahead trough the trouble of capturing and sysprepping when your using SCCM?

  5. #5

    tmcd35's Avatar
    Join Date
    Jul 2005
    Location
    Norfolk
    Posts
    5,665
    Thank Post
    850
    Thanked 893 Times in 738 Posts
    Blog Entries
    9
    Rep Power
    328
    Quote Originally Posted by bjornpreus View Post
    But why would you actually go ahead trough the trouble of capturing and sysprepping when your using SCCM?
    I thought much the same, but I did actually find a good reason! We're using App-V and the prerequisites are a pain to install as part of the task sequence, so I created a wim with them pre-installed

    Actually just re-read the OP and noticed "Secure Boot UEFI" not sure what difference that makes, but I'm probably being no help here

  6. #6

    Join Date
    Jul 2014
    Location
    Eindhoven
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Indeed App-V is quite a good reason to capture :P

    Secure boot is a option for UEFI boot. Since uefi is a direct file boot, you might wanna put a layer for security over it so it can't be tempered with

SHARE:
+ Post New Thread

Similar Threads

  1. Problems with PXE booting into WDS on Toshiba Laptops
    By Disease in forum O/S Deployment
    Replies: 7
    Last Post: 18th July 2013, 12:31 PM
  2. Replies: 9
    Last Post: 2nd November 2010, 10:39 AM
  3. [Fog] Anybody managed to PXE boot from a cardbus NIC?
    By Batman in forum O/S Deployment
    Replies: 3
    Last Post: 22nd September 2009, 02:26 PM
  4. WDS and PXE booting
    By powdarrmonkey in forum Wireless Networks
    Replies: 3
    Last Post: 19th June 2008, 09:44 PM
  5. Replies: 8
    Last Post: 8th June 2007, 09:32 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •