Hey, thank you for your help. My colleague installed powerCLI from the powershell with
Install-Module -Name VMware.PowerCLI -Scope CurrentUser
on his machine and gets the same error with our VMs. He had no powerCLI installed previously.
Note that i only installed the older versions after getting those error messages and reading the post that was shared as the first answer in this thread.
Did you remove the PowerCLI modules before installing the old version 6.5 R1?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
no, i had both installed, so i probably should remove the new version again and try the old version?
Indeed, they can't co-existBlog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
thanks a lot for your help again.
We dont want to use an old version of PowerCLI, we rather use Remote-Sessions with powershell to interact on the Guest OS, which seems to work fine,
and use PowerCLI only for the VM Management and not on the Guest OSs, while we get this error message.
We are currently using VMware Tools Version 11.0.1, and VMware PowerCLI 11.5.0, and dont want to go back to 6.* for PowerCLI.
It might be a firewall issue, since we are in different networks, and not a problem with the PowerCLI Cmdlets at all..
Using remote sessions is indeed an alternative, but opens another can of worms imho.
I'm not really a fan of allowing winrm all over the place.
If you ever find the actual reason for this, I would be very interested to learn about the actual cause of the problem.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
it might just be some obvious rookie mistake, since i just started using PowerCLI, but i can't figure it out at the moment.
i will post an answer if we find the cause of the error.