Can someone point me to some documentation that explains what the different colored icons mean when I select a guest to restore?  Some of the backups are Orange icons some of the backups are green with a red dot in the top left.

  Hi!

  I'm successfully using VMware PHP vCloud API to gather information from my vCloud Organitzation objects (orgs, vDCs, vShield Edges, vApps, VMs) (my scripts), but how can I get the usage of my Storage Profiles?

  On my tests, I get a reference to a vDC ($vdcRef), then I create a VMware_VCloud_SDK_Vdc object doing:

$sdkVdc = $service->createSDKObj($vdcRef);

  then I get it's StorageProfiles doing

$sdkVdc->getVdcStorageProfiles();

  but this array contains objects of class VMware_VCloud_API_VdcStorageProfileType , which has methods like getEnabled() , getUnits() , getLimit() , getDefault() and getDescription() , but it just shows me the limit (getLimit()), not it's current disk usage.

  Looking at API source, I realize that depending on your authorizations some methods return admin or a non-admin object. For example: on file "VMware/VCloud/Admin.php", you can see that the method getAdminVdcRefs() from VMware_VCloud_SDK_AdminOrg class returns "Admin Vdc references" for "System/Cloud Administrator" but it returns "Vdc references" for "Organization/Tenant Administrators/Users" (that's my case). Maybe if I where and administrator then I could get an object with more information about my Storage Profiles, I don't know.

  Any way, using vCloud Director web user interface I really can get my storage profile's usage. So my account really has permissions to get this information. This way I just can imagine two possibilities:
* or the VMware PHP vCloud API just provides this information to "System/Cloud Administrators"
* or it provides it but I'm not hitting it

  I bet second option :) How can I do it?

  If it's the first option (API is not for me), then at least I may be able to access this information requesting it to the vCloud REST API... but browsing it and folling links I can't get this information. I may be missing something.

  Thanks and best regards!
  /Ángel

I've been wanting a GUI driven SBMerge utility for quite a while now so I built one after my client wanted it due to slow typing skills.  If your a slow typist this is built for you!  From now on you can avoid the CMD prompt as much as possible as the hunt and peck method isn't your friend.  For myself, and even some people with fast typing skills should still find this GUI driven wrapper faster than using the CMD prompt, along with the added feature of logging each task along the way.  

As for the SBAssist, You should find the GUI use of this application easy to use, almost too simplistic.  The install is a simple file copy to the ThinAppBuild folder.  After that is completed you can run it by simply clicking on it when needed.

Keep in mind the this tool simple creates a GUI Wrapper that still uses SBMerge.exe underneath it does not replace it.  All best practices of using SBMerge.exe should still be observed.  If you are not familiar with those please see the link below
http://blogs.vmware.com/thinapp/2010/02/simple-steps-for-using-sbmerge.html

Delete or rename existing Sandbox for the application you plan on making changes to, this will make sure the application has a clean Sandbox.

Ready Set Go

PreSteps

1.     Close all application possible if opened.
2.     Delete current sandbox!
3.     Take a backup of the Build directory prior to using SBMERGE or SBASSIST

Start your SBMerge session.

1. Launch ThinApp’ed application and make changes as needed. including updated registry settings, update to program, etc.
2. Close Application,
   1. Verify sandbox is not in use.  If so a reboot of the VM might be required to close the locked files. This should not affect the SBMerge
3. Run SBAssist tool.
4. Select SandBox folder|
   
5. Select the project folder
   
6. Verify Information, if correct the App will run the command to generate a text file from SBMerge Print followed by Apply. OR If you didn’t backup of the Build directory prior please do this first!
   
7. A logfile is created in the ProjectDir of the application along with a overview logfile in the ThinApp build folder.
8. Run build.bat manually
9. Test application!
   
   

Enjoy,

Kevin E. Komlosy

VirtallyTangled

Hi all,

Happy to be back on vSphere Web Client development again.  In our solution we have helpful links to actions for users on the getting started pages.  Some actions are not available to Read Only users.  How do I hide those actions in actionDisplayInfos?

