KB: Troubleshooting a black screen when logging into a Horizon View virtual desktop using PCoIP (1028332)

Troubleshooting a black screen when logging into a Horizon View virtual desktop using PCoIP (1028332)

Symptoms

• When attempting to connect to a Horizon View virtual machine using the PCoIP protocol, a black screen is displayed temporarily and the client disconnects. Connecting to the same virtual machine using RDP protocol is successful.
• Internal PCoIP connections may be successful, however connecting externally results in a black screen.
• Connections from a PCoIP Zero Client fail, but connecting using the Horizon View software client is successful.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028332

VMware NSX Manager 6.0.5 install

1. General error when deploy NSX manager ova on vcenter 5.5 web client 

2.  Search the error and read some vcenter logs but didn't get any related error

3. Deploy use vSphere C# client is working:

SW ,HW,OS Compatibility note

I am trying to gather links and resource in terms of checking Compatibility when design, deploy or upgrade...

The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products:
• VMware ESXi/ESX Server 3.0 and later
• VMware Workstation 6.0 and later
• VMware Fusion 2.0 and later
• VMware ACE 2.0 and later
• VMware Server 2.0 and later
http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf

VMware Compatibility Guide Portal:
VMware provides support only for the devices that are listed in this document

http://www.vmware.com/resources/compatibility/search.php

Correlating VMware products build numbers to update levels (1014508)

VMware vSphere and vCloud suite build numbers table

This table provides a list of all VMware vSphere and vCloud suite build numbers and release dates. The build numbers are based on full installations. Patching ESXi/ESX hosts increments the build number that shows in vCenter Server.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014508


Enhanced vMotion Compatibility (EVC) processor support (1003212)
For hosts in cluster with different version of CPU

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003212




IBM servers OS support
http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/nos/vmware.html

KB Datastore renaming fails when the Virtual Infrastructure Client is connected directly to ESX host (1004845)

Datastore renaming fails when the Virtual Infrastructure Client is connected directly to ESX host (1004845)

Details

When the Virtual Infrastructure (VI) Client is connected directly to an ESX host, renaming a datastore fails.

Solution

To rename the datastore:

1. Log in to the VirtualCenter Server using the Virtual Infrastructure Client.
2. Select Host > Configuration > Storage.
3. Right-click on the datastore and select Rename, or click the datastore name directly.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Vmware KB Testing VMkernel network connectivity with the vmkping command (1003728)

Testing VMkernel network connectivity with the vmkping command (1003728)

Purpose

For troubleshooting purposes, it may be necessary to test VMkernel network connectivity between ESX hosts in your environment.

This article provides you with the steps to perform a vmkping test between your ESX hosts.

Resolution

The vmkping command sources a ping from the local VMkernel port.

 

To initiate a vmkping test from the console of an ESX Server host:

1. Connect to the ESX/ESXi host using an SSH session. For information see Tech Support Mode for Emergency Support (1003677) andUsing Tech Support Mode in ESXi 4.1 and 5.0 (1017910).
   
2. In the command shell, run the command:
   
   # vmkping x.x.x.x
   where x.x.x.x is the hostname or IP address of the server that you want to ping.
   
3. If you have Jumbo Frames configured in your environment, run the vmkping command with the -s and -d options.
   
   # vmkping -d -s 8972 x.x.x.x
   Note: If you have more then one vmkernel port on the same network (such as a heartbeat vmkernel port for iSCSI) then all vmkernel ports on the host on the network would need to be configured with Jumbo Frames (MTU: 9000) too. If there are other vmkernel ports on the same network with a lower MTU then the vmkping command will fail with the -s 8972 option. Here in the command -d option sets DF (Don't Fragment) bit on the IPv4 packet.
   
   
4. In ESXi 5.1, you can specify which vmkernel port to use for outgoing ICMP traffic with the -I option:
   
   # vmkping -I vmkX x.x.x.x
   
   Notes: 
   
   • ICMP response behavior has changed in ESXi 5.1. For more information, see Change to ICMP ping response behavior in ESXi 5.1 (2042189).
   • In releases prior to ESXi 5.1, the host will automatically select the vmkernel port based on the host's vmkernel routing/forwarding table. To display the host's vmkernel routing table, use the esxcfg-route -l command.
   • Verification of your MTU size can be obtained from a SSH session by using

esxcfg-nics -l

Output should be similar to:

# esxcfg-nics -l

Name    PCI           Driver      Link Speed     Duplex MAC Address       MTU    Description

vmnic0  0000:02:00.00 e1000       Up   1000Mbps  Full   00:50:56:17:0a:60 9000   Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)

