vCenter

If during the registration of a vCenter system you get a red line stating: "com.integrien.alive.common.security.ExpiredCertificateException" you most likely have an expired certificate on your vCenter server. Easiest to validate is point your browser to https://vcenterNameOrIP and then view the certificate.

Fix it by following version depending VMware process to replace vCenter Server certificate.

When an ESXi host in version 5.x or higher is managed by a virtual center it's management capabilities are limited to prevent damage to the virtual machines. One scenario which can become a big deal is however if your vCenter Server runs out of storage, which means you can not extend the storage that easily.

If you are really sure that you want to override this behavior here are the necessary steps, this will ensure you can later easily reconnect to the vCenter Server:

Especially in a growing environment you will identify a performance degrade on the MS SQL Server after some time.

There is an easy way to setup the most common jobs in a simple weekly maintenance plan.

Please login to the MS SQL Server serving your vCenter Server, or directly onto the vCenter Server if you use an internal database server.

After a restart of our vCloud Director we had found out that it had a problem connecting to the vCenter proxy service. Researching the problem with the VMware vCloud team identified a potential lock/db cras of the quartz database as the reason. The following procedure helps you identify and fix the scenario.

Please note that this is not an official VMware KB article, so you might open a SR with VMware first.

None of the cells have a vCenter Proxy service running