Hey there,

we got the same problem two weeks ago. One of our Datastores was suddenly unavailable.

Back then there where machines running on that Datastore.

We rebooted the server, the Datastore was back on but we had serious problems with locked files (which still isn't resolved).

See the Thread here:  http://communities.vmware.com/thread/319421?tstart=150

We now are in fear that there might be more locked files or some more trouble when rebooting the server.

We also would like to know the cause of that Datastore beeing unavailable.

We already tried  "vmkfstools -V" and looking at the problem with esxcfg-scsidevs -l / -a / -m (see output below!)

I was deleting some old backups of machines when the Datastore vanished (deleting some machines via the Console/SSH on the same Datastore worked a few minutes before).

I include the Console output at the time the Datastore was gone (see below).

Maybe someone has some useful tips on how to remount the Datastore / get it back online or can indentify the source of the problem!

Thanks in advance for replies, asgaroth

/vmfs/volumes/4bd88e21-e8b0d6ea-6c1a-003048c30e8c # rm -rf serverxyz.subdomain.domain



rm: cannot remove 'serverxyz.subdomain.domain/serverxyz.subdomain.domain-flat.vmdk': Resource temporarily unavailable

rm: cannot stat 'serverxyz.subdomain.domain/serverxyz.subdomain.domain.vmdk': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/serverxyz.subdomain.domain.nvram': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware-37.log': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware-38.log': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware-39.log': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/serverxyz.subdomain.domain-c1309193.hlog': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware-42.log': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware-41.log': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware-40.log': Device or resource busy

rm: cannot stat 'serverxyz.subdomain.domain/vmware.log': Device or resource busy

rm: cannot remove 'serverxyz.subdomain.domain': Device or resource busy

ash: getcwd: Device or resource busy





(unknown) # ls -al

ls: .: Input/output error

ash: getcwd: Input/output error





(unknown) # cd /



~ # ls -al /vmfs/volumes/





ls: /vmfs/volumes/4bd88e21-e8b0d6ea-6c1a-003048c30e8c: Input/output error

drwxr-xr-x    1 root     root                512 Jul 12 13:37 .

drwxr-xr-x    1 root     root                512 Jun 28 15:57 ..

drwxr-xr-x    1 root     root                  8 Jan  1  1970 386a41e4-ff1587ba-1385-2feaeed494ad

drwxr-xr-t    1 root     root               1960 Jul 12 12:56 4bc8414f-3206fe54-f06e-003048c30e8c

drwxr-xr-t    1 root     root               3500 Jul  8 22:30 4bd88e99-c67ad631-6c62-003048c30e8c

drwxr-xr-t    1 root     root                980 May 21 14:43 4dd7cf77-c3e57835-e9ef-003048c30e8c

drwxr-xr-x    1 root     root                  8 Jan  1  1970 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Datastore1 -> 4bc8414f-3206fe54-f06e-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Datastore2 -> 4bd88e21-e8b0d6ea-6c1a-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Datastore3 -> 4bd88e99-c67ad631-6c62-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Datastore4 -> 4dd7cf77-c3e57835-e9ef-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Hypervisor1 -> 386a41e4-ff1587ba-1385-2feaeed494ad

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Hypervisor2 -> 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0

lrwxr-xr-x    1 root     root                 35 Jul 12 13:37 Hypervisor3 -> e00f98e1-2bcc0c91-e7a2-3487611c1557

drwxr-xr-x    1 root     root                  8 Jan  1  1970 e00f98e1-2bcc0c91-e7a2-3487611c1557





~ # ls -al /vmfs/volumes/Datastore2





lrwxr-xr-x    1 root     root                 35 Jul 12 13:38 /vmfs/volumes/Datastore2 -> 4bd88e21-e8b0d6ea-6c1a-003048c30e8c





~ # ls -al /vmfs/volumes/Datastore2/





ls: /vmfs/volumes/Datastore2/: Input/output error





~ # df

Filesystem           1k-blocks      Used Available Use% Mounted on

visorfs                1338636    267996   1070640  20% /

vmfs3                488112128 328402944  159709184  67% /vmfs/volumes/4bc8414f-3206fe54-f06e-003048c30e8c

nfs                  315829740 135465900  180363840  43% /vmfs/volumes/0d6becf5-2ea0d633

nfs                  1175588244 230332944  945255300  20% /vmfs/volumes/fa828cd2-adbc3d72

vmfs3                976486400    578560  975907840   0% /vmfs/volumes/4dd7cf77-c3e57835-e9ef-003048c30e8c

vfat                    292752    139328    153424  48% /vmfs/volumes/e00f98e1-2bcc0c91-e7a2-3487611c1557

vfat                    255716     90204    165512  35% /vmfs/volumes/8c7e2fe8-f4c58d9f-34d3-8553ffee79a0

vfat                    255716     61804    193912  24% /vmfs/volumes/386a41e4-ff1587ba-1385-2feaeed494ad





~ # vmkfstools -V





~ # ls /vmfs/volumes/





0d6becf5-2ea0d633                    4dd7cf77-c3e57835-e9ef-003048c30e8c  Datastore4                           e00f98e1-2bcc0c91-e7a2-3487611c1557

386a41e4-ff1587ba-1385-2feaeed494ad  8c7e2fe8-f4c58d9f-34d3-8553ffee79a0  Hypervisor1                          fa828cd2-adbc3d72

4bc8414f-3206fe54-f06e-003048c30e8c  Datastore1                           Hypervisor2                          nfs-vmds1

4bd88e99-c67ad631-6c62-003048c30e8c  Datastore3                           Hypervisor3                          nfs-vmds2





~ # ls -l /vmfs/volumes/





drwxr-x---    1 root     root               4096 Jun 30 12:47 0d6becf5-2ea0d633

drwxr-xr-x    1 root     root                  8 Jan  1  1970 386a41e4-ff1587ba-1385-2feaeed494ad

drwxr-xr-t    1 root     root               1960 Jul 12 12:56 4bc8414f-3206fe54-f06e-003048c30e8c

drwxr-xr-t    1 root     root               3500 Jul  8 22:30 4bd88e99-c67ad631-6c62-003048c30e8c

drwxr-xr-t    1 root     root                980 May 21 14:43 4dd7cf77-c3e57835-e9ef-003048c30e8c

drwxr-xr-x    1 root     root                  8 Jan  1  1970 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0

lrwxr-xr-x    1 root     root                 35 Jul 12 13:59 Datastore1 -> 4bc8414f-3206fe54-f06e-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:59 Datastore3 -> 4bd88e99-c67ad631-6c62-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:59 Datastore4 -> 4dd7cf77-c3e57835-e9ef-003048c30e8c

lrwxr-xr-x    1 root     root                 35 Jul 12 13:59 Hypervisor1 -> 386a41e4-ff1587ba-1385-2feaeed494ad

lrwxr-xr-x    1 root     root                 35 Jul 12 13:59 Hypervisor2 -> 8c7e2fe8-f4c58d9f-34d3-8553ffee79a0

lrwxr-xr-x    1 root     root                 35 Jul 12 13:59 Hypervisor3 -> e00f98e1-2bcc0c91-e7a2-3487611c1557

drwxr-xr-x    1 root     root                  8 Jan  1  1970 e00f98e1-2bcc0c91-e7a2-3487611c1557

drwxr-x---    1 root     root               4096 Jun 30 12:36 fa828cd2-adbc3d72

lrwxr-xr-x    1 root     root                 17 Jul 12 13:59 nfs-vmds1 -> 0d6becf5-2ea0d633

lrwxr-xr-x    1 root     root                 17 Jul 12 13:59 nfs-vmds2 -> fa828cd2-adbc3d72





~ # esxcfg-scsidevs -l   

mpx.vmhba0:C0:T0:L0

   Device Type: CD-ROM   Size: 0 MB   Display Name: Local TSSTcorp CD-ROM (mpx.vmhba0:C0:T0:L0)   Multipath Plugin: NMP   Console Device: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0   Devfs Path: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0   Vendor: TSSTcorp  Model: CDDVDW SH-S202N   Revis: SB01   SCSI Level: 5  Is Pseudo: false Status: on          Is RDM Capable: false Is Removable: true    Is Local: true    Other Names:      vml.0005000000766d686261303a303a30   VAAI Status: unknown

mpx.vmhba32:C0:T0:L0

   Device Type: Direct-Access   Size: 998 MB   Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)   Multipath Plugin: NMP   Console Device: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0   Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0   Vendor: TinyDisk  Model: 2005-03-10        Revis: 2.00   SCSI Level: 2  Is Pseudo: false Status: on          Is RDM Capable: false Is Removable: true    Is Local: true    Other Names:      vml.0000000000766d68626133323a303a30   VAAI Status: unknown

