VI Toolkit with ESX 2.5.x

[technorock]

New to VI toolit and powershell but can really see some great benifits so want to learn more.

When trying Get-Viserver <hostname> - cannot connect to 2.5.x host

I beleive this is because 2.5.x uses SSH authentication and not http/https, not sure if this may also be because hosts security settings are set to high in MUI. Changed to low and restarted httpd but yet again no joy.

Is this a pure case that VI Toolkit does not support connectivity to ESX 2.5.x? Any help or advice gladly accepted.

[LucD]

The VI Toolkit requires an authenticated session with the VC before you can use cmdlets on other objects in the VI.

You should do something like this

Get-VIServer -Server <VC-server>
Get-VMHost -Name <ESX-server>

The 2nd cmdlet can "connect" to an ESX 3.5.x server without any problem.

[technorock]

LucD,

Thanks for that but sadly this is a connection issue to ESX 2.5.x and not 3.5.

To add more info, i am trying to connect to VC as LucD mentioned and switched on -debug which gave following information:

"Network connectivity error occured. Please verify that the network address and port are correct"

[LucD · Accepted solution]

Oops, misread the 2.5 for 3.5

Sorry about that.

The VI Toolkit release notes do not mention ESX 2.5.x.

So I'm afraid it will not be possible.

[halr9000]

I can confirm that only 3.0x, 3.5, and 3i are supported. 2.x used a different API.

Hal Rottenberg

Co-Host, PowerScripting Podcast (http://powerscripting.net)

[admin]

Correct. The toolkit does not support connecting to ESX hosts before 3.0. You're not necessarily completely out of luck, though, if you're managing them through a VirtualCenter server that is 2.0 or later (VC 2.0 and 2.5 do support ESX 2.5.x). If so, connect to the VC server and use the cmdlets through VC rather than direct to the host. If you have use cases where this doesn't work for some reason, we'd be interested in hearing about them.