I'm testing out a new VMware View 5.1 installation and having issues with the customization process
I have created a Windows XP Gold Image with the following relevant specifications
Windows XP Service Pack 3
Applied all Windows Updates
Disabled Windows Firewall
VMXnet 3 Virtual Adapter
Installed the KB944043
Installed the VMware Agent 5.1.1 (after the KB944043 applied)
I'm using a Virtual Distributed switch with ephemeral ports in vsphere 5.1
I release the IP and shutdown the VM
Take a snapshot of the VM named "TEST"
In View Manager I created a pool "TEST" using Linked Clones, point it at my snapshot "TEST" and use a sysprep customisation I created not quickprep
This is what happens
1. View Composer clones the VM to a replica
2. View Composer adds the PC names into Active Directory
3. after the VM's are all created they boot up, sysprep runs and reseals and reboots
4. I see a "VMware customizing in process"
5. Windows XP Mini-Setup runs
6. VM reboots
then it loops from number 4 through to 6 over and over
any one seen this one and got some tips?
From the VMware View Admin console I should also add that it reports the machines in the "customizing" stage
I have looked at many threads regarding this issue but none so far have solved mine.
After Mini-Setup occurs, does the agent flag something to indicate sysprep has completed or whats the timeline here?
Timeline of what I see working and what doesn't
I have attached the screen the VM's get too, it's the screen just after you see "vmware customizing in progress" before they reboot, and continue the loop
I'm getting close.
after performing a recompose I jumped into windows to watch it run the sysprep process, and I can see as soon as sysprep starts it removes the NIC on the machine
obviously the agent on the machine can't talk to the server as well as the machine can't join the domain as its not on the network
How can I get sysprep to stop removing the NIC information for that adapter? need to remove /generalize I would guess.
Where does view set what sysprep options it runs as the customization wizard doesn't have these options.
Here is some more info.
I have a VM in vCenter named "TEMPLATE - Windows XP"
If I clone this VM through vCenter, and use an existing customization specification I have created which joins the domain the following happens.
The VM is cloned.
If I edited the cloned VM, the cloned VM has the button unticked "Connect when power on" for the NIC
If I power on the cloned VM, the NIC is never connected.
Yet, when I do this test with another VM "TEMPLATE - Windows 7" which of course has Windows 7
the machine is cloned, I edit the VM the tick box "connect when powered on" is also not on
However, if I power on the Windows 7 VM, and then go back into the settings, I see the NIC HAS been connected.
My issue is only happens with Windows XP
I have a hunch that this is by design for disabliong the NIC initially, so that you dont have multiple machines with the same name trying to get the same IP on the network at the same time? This then gives time for sysprep to start, rename the PC and then the NIC is connected next reboot?
unfortunately the NIC is never connected for my Windows XP machine
has anyone seem this or similar?
The issue is not specifically View related, its more to do with the vCenter clone process.
So closing this thread and starting a new one in the right section.