Luc, I take back my previous statement, yes the VM is powered on before running the script, we are using 3rd party workflow engine for automation, which internally powers on the VM before running the scripts on Linux flavors but not for Windows. So, I was confused as we handle power on/off through another workflows right after and network setup and domain registration just before the VM goes live on the external network. Most of API for VMware is hidden behind the workflow engine and they are using Java Web API for most of the work, It has password reset option for Windows but not for Linux and that's why we are using the power shell cmdlets. All the files in the /tmp are 0 zero length, so I am not sure exactly the permission issue is coming from.
↧