Anyone run across a list of permissions needed to view everything like an Org Admin but not be able to change anything?
With my setup I am using vCD as more of a portal to view performance metrics, console access, service library etc etc within a managed environment, I don’t want users with the ability to create VMs, vApps, edit a VM like new disk but they can restart, shutdown and that’s about all I want them to be able to do.
We create the VMs, adjust resources, install and configure the LOB software and present access to their application via Horizon.
You can install any version of vCD to a vSphere cluster but also to a single host. It does not matter if DRS is enabled. For the appliance version it imports as a OVA. For the binary version, you can install it on compatible RHEL and CentOS VM.
The resource cluster (where the actual customers VM's run) must indeed have DRS enabled. Since vCD depends on Resource Pools. After you have installed vCD you can only add a vCenter server that has NSX enabled. This vCenter server manages the resource cluster.
I am trying to configure vCloud Director 9.7. [9.7.0.14534864] with vSphere 6.7u3 and NSX-T 2.5 [ 2.5.0.0.0.14663974]. The bellow error appears after providing NSX-T2.5 details.
[ 7aa04b99-e103-462e-99ef-0d011d1dc296 ] Could not register NSX Manager
- /api/2.0/global/heartbeat, error code 98
My NSX T install is configured and has TIer 0 Gateway
I have to create an extension (or plugin) on VCD portal, however, I am not having access to the portal. I had downloaded the open source disclosure package. I am not sure how to run or use it so I can create the extensions.
Can anyone please help me by pointing to the relevant documents or links.
We have to create a plugin (or extension) on VMware vCloud Director portal. The plugin shall be shown as the menu option in the portal and be used to perform required activity when clicked.
Can anyone please guide us with the documentation or links to achieve the same.
We have two provider VDCs tied to two diferent vSphere Clusters that are on different datacenters connected by dark fiber. We'd like to have the possibility to migrate tenants from one Provider VDC to other, from vSphere point of viewI know it'ss possible to move all VMs related to the tenant (I understand this is not the way to do it) however we're not sure if this is something that can accomplished in vCloud Director, the tenants are using NSX edge services and the NSX transport zone is the same for both provider VDC.
thanks in advance for any ideas or considerations.
I had 9.7.0.1 in a lab, and was having problems getting SAML for an ORG working, so I patched to 9.7.0.4. Now things are really broken.
Firstly, Help -> About is showing 9.7.0.15498291, which doesn't look like 9.7.0.4, not sure what it showed prior to patching...this is in the Flex and H5 UI. This is a higher build number than is shown currently here VMware Knowledge Base , so I guess it is 9.7.0.4 ?
Anyway, now when you go the Federation settings of an org, in the FlexUI the metadata URL is missing "cloud", that is it has [URL]/org/myorg/blah instead of [URL]/cloud/org/myorg/blah
if you download the metadata from the correct URL and import it, you will find that the assertion endpoints are also missing the "cloud" part in the URLs
So vCD seems to be trying (everywhere) to use URLs without "cloud", which does not work.
If you change the URLs to include 'çloud' in the ADFS properties, you just get an error in ADFS because vCD is actually enforcing the URL without 'çloud' in the redirect.
So now it is really broken, and there doesn't seem to be a way to roll back a vCD patch.....
on another note, SAML is still using SHA-1 even though the metadata xml has SHA-256....you have to manually change the IDP back to SHA-1. This was before patch to 9.7.0.4. CAn't see what it is doing now as its broken.
ok so it seems it wasn't the patch, I spoke too soon. My webconsole URL settings did not have /cloud on the end, my bad. Having corrected that, I have SAML working on 9.7.0.1 (rolled it back via snapshot anyway).
But I still have the outstanding question of why is vCD still using SHA-1, yet including SHA-256 in it's exported metadata?
The release notes for 9.7.0.2 state that it is a fixed issue that the metadata WAS including SHA-1 and they changed it to SHA-256 in the .2 patch, but this is not consistent with what I see - with 9.7.0.1 I see SHA-256 in the metadata, yet it is actually using SHA-1.
When i create a new VM from this template, the hostname is not changed, the password is not set. I can see in the logfiles c:\windows\temp that the customization did some stuff (like executing the windows activation script), but password and hostname are not set.
We're currently deploying vCloud Director for a customer. Their vcenter was upgraded from a windows based 5.5 to a 6.5 appliance but the original vshield manager was never upgraded and is not used anymore. Their existing vcloud director isn't working anymore since it doesn't support vcenter 6.5.
Is it possible to deploy a new vCloud director 10 appliance without NSX?
