23 Responses

  1. Welcome to vSphere-land! » vSphere 5.1 Link-O-Rama

    […] vCenter Server, ESX/ESXi hosts, and vShield Edge Appliances for vCloud Director 5.1 (KB Article) vSphere 5.1 Generally Available – Important Upgrade Considerations (Long White Virtual […]

  2. Doug B
    Doug B at |

    Michael, thanks for the timely post and quick rundown of some of the updated products and dependencies.

    Reply
  3. Ben Loveday
    Ben Loveday at |

    Great post mate, nice summary of the release and known issues!

    Reply
  4. Complete guide to all the essential vSphere 5.1 links | Wintual

    […] (KBTV Video) Installing VMware vCenter Server 5.1 using the Simple Install method (KBTV Video) vSphere 5.1 Generally Available – Important Upgrade Considerations (Long White Virtual […]

  5. Marco P
    Marco P at |

    Michael,

    I' trying to get my lab VCSA 5.0.0.5480 upgraded, also having trouble with a CA Signed cert. Trying to revert to default certs to see if this will do the trick.

    Reply
    1. @vcdxnz001
      @vcdxnz001 at |

      Hi Marco, I've updated my article with a couple of useful links including Troubleshooting the CA Signed Certs. That KB in particular is a must read in my opinion. I hope it helps you. Please let me know if it does.

      Reply
  6. Aaron DiLapi
    Aaron DiLapi at |

    Spent many hours on the phone with VMware support yesterday about an upgrade failure in the vCenter Server installer:

    Error 26002. Setup failed to register VMware vCenter Server to VMware vCenter Inventory Service

    Here is VMware's analysis so far:

    %temp%vcregtool.log reports the below error:

    [2012-09-11 19:53:57,701 main ERROR com.vmware.vim.dataservices.vcregtool.RegisterVC] Cannot read VC private key file C:ProgramDataVMwareVMware VirtualCenterSSLrui.key

    java.lang.NullPointerException

    at com.vmware.vim.dataservices.vcregtool.RegisterVC.loadVcPrivateKey(RegisterVC.java:478)

    at com.vmware.vim.dataservices.vcregtool.RegisterVC.loadVcProviderInfo(RegisterVC.java:300)

    Based on early reports I'm hearing of certificate trouble especially with CA signed certs (AD 2008 R2 in my case) I'm thinking this is all related. I'll follow-up this post if I manage to get anywhere. I'm interested in hearing if others are able to bypass issues by restoring the default cert (hope you backed yours up!).

    Reply
    1. Josh Coen
      Josh Coen at |

      Aaron, I ran into the same problem. I read on one of the communities post that someone was able to workaround it by replacing their CA signed certs with the original self-signed certs. I haven't tried it yet.

      Reply
    2. Tim Mori (@tim_mori)
      Tim Mori (@tim_mori) at |

      I ran into this error trying to get past a different one (http://communities.vmware.com/message/2116952#2116952)

      I attempted to create slightly different certs for vCenter and Inventory service by giving each a different Organization name in the subject of the csr. While this worked fine on 5.0 after restarting all the services. I got the 26002 error during the upgrade. Sort of a success because I did get past the 29107 error.

      There definitely seems to be an issue with either Windows 2008 R2 CA signed certificates, or the CA itself.

      Reply
  7. Mark Verwoerd
    Mark Verwoerd at |

    An other issue:

    VMware Converter 5.0 will crash when connecting to vCenter 5.1: http://communities.vmware.com/message/2113969

    Reply
    1. @vcdxnz001
      @vcdxnz001 at |

      Thanks for the heads up. I'd expect a new version of Converter soon. Also the PowerPath/VE patches are expected shortly too.

      Reply
  8. Mark Verwoerd
    Mark Verwoerd at |

    I found a workaround:

    Make a VM on ESXi 5.1.0 running ESXi 5.0.0, and use that Virtual ESXi 5.0.0 for Converter 5 to P2V your physicle machines. Gotta like VMware :)

    Reply
  9. Kernel Panic in vShield Manager after Upgrade to 5.1 « Long White Virtual Clouds

    […] and are upgrading their lab environments.  I wrote about a number of considerations in my article vSphere 5.1 Generally Available – Important Upgrade Considerations. However a specific issue has come up with some upgrades of vShield Manager  to 5.1 that you need […]

  10. VMware Communities Roundtable Podcast – Show Notes #203 – What’s New in vSphere 5.1 Storage | VMTN Blog - VMware Blogs

    […] [Michael Webster Blog] vSphere 5.1 Generally Available – Important Upgrade Considerations […]

  11. vSphere 5.1 Gotcha with Single Sign On (SSO) « Long White Virtual Clouds

    […] source discovery error (2034374), which is one of the errors that I spoke about in my article vSphere 5.1 Generally Available – Important Upgrade Considerations. When you run into this error you will have to sign into vSphere Web Client using the […]

  12. Upgrade to vSphere 5.1 - Step 1 | VMwaremine - Mine of knowledge about virtualization

    […] See great article from Michael Webster site about upgrade considerations  […]

  13. Upgrade from vSphere 5 to vSphere 5.1 - Part 3.1 | VMwaremine - Mine of knowledge about virtualization

    […] See great article from Michael Webster site about upgrade considerations  […]

  14. Upgrade from vSphere 5 to vSphere 5.1 – Part 4 - VMware vSphere Update Manager | VMwaremine - Mine of knowledge about virtualization

    […] See great article from Michael Webster site about upgrade considerations  […]

  15. vSphere 5.1 Link Documentação « Osvaldoneris's Blog

    […] the Simple Install method (KBTV Video) Installing ESXi 5.x in VMware Workstation (KB Article/Video) vSphere 5.1 Generally Available – Important Upgrade Considerations (Long White Virtual Clouds) ESXi 5.1 Upgrade fails with the error: Cannot execute upgrade script on […]

  16. Tim S
    Tim S at |

    Has anyone figured out how to do this yet? Is it any better with newer versions of 5.1? I am getting ready to upgrade and these comments are making me pretty nervous since I have CA signed certs on Win 2008 also.

    Reply
    1. @vcdxnz001
      @vcdxnz001 at |

      Hi Tim, We have figured out how to do the certs. Firstly you'll need to make sure your certs have a bit strength of 2048 or greater. Then you can have a look at the article on changing out certs as relevant at the following location – http://longwhiteclouds.com/2012/10/27/updating-ca…. The upgrade process itself should be better with 5.1b, which has recently come out.

      Also thanks for prompting me to update the article. I missed the update when the SSL articles were published. I wish you luck with the upgrade. I would recommend you test it in your lab or offline if you can before doing production. Good luck.

      Reply
  17. Aaron DiLapi
    Aaron DiLapi at |

    My issues were resolved with the release of 5.1.0a and I have been running vCenter 5.1 smoothly since the release of the updated installer. I suspect 5.1.0b further improves the upgrade situation.

    Reply
  18. » Disabling vSphere 5.1 Single Sign-on (SSO) – Don’t do it! Long White Virtual Clouds

    […] vSphere 5.1 Generally Available – Important Upgrade Considerations […]

Leave a Reply