Getting started with the vCSA 6.x – Part 3


In part 1 and part 2 of this series about the vCSA, we have covered topics like; the shells, filesystem, services, health, logging, database and some extra tools. Recently I realised there a few more topics worth mentioning.

Appliance MUI

In pre 6.0 releases of the vCSA, there was a vCenter Server Appliance Management Interface, better known as the VAMI. This management interface is written in HTML5 and is now called the e Appliance Management User Interface (Appliance MUI).

You will find the new management interface in vCSA 6.0 and 6.5, however there are some differences.

You can login to this interface, using: https://<vCSA fqdn or IP>:5480. Us a local account such as the “root” account.

Fig. 1 – Summary vCSA 6.0.

Read the rest of this entry »

About update levels and build numbers (VMware)


You are working on a project, e.g. installing the latest VMware Horizon View on a vSphere 5.5 Platform. The VMware Product Interoperability Matrixes can help you determine which versions of ESXi are compatible with View.


This is not the best example, as this version of View runs on almost all version of ESXi, you might see the issue, as ESXi presents no update levels, just build numbers. So how do you match Update levels to Build numbers?

Read the rest of this entry »

VCAP5-DCA Objective 5.2 -Deploy and Manage complex Update Manager environments



  • Install and configure Update Manager Download Service
  • Configure a shared repository
  • Configure smart rebooting
  • Manually download updates to a repository
  • Perform orchestrated vSphere upgrades
  • Create and modify baseline groups
  • Troubleshoot Update Manager problem areas and issues
  • Generate database reports using MS Excel or MS SQL
  • Upgrade vApps using Update Manager
  • Utilize Update Manager PowerCLI to export baselines for testing
  • Utilize the Update Manager Utility to reconfigure vUM settings

Install and configure Update Manager Download Service

Official Documentation:
Installing and Administering VMware vSphere Update Manager 5.0, Chapter 9 “Installing, Setting Up, and Using Update Manager Download Service”, page 57.

Short Recap: Update Manager enables centralized, automated patch and version management for VMware vSphere and offers support for VMware ESX/ESXi hosts, virtual machines, and virtual appliances.
With Update Manager, you can perform the following tasks:

  • Upgrade and patch ESX/ESXi hosts.
  • Install and update third-party software on hosts.
  • Upgrade virtual machine hardware, VMware Tools, and virtual appliances.

Update Manager requires network connectivity with VMware vCenter Server. Each installation of Update Manager must be associated (registered) with a single vCenter Server instance. The Update Manager module consists of a plug-in that runs on the vSphere Client, and of a server component, which you can install either on the same computer as the vCenter Server system or on a different computer.

You can deploy Update Manager in a secured network without Internet access. In such a case, you can use the VMware vSphere Update Manager Download Service (UMDS) to download update metadata and update binaries.

Upgrading vSphere objects and applying patches or extensions with Update Manager is a multistage process

in which procedures must be performed in a particular order. VMware recommends following this procedure.

Read the rest of this entry »

Update Notice


I do like to keep my older post up-to-date (as long as it makes sense). For that reason these posts have been updated:

By the Way, per April 28th 2011, VMware hast just released Patch Release ESXi410-201104001 for ESXi 4.1. See this KB for more info.