Two Issues:
1. I have the --bootproto=static --ip=10.10.10.10 .... statement at the top of the kickstart but during installation I get an initial warning message /popup box that states a DHCP server could not be found (?!?!?). The installation continues successfully and does assign the static IP address and all other parameters. Why is there a WARNING about DHCP when I'm assigning a static ip address?
Added: This doesn't happen when built in a VM - but does on a physical server.
Below is the top 5 lines of the kickstart:
===============
network --bootproto=static --device=vmnic0 --ip=10.10.10.10 --gateway=10.10.10.1 --nameserver=10.10.10.2 --netmask=255.255.255.0 --hostname=esxi1.home.local --vlanid=551 --addvmportgroup=0
install --firstdisk=mptsas,local --overwritevmfs
rootpw --iscrypted {password}
accepteula
reboot
===============
2. For this particular implementation, there is no DNS for the hosts (please don't argue over this point). But if I omit the --nameserver parameter, which the document states is OPTIONAL, I still get the Warning/Popup about the nameserver not being set. The installation continues on successfully eventually, but, AGAIN, why the WARNING? These are automated installs and there should NOT be a warning about an optional setting - especially that temporarily stops an automated installation.
Is there a way to suppress the warning messages?
Any/all assistance would be greatly appreciated.
-- JC