Hi,)
I've been trying to grasp my head around the excellent script (orignally created by William Lam) to be able to vMotion a running VM from one Datacenter to another in different vSphere enviroments.
However all I end up with is the following:
Exception calling "RelocateVM_Task" with "2" argument(s): "
Required property key is missing from data object of type ServiceEndpoint
while parsing serialized DataObject of type vim.ServiceDirectory.ServiceEndpoint
at line 1, column 303
while parsing property "service" of static type ServiceEndpoint
while parsing serialized DataObject of type vim.vm.RelocateSpec
at line 1, column 297
while parsing call information for method RelocateVM_Task
at line 1, column 218
while parsing SOAP body
at line 1, column 207
while parsing SOAP envelope
at line 1, column 38
while parsing HTTP request for method relocate
on object of type vim.VirtualMachine
at line 1, column 0"
At C:\Users\anders.johansson\Desktop\MoveVMAcrossSSO.ps1:69 char:1
+ $task = $vm.extensiondata.RelocateVM_Task($rspec,"defaultPriority")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : VimException
I'm not a PS guru, but it seems some property has either changed or is missing. I can do RelocateVM within the same Datacenter (both source and target) from PowerCLI without any problem, it's the ServiceEndPoint that does not work.
I have included the $rspec variable:
Service
Folder
Datastore
Host
DeviceChange (Convert to dVS)
Source vSphere is 5.5 (Windows) and destination is Linux appliance (6.0.0)
Has anyone had success with this lately?
Did you already see this thread Re: cross vCenter vmotion error
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
PowerCLi script had worked for me without any change. In my case, both ESXi and vCenter were on 6.0 release
Recently I have written Java SDK script for the same requirement: Refer my blog post : http://vthinkbeyondvm.com/want-to-vmotion-a-vm-from-one-vcenter-server-to-another-vcenter-using-vsph...
Yes, sorry I forgot to mentioned that, the UUID is converted to uppercase (even thought the documentation does not show the variable as uppercase)
I'm afraid I do not have the luxary to run 6.0 on both vspheres. It seems that doing a convertion between 6.0 and 6.0 works fine but not with 5.5.
The support is of course not documented and, based on my experience you are without luck if running <6.0
Has not a single sole here done a migration from 5.5 to 6.0 with different SSOs?
