PowerCLI 4.0 U1 doesn’t reconnect to VIServer

When I was testing with the new PowerCLI feature to work with multiple VIServers, I ran into a bug. Whenever you disconnect from a VIServer you can’t reconnect to that server. You can however connect to another VIServer, but never to the same VIServer again.

PowerCLI 4 reconnect bug

As a workaround for this problem close your PowerCLI session and start a new one or…

Specify a username and password when connecting

Connect-VIServer <servername> -user <username> -password <password>

So it looks like the problem is only related to using passthrough authentication.

Related posts:

  1. Reconnect ESX hosts using PowerShell Tweet This week I ran into problems with vCenter server and almost all of my VMs were orphaned in vCenter. To resolve this issue I needed to disconnect/connect each ESX...
  2. Setting custom attributes with VMware PowerCLI Tweet Last week I wanted to extend my vCenter with some extra custom attributes on my VMs. This would extend the usability of the Export List feature for reporting purposes....
  3. ESX console password aging Tweet Yesterday I did a post on how to change your ESX root password using a Powershell script and told you that I, as a good administrator, didn’t change my...
  4. Export and import customization profiles using Powershell Tweet One great thing in the automation of VM deployments is the use of customization profiles. These profiles are stored inside the vCenter Server database. However, when you loose the...

3 Comments on “PowerCLI 4.0 U1 doesn’t reconnect to VIServer”

  1. #1 PowerCLI 4.0 Update 1- Another leap forward | Arnim van Lieshout
    on Nov 27th, 2009 at 3:51 pm

    [...] When I was testing with this new feature I ran into a bug. Whenever you disconnect from a VIServer you cannot reconnect to that same server again. You can however connect to another VIServer, but never the same again. See my earlier blog post about this bug here. [...]

  2. #2 daniel
    on Jan 26th, 2010 at 2:56 pm

    Is there any official word on this? It’s really annoying when running scripts in say PowerGUI and having to restart the entire application to rerun the script. I refuse to specify a password and have it stored in cleartext :)

  3. #3 Arnim van Lieshout
    on Feb 1st, 2010 at 9:33 am

    As far as I know it’s reported as a bug, so we have to wait for a new release. In the mean time you could use the New-VICredentialStoreItem and Get-VICredentialStoreItem cmdlets to store your username/password in a credentialfile instead of using clear text.

Leave a Comment