Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options

[Wayne Workman]

@Arrowhead-IT said:

a vm that usually required a few tries

I’ll be trying these things out next week. I will post what differences I notice.

What version of Windows Server are you running DHCP on? I ask because there are differences. I’m running 2012 R1

[JJ Fullmer]

@Wayne-Workman Thanks
I’m on 2012 R2 dhcp ver 6.3

[Sebastian Roth]

@Arrowhead-IT AFAIK pxe booting (the FOG style) has nothing to do with router (all on the same subnet) or hostname/DNS. Maybe just undo/redo the settings to verify if those really make a difference.

Why would the VM take “a few tries”. This should not be the case. Maybe some missconfiguration in your DHCP setup that you fixed now?!

[JJ Fullmer]

@Sebastian-Roth Yeah, our dhcp does have some serious issues actually. We’re working on narrowing it down. Sometimes computers get ips from the ip phone scope, even when they have an ip reservation. Pretty sure it has to do with some incompatible firmware on one old hp switch we’re phasing out. I was just hoping to have found something that just worked around other issues.

And sadly, after trying to boot a different vm a few minutes ago, same esxi server and same type of virtual network adapter E1000 as the other, it took a few tries again to get an address in the initial pxe boot.

Thanks for the input though, just more confirmation that our network needs an overhaul.
I just want to hit reset of the whole data center infrastructure and start again. But that’s not actually a good idea, I know that, people need to do their jobs or something silly like that.

[Wayne Workman]

@Sebastian-Roth said:

AFAIK pxe booting (the FOG style) has nothing to do with router (all on the same subnet) or hostname/DNS. Maybe just undo/redo the settings to verify if those really make a difference.

Maybe bare metal is just better ?

[JJ Fullmer]

@Wayne-Workman well, it happens on physical machines too. Maybe CentOS is just better than ubuntu for hosting fog?

[MRCUR]

@Arrowhead-IT said:

And sadly, after trying to boot a different vm a few minutes ago, same esxi server and same type of virtual network adapter E1000 as the other, it took a few tries again to get an address in the initial pxe boot.

You should really be using VMxnet 3 as the adapter for every guest on ESXi. VMware does not actually recommend that you use the E1000.

[JJ Fullmer]

@MRCUR I’ve heard that, but I couldn’t get the vmxnet adapter to boot to pxe. E1000 was the only one that worked ever for me. If you’re saying you have gotten it to work, then maybe I should try it again.

[JJ Fullmer]

@Arrowhead-IT I did just try vmxnet3 again after we had done some dhcp configuration fixes over the weekend. It worked on the first try, I guess my problem was elsewhere. I haven’t tried unsetting the experimental options yet.

[MRCUR]

@Arrowhead-IT It’s definitely worked for test VM’s that are used for image testing, but it’s also a more general comment for ESXi in general. Worth checking your server guests to ensure they’re all on vmxnet3.