Yes, that is at the core of why this is a problem for me. The job itself never comes out of the status "running", and if you look at the output of one of the jobs, you see that the move started and finished, but it doesnt continue after that
Here is the output from the job after the task has been finished in VC for 1 hour:
Here is an example of the job execution with the "-runasync" flag on the move-VM command:
Getting VM Object
Getting Datastore Object
Moving VM
VERBOSE: 2/19/2013 4:12:47 PMMove-VMStarted execution
VERBOSE: Performing operation "Move-VM" on Target "Moving VM 'exampleVM'".
RunspaceId : 544746c4-91c2-4a41-b628-b3cd5ddb135d
ServerId : /VIServer=user@vcenter.domain.com:443/
State : Running
IsCancelable : False
PercentComplete : 0
StartTime : 2/19/2013 4:12:49 PM
FinishTime :
ObjectId : VirtualMachine-vm-3211
Result :
Description : Relocate virtual machine
ExtensionData : VMware.Vim.Task
Id : Task-task-65476
Name : RelocateVM_Task
Uid : /VIServer=user@vcenter.domain.com:443/Task=Task-task-65476/
VERBOSE: 2/19/2013 4:12:50 PMMove-VMFinished execution
Im Done Moving
Disconnecting from VCenter
Disconnected
I am not concerned with the receive-job output, rather the job completeting so the next job in the queue can start.