Skip to content

VMware Host Client 1.0 and vSphere HTML Client Fling

vSphere 5.x provided a web-based client user interface, the vSphere Web Client, for connecting to the vCenter Server and managing you vSphere environment; however, it did not provide a web-based client for connecting directly to an ESXi host.  Instead, whenever you needed to manage an ESXi host directly, you had to use another tool, such as the vSphere Client (the thick client).

VMware recently announced that beginning with vSphere 6.0 Update 2, a new HTML 5 based ESXi host client is shipped that can be used to connect directly to and manage an ESXi host.  The client is embedded into ESXi.  Immediately following the installation of ESXi 6.0 U2, you should be able to use a supported web browser to browse to the host’s management IP address (or https://host-ip-address/ui/#/host) and logon using the root account.  The client will allow you manage the ESXi host and virtual machines with a feature set similar to what you would expect using the vSphere Client to manage a host directly in vSphere 5.  Because you are connected directly to a specific ESXi host, you should not expect to be able to perform functions that require vCenter Server, such as vMotion operations.

To gain familiarity with this tool in vSphere version prior to 6.0 Update 2, you can experiment with this Host Client VMware Fling.  Don’t forget that Flings should not be used in production environments.

Another useful and interesting Fling is vSphere HTM5 Web Client which is effectively a new version of the vSphere Web Client, but uses HTML5 instead of Adobe Flash.  Apparently, this will eventually evolve and become part of the actual product, but for now the Fling is available for non-production use.  It gives you the opportunity to gain familiarity now and provide feedback.  The Fling does not contain the full feature set that the eventual product will contain, but it does provide these features:

  • ability to connect to vCenter Server
  • VM Power Operations (common cases)
  • VM Edit Settings (simple CPU, Memory, Disk changes)
  • VM Console
  • VM and Host Summary pages
  • VM Migration (only to a Host)
  • Clone to Template/VM
  • Create VM on a Host (limited)
  • Additional monitoring views (Performance charts, Tasks, Events)
  • Global Views (Recent tasks, Alarms–view only)


vLoreBlog 2016

Now that I am well settled into my new role at Rackspace and have completed writing the drafts for my chapters of the upcoming Official VCP6-DCV Cert Guide (VMware Press, Pearson), I have a clear idea on information that I want to share within the virtualization and cloud community.  Beginning now I plan to aggressively post on the following topics.

  • VMware technical tidbits:  Information that I encountered as I engage in design projects and professional services engagements that I expect you will find useful.
  • VMware certification:  Specific advice on obtaining VMware Certification, plus details on various topics covered by the exams.

To get the ball rolling, today I published a page on vSphere 6 Page Sharing, Salting, and Memory States.  This information may be useful to you as you analyze the behavior of your environment and explore means to increase the impact of page sharing.  It may also be useful to you as you prepare for the VCP6-DCV exam.

My VMworld Presentations

I plan to deliver the following three presentations at VMworld next week in the Rackspace Booth.

Upgrade to vCenter Site Recovery Manager 6.0 and vSphere Replication 6.0:  Four Keys to Success.

Date / Time: Monday – August 31 11:30 AM (Pacific Time)


You currently rely on a successfully implemented disaster recovery (DR) solution built upon vCenter Site Recovery Manager (SRM) 5.5 and vSphere Replication 5.5; but, due to its complexity and the perceived risks, you avoided upgrading to version 5.8.  Now, version 6.0 is available with features you want.   How do you successfully upgrade your DR solution, while minimizing risk and disruption?

Engage with a Senior Integration Consultant from Rackspace to learn the 4 Keys to success for upgrading SRM and vSphere Replication, such as avoiding common pitfalls, selecting the best upgrade path, establishing a rollback plan and implementing new features.

How to Design a Reliable Disaster Recovery Solution: The Keys to Success

Date / Time: Tuesday  – September 1 –  3:30 PM (Pacific Time)


You are finally ready to design a new disaster recovery (DR) solution, but you do not know where to start.  Everyone tells you that they have the solution that can provide DR for your vSphere environment, where most of your applications run, but which solution is right for you?

Join with a Senior Integration Consultant from Rackspace to learn how to design a reliable DR solution that is not focused on a product, but focused on your unique requirements.   Learn the keys for a successful design:  Simple design methodology,  resiliency /manageability,  application details, recovery plans., success criteria and non-disruptive testing.

VMware vRealize Operations:  Using Out-of-the-box Actions and the vRO Solution and Workflow Package

Date / Time:  Wednesday  – September 2 –  1:30 PM (Pacific Time)


VMware vRealize Operations (vROps) 6.0 uses the concept of symptoms, recommendations, and actions to enable you to monitor, analyze, and remediate issues in your vSphere environment.  Out of the box, it provides powerful functionality that helps reduce the mean time for identification and resolution of problems.  In this session, you will see how to customize alerts and recommendations in vROps by assigning built-in actions, such as deleting snapshots, powering off virtual machines, and changing resource usage to address common issues.  Additionally, you will see how easily you can extend the power of automating remediation by implementing the vRealize Orchestration (vRO) Solution and Workflow Package for vROps, which includes popular actions such as decommissioning hosts, migrating virtual machines, and upgrading VMware Tools.

Changes to VMware Certification

Earlier this year, VMware announced changes to their certification program, which many people in the community were already struggling to grasp.  Here is my attempt to simply it:

  • The program offers 4 tracks:  Data Center Virtualization (DCV – focused on  vSphere), Desktop and Mobility (DTM – focused Horizon Suite), Cloud Management and Automation (CMA – focused on vRealize Suite), and Network Virtualization  (NV – focused on NSX).
  • It provides 4 main levels in each track:  Associate (VCA), Professional (VCP), Implementation Expert (VCIX), and Design Expert (VCDX).
  • VCA’s can successfully explain the concepts associated with the technologies and products in the track.  They can successfully engage in discussions related to the track, such as discussions on conceptual solution design, using proper vocabulary.
  • The main requirement for VCA is successfully passing an online exam.
  • VCP’s can independently, successfully install the technologies and products in the track in a manner that is adequate for Proof of Concept Testing.   They can also implement production-ready solutions based on these technologies and products by applying installation procedures and design documents provided by solution architects.
  • The main requirements for new VCPs are to attend an official course and to pass two exams.  The first is a core fundamentals exam focused on vSphere.  The second exam is a professional exam based on the specific track.  Previously, this level only required passing a single exam.  Current VCPs can follow migration paths that have fewer requirements.
  • VCIX’s can demonstrate their ability to design and implement solutions based on the technologies and products in the track well enough to be considered as a minimally qualified candidate for the  VMware Professional Services Team.  Previously, this level was called VCAP (advanced professional), but the new name focus on Implementation.
  • The main requirements for VCIX are to become a VCP in any track and to pass two exams on the specific track:  a VCIX-Lab exam (hands-on, implementation exam) and a VCIX-Design exam.   Previously, this level contained two separate VCAP certifications, but now it is a single certification that requires passing both exams.
  • VCDX’s can successfully perform the role of solution architect involving the technologies and products in the track.
  • The main requirements for VCDX are to become VCIX in the track, submit a design and application, and to successfully defend it to a VCDX panel.

In summary, the main changes from the previous certification program is that new VCP candidates must pass two exams, the purpose and name of VCAP has been changed to VCIX,  and two exams must be passed for VCIX.

NOTE:  Current VCPs of any track may only need to pass a single exam to become VCP6-DCV.

Be certain to examine the detailed requirements and migration paths on the VMware Certification page.


Discussion on VMware Certification

Tomorrow, I plan to deliver this presentation at a VMUG Louisville event

  • Presentation Name = Discussion on VMware Certification
  • Topics:
    • Currently available certifications, tracks, and levels.
    • VCP5-DCV and VCAP5-DCA requirements
    • Exam Expirations
    • Details and advice  VCP5-DCV Delta Exam and Recertification
    • Recommendations on  preparing for the VCP5-DCV and VCAP5-DCA exams.
  • Duration: about 45 minutes

Also at the event:

  • A fellow vExpert – Kendrick Coleman – presents on vCloud Air API Usage
  • Presentation by Nimble Storage
  • Lunch, giveaways, and colleagues

Location and Registration:


VCAP Exams on vSphere 5.1 Expiration

The certification exams for VCAP5-DCA and VCAP5-DCD on vSphere versions 5.0/5.1 are set to expire on January 31, 2015.  The exams for vSphere version 5.5 will continue to be available.  So, if you plan to seek the VCAP5-DCA certification and prefer to be tested on vSphere 5.0 / 5.1, then you should plan to take the VDCA510 exam by the end of January.  Likewise,  if you plan to seek the VCAP5-DCD certification and prefer to be tested on vSphere 5.0 / 5.1, then you should plan to take the VCDC510 exam by the end of January.  Otherwise, you can take the VDCA550 and VDCD550 exams, which cover vSphere 5.5, at any time.

For those of you that choose to use the Official VMware VCAP5-DCA Cert Guide from the VMware Press to prepare for the VCAP5-DCA exams, be sure to purchase the Premium Edition, which includes online content that covers the blueprint for the VDCA550 exam.  The online materials include information on using the vSphere Web Client, new features in vSphere 5.5, items that covered in the VDCA550 blueprint (but not covered in the VDCA510 blueprint), and additional practice exams.


Manually Using SYSPREP in Windows 2012 VMs and Templates

Recently, on a professional services engagement, we encountered a situation, where the Customization Wizard was failing to successfully apply SYSPREP to Windows 2012 Servers.  Because our main objective and my time was focused on other areas, we could not take time to resolve the underlying the root cause, so we needed a work-around.   This led us to applying SYSPREP manually, which I had not done in a long time.  Here are the details that we applied toward using SYSPREP manually in a VM template


Our main concern is if we deploy two VMs from a template or VM that already has a SID, then an issue may occur if we try to add both new VMs to the domain.  The following error may occur when adding the second VM.


To fix this in the second VM, you can use these steps:

1 – Open RUN and enter sysprep


2 – Right-click on sysprep and choose Run as Administrator


3 – In the System Preparation Tool Window, set the System Cleanup Action dropdown = Enter System Out of Box Experience (OOBE). check the Generalize box, and set the Shutdown Options to Reboot.


4 – SYSPREP will run the necessary action and restart Windows.

5 – As Windows reboots, it will prompt for new Settings.  Apply the appropriate settings for this VM.   Windows will now have a new SID.

6. – After Windows starts, you should be able to successfully add it to the AD domain.


To avoid this issue in the future, deploy a Windows VMs from a template where SYSPREP has been used to strip the SID and where Windows will prompt for new settings on the next boot.  To prepare the template, perform these steps:

  • In a new VM, install Windows 2012 R2
  • Install VMware Tools
  • Install all Windows Updates
  • Use Steps 1 to 3 from above, except on step 3, set the Shutdown Options = Shutdown (not restart)
  • After Windows shutdown finishes, use the vSphere Client to right-click on the VM and choose Convert to Template




Forgot ESXi Password? Here is a fix.

Here is a slick way using host profiles.  It calls for using a host profile and using the Configure a fixed administrator password option.   Details at:


But, it may not be supported.  The statement in the following KB article indicates that the only supported way to reset the root account password on an ESXi host is to reinstall ESXi.

Choosing the Best NIC Teaming Load Balancing Policy in vSphere

Frequently, on my professional services engagements, my customer will ask me which NIC Teaming Load Balancing option is the best choice when configuring virtual switch port group in VMware vSphere.  The following represents my typical answer:
Here are guidelines for choosing the best NIC Teaming Load Balancing policy:
  • Based on IP hash – Use this only for Etherchannel (port channel).  If the uplinks on a standard virtual switch or distributed virtual switch connect to an Etherchannel, then set the NIC Teaming Load Balancing to IP Hash for each virtual port group that uses these uplinks.    This could also be used when implementing new features in vSphere 5.1 and 5.5 that allow LACP to be configured on the physical uplinks of a distributed virtual switch.
  • Based on originating virtual port – This is the default.  It has traditionally been the best setting for most virtual port groups, whenever Etherchannel is not involved.  It is still the best setting in most cases when Ethernet is not involved for standard virtual port groups,  Load Based Teaming (LBT) is often preferred in this case for distributed port groups
  • Based on source MAC hash – This is seldom used, but is preferred whenever you want to control the placement of VMs based on their MAC address assignments.
  • Based on physical NIC load – This is also called Load Based Teaming (LBT).  It is a fairly new feature on dvSwitches and is typically preferred over port-based teaming, because the two perform identically, except that LBT includes intelligence to migrate virtual adapters from a busy uplink to a lesser active uplink.  In many cases, this is preferred over using Etherchannel to provide a scalable NIC Team that does not require special settings on the physical switch, so it is easy to manage.  However, Ethernet is still preferred in cases where the best resiliency, scalability, and performance is needed.
  • Explicit Failover – Used in cases where the administrator prefers to manually balance the workload by placing some VMs and vmkernel virtual adapters on specific port groups that utilize a specific set of active ports.  A common example, is where the Management Network and vMotion are the placed on a virtual switch by themselves – often the Management Network is set to use vmnic0 as Active and vmnic1 as Standby and vice versa for the vMotion port.


LACP, LAG, Etherchannel and vSphere 5.5 – a simple explanation

I have often stumbled when trying to explain the differences and the relationships between Etherchannel, LACP, and IEEE802.3ad.  I began stumbling more when I learned that vSphere 5.5 supports Enhanced LACP and LAGs.   Here is my best attempt to clarify.

Etherchannel:  an Etherchannel is a logical channel formed by bundling together two or more links to aggregate bandwidth and provide redundancy.  Another acceptable name for Etherchannel (an IOS term) is port channel (an NXOS term).  Another acceptable name is Link Aggregation Group (LAG)

LACP:  a standards based negotiation protocol used to dynamically build an Etherchannel.  It is known as the IEEE 802.1ax (or IEEE 802.3ad) Link Aggregation Control Protocol (LACP).    It is a protocol used to build Etherchannels (LAGs) dynamically.   LAGs (Etherchannels) can be be also be built statically without using LACP.

IEEE 802.1ax:  The IEEE working group that defines port channel, EtherChannels and link aggregation.  Orinally, the working IEEE group was 802.3ad, but in 2008 it was replaced by 802.1ax.

IEEE 802.3ad:  the original IEEE working group for port channel, EtherChannel, and link aggregation.  Although it has been replaced with 802.1ax, referring to IEEE 802.3ad is typically acceptable.  So references to IEEE 802.3ad LACP are common.

vSphere pre version 5.1:  the standard virtual switches and distributed virtual switches provided natively by VMware vSphere 5.0 and earlier do not support LACP (dynamic LAG / Etherchannel creation); however, they support statically built LAGs (or this may be called static LAGs or static Etherchannels)

vSphere 5.1:  the distributed virtual switches provided natively by VMware vSphere 5.1  support LACP (dynamic LAG / Etherchannel creation).  The support is limited to one LAG per ESXi host and per dvSwitch

vSphere 5.5:  the distributed virtual switches provided natively by VMware vSphere 5.5  support LACP (dynamic LAG / Etherchannel creation).  It supports 64 LAGs per ESXi host and 64 LAGs per dvSwitch.