I would like to install the vSphere Update Manager on a Windows Server 2008 R2 machine. The R2 is 64bit OS, but the Update manager needs a 32 bit version of ODBCAD. The vCenter Server located on the same machine, and I have already configured both ODBC DSN.
In my previous article I wrote about the problems during logging in to a vCenter Server. The fully automated script disconnecting phase was a little bit problematic. Here is my solution.
If you want to save time, you will need to automatize. A lot of automation tools available provided by the VMware, such as the vCLI and vMA, but if you came from the Microsoft side, your choice will be the PowerCLI, because it provides a Windows PowerShell interface.
In the case when you don’t have enough hardware to test ESXi environment there is a chance to run virtual ESX(i) environment on ESX or ESXi . Obviously in this case the performance of the virtual ESX(i) environment won’t be ideal therefore the primary function for this environment is for testing functions.
When you see the error below, you can bet that something is wrong with your Orchestrator’s vCenter Server connection configuration:
Without the Inventory view, you cannot configure several elements of the workflows, execute them, etc. So we need to fix this.
According to the following KB article: http://kb.vmware.com/kb/1017516 the rootcause can be the wrong format of the username you set on the Orchestrator’s connection properties tab. Currently it is not supported to use the domain name\username combination, even if the vCenter server is a member of a domain.
But you can also get the error above when the certificate is not properly configured on the Orchestrator Configuration website.
The Orchestrator Configuration website’s password is something similar to the one you use for Active Directory Restore Mode. You don’t use it everyday but when you need it, you need it badly.
In case you forgot the password for the Configuration website, do the following:
If you have to maintain a large VMware vSphere farm, sooner or later you will realize that the number of the requested Virtual Machines are constantly growing from day to day. And the worst thing is that these requests are usually come via mails or from your supervisor directly (“George from the Developers team needs a new server, could you please support him”). Wouldn’t be nice to automate (and control) these request with pre-defined workflows and a provide a web-based form for the VM ordering?
VMware offers the vCenter Lab Manager (http://bit.ly/f3MLYA) for scenarios like this, but the vCenter Orchestrator 4.1 (http://bit.ly/ge3fo2) provides even more. It gives you total freedom, you can create your own workflows and automate your daily tasks within your Cloud. It comes with the vCenter Server, so when you install vCenter, you install Orchestrator as well in the background.