Have a question regarding a custom kickstart file(below) that we use, which is embedded within our deployment iso. Event though we are explicitly listing vmnic2 for the console, the image is deploying it to both vmnic0 and vmnic2. This causes an issue because vmnic0 is not trunked, so we have to go in and reconfigure the mgmt network to get remote access by removing it.
I realize I can script around to remove it, but was just wondering if anyone had encountered this. It's only an issue under 5, we use the same approach for 4.1 with no problem. Thanks.
---------------------------------------------------------------
accepteula
rootpw --iscrypted blahblah
install --overwritevmfs --firstdisk=local
network --bootproto=static --device=vmnic2 --ip=10.10.10.1 --gateway=10.10.10.10.1 --nameserver=10.10.10.2 --netmask=255.0.0.0.0 --hostname=esx5host.domain.org --vlanid=1 --addvmportgroup=0
reboot
%firstboot --interpreter=busybox