Hi
When one run the workflow 'Add vCenter server Instance', the credentials that are supplied are they just used for that point in time. Similar to how you join and ESXi host to a vCenter ?
Thanks
Hi
When one run the workflow 'Add vCenter server Instance', the credentials that are supplied are they just used for that point in time. Similar to how you join and ESXi host to a vCenter ?
Thanks
Author : jacquiew
Topic Name : VMware Horizon Client for Windows User Guide
Publication Name : VMware Horizon Client for Windows User Guide
Product/Version : VMware Horizon Client for Windows/4.10
Question :
I'm trying to download and install VMware Horizon Client - 5.1.0 - build 14045148. It clocks for a few minutes and then displays message "Download VMware Horizon Client failed. When I try to connect to my workstation without this update, I can log in, then the connection closes right away.
What are the official limitations including commercial use for the free ESXi Hypervisor?
Hi
when standing up a new instance of VRO, one has to add the appropriate authentication provider. In my case it is vsphere. The part I am confused about is, what purpose does the admin group serve. I have tried the following
Created a group called VCOAdmin in the vsphere.local domain.
Added an active directory group to the group
Made VCOAdmin the admin group for the authentication provider
When I test, my AD user that is part of VCOAdmin group test succesfully as having admin access to VRO
When I log out of the control center and try log in with my AD user the log in fails, I can however log into the VRO client HTML5 and Java.
I am also not able to execute API calls with this account.
What am I missing ?
Hi I have experienced this today, Logged a ticket with VMware support and also found this on our Skyline set up
Link to the KB :VMware Knowledge Base
Im now trying to hunt down that driver package, although not sure why it hasn't been released in to vum as a normal patch yet
Will update further when support come back
Thanks
Adam
Do you mean you are seeing this when Windows Updates installs KB4507460 and our VMWare tools get upgrqaded to the version that comes with 6.0u3?
Or did it occur with the same updates/versions, when upgrading tools from 6.0u3 version?
The credentials you enter are used to retrieve the vCenter inventory and to perform any activities requested as part of vRO workflows within vCenter e.g. if you run a workflow that creates a virtual machine, vRO will connect to vCenter using the entered credentials to log in and create the new VM. So the account used needs to have sufficient permissions to access all parts of the vCenter inventory that you want to orchestrate via vRO.
The limitations are basically 8 vCPUs per VM, and the restricted API, which eg. prevents from managing the host in vCenter, and using most commercial VM based backup software.
There's however no restriction regarding commercial use, except for the written limitation for less then 100 hosts (you can see this on the registration page, below the license key).
André
To populate an input in vRO with a set of values returned from a REST operation you can do the following:
1. Create an action in vRO that performs the REST operation and returns a value or array of values in the format needed for the input form e.g. string format
2. Create a new workflow with an input parameter in the same format as the results from the REST operation in step 1
3. On the Presentation tab of the workflow edit the input parameter to use the Predefined Answers property and link it to the Action created in step 1
Now when you launch the workflow the action will be called by vRO, running the REST operation and populating the list of values for the workflow input parameter. You can perform these steps with multiple input parameters and REST operations, just create new actions for each REST operation and link them to individual input parameters e.g. one action and input parameter for Services, and one for Service Groups.
Whilst this article was created for a much earlier version of vRO the process to link the action to an input parameter is still valid and it is worth reading to understand how it works, the vCO Workflow Presentation section in particular will guide you through the configuration. https://www.vcoteam.info/articles/learn-vco/290-dynamic-input-values-based-on-other-inputs.html
Only a guess. Did you already verify that no other VMkernel port group has vMotion (accidentally) enabled in its settings (e.g. the "Management Network")?
André
Well, what you said is correct only when the vCenter server instance is added in so called 'shared session' mode.
The 'Add a vCenter Server instance' workflow provides an option to select also another mode - 'session per user' - in which case the credentials supplied in the workflow will be used only for registration purposes, but when later you perform another operation that calls vCenter API, the call will be made using the account of the current user. For example, if you login to vRO Java client with user@domain.com account and run some vCenter-related workflow like 'Rename VM', the operation on the vCenter will be invoked using user@domain.com account and not the account you supplied earlier in the workflow 'Add a vCenter Server instance'.
Hi,
To login in vRO Control Center, you have to use root account, not an account from the configured admin group.
Thanks for your reply. Does the below image depict where you would expect to set the virtual hardware version? If so, this is where I am unable to select 3.0. Please note that a second VM on the same host is able to select USB 3.0. The second image is WIn7 and was created some time ago in VMWare Workstation Pro 11.
If I'm not looking in the correct place, could you please assist me in finding where the correct spot to look would be.
Cheers, Owen
I installed a windows server 2016 on ESXi 6.7U2 using most of the defaults, including Secure boot with the intention of installing View Composer 7.9. In order to complete the install I had to turn off Secure Boot, install and then turn it back on. during a composer operation, I get Disk Fault errors. After looking at the UFA log and seeing issues with the creation of the disk, spindle.... I made a guess that it was related to secure boot. Turned it off on the composer server and everything works properly.
Ok, so what is the function of the admin group you have yo configure in the authentication provider wizard ?
The last upgrade I worked on was going from 5.1 to 6.5, where we upgraded to 5.5 first, then jumped straight to 6.5. This was in order, doing the vCenter first, then the hosts using the VUM on the newly migrated/upgraded vCenter Server. This next environment is currently running Windows vCenter Server 6.0.0 (6.0U2) with the hosts we have running at 5.1.0 (5.1 Patch 9).
The plan here is to get everything to 6.5, which means migrating and upgrading this vCenter Server to the appliance, as well, then upgrading the hosts to match. It seems better to take a different approach where rather than going from 5.1 to 5.5 to 6.5, we'll go from 5.1 to 6.0 to 6.5, considering the vCenter is already at 6.0.0.
Another difference between these environments is that these hosts are currently running their hypervisors from an SDHC card. We bought 32GB cards, but a teammate went out of order and manually upgraded one of the 2 hosts we have to 6.5 independently on a 32GB card. When learning of the premature jump, we decided to remount the 4GB SD card with the 5.1 system into the machineso we could pull the host back into the cluster and do the vCenter upgrade first, and use the VUM to perform the upgrade of the hosts.
The concern here is SD card space. Will the 4GB card be sufficient? For how long? Can it be upgraded somehow to a bigger card later without significant issues? I understand the minimum requirement is a 1GB card for ESXi 6.5, but what are best practices for upgrading, especially when using VUM from the VCSA (assuming it was upgraded successfully) and a 4GB card already loaded with 5.1? It's a rather tiny environment with only 2 hosts at this time, and about 7 running VMs (will be 8, with the VCSA completed). I've run into issues with ramdisk when upgrading on local datastores, and I've never done this with a host running ESXi from an SD card, so I would like to have some expectations and requirements, given the above information. Thanks, in advance.
Hi,
I'm dry studying VMware HCX and have tried getting a quick feature overview with comparison to vSphere mobility options (see sheet). Replicated Assisted vMotion (RAV) is a vSphere 6 vMotion enhancement. Transition overlay networks and proximity routing are HCX-only techniques for HCX RAV, right? Is it a requirement for HCX OS Assisted Migration?
--Daniel
Members of the admin group will have administrator privileges in vRO. That is, they will have full access to vRO features / content, and will be able to set permissions that control access to features / content for other users / groups.
No, same issue as reported, even if VMtools are up to date but you have set to check at reboot and you install the KB mention in this chain it gets uninstalled and network gone.