Connect-VIserver -AllLinked Issue

[aerodevil]

I've had difficulty getting this functionality to work.  I get the following error when issuing command

Connect-VIServer -Server VC -AllLinked:$true

I have tried it a variety of iterations and still get the "Invalid URI: The hostname could not be parsed."

I assume I'm missing something straightforward here.  Thanks!

[jake_robinson_b]

What does Get-PowerCLIConfiguration return for you? (Hint: Default Server Mode should be multiple)

[LucD]

I think that is in the screenshot :smileygrin:

[jake_robinson_b]

Thanks, Luc. <facepalm> :smileygrin:

[LucD]

I trust you also tried with the FQDN of the VC ?

[aerodevil]

Yes, in the screenshot

I have tried FQDN and other aliases that we use. I have also tried to connect to other systems in the linked mode environment.

It connects to the initial system but it feels like it is not getting the rest of the names.  It's as if it is not parsing the list/array of other systems identified for linked mode.  Make sense?

[aerodevil]

Also keep in mind that the vCenter servers are v4.1 and I'm running PowerCLI 5.0.1.  I was not able to identify any documented issues using -AllLinked with 4.1 vcenter servers.  Are there any dependencies that I'm missing?

I have also tried this with PowerCLI 5.0.1 32-bit and 64-bit

[GuilhermeAlves]

I was getting the same issue yesterday. Then i realize i was not passing the right object to the Connect-viserver cmdlet.

It must be a String and i was passing an object from an array without converting it. Maybe .toString() solve your problem too. 😃

See also: Connect-VIServer - vSphere PowerCLI Cmdlets Reference