vmnic1  0000:02:01.00 e1000       Up   1000Mbps  Full   00:50:56:17:0a:65 9000   Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)

esxcfg-vmknic -l 

Output should be similar to:

# esxcfg-vmknic -l

Interface  Port Group/DVPort   IP Family IP Address                    Netmask         Broadcast   MAC Address          MTU     TSO     MSS       Enabled Type

vmk1       iSCSI  IPv4      10.10.10.10                                255.255.255.0   10.10.10.255 00:50:56:XX:XX:64    9000    65535     true    STATIC

A successful ping response is similar to:

 

# vmkping 10.0.0.1
PING server(10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=10.245 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.935 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.926 ms

--- server ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.926/4.035/10.245 ms

 

An unsuccessful ping response is similar to:

 

# vmkping 10.0.0.2
PING server (10.0.0.2) 56(84) bytes of data.

--- server ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 3017ms

 

Notes:

• If you see intermittent ping success, this might indicate you have incompatible NICs teamed on the VMotion port. Either team compatible NICs or set one of the NICs to standby.
• If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution. If you are testing connectivity to another VMkernel port on another server remember to use the VMkernel port IP address because the server's hostname usually resolves to the service console address on the remote server.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003728

Vmware Cluster datastore path dead

Symptoms:

1. have 4 esxi5.1 hosts (esxi01-04) in vmware cluster, VM in two specific datastore cannot start up on esxi01 host
2. checked the iSCSI Network adapter should be fine as only two datastore have issue
3. checked the LUN mapping is fine
4. Try rescan and refresh datatstore didn't solve the issue
5. Try to disconnect and re-mount the datastore on esxi01 didn't solve the problem . 
6. For a reason to resume service asap, migrate all VMs to TEMP datastore, unmount and detach the datastore for all esxi host
7. unmaping LUN on storage side, rescan datastore on vmware cluster the problem LUN should be disappear.
8. Remap LUN to esxi hosts, add to datasore cluster again, re-signature and format the LUN, put VM on it for testing 

Search through esxi logs and get result below:

standard input)-2014-05-xxT03:09:31.297Z cpu6:8198)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a9800037536d72502444xxxxxxxxb" state in doubt; requested fast path state update...
(standard input)-2014-05-xxT03:09:31.594Z cpu4:8401)ALERT: NMP: vmk_NmpVerifyPathUID:1167:The physical media represented by device naa.60a9800037536d72502444xxxxxx (path vmhba32:C0:T0:L13) has changed. If this is a data LUN, this is a critical error. Detect
(standard input)-2014-05-xxT03:09:31.594Z cpu4:8401)WARNING: ScsiDevice: 1422: Device :naa.60a9800037536d72502444xxxxxxx has been removed or is permanently inaccessible.
(standard input):2014-05-xxT03:09:32.410Z cpu4:8196)WARNING: HBX: 1548: HB failed due to no connectivity on [HB state abcdef02 offset 4059136 gen 17 stampUS 1847607014728 uuid 535950b3-29e2ce5d-488a-0025b501011f jrnl <FB 70200> drv 14.58] on vol 'XXXXXXX'
(standard input)-2014-05-xxT03:10:50.461Z cpu10:8202)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a9800037536d72502xxxxxxxx" state in doubt; requested fast path state update...
(standard input)-2014-05-xxT03:16:42.380Z cpu15:10515)WARNING: Vol3: 1717: Failed to refresh FS 535daf66-4b90cce6-fa7c-0025b50100ee descriptor: Device is permanently unavailable
(standard input)-2014-05-xxT03:16:42.661Z cpu15:10515)WARNING: Vol3: 1717: Failed to refresh FS 535daf66-4b90cce6-fa7c-0025b50100ee descriptor: Device is permanently unavailable

not sure whether this KB describe the exact issue but at least they got similar symptoms

