To be honest PowerShell historically does not handle variants particularly well. We may have regressed in this area, which would be bad, so we have question and some pointers to articles that may help.
Can you give us the information in $PSVersionTable, please?
There is a good article in StackOverflow that talks about using Variants and offers some suggestions: http://stackoverflow.com/questions/30512785/retrieving-session-id-from-com-method
One of the better suggestions is in a link from that article: http://www.archivum.info/microsoft.public.windows.powershell/2010-01/00361/RE--quot-Invalid-callee-quot--calling-a-com-object.html. While the content is valuable, I will apologize in advance for the ad placement on that page :-(David Wallis commented
I've tried this with WMF 5.1 and have the same issue.. Really need to resolve this as it prevents upgrading powershell on these machines.David Wallis commented
I don't see anything of use in those articles.. the code in the method Connect-OrchestratorComInterface located here: https://github.com/davidwallis3101/OrchestratorCOM/blob/master/OrchestratorCOM.psm1
uses new-object to create an object to receive the handle - this works in wmf4 but not in v5..
I'm wondering still if I do a getType on $oHandle on wmf4 and 5 whether they are the same?
Is the variant wrapper part of powershell or .net?