naa.600050e0d7beda002095000037530000

   Device Type: Direct-Access   Size: 953664 MB   Display Name: Local AMCC Disk (naa.600050e0d7beda002095000037530000)   Multipath Plugin: NMP   Console Device: /vmfs/devices/disks/naa.600050e0d7beda002095000037530000   Devfs Path: /vmfs/devices/disks/naa.600050e0d7beda002095000037530000   Vendor: AMCC      Model: 9650SE-8LP DISK   Revis: 4.10   SCSI Level: 5  Is Pseudo: false Status: on          Is RDM Capable: false Is Removable: false   Is Local: true    Other Names:      vml.0200000000600050e0d7beda002095000037530000393635305345   VAAI Status: unknown

t10.AMCC____9QJ0ZCFYD87EFE007FC4

   Device Type: Direct-Access   Size: 953664 MB   Display Name: Local AMCC Disk (t10.AMCC____9QJ0ZCFYD87EFE007FC4)   Multipath Plugin: NMP   Console Device: /vmfs/devices/disks/t10.AMCC____9QJ0ZCFYD87EFE007FC4   Devfs Path: /vmfs/devices/disks/t10.AMCC____9QJ0ZCFYD87EFE007FC4   Vendor: AMCC      Model: 9650SE-8LP DISK   Revis: 4.10   SCSI Level: 5  Is Pseudo: false Status: on          Is RDM Capable: false Is Removable: false   Is Local: true    Other Names:      vml.010000000039514a305a434659443837454645303037464334393635305345   VAAI Status: unknown

