Hi
I'm looking to gather all my linked vcenters and psc server names, and version info.
I found Williams vami module, but that seems to only work for cloud systems as it's using Get-CisService -Name 'com.vmware.appliance.system.version'
What is the non-cloud equivalent?
Do i need to login to all my vcenters using connect-viserver -Alllinked ?
Thanks
John
PS C:\> $service
Name Documentation
---- -------------
com.vmware.appliance.system.version {@name Version} {@term service} provides {@term operations} Get the appliance version.
com.vmware.appliance.system.version {@name Version} {@term service} provides {@term operations} Get the appliance version.
PS C:\>
I don't have any 6.7 environments to test with. I have several at 6.5, get the same issue on the few different ones i've tried.
On the Connect-CisServer -Server it's asking for the VCenter server right?
Now we are getting somewhere!
You have 2 entries where there should only be 1.
Can you check what is in $global:DefaultCisServers
For one reason or the other, you seem to have 2 connections open, and that explains the error message.
Stop/start your PS session, then do the Connect-CisServer again and make sure there is only 1 entry in $global:DefaultCisServers.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
i connected to the PSC before while trying to test.. that was the 2nd connection in $global:DefaultCisServers
it wasn't logged in
I would suggest to stop/start your PS session and start from scratch again.
The $service variable should only show 1 line
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
it does,
And so should $global:defaultCisServers
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Btw, the last error is different, it now says there is a problem with authentication.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
correct just 1
PS C:\> $global:defaultCisServers
Name User Port
---- ---- ----
vcenter.domain.com Administrator@VSPHERE.LOCAL 443
PS C:\>
start of powercli to finish
Ok, so there is an authentication error.
That might be the issue described in KB50112300
Do you use an integrated PSC?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
external psc