In part 3, we finished the setup of our appliance. But if we really want a polished installation we still have a “little” thing to do: replace the self-signed certificates by certificates signed by our internal Certificate Authority.
Let’s be honest: replacing certificates for the vSphere platform has always been a mess (to say the least) ! But thanks to the great work of Michael Webster and Derek Seaman, things got better! First, they produced clear procedures to replace the certificates. Then Derek went a step further and wrote a powershell script that automates the first part of the process (certificate generation).
In parallel, VMware greatly improved its own documentation (… maybe with the support of the two guys above ), and even has a tool which can update certificates on some VMware products… But not the vCSA!
Let’s sum it up: we are still waiting for the perfect tool, but in the meantime, there are clear (but lenghty ) procedures to update the certificates. And so… Let’s do it!
In Part 2, we left our vCSA in a running state, technically ready for managing ESXi servers in production. In a small environment or a test lab, we could stop there. But for an appliance that is going to manage a production virtual infrastructure, we could improve our setup a little bit.
In this article, we are going to configure an SMTP server and implement monitoring for the appliance’s database disk.
In the previous article we deployed the vCenter Server Appliance and made a basic setup. In this article, we will go a step further and cover the licensing and authentication for your new vCSA
I’m a huge fan of the vCSA (vCenter Server Appliance). Since version 5.5, I consider it suitable for production and will perfectly replace a manually installed Windows server. In fact, the Windows-version even looks like a dinosaur now :).
In this article, we are going to deploy a new virtual appliance on a standalone ESXi host and make the initial configuration.
Unless you want to implement Linked Mode, the vCenter Server Appliance (vCSA) is now really well suited for a production environment.
The installation of the appliance is pretty straightforward and will let you skip the lenghty installation of the Windows machine, the SQL server and all relevant vCenter components (Single Sign On, Inventory Service, vCenter…). You will get a vCenter up and running in a few minutes!
What about updating ? Well, it’s even easier than the installation! Let’s go through the process by updating our vCSA from 5.5 update 1 to 5.5 update 2 (it should work for any 5.x update also).