t10.AMCC____9QJ16PFCD87EFE00CB5E

   Device Type: Direct-Access   Size: 953664 MB   Display Name: Local AMCC Disk (t10.AMCC____9QJ16PFCD87EFE00CB5E)   Multipath Plugin: NMP   Console Device: /vmfs/devices/disks/t10.AMCC____9QJ16PFCD87EFE00CB5E   Devfs Path: /vmfs/devices/disks/t10.AMCC____9QJ16PFCD87EFE00CB5E   Vendor: AMCC      Model: 9650SE-8LP DISK   Revis: 4.10   SCSI Level: 5  Is Pseudo: false Status: on          Is RDM Capable: false Is Removable: false   Is Local: true    Other Names:      vml.010000000039514a3136504643443837454645303043423545393635305345   VAAI Status: unknown

t10.AMCC____U34961226AEF5C004A68

   Device Type: Direct-Access   Size: 476827 MB   Display Name: Local AMCC Disk (t10.AMCC____U34961226AEF5C004A68)   Multipath Plugin: NMP   Console Device: /vmfs/devices/disks/t10.AMCC____U34961226AEF5C004A68   Devfs Path: /vmfs/devices/disks/t10.AMCC____U34961226AEF5C004A68   Vendor: AMCC      Model: 9650SE-8LP DISK   Revis: 4.10   SCSI Level: 5  Is Pseudo: false Status: on          Is RDM Capable: false Is Removable: false   Is Local: true    Other Names:      vml.01000000005533343936313232364145463543303034413638393635305345   VAAI Status: unknown





