1. I think so long as the VMs land in the Same Org vDC Pool on the other side.
2. You (think) should be able to migrate using Manage & Monitor > Resource Pools > Double click the source resource pool > Right Click and select Migrate.
1. I think so long as the VMs land in the Same Org vDC Pool on the other side.
2. You (think) should be able to migrate using Manage & Monitor > Resource Pools > Double click the source resource pool > Right Click and select Migrate.
Can someone remind me what the minimum permissions are to allow non-Org admins to be able to see Public Catalogs.
I have some ISOs shared via public catalog between two distinct orgs, and I don't want to subscribe and cause them to clone inside the same datacenter.
Just trying to sort out what's the minimum extra privileges I would have to give to an App Author to be able to see the public shared catalogs.
I know the sharing works, as the Org Admin role can see the Public Shared catalogs and insert media to a VM without error.
Those features usually require the VMRC.
If you are using the vSphere UI, you have to launch the VMRC to get this sort of feature or function ... or use the older C#/Fat client if you are using older versions of vSphere.
vCloud Director uses an HTML5 console, but that doesn't support console copy/paste.
Hi to all,
I would appreciate help with following problem in vCloud Director environment we have.
Customer is asking for functionality to change password for default administrator in guest OS (in cases where end customers forgot password).
We were able to change administrator password using guest OS customization. It is same if we do that using vCloud Director GUI or from vRO worklow - behavior we experience is the same.
If we tick only "Enable guest customization" and "Auto generate password" (and untick "Change SID"), Power ON and force customization, password is changed but at every reboot cycle of VPS we see "VMware Image Customization in progress" screen. Beside that, we see in registry that sysprep was not finished, same like described here VMware Knowledge Base . Templates are created using correct operating system.
Here are settings which produce this behavior, like I sad, same is if we do that using vRO workflow.
Doe anyone saw this before? Changing registry on every provisioned VPS is not best option to solve this...
or
guestCustomizationSection.enabled = true;
guestCustomizationSection.adminPasswordEnabled = true;
guestCustomizationSection.changeSid = false;
guestCustomizationSection.adminPasswordAuto = true;
guestCustomizationSection.resetPasswordRequired = false;
guestCustomizationSection.adminAutoLogonEnabled = false;
guestCustomizationSection.adminAutoLogonCount = 0;
Environment consist of:
vCenter Server 6.0.0, 7037393
ESXi 6.0.0, 3825889
vCloud Director 8.2.0
I woul appreciate any help.
Thank you.
Goran
According to vCD 9.1 release notes, from vCD 9.1, VM use SRIOV workload is supported. But we can not find out how to use the SRIOV from the vCD from UI / API. Does it has any document about the how to create a vm which use SRIOV in vCD? Or the detail steps to enable the VM to use the SRIOV network?
Many views, but no answer...
Anyone?
Hi!
From VMware Documentation
SR-IOV (Single-Root input/output Virtualization)
The configuration is done per virtual machine from within vCenter itself, but vCloud Director will not affect the workload configuration.
Hope it helps
Hello.
We installed vCloud Directors cells with private IP (192.168.25.19-21).
Now, if i go in Edge Gateways to Edge Services, i redirected to this URL.
Can i change this behavior?
I need to go to my public FQDN, like this https://portal.something.com?
Or must we change IP adresses to public on vCloud cells?
I found the answer to my question.
Administration--> Public Addresses-->HTTPS REST API base URL: https://portal.yourdomain.com/
After that Edge Gateway-->Edge Gateway Services opens as expected.
We had the same issue - we were absolutely sure that the certificates and Public URIs were set correctly, but still getting 'No Datacenters are available' in the tenant portal. (All other /provider portal functionality worked fine and the other tabs in the tenant portal worked, just not the datacenters one).
Just found the fix courtesy of a comment by Tomas Fojta in the vExpert slack channel:
Make sure that DNS on the cell servers can resolve the FQDN of your cloud platform correctly.
In our case we have 3 cells behind a load balancer, for the sake of this example lets say 192.168.0.1, 192.168.0.2 and 192.168.0.3 are the cell internal IP addresses and 'cloud.provider.com' is the portal URI. So on cell 1 I add:
192.168.0.1 cloud.provider.com
To the /etc/hosts file (and so on for each cell server using it's local interface address). After this change the Datacenters tab now correctly populates in the tenant portal. No restart of cell services required either.
Weird as these servers all have DNS accessible and are able to resolve the FQDN of our cloud, but this definitely fixed the issue for us.
In vCD 9.x VMRC makes a (welcome) return as an additional option for server consoles, although must admit I haven't tried copy/paste yet...
I had the exact same issue. Exporting as Base64 worked - thank you guys
So, I have 3 isolated cells of vCloud running across the Globe, 2 in the states(one is version 9 and another 9.1) and 1 in Asia pacific(version 9.1).
The Catalog transfer work perfectly with the Asia vCloud to both US ones and vice versa, but errors out when I try transferring between the vCloud in Same location(US ones).
Also changing certificate to Base*64 format while resolving tenant portal does not work in the vCloud 9.1 at US location but works in Asia one
Attached is the errors and problem Description -
Any Help would be appreciated
VMRC does provide a work around for clipboard operations, but it does require an external agent "installation" on host PC's(which is a big no for many users).
I've written up the 'fix' for this in our scenario here: https://vexpert.me/18I
Hello,
For an Org vDC in the section monitor I can see that 80% of the storage is used -> 800GB
If I look in the storage policy of this org vDC I can see that 900GB have status Requested. (Requested 900 - Limit 1000)
Can someone explain the difference ?
Hello
I have this scenario :
One Oorganization containing the catalogs of Windows Servers and Linux and in this organization I have a VM policy to store the templates in a specific datastore. This police does not need IOP limitation (Name ex: StoragePolicy-Public
An organization of a client tries to deploy the catalog VM and has an error because this police has IOP limitation.
How do I deploy catalog VMs with IOP limitation?
vCD 9.1 console language dropdown does not have UK English available. The closest is US English. Changing the OS keyboard layout does not make a difference. Windows Server 2016 has a on-screen keyboard which i can use however it is annoying. Does anyone know how i can change the vCD console keyboard to UK English for British keyboards at all?
Hi BostanHussain - I do not believe it's possible on changing the default language as vCD utilizes the VMware HTML Console. However, with 9.1, the VMRC option is natively supported and there are keyboard customizations available.
Hi, I am testing CSE and I have the exact same issue, only with the Ubuntu16.04 image. It's not installing VMware tools and can not perform
Guest operation inside the deployed VM.
waiting for process 1284 on vm 'vim.VirtualMachine:vm-134' to finish (46)
exception, will retry in a few seconds, vm 'vim.VirtualMachine:vm-134'
exception: (vim.fault.GuestOperationsUnavailable) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = 'The guest operations agent could not be contacted.',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) []
}
Traceback (most recent call last):
File "/root/.local/lib/python3.6/site-packages/vsphere_guest_run/vsphere.py", line 86, in execute_program_in_guest
processes = pm.ListProcessesInGuest(vm, creds, [pid])
File "/root/.local/lib/python3.6/site-packages/pyVmomi/VmomiSupport.py", line 580, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/root/.local/lib/python3.6/site-packages/pyVmomi/VmomiSupport.py", line 386, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/root/.local/lib/python3.6/site-packages/pyVmomi/SoapAdapter.py", line 1366, in InvokeMethod
raise obj # pylint: disable-msg=E0702
pyVmomi.VmomiSupport.vim.fault.GuestOperationsUnavailable: (vim.fault.GuestOperationsUnavailable) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = 'The guest operations agent could not be contacted.',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) []
Anyone know of a fix for this?
Thanks