Hi,
because we were force to leave the linked mode, we cannot use the connect-viserver -alllinked anymore..
So google told me to use connect-viserver vc1 , vc2
You can check this if you check the value $global:DefaulViServers
In my case, there is only vc2 listed, even if the connect to both vcenters works fine...
Version is PowerCLI 5.1 Release 1
Why?
Thx in advance
Chakoe
Add the Scope parameter
Set-PowerCLIConfiguration -DefaultVIServerMode Multiple -Scope Session
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
You can indeed run Connect-VIServer against multiple vSphere servers.
How did you run the cmdlet ? Like this
Connect-VIServer -Server "vc1","vc2"
And the account under which you run the cmdlet has access to both vCenters I assume ?
Btw, are you sure you displayed
$global:defaultviservers
and not
$global:defaultviserver
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
yes, as cou can see in my PN... this fails
Indeed I see, but are you running your session in "multiple" mode ?
Do a
Get-PowerCLIConfiguration
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Try setting PowerCLI to multiple mode and then try connecting multiple servers
Set-PowerCLIConfiguration -DefaultVIServerMode multiple -Confirm:$false
PowerCLI D:\> Set-PowerCLIConfiguration -DefaultVIServerMode Multiple
Perform operation?
Performing operation 'Update vSphere PowerCLI configuration.'?
[J] Ja [A] Ja, alle [N] Nein [K] Nein, keine [H] Anhalten [?] Hilfe (Standard ist "J"): A
Scope ProxyPolicy DefaultVIServerMode InvalidCertificateAction DisplayDeprecationWarnings WebOperationTimeout
Seconds
----- ----------- ------------------- ------------------------ -------------------------- -------------------
Session NoProxy Single Unset True 300
User NoProxy Single
AllUsers NoProxy Multiple
Add the Scope parameter
Set-PowerCLIConfiguration -DefaultVIServerMode Multiple -Scope Session
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Thank you! Works now!