The SDK offers lots of advantages over thinreg and will be faster as it does not require Windows to shell out. The SDK for ThinApp recently got an update to version 4.7.3 and this prompted me to revisit login scripts I had previously written using thinreg.exe If the VM is then powered on, it moves into the Available state.įull details of these steps can be found on Andre Leibovici's blog. View Manager puts the linked clone into the Provisioned state.The View Manager Server powers off the clone and takes a snapshot of the customized, powered off clone (to give us our refresh state).

T hen the View Agent sends a message to the View Manager server. The View Composer Agent waits for Sysprep to finish before notifying the View Agent that customization is complete.

Sysprep is now run on the linked clone from within the guest.

The machine is now joined to the domain.

Inside the Guest OS on the linked clone, the View Composer Agent sees that it is starting for the first time and calls NetJoinDomain with the machine password cached on the internal disk.

View Manager powers on the linked clone.

View Manager calls the vCenter API customizeVM_Task to customize the VM with the customization specifications.

Once the linked clone disks have been created, View Manager puts the VM into the Customizing state.

So what are the steps that take place when View customizes with Sysprep?

Vmware thinapp no popup