Spiceheads,

I was trying to spin up a test Hyper V VM and sure enough I am recieving

hyperVerror.PNG

This is a Gen 2 Machine and within the last 3 months I have built about 6 VM’s without an issue. It is receiving an IP (but I can’t ping it) and it is getting the correct IP for the WDS server… I have never had to set up any options in my DHCP server. It just worked. Why?

8 Spice ups

did you assign it to the correct vswitch?

@jenyus

I believe so. I assigned it the same one that is assigned to another Hyper V on this machine…

basp.PNG

Are the other VMs also Gen2? I’m seeing some threads about Gen2 VMs and DHCP Options 60, 66, and 67.

@JJoyner1985

Yep. I tried configuring option 66 to the IP of the WDS server and 67 to the file listed… No dice… I saw something about 60 but I don’t see it listed on my dhcp server. Additionally i should disclosure DHCP and wds are on different servers.

Is anything else able to boot to your PXE server? Or is it just that one VM?

Is anything else that is using secure boot able to boot to your PXE server?

…on the same subnet as the server with the issue?

1 Spice up

@Tim_G

I can boot to it just find on a vostro 230… I tested a secure boot on a laptop, no problem (EDITED*)… However when i disable secure boot on the server I get the same message.

Is the VM on the same VLAN as your WDS server?

@Gary D

Yes sir. Same vlan, same subnet,

Can you RDP into the Hyper-V host? I just went through this same thing, and Windows Firewall had gotten hosed. This will help verify if that’s the issue or not.

From your screenshot, it looks like it’s connecting just fine… it even downloads the NBP file.

Since it’s a Gen2 VM, which OS (and 32 or 64-bit?) are you trying to deploy to it?

@Big Green Man

I can RDP into the host, but I am literally just trying to build the server.

@Tim_G

Usually it will boot into and I pick what boot file to deploy x86 or x64… I know with Gen 2 you have to use x64 and was planning on installing 2012 r2 from my mdt share