Reading Time: 3 minutes After updating the vCenter Server part to version 5.5, you can focus on the host part. The update of the ESXi host can be completed, as usual, in several ways: Manual update with the installation CD of ESXi (by selecting upgrade and keep VMFS datastore) Manual update using the CLI Automatic updating via vSphere Update Manager (VUM) There are other ways, all discussed in the VMware KB 2058352 (Methods for upgrading to ESXi 5.5).
Reading Time: 5 minutes The VMware vCenter upgrade has some possible issue, considering also that the SSO part is changed from the one implemented in vSphere 5.1. VMware has released the vSphere 5.5b (specifically for the vCenter Server application, both installable and vCSA editions) just before the Christmas holiday. Mostly another bunch of fixes around vCenter Single Sign-On functionality and upgrade errors, so be sure to use this one for the upgrade to reduce the possible issues. Note that most of the issues are related to the vCenter components:
Reading Time: 4 minutes The procedure for upgrade to VMware vSphere 5.1 is quite similar to the upgrade path to vSphere 5.1 (and almost similar also to the upgrade path to vSphere 5.0) and is well described in the specific guide (vSphere Upgrade Guide). And first to all, you have to analyze the pro and the cons of a product upgrade, for more information see also: VMware vSphere 5.5 – Upgrade or not upgrade? You have also to consider (particularly for small enviroment) if apply an upgrade or rebuild. Anyway, some points are quite common for each major vSphere […]
Reading Time: 4 minutes In the previous post we have talk about the VMware Horizon View Event database and how purge the old data in order to free some space. You can have similar issue also with the VMware vCenter Server database, considering that it can continuous grow due to the statistics and also due to the events/tasks. In really small system a simple solution could be re-install a fresh version of vCenter Server (maybe during an upgrade) and re-create all the configuration stored only in the vCenter Server database. But in several cases this approach is not realistic. […]
Reading Time: 3 minutes In an installation of VMware Horizon View one requirement is the VMware Composer database to keep track of the various pools with linked clones. But this is the only mandatory DB (if you have linked clones), because for the various View Connection Servers there isn’t any strictly database strictly requirement, since they exchange and share data via a specific data structure based on Active Directory Lightweight Mode (actually an LDAP tree replicated between each replication server). But in real scenario, it becomes useful, from the management point of view, set up a shared database for […]
Reading Time: 2 minutes One possible issue during an upgrade to VMware vSphere 5.1 or 5.5 (but also in a new installation) is related with the introduction of the the SSO (introduced in vSphere 5.1) component in vCenter Server that handle the authentication across the different vCenter Server components, but also against the users. In some cases you may have the following issues during the user autentication: You can log into vCenter Server 5.1 or 5.5 with the vSphere Client or vSphere Web Client only with local users Logging into vCenter Server 5.1 or 5.5 using the vSphere Client […]
Reading Time: 2 minutes In most cases (in small environment) a default installation of vCenter Server and its components could work. Considering that the default disk of Windows Server 2008 R2 and 2012 is 40 GB (at least in a VMware virtual environment) it can store all the installation without any directory changes. Except for the Upload Manager (VUM) that need a reasonable space for store the patches (usually not more than 20GB, but in some case also more, and the installer suggest at least a 120 GB disk). If you forget to change the patches directory during the […]
| Disclaimer & Copyright
