I. vSphere 6.5 Release -What Is New?
vSphere 6.5- Technical Overview
1. ESXI Virtual Server
2. Vcenter Server
*Improved Appliance Management
*VMware Update Manager
*Native High Availability
*Built-in Backup / Restore
Performance Improvement in both vSphere Web Client and
fully supported HTML5-based vSphere Client.
*vCenter Server Appliance built in installer Migration Tool.
*Migration Tool has several improvements over the recently released vSphere 6.0 Update 2m release.
Supported on Windows vCenter Server 5.5 and 6.0
( If you’re currently running a Windows vCenter Server 6.0, this is your chance to get to the vCenter Server Appliance using this Migration Tool. )
The Migration tool which allows for more granular selection of migrated data as follows:
*Configuration, events, and tasks
*Configuration, events, tasks, and performance metrics
*VMware Update Manager (VUM) is now part of the vCenter Server Appliance.
*Vcenter Inventory, and alarm data is migrated by default.
This will be huge for customers who have been waiting to migrate to the vCenter Server Appliance without managing a separate Windows server for VUM.
If you’ve already migrated to the vCenter Server Appliance 6.0 the upgrade process will migrate your VUM baselines and updates to the vCenter Server Appliance 6.5.
*Improved Appliance Management
Another exclusive feature of the vCenter Server Appliance 6.5 is the improved appliance management capabilities. The vCenter Server Appliance Management Interface continues its evolution and exposes additional health and configurations. This simple user interface now shows Network and Database statistics, disk space, and health in addition to CPU and memory statistics which reduces the reliance on using a command line interface for simple monitoring and operational tasks.
*vCenter Server High Availability
*Active, Passive, and Witness nodes which are cloned from the existing vCenter Server.
*Failover within the vCenter HA cluster can occur when an entire node is lost (host failure for example) or when certain key services failures.
*vCenter Server 6.5 has a new native high availability solution that is available exclusively for the vCenter Server Appliance.
Backup and Restore
*Built-in backup and restore for the vCenter Server Appliance.
*Running embedded with the appliance.
*This new out-of-the-box functionality enables customers to backup vCenter Server and Platform Services Controller appliances directly from the VAMI or API, and also backs up both VUM and Auto Deploy.
vSphere Web Client
*Support based on the Adobe Flex platform and requires Adobe Flash.
*HTML5-based vSphere Client:
*Inventory tree is the default view
*Home screen reorganized
*Renamed “Manage” tab to “Configure”
*Removed “Related Objects” tab
*Performance improvements (VM Rollup at 5000 instead of 50 VMs)
*Live refresh for power states, tasks, and more!
*Supported version of the HTML5-based vSphere Client
*Built in vSphere Client is built with vCenter Server 6.5 (both Windows and Appliance)
*Clean, consistent UI built on VMware’s new Clarity UI standards
*Built on HTML5 so it is truly a cross-browser and cross-platform application
*No browser plugins to install/manage
*Integrated into vCenter Server for 6.5 and fully supported
*Fully supports Enhanced Linked Mode
*Users of the Fling have been extremely positive about its performance
3. Auto deploy
Auto Deploy 6.5 GUI Configuration. We will now walk through the new Auto Deploy GUI and create a custom ESXi image with deploy rules to boot ESXi hosts.
II.vSphere 6 Release-What Is New?
*Increase ESXi Host Configuration Maximums
*Virtual Hardware Upgrades
*Improved ESXi account and password management
*Auditability of ESXi admin actions.
Virtual Machine Compatibility Level with ESXi 6.0
*VNUMA virtual machine with the hot-add memory option without requiring any downtime.
*VDDM 1.1 GDI Acceleration helps reduce memory footprint. For example, Windows Manager compositing engine no longer needs to keep a system memory copy of all surfaces used by GDI/GDI+ ; WDM 11. is supported on Windows 7 and above.
*USB 3.0 x HCI supported; allows USB devices to run at full speed.
*Serial and Parallel Port Enhancements leverages vHW11 32 serial support.
ESXi Account Management
vSphere 6.0 provided enhanced capabilities for :
*Management of local users and permissions
*Easier compliance to local security policies
*Control of user access and privileges for ESXi
VMware ESXI 6.0 Single Host
Vsphere 6 Enhanced User Interface – Web Client is more responsive, more intuitive, and more streamlined than ever before.
Vsphere Hypervisor Enhancements:
VMware ESXi™ 6.0 has dramatically increased the scalability of the platform. With vSphere Hypervisor 6.0, clusters can scale to as many as 64 hosts, up from 32 in previous releases. With 64 hosts in a cluster, vSphere 6.0 can support 8,000 virtual machines in a single cluster. This enables greater consolidation ratios, more efficient use of VMware vSphere Distributed Resource Scheduler™ (vSphere DRS), and fewer clusters that must be separately managed.
Each vSphere Hypervisor 6.0 instance can support as many as 480 physical CPUs, 12TB of RAM, and 1,000 virtual machines. By leveraging the newest hardware advances, ESXi 6.0 enables the virtualization of applications that were once thought to be nonvirtualizable.
Here is comparison between 5.5 and 6.0 version.
ESXi Security Enhancements
ESXi 6.0 enables management of local accounts on the ESXi server, using new ESXCLI commands. The ability to add, list, remove, and modify accounts across all hosts in a cluster can be centrally managed using a vCenter Server system. Previously, the account and permission management functionality for ESXi hosts was available only with direct host connections. Setting, removing, and listing local permissions on ESXi servers can also be centrally managed.
There are two new settings available in ESXi Host Advanced System Settings for the management of
local account failed login attempts and account lockout duration. These parameters affect SSH and
Services connections but not DCUI and console shell access.
Password Complexity Rules
In previous versions of ESXi, password complexity changes had to be made by hand-editing the
/etc/pam.d/ passwd file on each ESXi host. In vSphere 6.0, this has been moved to an entry in Host
Advanced System Settings, enabling centrally managed setting changes for all hosts in a cluster.
Prior to vSphere 6.0, actions at the vCenter Server level by a named user appeared in ESXi logs with the “vpxuser” username—for example, [user=vpxuser].
In vSphere 6.0, all actions at the vCenter Server level against an ESXi server appear in the ESXi logs with the vCenter Server username—for example, [user=vpxuser:DOMAIN\User].
This provides a better audit trail of actions that were run on a vCenter Server instance that conducted corresponding tasks on the ESXi hosts.
Flexible Lockdown Modes
Prior to vSphere 6.0, there was one lockdown mode. Feedback from customers indicated that this lockdown mode was inflexible in some use cases. With vSphere 6.0, the introduction of two lockdown modes aims to improve that.
The first mode is “normal lockdown mode.” The DCUI access is not stopped, and users on the “DCUI.Access” list can access DCUI.
The second mode is “strict lockdown mode.” In this mode, DCUI is stopped.
There is also a new functionality called “Exception Users.” These are local accounts or Microsoft
Active Directory accounts with permissions defined locally on the host where these users have host
access. These Exception Users are not recommended for general user accounts but are recommended for
use by third-party applications—“Service Accounts,” for example—that need host access when either
normal or strict lockdown mode is enabled. Permissions on these accounts should be set to the bare
minimum required for the application to do its task and with an account that needs only read-only
permissions to the ESXi host.
Smart Card Authentication to DCUI
This functionality is for U.S. federal customers only. It enables DCUI login access using a Common
(CAC) and Personal Identity Verification (PIV). An ESXi host must be part of an Active Directory
Expanded Support – Expanded support for the latest x86 chip sets, devices, drivers, and guest operating systems. For a complete list of guest operating systems supported, see the VMware Compatibility Guid
Amazing Graphics – NVIDIA GRID™ vGPU™ delivers the full benefits of NVIDIA hardware-accelerated graphics to virtualized solutions.
Instant Clone* – Technology, built in vSphere 6.0, that lays that foundation to rapidly clone and deploy virtual machines, as much as 10x faster than what is currently possible today.
Transform Storage for your Virtual Machines – vSphere Virtual Volumes* enables your external storage arrays to become VM-aware. Storage Policy-Based Management (SPBM) allows common management across storage tiers and dynamic storage class of service automation. Together they enable exact combinations of data services (such as clones and snapshots) to be instantiated more efficiently on a per VM basis.
Network IO Control – New support for per-VM Distributed vSwitch bandwidth reservations to guarantee isolation and enforce limits on bandwidth.
Multicast Snooping – Supports IGMP snooping for IPv4 packet and MLD snooping for IPv6 packets in VDS. Improves performance and scale with multicast traffic.
Multiple TCP/IP stack for vMotion – Allows vMotion traffic a dedicated networking stack. Simplifies IP address management with a dedicated default gateway for vMotion traffic.
vMotion Enhancements – Perform non-disruptive live migration of workloads across distributed switches and vCenter Servers and over distances of up to 100ms RTT. The astonishing 10x increase in RTT offered in long-distance vMotion now makes it possible for data centers physically located in New York and London to migrate live workloads between one another.
Replication-Assisted vMotion – Enables customers, with active-active replication set up between two sites, to perform a more efficient vMotion resulting in huge time and resource savings – as much as 95 percent more efficient depending on the size of the data.
Fault Tolerance (up to 4-vCPUs) – Expanded support for softwarebased fault tolerance for workloads with up to 4 virtual CPU
Content Library – Centralized repository that provides simple and effective management for content including virtual machine templates, ISO images and scripts. With vSphere Content Library, it is now possible to store and manage content from a central location and share through a publish/subscribe model.
Enhanced User Interface – Web Client is more responsive, more intuitive, and more streamlined than ever before.
Cross-vCenter Clone and Migration – Copy and move virtual machines between hosts on different vCenter Servers in a single action.
Vcenter Server Enhancements Vcenter Server Architecture Changes
Vcenter Server 6.0 simplifies planning and deployment by offering two deployment models.
The first, embedded, deploys the new Platform Services Controller (PSC) and the vCenter Server system on the same machine.
The second, external, deploys the PSC and the vCenter Server instance on separate machines.
All vCenter Server services—such as VMware vCenter™ Inventory Service, VMware vSphere Web Client, auto deploy, and so on—are installed along with vCenter Server. There are no longer separate installers for these components, simplifying the architecture by combining functions onto a single machine. VMware vSphere Update Manager™ remains as a standalone Microsoft Windows installation.
Vsphere 6 Release -What Is New?
vSphere 6.0 Web Client: Still Flash, But Vastly Better User Experience
Vsphere 6 Upgrade Path and Options.
Before you begin, make sure that you read the vSphere 6 upgrade guide, the vSphere 6 release notes, the Hardware and Guest OS Compatibility Guide and the Product Interoperability Matrix from VMware before you start the upgrade process. Also, make sure your environment meets the software and hardware requirements as described in the upgrade guide.
Since the vSphere 6 introduces the VMware Platform Services Controller, you should have a look at the vCenter Server upgrade path example as described in the upgrade guide to fully understand the changes in your environment after the upgrade for vSphere 6. For example: I am running a simple installation of the vCenter Server (Inventory Service, Web Client, Single Sign-On) on a Windows Server 2008 R2 virtual machine with Update Manager, Auto Deploy, Dump Collector, Syslog and a Microsoft SQL Server 2008 R2 Express. So according to the upgrade guide, my new vCenter Server infrastructure.
The upgrade of your environment to VMware vSphere 6.0 is performed in a phased manner. The components that are upgraded in earlier phases are fully compatible with components whose upgrades have not yet occurred. – See more at: http://www.vmware.com/products/vsphere/upgrade-center/upgrade.html#sthash.zcolKAMA.dpuf
1vCenter Server 5.5 to 6.0 Upgrade on Windows with Embedded Platform Services Controller
2vCenter Server Appliance 5.5 to 6.0 Upgrade with Embedded Platform Services Controller
3vCenter Server 5.5 SSO-HA Upgrade to vCenter Server 6 PSC
4vCenter Server 5.5 to 6.0 Upgrade with External SSOVsphere 6 Suite Features and Limitation
Long Distance vMotion, Cross vSwitch and vCenter vMotion
vMotion of MSCS VMs using pRDMs
vMotion now can be routed (L3)
Fault Tolerance of VMs with upto 4vCPU (Network Constraints min 1GbE/CPU still apply)
Content Library (Replicate templates, ISO etc across multiple vCenters)
NFS 4.1 support
Instant Clone (aka VMFork)
vSphere HA Component Protection
Storage DRS and SRM support
Network IO Control per VM reservations
Storage IOPS reservations
Platform Services Controller architecture for vCenter – for SSO , licensing and integrated Certificate Authority
Linked Mode support for vCenter Server Appliance
64 hosts per cluster
8000 VMs per cluster
480 CPUs per host
12TB of memory
1000 VMs per host
128 vCPUs per VM
4TB RAM per VM
Compression of replication traffic configurable per VM
Isolation of vSphere Replication host traffic
vSphere Data Protection now includes all vSphere Data Protection Advanced functionality
Up to 8TB of deduped data per VDP Appliance
Up to 800 VMs per VDP Appliance
Application level backup and restore of SQL Server, Exchange, SharePoint
Replication to other VDP Appliances and EMC Avamar
Data Domain support
Planning for the Upgrade:If you are planning for an upgrade, the first thing you have to do is ensure that there is product interoperability with all the third party tools and plugins that you use everyday. If you are confident that its going to be OK, this is how to plan for it. Ensure you plan and test this on a non-production environment. Stress test the new environment with application VMs and other tests that you generally perform on a green fields environment. Write out your plan. My plan (for my lab is as below)Plan out your SSO deployment model and how to upgrade to the new PSC model. (Always deploy PSC in a HA mode with multiple VMs. It has inbuilt replication and so you don’t have to setup anything for it ).
Snapshot your SSO Server and then Install the new PSC (Platform Services Console) and ensure that SSO and licensing of the existing environment is migrated over. Once everything works, don’t forget to delete that snapshot.
Snapshot the vCenter Server (including the SQL Server and the vCenter DB) and upgrade the components of the Management Platform (vCenter, VUM etc). Delete Snapshot again.
Ensure all the licensing is intact and that you can login with the required permissions. This is paramount to test this as you don’t want to upgrade and then realise that it needs newer permissions etc.
Upgrade your hosts one by one using VUM update.
Test out each of the new features that you want to use in your environment.
Document everything I mean everything this way you can run through all the tests you’ve done and repeat any with less than satisfactory results.
Test all the failed tests after all the components have been upgraded. If it still fails the test, if you have VMware Support for your non-production licenses then log a case with VMware Support.
Once resolved, re-run your tests until all of them are successful.
Great Video on Vsphere 6 Upgrade Options.
How To Upgrade To Vsphere 6 From A Command Line
Vsphere 6 Upgrade Path and Options.
Vsphere 6 Upgrade Methods
VMware Vsphere 6.0- All About Vsphere 6. This page is dedicate for ESXI, Vcenter, Vcenter Update Manager and Other Vsphere 6 Products.
Vsphere 6.0 was released 03/12/2015
Check it out —> http://www.Vmwmare.com
Vsphere 6 Lab Tutorial – Awesome Video.
How to build your awesome virtualization home lab with VMware vSphere 6.0 (ESXi & vCSA)
ESXI 6.0 Single Host Installation
Step 2. ESXI 6 Installer Loading
Step 3. ESXI 6 Installer Loading Modules..
Step 4. ESXI 6.0 Installer HCL Welcome Page.-Click Continue.
Step 5. ESXI 6.0 Installer EULA.-Click F11 To Accept and Continue
Step 6. Select VMFS partition -Local- Press Enter to Continue.
Step 7. Select Keyboard Layout- Default US.-Press Enter to Continue.
Step 8. Enter a root password- and Press Enter to Continue.
Step 9. Installing ESXI 6.0.0 ..
Step 10-ESXI 6.0 Installation Complete.
Step 11.-ESXI Single Host Installation
Vsphere Client Download from newly ESXI 6.0 Build.
Step 1. Go to the ESXI host Address. i.e via web browser —->
http://<ESXI FQDN or IP Addresss>
Step 2. Click on Download vSphere Client for Windows.
Step 3. Run Vsphere Client.exe after complete download from web browser.
Step 4. Click Next To Continue Vsphere Client 6.0
Step 7. Click Finish to Complete Vsphere Client 6.0 Installation.
Step 8. Log into Newly ESXI 6.0 Via Vsphere Client 6.0
This page will illustrate All about Vsphere Version 5.1- ESXI, Vcenter and Vcenter Update Manager Installation and Configuration. .
1. How to Configure Vnetwork Standard Switch on ESXI.
*For more information on Virtual Networking and Virtual Switch- Reference VMware Virtual Infrastructure Section Virtual Network and Switches.
ESXI Default Standard Virtual Switch Configuration
Great VMware Learning -Configuring vNetwork Standard Switch Video
Standard Switch:Vswitch0 Configuration Steps
Setting Up vSphere Networking with vSphere Standard Switches
This document is targeted installation of VMware ESXI 5.x. The purpose and scope illustrate VMware vSphere ESXI 5.0 Installation and Configuration on Vmware Workstation 10.
*Typical you would do the same with server/blade hardware. This document will not cover Blade or Server Hardware Installation.
*For ESXI Installation illustration, will leverage VMware Workstation 10
VMware ESXI 5.0 and up ISO.
1.1 Open Vmware Workstation–> New Virtual Machine.
1.1.1 New Virtual Workstation
1.1.2 Mount ESXI 5.X ISO to CD under Installer Disc/Installer disc (DownLoad from http://www. Vmware.com)
1.1.3 Choice the default configuration and Finish to start ESXI Installation.
1.1.4 We will provide illustration of the a graphical installation steps for Vmware ESXI 5..1:
1.5 Press F11 to accept VMware End User License Agreement.
1.6 ESXI Installer will scan for Installation location.
1.7 Press Enter to choice the default location of the ESXI Installation Location: Default Local, Custom: Remote(none).
1.8 Select keyboard Layout: Default US, and press enter to continue with installation.
1.9. Prompt to input the Root password.
2.0. System will scan and prompt
2.1 Confirm Installation by press F11(Install).
2.2 Installation Status with percentage completion displayed.
2.3 ESXI has been successfully installed . Press Enter to reboot to complete installation
2.4 Rebooting Server Prompt to complete ESXI Installation.
2.5 ESXI Loading .. to boot to newly ESXI Installation.
2.6. ESXI Installation will automatically set to DHCP.
3.0 Set ESXI to Static IP address.
*Prerequisite reserve a static IP address from local Bind or AD DNS server.
3.1 Press F2 to log into newly ESXI Host . User ID Root and Password (set during installation- section 1.9 ESXI Installation, set root password)
3.2 Select Configuration Management Network Option to set ESXI IP to Static Addressing. –
3.3 Select IP Configuration Option to set ESXI IP to Static Addressing
3.4 Select Set Static IP address and network configuration:
3.5 Press Enter to continue newly IP address changes.
3.6 You will get take back to IP Configuration Screen and set the new IP address been set.
3.7. Press ESC to Exit screen to complete changes.
3.8 Select Y to apply changes and restart management network.
3.9 Press ESC to log off ESXI Host. You should see the Static IP address illustrate at ESXI Main Screen.
In next ESX Installation postings , we will incorporate adding Data store and Creating New VM host on stand alone ESXI Host.
4.1 Vsphere ESXI .5.1
4.2 ESXI 5.X Installation Guide
ESXI Upgrade/Migration Paths – Single and Enterprise Approach.
ESXI Single Host Upgrade Great Tutorial Video-
*How to Install Vcenter.
*How to Configuration-ESXI, and Vcenter,
*How To Security-ESXI , and Vcenter
I. Title: Installing and Configuration of VMware Vcenter 5.5.
- Scope of Document :Installation of Vmware Vcenter Server, Update Manager, and Inventory Services, SSO and Web Client.
2. Step by Step Vcenter 5.5 Installation and Configuration.
II. Title: Deploy and Configure Vcenter Server Appliance 5.5-
- Scope of Document The scope of the document illustrate deploy, install and configure Vmware Vcenter Server Appliance
- Prerequisite Requirement
VMware-vCenter-Server-Appliance-220.127.116.1101-1398493_OVF10 vCenter Server Appliance 5.5.x:
- At least 70 GB
- A maximum of 125 GB
|vCenter Server Appliance Hardware||Tomcat||Query Service (QS)||Policy Based Storage Management (SPS)|
|Small inventory (1-100 hosts or 1-1000 virtual machines)||512 MB||3 GB||1 GB|
|Medium inventory (100-400 hosts or 1000-4000 virtual machines)||512 MB||6 GB||2 GB|
|Large inventory (more than 400 hosts or 4000 virtual machines)||1 GB||12 GB||4 GB|
Steps by Step- Deploying Vcenter 5.5 by OVA
Title :Interactive Installer Existing 5.1 Upgrading to ESXI to 5.5
Scope: ESXI Upgrade from 5.1 to 5.5 in preserving all configuration and settings from previous ESXI 5.1 Host Build Installation.
*ESXI 5.5 ISO
*Previous ESXI 5.1 Host Installation and Configuration.
Interactive Installer Existing 5.1 to Upgrading VSphere ESXI to 5.5 Step by Step Guide.
Upgrade or migrate interactively using an ESXi installer ISO image on CD/DVD or USB flash drive
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058352#Upgrade or migrate interactively using an ESXi installer ISO image on CD/DVD or USB flash drive
Vmware Vsphere vCenter 5.5 Install Guide On Windows 2012 R2.
This document is targeted installation of Vmwae Vsphere 5.5 vCenter Server.
The purpose and scope in implementing vCenter 5.5 Server to leverage
- Storage VMotion,
- VMware High Availability (VMHA),
- VMware Distributed Resource Scheduler (DRS).
1.2 Scope of the document:
Cover only Vcenter Server Core Installation.
- Download VMware-VIMSetup-all-5.5.0-1378901-20131001 from VMware download
- Windows 2012 R2 OS
- Min CPU, RAM and Disk requirements
- CPU x 2, RAM 2G to 4G, and Disk 50 G
- vcenter Host DNS -FQDN and AD Membership Registered to both AD and DNS. i.e
VMware Vsphere vCenter 5.5 Install Guide On Windows 2012 R2-Click Here Download
1.1 Add ESXI Host To Vcenter. Vsphere Web and Fat Client.
Scope: this section will illustrate procedures adding ESXI Host to the Vcenter in both Web vsphere Client and Fat Client..
VMware Vsphere Adding ESXI Host To Vcenter-Web and Fat vSphere Client. Click Here To Download.
VMware Update Manager 5.5 Standalone Installation
*The section will illustrate on how to install stand-alone VMware Update Manager because resource constraints having everyone on Vcenter host or Vcenter is an Appliance.
Installation steps for vSphere Update Manager 5.5
- Mount the vSphere 5.5 installation media. The installation wizard appears.
- In the left pane, under VMware vCenter Support Tools, click vSphere Update Manager and then click Install.Note: If any of the prerequisites are not met, they are listed in the right pane under Prerequisites.
- Select the appropriate language from the dropdown and click OK.
- In the welcome screen, click Next.
- Review the End User License Agreement. If you agree, select the I accept the terms in the license agreement option and click Next.
- Optionally, select the Download updates from default sources immediately after installation option and click Next.
Note: This option automatically checks for downloading updates. If you want to review the default download sources or configure vSphere Update Manager to use a shared repository, deselect this option.
*check download updae from default source immediately after installation.
- Enter the vCenter Server URL and a username and password and then click Next.
Note: Ensure that the username entered has a minimum of Register extension privilege to be able to register vSphere Update Manager with vCenter Server.
- Select the database solution for vSphere Update Manager and then click Next.You can use one of these options for the database:
- Install a Microsoft SQL Server 2008 Express instance.
- Use an existing supported database.To use an existing supported database, select the Data Source Name (DSN) from the dropdown.Note: For information about specific database versions and service pack configurations supported with vCenter Server 5.5, see the VMware Product Interoperability Matrixes.
- Optionally, from the dropdown, select either the IP address or the Fully Qualified Domain Name (FQDN) of vSphere Update Manager and then click Next.
Note: Ensure that vCenter Server and the ESXi/ESX hosts can resolve the vSphere Update Manager.
- In the dialog that appears, check if the alternative TCP port numbers for the SOAP, Web, and SSL ports of vCenter Server appear and then click Next.Note: These field are automatically populated with the appropriate URL and port numbers if the service is installed in the current system. The default ports are 8084, 9084, and 9087 respectively.
- Optionally, select the Yes, I have Internet connection and I want to configure proxy settings now option and click Next.
- Provide the proxy server address and the proxy server port and then click Next.
- Optionally, select the Authenticate proxy using the credentials below option if your proxy server requires authentication and then click Next.
- Optionally, provide an alternative installation location and then click Next.Notes:
- The path must conform to NTFS naming restrictions. For more information, see the Microsoft TechNet article Naming Files, Paths, and Namespaces.
- The installation requires 120 GB of disk space to be available. For more information, see the Update Manager Hardware Requirements section in the Installing and Administering VMware vSphere Update Manager Guide.
- If the current system does not have 120 GB of disk space available, a warning is displayed when you click Next. Click OK to acknowledge the warning.
- In the Ready to Install screen, click Install to start the installation.
- When the installation completes, click Finish.
Post installation of vSphere Update Manager 5.5
VMware Update Manager Tab-Should appeared Already on Vcenter- You should see Update Manager Tab on the Vcenter.
Also confirm if Plug in is enabled. Menu —–>Plug-ins
After installing vSphere Update Manager 5.5:
- Perform a complete backup of the upgraded vSphere system and create a regular backup schedule.
- Install the Update Manager Client Plug-In for the vSphere Client. For more information, see the Install the Update Manager Client Plug-In section in the Installing and Administering VMware vSphere Update Manager Guide.
- Enable the Update Manager Web Client Plug-In. For more information, see Enable the Update Manager Web Client Plug-In section in the Installing and Administering VMware vSphere Update Manager Guide.