~ # esxcfg-scsidevs -a

vmhba0  ata_piix          link-n/a  ide.vmhba0                              (0:0:31.1) Intel Corporation 631xESB/632xESB IDE Controller

vmhba1  3w-9xxx           link-n/a  unknown.vmhba1                          (0:1:0.0) 3ware Inc 3ware 9650SE

vmhba32 usb-storage       link-n/a  usb.vmhba32                             () USB                         

vmhba33 ata_piix          link-n/a  ide.vmhba33                             (0:0:31.1) Intel Corporation 631xESB/632xESB IDE Controller





~ # esxcfg-scsidevs -m

t10.AMCC____U34961226AEF5C004A68:1                               /vmfs/devices/disks/t10.AMCC____U34961226AEF5C004A68:1     4bc8414f-3206fe54-f06e-003048c30e8c  0  Datastore1

naa.600050e0d7beda002095000037530000:1                           /vmfs/devices/disks/naa.600050e0d7beda002095000037530000:1 4dd7cf77-c3e57835-e9ef-003048c30e8c  0  Datastore4

t10.AMCC____9QJ16PFCD87EFE00CB5E:1                               /vmfs/devices/disks/t10.AMCC____9QJ16PFCD87EFE00CB5E:1     4bd88e99-c67ad631-

We can restart the Installation Wizard with the following command:

/usr/sbin/vcac-vami installation-wizard activate

However the parameter for vRA settings is remaining unexpectedly. So is there any good way to clean this parameter?

I think it's appropriate to see the following directory. But I can't find how to clean installation parameter.

/opt/installation-wizard/

/opt/vmware/share/vami or vami-common

I receive the following errors every time I try to download the any new bits.  I was attempting to download the new NSX_624 bits, but noticed I get this same error with any download.  Please assist.

Hi all

I installed Fedora 24 on VMware three times after install the VMware tools, first error I see "failed to find cpu0 device" and sometimes error "backlog limit exceeded" , finale failed to load and it's remains in black screen

Message was edited by: MML_Professional

With the announcementof the VMware Validated Design for Software-Defined Data Center 3.0 it is my pleasure to share the digital reference poster.

This poster depicts many portions of the fundamental architecture for both quick reference and discussion.

Download the VMware Validated Design for SDDC 3.x Poster

Got Questions or Want to Follow Updates?

• Provide general feedback or ask a question on VMware Validated Designs, by selecting the "Start a Discussion" button here in this community.
• Follow this community by selecting the "Following in" button in the community banner. You will receive general notifications when new content is available.

At VMworld 2016 we released some new demo videos for the VMware Validated Design for Software-Defined Data Center. These videos provide a tour of the the components as deployed in the SDDC design.

Core Platform

The VMware Validated Design for SDDC is a blueprint for the private cloud that results in an SDDC that is consistent, thoroughly documented, extensively tested from end-to-end, and continuously validated to incorporate new releases of software components. In this video, we will demonstrate some of the core platform components of a private cloud based on this design.

Software-Defined Storage

In this video, we will demonstrate the configuration of VMware Virtual SAN for use in this design.

Software-Defined Networking

VMware NSX reproduces the complete set of Layer 2 through 7 networking services in software. This includes: switching, routing, access control, firewall and load balancing. In this video, we will demonstrate the configuration of VMware NSX for use in this design. This demo focuses primarily on the configuration in management stack.

Cloud Operations with vRealize Operations

Once an SDDC has been deployed, its ongoing performance and health must be continually monitored, and administrators must be notified any time problems develop, or capacity constraints are reached. In this video, we will review the deployment and configuration of vRealize Operations in this design.

Cloud Operations with vRealize Log Insight

VMware vRealize Log Insight provides centralized log aggregation and log analytics. It increases the operational visibility, facilitates troubleshooting and root cause analysis in the SDDC. In this video, we will review the configuration of vRealize Log Insight, based on this comprehensive SDDC architecture.

