Hi John,
> Thanks, Do you know what comes under pre customization and what comes under post customization?I assume Computer name and Network
> settings comes under pre customization? and SID and admin pass and other things under post customization, Can you please explain if you know
> about this.
You're mixing concepts a little bit. Pre- and post-customization related only to what is called "customization script" - that's what you enter into the big text box in the UI. Now you can think of that like big .bat (or .sh for Linux) file which is invoked during customization process with two possible arguments: "precustomization" and "postcustomization. See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026614.
The overall flow in VCD 5.1 is something like this:
1. set computer name (only if different from existing one) and DNS suffix
2. check if marker file exists and if so - do network settings, reboot and that's it ("reconfiguration flow")
otherwise continue:
3. if Vista+, do network settings (this step is not present in 5.1 GA build, but should be in VCD 5.1.1. it was added because some users wanted to activate against KMS inside "precustomization" in order to avoid issue with "rearms")
4. run customization script with "precustomization" parameter
5. if SID is unselected, do network settings, do password set/reset, schedule customization script to run with "postcustomization" parameter after reboot via Windows Scheduler Task, create marker file, reboot
otherwise two additional steps:
6. run sysprep and reboot (customization will be invoked during "mini-setup" phase)
7. in "mini-setup" phase, do network settings, do password set/reset, schedule customization script to run with "postcustomization" parameter after reboot via Windows Scheduler Task, create marker file, reboot
the very last thing (for both SID and NO SID): Windows Scheduler Task is invoked after the last reboot and customization script is run with "postcustomization", then the task is deleted
There are some additional corner-cases like Windows 2000 or "respecialize" operation in Windows 8, but overall it works along those lines.
> And also how can i run one customization script to all VMs in a vApp at a time? Or do i have to go each machine and go to properties and run script from there?
I'm not sure I understand the question about running script. Customization is generally configured per VM. Of course if you configure all VMs and then "Start" vApp, depending on Startup Sequence, individual VMs will power on and customization will occur in those (if enabled).
/Andrii