I'm deploying W2K3 Ent R2 servers, therefor I've created a standard template-file.
I'm reading the template and choosing "Use the customization wizard to temporary adjust the specification before deployment".
When changing the IP configuration the Gateway and DNS settings aren't deployed.
Anyone experienced this be4?
Using ESX 3.0.1 and VC 2.0.1
Yes, the script only fixes the network configuration problem. The join domain issue is of a different nature. The issue with the join domain operation is that the script runs \*after* the join domain sequence upon the first automatic login. Hence, when the guest OS attempts to join the domain, the network configuration is still not configured correctly and the domain obviously cannot be reached.
Perhaps a work-around could be to create a template with a valid IP address configuration (DHCP or dedicated to the template VM). When the guest OS then starts after being deployed from the template, at least the network configuration should still be correct and allow a join domain operation. Of course, such a solution would require that the newly deployed VM always be initially connected to the same subnet/VLAN in the case of using a dedicated IP address or the availability of a DHCP server in the case of using DHCP.
has there been a solution for this problem.. coz, i am running into the same problem on migration of p 2 v, and the virtual box, is customized to take differenent hostname and ip.. but vm doesnt seem to like the static ip assigned..