Just thought I would update the list with my solution for this...
A very smart colleague pointed me to the
method in Windows.pm classes. Using this I am able to force the VM to
reboot after I change the VM name, but still retain control so I can
join it to the domain.
One note to others who are working with changing VM names...
I found that changing the VM name ruined the sshd setup on my VM. It
required me to re-run the update_cygwin.cmd. Obviously I couldn't do
this from VCL since ssh was not working. I tried to add a registry
so it would run on startup.
This did not work and I discovered that RunServices is apparently not
supported in Win7? Instead I was able to use schtasks.exe to create a
scheduled task to run update_cygwin.cmd.
On 3/31/11 11:18 AM, Liz Wendland wrote:
I am trying to do something that might not be possible in VCL, but
maybe someone out there has an idea how I could make an easy
modification to do it.
We use VMware to provision our images on demand. We don't necessarily
need to sysprep them - the VMs are pretty much ready to go after
loading. Except for two things:
* We need to rename the computer
* We need to join the computer to our domain
I have a script that can do both things, but it doesn't seem to work
unless we reboot after each command. I have been able to get one
reboot to happen by setting the imagemeta.postoption = 'reboot'.
So my questions are:
1) Is it possible to get two reboots? i.e. somehow have my script do a
reboot and have VCL pick up where it left off?
2) Is there already some way built into VCL to do what I want? I see
a script in the Sysprep folder called set_computer_name.vbs but I
believe this only gets called during Image Capture. We don't know
what we want to name the computer until we are provisioning it for the
Please let me know if I am not explaining things coherently.