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, I am experiencing the same exact thing. I am also using R2, but Std. My network settings are not being pushed down to the machine which causes my template domain join to fail. I have VC 1.4 and ESX 2.5.4
I am seeing the same issue. VM's created from templates fail to join the Domain during creation. I always have to wait for it to timeout and join later. W2K3 Enterprise and Standard. VC 2.1, ESX 3.1
The templates are set to use DHCP.
Message was edited by: me
Wow, case is still open. Met with another person in my company who also is having problems using the guest customization. If he tries to add the newly created template to the domain via the customization .xml file it fails, if he just adds it to a workgroup it succeeds. I am sort of seeing the same thing on my end, except now the mini setup hangs at the windows licensing screen. If I click on the console, the mini setup continues, if not it just sits there on that screen. Sort of feels like this feature is a beta feature. Will keep you updated. I am going to give another couple weeks and then start turning up the heat.
I posted this in the VC services forum as well. We are seeing the same behavior, only IP and subnet mask being applied, no default gateway, DNS, etc. even though these are in the customization template the vm is deployed with.
The customization template was created from scratch, not imported.
This is ESX 3.01, vc 2.0.1.
We experienced something similar to this - deploying a template and specifying an IP address during the pre-deployment configuration wouldn't work - the server would boot but the IP would be 0.0.0.0 with the correct subnet but no default gateway.
I coverted the template back to a virtual machine, booted it up and change its IP address from a static on to DHCP, shut it down, converted to template, and then deployed a VM from the template, specifying a static IP and then when the machine booted, the IP was set.
However, the gateway, subnet, DNS, and WINS servers were no longer set as they were in the image.
Message was edited by:
Hmmm... I just tried this, setting the template to use DHCP. I'm still getting the same results. IP and subnet mask are populated with settings spec'd in deployment wizard, but DNS, default gateway and DNS suffixes are blank, even thought they were spec'd as well.
After rereading your post, I realize we are talking about different problems. You were not picking up the IP, whereas we are not picking up the DNS, gateway and suffixes.
I found a log in the temp directory of the deployed guest called bootrun-script.log. In this log it clearly has the settings as spec'd in the deployment wizard. Something is hindering it from being properly set, however. The script that generates this log is run out of c:\windows\vmware_imc, which ultimatly gets removed at the end of the process. I was hoping to run the script manually to see if it threw any errors.
Still waiting for a solution to the above request.
Thanks for the response!