VMware ESXi 8 has dropped the compatibility with a lot of old CPU models, a...
Spectre and Meltdown bugs seems something from the past (my last blog post...
RVTools 4.7.1 is a Windows .NET 4.7.2 application which uses VMware vSphere...
System virtualization remain the foundation of several datacenter infrastru...
In VMware Workstation 17.6.1, when I create a Rocky Linux VM, there is no w...
Veeam Backup & Replication 13, the next next major release, will be pro...
One year ago, Broadcom killed the Free vSphere Hypervisor, but now, with th...
Veeam Backup and Replication support PostgreSQL (only on Linux) using Appli...
CentOS Linux was a freely available, community-supported Linux distribution...
Sometimes you need to verify your security products to be sure that they ar...
Reading Time: 2 minutesThe vCenter Operations Manager 5.0 is a powerful tool for monitor a vSphere environment.
But, as writtent in the previous post, the software is distribuited using a vApp (with two VMs) that means the you need DRS if you deploy it on a VMware Cluster. Note that if you deploy it on a standalone ESXi host it does not require DRS.
So how deploy this vApp with a vSphere edition lower than the Enterprise edition?
The core of vCenter Operations Management is a vApp with two VMs:
Both must stay in the same network and on the same cluster. Really curios the choice of the OpenVPN to handle communications between the VM… Maybe there is some future plan to build a multi-tenant solution? Or simple a single UI with multiple collectors?
The installation is quite simple and is basically a OVF deployment. For more info see:
There are some points that you must check during or before the installation:
Note also that other suite components are different piece of software:
Reading Time: < 1 minuteThe vCenter Operations Management Suite is the product designed from VMware to monitor and manage a vSphere infrastructure (but not only).
Similar as other VMware products there are several editions (for a detailed overview see the comparison page):
Reading Time: 5 minutesFrom an initiative of Gregg Robertson, this is a short interview. The original page is at: VCDX Spotlight- Andrea Mauro
As most people I’ve started of course with VMware Workstation and honestly not with the ESX 1.0 (I remember that was not possible, at least in my Country) to have an evaluation or trial version.
My first virtualization project (for academic purposes) was building a virtual honeynet with Linux UML (it was the end of 2001). My first virtualization project based for a production system virtualization solution was instead with VMware ESX 2.5.
After that I’ve follow a lot of virtualization projects and I’ve started also to give some contribution to the VMTN Community (my nick is AndreTheGiant). This probably has open new perspectives, outside the limits of my Country and my native language (that isn’t English). For example, I’ve tried to applied with success to the VCDX3 path and also to vExpert 2010, 2011 and 2012.
Reading Time: < 1 minuteSome months ago I’ve wrote about a possible Storage vMotion issue with Symantec Backup Exec. Recently there were some cases where vCenter Server progress status is not correctly updated for a Backup Exec 2012 job (for example it remains fixed to 5% for some days).
This support page descrive a possible workaround solution:
Link collection of the precendent posts:
For previous upgrade paths see also:
In the previous post we have talk about the steps for a successful View 5.1 upgrade. Now let’s add some operative notes.
If you have already configure it in View 4.6 or 5.0 the setting and the schema will be maintained. So no extra effort is required.
The upgrade will begin like a new installation with some differences compared to previous version.
Some new windows during the installation are the warning for the certificates requirements and the data recovery password (the password is required when you restore the View LDAP configuration from a backup):
There is also the usual window about the firewall port and a new one about the User Experience Feedback:
As usually the upgrade is just a new reinstallation and a new paring password is required. But the external URL are maintained correctly. The only issue, is that, during the service restart you will loose the connection to the specific Secure Server.
As written in first post (VMware View 5.1 upgrade path – Check-list) starting from 5.1 the upgrade procedure will probably change.
The in-place upgrade is really simple (note that is still a 32 bit software) and works without issue. Also it can use the existing DB connection and existing certificate.
| Disclaimer & Copyright
