Afaik these are the requirements on both sides:
1) Machine where you run Invoke-VMScript
- PowerShell v1 or v2 CTP3 (haven't tested with the other v2 previews)
- VITK v1.5 build 142961
2) The guest where you execute the script
- up-to-date version of the VMware Tools
- PowerShell v1 or v2 CTP3 (haven't tested with the other v2 previews)
At first I was confused by the
-HostUser parameter.
This is
not an account defined on the VC but an account on the ESX server (the hyper-visor) !
I use an account that is in the same groups as root but doesn't have UID=0.
At this moment I don't know to which groups the -HostUser should at least belong.
A simple example with the "dir" command:
get-vm <VM-name> | `
Invoke-VMScript -ScriptText "dir" -HostUser <ESX-account> -HostPassword <ESX-password> -GuestUser <guest-account> -GuestPassword <guest-password>
For the -GuestUser you can give:
1) a local account on the machine (with the required permissions of course)
2) a domain account (if the guest is in a domain) in the formats:
a) "account" (provided the guest is in the same domain as the host from which you run the Invoke-VMScript cmdlet ==> this requires further investigation or clarification)
b) "domain\account"
And don't forget that Carter made a
great video on the Invoke-VMScript cmdlet.
