Windows 2008 R2 NIC disconnected when converted from a template and started using start-vm workflow in VCO

[pratt26]

Hi,

Have a very strange issue. I wanted to perform patching using a VCO workflow on both my Windows 2012 R2 template and Windows 2008 R2 templates. My Windows 2008 R2 template when converted and started by the VCO workflow does NOT get an ip address. Yet, when I manually turn on the Windows 2008 R2 template after being converted manually, it DOES get an ip address immediately. So weird.  There is no issue with Windows 2012 it works great. NOTE: The workflow that starts the vm only turns it on (and is a built in workflow built by vmware) Last, today I built a new template and has the same issue. NIC is VMXNET3 and problem sure seems to be OS specific, has anyone seen this before?

Thanks

[a_p_]

Not sure whether this is related, but maybe worth looking at (http://kb.vmware.com/kb/1020078)

André

[pratt26]

Thanks Andre, I have stumbled on this one before. I can deploy from Template fine, I cannot service the template and get an ip.

[pratt26]

FYI....Same issue with the E1000 adapter (working to rule things out)

[pratt26 · Accepted solution]

I found this article and fix it. It looks like a known issue with VSphere 5.1

VMware KB: Registering or deploying a virtual machine template fails