Unless I've got this wrong, the pre-req checker when deploying IAAS in custom mode states that the service account under which IAAS runs needs logon as a batchjob rights (which it asks you to configure within the local security policy).
What I noticed is that either this is incorrect or its not the only requirement..... The same service account also requires the privilege of logon as a service rights too without which the "VMware vCloud Automation Center Service" will fail to start. And for some reason, the pre-req checker doesn't check for this by default.....
Without this privilege, the service fail to start and logs the error message
Anyone else encountered the same??
Cheers
Chan
That's right, you need both: Log on as a batch job and Log on as a service. That worked for me, as VMWare technical people guided me.
Hope they'll add this validation check to the pre-req checker in due course......