Home > Blogs > VMware Support Insider


ALERT: vSphere 5.1 is not compatible with any versions of VMware View

AlertVMware vSphere 5.1 is not currently supported with any versions of VMware View.

vSphere 5.1 is in the process of being certified against VMware View. We recommend that you do not upgrade vSphere above the supported versions listed in the VMware View 5.1 Release Notes.

For further updates and more information on this alert, refer to KB article:
vSphere 5.1 is not compatible with any versions VMware View (2035268).

15 thoughts on “ALERT: vSphere 5.1 is not compatible with any versions of VMware View

    1. Nathaniel Manzi

      Unless specifically stated you shouldn’t expect anything new to be supported with any software. Doesn’t mean it won’t work, it’s just unsupported. It takes time to test and educate support technicians.

  1. Rick BlytheRick Blythe Post author

    This information was in the release notes as well as the above knowledgebase article, which was published yesterday. This is not day-after news.

    1. Daniel Vexoe

      First of, I think this is near preposterous.

      Secondly, the release note for vSphere 5.1 does not mention this in any way, Rick.
      The only mention of View is that “Enabling or disabling View Storage Acclerator might cause ESXi hosts to lose connectivity to vCenter Server”.
      And if are you refering to the View 5.1 Release Notes that clearly states “VMware View 5.1.1 is supported on … vSphere 5.0 or later” I simply don’t get it…?!

      Best regards, Daniel…

  2. Pingback: vSphere 5.1 currently not compatible with any View version at That's my View

  3. Pingback: #Veeam Backup & Replication e il supporto a vSphere 5.1

  4. Pingback: #Veeam Backup & Replication and vSphere 5.1 support

  5. Observer

    Overheard in an IT meeting:

    Person1: We are moving forward with upgrading to vSphere 5.1.
    Person2: Seriously? It’s been out for just a few weeks?
    Person1: We’ve done testing in our lab and found that everything works.

    Afterwards
    Person2: Anyone can do whatever they want on their last day of work.

  6. Rick Blythe

    Daniel, while I didn’t write the release notes myself, I asked an engineer from the View team to clarify what we mean in the notes. He told me that when we say 5.0 and up is supported, it does not include 5.x
    I can understand the confusion over this completely, and I have suggested we improve our wording.

    I ask that you be patient, but I am strictly forbidden from saying anything about when it will be supported. My hands are tied.

    I hope this helps.

  7. Mark

    Really wish I had better warning (and yes, that document is confusing), upgrading the Appliance was a serious headache. Even so, our View 5.1.0 server detected the vCenter Server 5.1 and neatly switched its API from 5.0 to 5.1. All the functionality we use still works with View 5.1.0 and vSphere 5.1. I’m afraid to touch it now though, let alone update it to 5.1.1. Perhaps not supported doesn’t necessarily mean non-functional?

    1. Mark

      Probably everything works but simply hasn’t been internally tested and confirmed yet. As a result VMware reserves the right to refuse support on this combination. The functionality is present, as is evident by the fact that View 5.1 already has a 5.1 API available. I haven’t tested composer integration/functionality yet though.

  8. Jean-Marc Trappier

    Hey all, as it was stated above, chances are everything will work perfectly, the note only states that the solution isn’t fully supported (even not supported at all) but this doesn’t mean it won’t work. So if you upgraded your vCenter, don’t be so anxious to downgrade it, you may not even notice any trouble at all.

    VMware will open the ticket and I never saw VMware closing one stating “you are not in a fully supported scenario, you’re on your own unless you fit the interoperability matrix”.

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

Comments are closed.