Cloud Management and Automation with vRealize Automation

VMware vRealize Automation provides the Service Catalog and self-service portal for the Software-Defined Data Center. In this video, we will review the deployment and configuration of vRealize Automation based on this comprehensive SDDC architecture.

皆さんこんにちは。て頂きたいことがあります。

ホストはWindows8.1Pro64bit

ゲストはWindowsXPPro32bit SP3

ゲストの方で、USB3.0対応のポータブルハードディスクを使いたいのですが、どのようにしたらら良いか教えて頂けませんか？

よろしくお願いします。

I just received an e-mail from VMware tech support, telling me that 8.5 is coming... no word on whether or not it in fact fixes the issue that stopped me from using it (black screen when wake-from-sleep even with VMware quit/not running).

Any news if this fixes it?

Buenas,

quiero hacer ese upgrade de ESXi y previamente pasaré por ESXI5. En la HCL de vmware el hardware no aparece soportado para la version 6, pero si funcionara mi duda es si respetará la configuración de host, sobretodo el networking, ya que hay dos ethernets en team con IP Hash.

Un saludo

.

hi i have more that 20 servers now i see their model all of them has same model

Intel Xeon E5-2600 Series

and see this in vmware fot that model

VMware Compatibility Guide - cpu

and now i have a server with this cpu model:

Intel Xeon E5-2600-v2 Series

VMware Compatibility Guide - cpu

i understand this :

1 - Intel Xeon E5-2600 Series is a SandyBridge-EP 2S  and Intel Xeon E5-2600-v2 Series  is IvyBridge EP  and Intel Xeon E5-2600 Series can not support  IvyBridge now i think we can not put these kind of cpus in one cluster with EVC

Is this correct ?

and the other question that i think is :

2 - i think if put these 2 kind of different servers on a cluster with EVC mode my vm can migrate from E5-2600 to E5-2600-v2 but can not migrate from E5-2600-v2 toE5-2600  is this correct ?

Hi,

We have a requirement where we have to integrate BMC BSA with VRO...as far i have checked it can be done through BMC SA plugin..but is there any option to connect to BSA without using plugin from VRO...

Thanks,

Mano

Hello Team,

I am trying to install iSCSI Software adapter in my lab machine. But every time in task status Change software internet SCSCI status completed successfully. But when i check in Storage Adapter respective adapter is not visible (vmbha33 is not visible) in storage.

Can anybody please suggest me how to resolve this issue. Without this option am unable to continue my lab to add iSCSI/NFS disk in my lab.

I attached herewith respective screen shot, i think these information are sufficient to help me.

Regards

GaneshSS

hi All

I installed ESXi on a Asrock X99 Extreme6 mainboard. Everything works fine except the Atheros network interface.

I allready tried the Atheros AR8161 VIB Driver and

• net-atl1: Attansic/Atheros L1 Gigabit Ethernet driver
• net-atl1e: Driver for Atheros(R) AR8121/AR8113/AR8114/AR8131/AR8132/AR8152 PCI-E Ethernet NICs

Does anyone has a VIB driver file for the atheros ar8171 interface?

Thanks,

Stefan

Hi All,

I'm working on integration with our internal systems, however, I have come to the point where I would like to cancel provisioning due to lack of IP addresses in given subnet. Unfortunately, when I have defined it in lifecycle:

   payload>lifecycleState> phase : PRE

   payload>lifecycleState> state : VMPSMasterWorkflow32.Requested

and exit workflow with an error/exception -> provisioning continues. Is there any way to cancel provisioning process?

I am working on vra7 with vro7. 

Help will be appreciated!

in App volumes 2.11 I see a lot of pending actions, now 1793 pending actions. mostly the following actions

If i assign apps stacks to a users this doesn't doe anything because all the pending jobs need to be done first.

I already restarted the app volume server. but doesn't solve the problem.

does anyone know why these actions stay pending and how to solve it?

or can I delete pending jobs

Is vCloud Director 5.5 appliance available to download?

Thank you,

Victor