I had no problem running get-viserver on earlier versions. Now I get the message:
Get-VIServer : Input string was not in a correct format.
At line:1 char:13
Any ideas?
Thanks!!
Yes, go for VITK v1.5.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Get-VIServer is an alias for the Connect-VIServer cmdlet.
It is defined in the %ProgramFiles%\VMware\Infrastructure\VIToolkitForWindows\Scripts\Initialize-VIToolkitEnvironment.ps1 script.
Could it be that you didn't execute that script ?
That is normally done via the VMware VI Toolkit shortcut.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Really, strange I don't have the scripts directory, nor am I able to run connect-viserver ("not recognized as a cmdlet, function, operable program, or script file").
I can however run get-viserver for servers prior to this version, just not ones on esx3.5u3.
Can you run Get-PSSnapin and does the list that it returns contain an entry named "VMware.VimAutomation.Core" ?
And when you do a Get-Alias do you see an entry for Get-VIServer ?
What VITK version/build are you running ?
You can do a Get-VIToolkitVersion to see that.
Perhaps it would be useful to reinstall the VITK latest build.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
VMware.VimAutomation.Core does show up when i run get-pssnapin.
Get-VIServer does now show up as an alias.
I am running VMware VI Toolkit for Windows 1.0 (Beta) build 81531
I will try reinstalling.
Yes, go for VITK v1.5.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Thanks that worked!!