I know that currently when you add a vApp to the catalog that the database needs to be updated to re-enable the change SID checkbox, which I have done. So now when I deploy vApps from the catalog the SID changes and the VM's inside the vApp are added to the domain properly.
Here is the issue I have not been able to workaround:
Create a new vApp and add the VM that has change SID checked in the catalog and it creates the vApp without those options checked and therefore none of the machines are added to the domain and no sysprep happens.
Is there a fix for this that is seperate from the fix noted in this kb:
Yes, it's an instance of same issue. It should be fixed in the next update release.
Regrettably, I can't seem to find any good workaround for Build vApp/Add VM workflows other than editing VM afterwards before power-on.