VMFS Resignature causes thrashing between multiple VMware ESXi 4.x/5.x and ESX 4.x hosts (1026710

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026710

Unmounting a LUN or detaching a datastore/storage device from multiple VMware ESXi 5.x hosts (2004605)
This article provides steps to unmount a LUN from an ESXi 5.x host, which includes unmounting the file system and detaching the device. These steps must be performed for each ESXi host.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004605

Using Power CLI/vim-cmd to upgrade VM version of virtual machine

vim-cmd vmsvc/getallvms
vim-cmd vmsvc/upgradM-ID] vmx-[e [VHW-VERSION]

PowerCLI:
$vm=Get-VM -Name VM-NAME
$vm.Version

Set-Vm -VM (Get-VM -Name [VM-NAME]) -Version v[HW-VERSION]

Ref:
http://www.virtuallyghetto.com/2013/10/quick-tip-using-cli-to-upgrade-to.html

Implementing VMware vSphere 5 Auto Deploy on the Cisco Unified Computing System

This document provides an overview and detailed procedure for installing and configuring the VMware vSphere 5 Auto Deploy feature on a Microsoft Windows server. VMware vSphere is an industry-leading virtualization platform, transforming data centers into dramatically simplified cloud infrastructures and enabling the next generation of flexible, reliable IT services. Cisco Unified Computing System ™ (Cisco UCS ™) and VMware vSphere together enable rapid application and infrastructure deployment with greater security, availability, and performance leading to increased return on investment (ROI) and reduced total cost of ownership (TCO) for computing environments.

http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/whitepaper_c11-701953.html

vCenter Server and ESXi/ESX host build numbers to update levels

get ESX build # command

• uname -a 
• esxcli system version get

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014508

VMware vCenter Server performance and database troubleshooting

The following links provide detailed steps for vCenter server performance troubleshooting:

• vCenter Server does not start.
• vCenter Server is slow to respond.
• vCenter Server fails after an indefinite amount of time.
• When connected to a Microsoft SQL database, the vCenter Server vpxd.log contains an entry similar to:
  
  ODBC error: (42000) - [Microsoft][SQL Native Client][SQL Server]Could not allocate space for object <object> in database '<database>' because the '<filegroup>' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup." is returned when executing SQL statement "<sql statement>".
• When connected to an Oracle database, the vCenter Server vpxd.log contains an entry similar to:
  ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-01653: unable to extend table <table> by <size> in tablespace <tablespace> is returned when executing SQL statement <SQL Statement>.
• You see this error when attempting to connect to the SQL database server:
  ODBC error: (08S01) - [Microsoft][SQL Native Client]Named Pipes Provider: No process is on the other end of the pipe.
• The VirtualCenter Server service cannot authenticate with the database.
• You cannot connect to the database repository through SQL Server or Oracle.
• The vCenter Server database is corrupt.

Note: The vpxd.log files are located in %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003979#growth
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003979#slowdb

• High disk usage of the VMware vCenter Server database
• High disk usage of the VMware vCenter Server database transactional logs

Note: If you are using Microsoft SQL, there is a way to validate where space is being consumed within a Microsoft SQL database.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1028356

For troubleshooting or maintenance purposes it may be necessary to defragment the indexes on your Microsoft SQL database server. This article provides the steps perform a defragmentation of the indexes to increase performance of the database.

Due to the database schema enhancements made in vSphere 5.1.x and later versions, defragmentation of the vCenter Server database is no longer required.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003990

VMware KB - vSphere Client and vSphere PowerCLI may fail to connect to vCenter Server 5.5 due to a Handshake failure (2049143)

Error:
"This results in the error No matching cipher suite on the server side, and a Handshake failure on the vSphere Client or vSphere PowerCLI side"

Background:
When installed on a Windows XP or Windows Server 2003 host machine, the vSphere Client and vSphere PowerCLI may fail to connect to vCenter Server 5.5 due to a Handshake failure. vSphere 5.5 uses the Open SSL library, which, for security, is configured by default to accept only connections that use strong cipher suites. On Windows XP or Windows Server 2003, the vSphere Client and vSphere PowerCLI do not use strong cipher suites to connect with vCenter Server. 

• The solution is to allow weaker cipher in Vcenter5.5 and Esxi 5.5 Host
• Add the <cipherList>ALL</cipherList> parameter between the <ssl>...</ssl> section of the configuration file
• Please make sure you have a backup copy of the config file before edit
• For Windows-based vCenter Server
  C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg
  
  For the vCenter Server Appliance
  /etc/vmware-vpx/vpxd.cfg
  
  For ESXi 5.5
  /etc/vmware/rhttpproxy/config.xml    

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2049143&sliceId=1&docTypeID=DT_KB_1_1&dialogID=47844467&stateId=1%200%2047848621

Veeam Backup & Replication 7.0 feature

Veeam Backup & Replication 7.0

 

Inline data deduplication

Veeam Backup & Replication deduplicates identical blocks of data when backing up multiple VMs in one job, and eliminates empty space on logical disks of VMs. Use of deduplication dramatically reduces storage costs: you can reduce the backup size up to 90% when backing up VMs created from the same template

Use changed block tracking data check box is selected. For VMware VMs with hardware version 7 or later, Veeam Backup & Replication employs VMware vSphere Changed Block Tracking (CBT). Instead of scanning VMFS to know which data blocks have changed since the previous job run, Veeam Backup & Replication queries the CBT module to get the list of changed blocks. Use of CBT increases the speed and efficiency of block-level incremental backups. For example, if only 5% of a VM changed since the last backup, incremental backup will be performed 20 times faster.


There are some facts about CBT:

• The CBT mechanism is implemented as a file system filter driver.
• Information on data blocks that have changed is registered in special .ctp files 
• .ctp files are stored in the C:\ProgramData\Veeam\CtpStore folder on standalone Hyper-V hosts or on every node of the Hyper-V cluster.
• notes.txt file. This file contains basic information about the VM such as VM name and ID, and describes for which .vhd files changed block tracking is enabled.
• The backup window of incremental jobs may increase dramatically when CBT is disabled ,as Veeam Backup & Replication will read all of VM data to detect what blocks have changed since the last job run.

http://helpcenter.veeam.com/backup/70/hyperv/changed_block_tracking.html

Exclude swap file blocks from processing check box is selected.

Swap files are dynamic and change intensively between runs of a backup job. With this option selected, Veeam Backup & Replication will identify data blocks of the Windows pagefile in the guest OS and exclude them from processing, which will result in increased performance and a smaller size of increments.

Application-aware image processing, which will ensure proper restore of VSS-aware applications. To back up running VMs with VSS-aware applications (such as Active Directory, Microsoft SQL, Microsoft Exchange, Sharepoint), Veeam Backup & Replication uses application-aware image processing based on Microsoft VSS. Jobs with application-aware image processing produce transactionally consistent backups, which, unlike crash consistent backups, guarantee proper recovery of virtualized applications without any data loss.

• Guest OS file indexing, which will enable you to search for guest OS files in backed up VMs and restore files in 1 click. With this option selected, Veeam Backup & Replication creates a catalog (or index) of VM guest OS files. To learn about the 1-click restore

Make sure that the Truncate logs on successful backup only option is selected to correctly handle transaction logs after the backup job is completed. In this case, if the backup job finishes successfully, Veeam Backup & Replication will truncate transaction logs so that they do not overflow storage space. If you use an additional third-party backup tool that maintains consistency of transaction logs, select the Do not truncate logs option to prevent possible conflicts.

On the Indexing tab, select the Index everything option to perform indexing of the

Monitor job performance in real time

Recovery

Instant VM Recovery*, which uses the vPower technology to start a VM directly from a compressed and deduplicated backup file. Instant VM Recovery creates a "temporary spare" of the original VM and provides the minimum restore time possible (several seconds to several minutes).

MICROSOFT EXCHANGE AIR WIZARD 7.0 RELEASE NOTES http://veeampdf.s3.amazonaws.com/release_notes/veeam_backup_ex_air_7_0_release_notes.pdf?AWSAccessKeyId=AKIAJI4MX44AEVG3NBLA&Expires=1389167061&Signature=fqZjtdX6VCUAgq4obl%2BZSByyLkc%3D

Performing Item-Level Restore

Select the mailbox from which you want to restore Microsoft Exchange items (e-mails, contacts, appointments and so on).

In the Mailbox account field, specify the account of the user whose mailbox you want to access. To quickly find the necessary account, enter the first characters of the account in the field and click Checkon the right or press [ENTER] on the keyboard. The Microsoft Exchange Recovery wizard will form a list of available accounts starting with entered characters so that you can choose the necessary one.

The information about the server hosting the selected mailbox will be displayed in the lower part of the window.

If prompted, specify the credentials to be used to access the specified mailbox in production environment.


NOTE:
This account should have sufficient access rights for the specified mailbox, 
otherwise you will not be able to proceed. If necessary, contact your 
Exchange administrator.

Select the mode in which you want to restore items from the selected mailbox. You can choose to work only with those items that have changed since the point you selected, or work with all items in this mailbox.

At the Item Filter step of the wizard, you can specify filter criteria that will help you find the necessary item. Use the Add Criteria list at the bottom of the window to add any item fields you need. Fill in the fields so that the Microsoft Exchange Recovery wizard can apply the filter.

After you provide the search filter, the Microsoft Exchange Recovery wizard will look for the necessary items and display the list of those that match the specified criteria. Select check boxes next to the items you want to restore. You can use the Mailbox item type field at the top to display items of the necessary type only.

Specify to which location you want to restore the selected item(s). You can restore items back to the original mailbox on the production Microsoft Exchange server or save them as individual files to the selected folder.

NOTE:

Microsoft Exchange Recovery wizard does not allow you to save items restored
from Microsoft Exchange 2010 to a file. For this reason, 
the File system option is disabled for Microsoft Exchange 2010


Specify options for the mailbox or folder to which you want to restore Microsoft Exchange items.

●If you have selected to restore items to a mailbox, select the mailbox folder to which restored items should be placed. You can additionally select to mark restored items as Unread. If you are restoring multiple mailbox items, you can select the Preserve folder hierarchy check box to keep the initial folder structure.

●If you have selected to restore items to a folder, specify the path to the folder to which restored items should be placed.

Review the settings you specified and click Restore. The selected items will be restored to the specified mailbox/folder in the production Microsoft Exchange server or saved as individual files to the selected folder.

http://helpcenter.veeam.com/backup/70/uair/uair_exch_restore.htm

Other key enhancements include:

Virtual Lab functionality, including Sure Backup, is now available for Microsoft Hyper-V. This allows item level restores in SQL, Exchange and Active Directory using Veeam U-AIR wizards which have also been updated in v7 making restores easier and quicker.
The ability to take backups from storage snapshots provides huge performance improvements, additional storage system support has been added into B&R v7 which now includes HP 3PAR/StoreServ and HP StoreVirtual VSA.
Veeam Explorer has been updated, adding-in support for Microsoft Sharepoint 2010 and Microsoft Exchange 2013, as well as now allowing restores to Office 365 and improving overall restore performance into existing Exchange environments.

Performance improvements offered across both VMware and Hyper-V environments include:

Change Block Tracking optimisations and improved speed for file level recovery operations. Specific to VMware it is now possible to transparently backup vCenter without the need to specify which host it is running on and snapshots can be committed concurrently. With Hyper-V there is now extended support available for ODX enabled storage and clustered disks along with performance improvements for load balancing.

http://www.eacsblog.com/2013/09/whats-new-in-veeam-backup-replication-v7/

Insight into Guest OS Recovery

Together with full VM recovery, Veeam Backup & Replication offers Instant File-Level Restore (IFLR) which lets you recover guest OS files and folders from the VM backup. In contrast to competitive solutions, IFLR does not require a specific file-level backup –restore of guest OS files, as well as all other restore options, are available from the same image-level backup. Neither should you extract the VM image from the backup prior to restore – VM guest OS files can be recovered on-the-fly, directly from a regular backup (or from a VM replica). This makes the restore process extremely fast and does not require you to provision additional storage resources.

Veeam Backup & Replication provides three options for guest OS files recovery:

• Recovery from Windows-based file systems (FAT, NTFS and ReFS)

• Recovery from 15 most used file systems (including Linux, Unix, BSD and soon) with the multi-OS restore wizard

• Universal File-Level Recovery*for any OS or file system through leveraging the Instant VM Recovery technology*

VM guest OS files can be recovered to the latest state or any good to know point in time.

Install / Upgrade VMware ESXi 5.5.0 GA from ESXi with USB drive on HPz420

The background: 
As the workstation HP z420 is not in he HCL of the vsphere5.5 and I find that the network adapter is not recognized if installing the ESXi 5.5 host with the installation image from vmware. This error interrupt the installation process and it could not be skipped: 

"No network adapters were detected. Either no network adapters are physically connected .."

1. Try using the HP Custom Image for ESXi 5.5.0 GA Install CD-September 2013 -here to install the ESXi 5.5 but the network adapter still not to be detected. 

2. The HP z420 come with Intel 82579LM nic on the X79 motherboard, we need use ESXi-Customizer to inject the 82579LM nic driver into the installation image, first download files in follow links:

ESXi-Customizer http://www.v-front.de/p/esxi-customizer.html
VIB file net-e1000e-2.1.4.x86_64.vib  from http://ftp2.pl.freebsd.org/pub/VM/VMware/Drivers/net-e1000e-2.1.4.x86_64.vib
ESXi5.5 image from vmware download

3. The image marking process is straight forward, just prepare those files and click run 

4. After the customized image file is ready, we convert it into usb boot image with UNettbootin  
run the tool as administrator

* The usb drive should be erase first to ensure no other boot files exist

5. Use the USB to boot the workstation.

6. Enter to continue

7. Press F11 to accept the EULA and continue 

8. For upgrade , we can use F1 to view the disk detail and get where the system disk is 

9. Press F11 for Upgrade

10. Select  "Upgrade ESXi , preserve VMFS datastore"

11. Wait the upgrade complete and restart the server 













12. Include the BIOS information as reference