[We are using vcenter 5.1 update 2]
I created a new template for Server 2012 R2 and I created a custom spec to go along with it. I went to test the deployment the other day and it looked like the custom specs didn't quite finish. It had set the local admin password and named it but it didn't join the domain. I eventually figured out that after deployment, the NIC becomes disconnected despite me having 'connect at power on' checked in the template. We are using the VMXNET 3 adapter.
I have been messing around with the template for the last 2 days and I am stuck as to why it is not working. I have tried the following...
-verified windows firewall is turned off (all 3 options) (Re: ESXi 5 VM / Server 2008 R2 loses network connection after reboot)
-removed NIC; cleaned up registry at HKLM\System\CurrentControlSet\Control\Network\; rebooted; readded NIC (this was to eliminate any ghost NICs) (http://vnetwise.wordpress.com/2012/06/09/vmware-template-deploymentspart-1-trying-to-modify/)
-removed vmware tools and reinstalled. (http://vnetwise.wordpress.com/2012/06/09/vmware-template-deploymentspart-1-trying-to-modify/)
-on the NIC in the OS, unchecked 'allow computer to turn off to save power' (Re: ESXi 5 VM / Server 2008 R2 loses network connection after reboot)
-verified that my new 2012R2 template is using the same host and storage cluster as my 2012 template that does work. Also on the same Distributed Port Group. (Basically, all of the vcenter settings are the same between the two templates)
-also tried disabling the NIC in the template (Windows Server 2012 Guest Customization)
I have re-deployed the same server about 10 times and each time after deployment, you can see it reboot and try to start the customization but it hangs. If I manually turn the NIC back on it finishes correctly. The problem is I don't want to have to do that every time I deploy a server. Why is it turning the NIC off and unchecking my option to connect at power on and how do I fix this?
Any help is much appreciated!
-Adam