So far, we’ve created our tenant and we got the tenant setup with Active Directory authentication. The next step we want to take is to create a vSphere endpoint that will allow vRealize Automation to communicate with the vSphere environment and discover compute resources, collect data, and provision machines. To begin, we must first login to our tenant as a IaaS administrator. Once we have done that, we want to navigate to Infrastructure > Credentials to enter in the credentials that the endpoint will use to login in order to see the available resources. Click New.
After the initial deployment of your vCenter Server Appliance and Platform Services Controller, one of the first things that you want to do if you are using Active Directory is to join your PSC to the domain. In this blog post we are going to walk through doing just that. Like Active Directory domain controllers, the PSC really depends on time being synchronized within your network. The easiest thing to do would be to point all of your devices to the same NTP source. So before beginning, make sure the time is the same on all your devices. Once you have verified that, log into the PSC web UI as the admin account.
I’ve really come to appreciate more and more the VCSA. One of the times that I really appreciate it, is when it’s time to apply patches/updates to it. This post is just a simple….and I do mean simple…look at how to update your external PSC and then your VCSA when there’s a new update from VMware.
First things first….make sure you have a good backup of your VCSA and PSC. Also I recommend taking a snapshot of your PSC and VCSA but without preserving the VM’s memory state.
Then login into your PSC using the root account at https:// <FQDN or IP of appliance>:5480. Once logged in, go under the Update section.
After much feedback and success coming from the ESXi Embedded Host Client, VMware Labs has decided to release a HTML5 Web Client Fling. The web client in itself is packed with a lot of features, so this first release will only have some of the more common features and actions that are used.
Here are a list of the features/workflows that are available in this release:
- VM Power Operations (common cases)
- VM Edit Settings (simple CPU, Memory, Disk changes)
- VM Console
- VM and Host Summary pages
- VM Migration (only to a Host)
- Clone to Template/VM
- Create VM on a Host (limited)
- Additional monitoring views (Performance charts, Tasks, Events)
- Global Views (Recent tasks, Alarm-view only)
The web client fling has been packaged as a OVA file, so it can be easily deployed within your existing vSphere 6.0 environments.
- 2 vCPU, 4 GB RAM, 14 GB
- vCenter 6.0 installation (VCSA or Windows). The H5 client appliance will need 4 GB RAM, 2 vCPUs and the hard disk will grow up to 14 GB.
- Recommended browsers – Chrome, Firefox, IE11. Others may work, with some functional or layout issues. Window vCenter: Was tested with a vCenter on Windows Server 2012 R2, but should work with other versions as well.
Since these are the early stages of this Fling, VMware is seeking feedback from customers using it. Check out the VMTN page to give your feedback. Also you can share your thoughts on social media using #h5client.
So, I was rebuilding my lab yesterday…getting ready to begin studying for the VCAP exams…and after building the vCenter server, I go to log in for the first time and get this…
Now I just know that I’m typing in the password correctly. I mean, I did just make it 10 minutes prior to this! But whatever the case, I can’t get in. So now I need to reset the password on the SSO admin account. Here are the steps to do just that.