HTML5 – Page 4

Quick Tip - Pre-filled credentials in the vSphere 6.0 Web Client

08.24.2015 by William Lam // 17 Comments

This past weekend I was finishing up a couple of demo recordings for my VMworld sessions in case the live demos fail for whatever reason, which has happened to me in the past. A few of the demos involve the vSphere Web Client UI and I thought instead of wasting time and potentially fat fingering credentials up on stage, I would try to do everything I can to remove any potential hiccups. In vSphere 6.0, the vCenter Single Sign-On page is now completely in HTML and this not only means you can customize the UI as I have shown here but you can also do some other neat tricks with it.

I decided to update the HTML page to automatically pre-fill both the SSO username and password, so that when I need to login to the vSphere Web Client, I just have to hit the tab key and then click on the login button.

Disclaimer: Outside of a home lab or demo purposes, there is really no good reason for this. I can already hear Mike Foley sighing right now 😉 This also means that anyone who knows the address of your vSphere Web Client can just login, so you may want to only pre-fill the username and still type out the password in case you are concerned with that.

To pre-fill the value for the SSO username and/or password, you will need to edit the following file:

Windows VC: C:\ProgramData\VMware\vCenterServer\runtime\VMwareSTSService\webapps\websso\WEB-INF\views\unpentry.jsp
VCSA: /usr/lib/vmware-sso/vmware-sts/webapps/websso/WEB-INF/views/unpentry.jsp

For pre-filling the username, you will need to add a "value" property along with its actual value in the following section:

<input id="username" class="margeTextInput" type="text" value="*protected email*"/>

For pre-filling the password, you will need to add a "value" property along with its actual value in the following section:

<input id="password" class="margeTextInput" type="password" value="VMware1!"/>

Once you have saved your changes, you can then reload the browser and you should see that the vSphere Web Client now has both the username and password automatically pre-filled when the webpage loads.

New HTML5 Embedded Host Client for ESXi

08.11.2015 by William Lam // 61 Comments

How many of you remember the old WebAccess interface that came with classic ESX 2.0? I know I sure do! It was a very useful interface that allowed administrators to easily manage their ESX hosts through a web browser that provided basic VM creation, troubleshooting and most importantly initial bootstrap configurations for greenfield deployments where a vCenter Server may not be available yet.

I have always felt that having a simple web interface that customers can just point their browser to an ESX(i) host after an installation would be the most intuitive from a user experience standpoint. About a year ago, I was involved in a project with two VMware Engineers, Kevin Christopher and Jehad Affoneh, when we worked on an early prototype of an optimized Embedded Host Client for ESXi. We socialized the prototype across many different teams at VMware and the overwhelming feedback was super positive. Earlier this year, with the help of the ESXi PM and the Engineering team, they decided to take the concept of the prototype to the next level and really turn it into something that could really be used by customers.

UPDATE: (08/25/15) - v2 has just been released, be sure to take a look at this blog post for more details.

Today, I am very happy to announce the release of a new VMware Fling: HTML5 Embedded Host Client for ESXi which is currently distributed as a simple installable VIB. The Fling currently only supports ESXi 6.0 (however, there is a workaround ESXi 5.x which you can find below). In this first release, the Free ESXi Hypervisor is not supported, but the plan is to add support for this in a future update. Here is a list of some of the supported operations in this first release:

VM operations (power on, off, reset, suspend, etc.)
Creating a new VM, from scratch or from OVF/OVA (limited OVA support)
Configuring NTP on a host
Displaying summaries, events, tasks and notifications/alerts
Providing a console to VMs
Configuring host networking
Configuring host advanced settings
Configuring host services
License management

Once the VIB is installed, which does not require a system reboot, you simply just point your web browser to the following URL: https://[ESXI-HOST]/ui and login with an administrator account.

One of my favorite features of the Embedded Host Client is the integrated VM Console which is accessible directly within the browser and does not require any additional plugins or installers. I do want to mention that the VM Console feature is currently only available when installed onto an ESXi 6.0 host. One other caveat that I would like to point out is that for customers who wish to try the Embedded Host Client on ESXi 5.5 or on ESXi 6.0 host which have been upgraded from an ESXi 5.x environment, the following workaround is required:

ESXi 5.x or ESXi 6.0 (upgraded from ESXi 5.x) workaround:

Step 1 - SSH to your ESXi host and open the following configuration file:

/etc/vmware/rhttpproxy/endpoints.conf

Step 2 - Remove the following line and save the changes

/ui local 8308 redirect allow

Step 3 - Restart the reverse proxy by running the following command:

/etc/init.d/rhttpproxy restart

Step 4 - Open a browser to the following URL: https://[ESXI-HOST]/ui/ and note the additional trailing "slash" at the end of the URL. This is mandatory else the Embedded Host Client page will not properly load.

Note: This only applies to ESXi 6.0 hosts which have been upgraded from ESXi 5.x or pre-ESXi 5.5 Update 3 systems. You may also noticed translation errors when running the Fling on pre-ESXi 6.0, this is expected. For the best experience, we recommend using ESXi 6.0 or waiting until ESXi 5.5 Update 3 is released which will resolve this problem.

Having spent the last couple of months working with both of the Engineers: Etienne Le Sueur and George Estebe, I was able to help provide feedback and usability enhancements and I think you will really like what is there in this first release. I do want to stress that this is in no way, shape or form a comprehensive replacement for the existing vSphere C# Client functionality, but I think it could be a good start if the feedback from customers is positive. I really hope you do give this a try in your lab environment and please let us know what features and capabilities we should add next. There is a variety of way you can provide feedback by leaving a comment on this blog post, leaving a comment on the Flings page.

Big thanks goes out to both George and Etienne who took on the challenge and did a fantastic job on the Fling!

Standalone VMRC (VM Remote Console) re-introduced in vSphere 5.5 Update 2b

10.10.2014 by William Lam // 53 Comments

The VMRC (VM Remote Console) has gone through several transitions from initially being available as a standalone Windows application to an integrated browser based plugin with the release of the vSphere Web Client. In the latest vSphere 5.5 Update 2b release, a new standalone VMRC has been re-introduced to provide an alternative way to launch a VM console. The reason for this is due to the deprecated and eventual removal of NPAPI (Netscape Plugin Application Programming Interface) based plugin support from all modern web browsers which the current VMRC implementation leverages. Here is a quick excerpt from the vSphere 5.5 Update 2b release notes:

Inability to open virtual machine console using Google Chrome browser when NPAPI support is deprecated
When the NPAPI support in Google Chrome is deprecated, the virtual machine console provided in the vSphere Client Integration Plugin might no longer function when the Chrome browser is updated. As a result, you might be unable to open the virtual machine console using the Google Chrome browser and you might not be able to connect to devices.

UPDATE (10/21/14) - Looks like the standalone VMRC has just been made available and you can now download it by either following the link in the vSphere Web Client if you are on vSphere 5.5 Update 2b OR simply by going to http://www.vmware.com/go/download-vmrc

UPDATE (10/12/14) - It looks like the standalone VMRC is currently not available for download just yet. You can continue using the existing methods to connect to your VM Console, the new Standalone VMRC is NOT required but the links have been put in place to proactively get ready for NPAPI deprecation (more details below). You can subscribe to VMware KB 2091284 which will be updated when the download is available.

UPDATE (05/31/15) - If you are connecting directly to an ESXi host you can either use the vSphere API to query for the VM MoRef ID or you can easily pull it by running the following command directly in the ESXi Shell:

vim-cmd vmsvc/getallvms

The deprecation of NPAPI support is nothing new and has actually been communicated by all major web browsers for quite some time now. To ensure that VMware customers are not affected when this change goes into effect, a new standalone VMRC is being introduced to preempt the upcoming change and provides a new way of launching a VM console using the vSphere Web Client as seen in the screenshot below.

To be able to open a VM Console using the new standalone VMRC, you will of course need to have it installed first. You can find the link to the download on VMware.com but there is also a direct link provided on the VM Summary page in the vSphere Web Client. In addition to the new standalone VMRC, you will still be able to use the existing method as well as the HTML5 based VM console. The HTML5 console continues to work if you do not have CIP (Client Integration Package) installed on your Windows system or if you are running on a Mac OS X system. I am sure many of you are probably asking when will there be Mac OS X version of VMRC? I know I definitely am 🙂 The good news is that this is being worked on and hopefully we will see a Mac OS X version in the very near future.

Furthermore, the new standalone VMRC also includes some nice enhancements that I know some of you have been asking for, especially those that have used the previous standalone VMRC application. The new VMRC can now be directly launched using the following two URI methods:

vmrc://[USERNAME]@[VC]/?moid=[VM-MOREF-ID]
vmrc://clone:[VC-TICKET]@[VC]/?moid=[VM-MOREF-ID]

Here is a screenshot of the standalone VMRC application:

The first method accepts basic authentication using username/password, the vCenter Server address and the VM MoRef Id. Here is an example of what that would look like:

C:\Program Files (x86)\VMware\VMware Remote Console\vmrc.exe vmrc://*protected email*/?moid=vm-37

The second method accepts a vCenter Server session ticket which you can generate by using vSphere API acquireCloneTicket() method. A quick way to test this example is by using the vSphere MOB and making a call to acquireCloneTicket using the following URL https://[VCENTER-SERVER]/mob/?moid=SessionManager&method=acquireCloneTicket and then specifying the ticket as seen in the example below.

C:\Program Files (x86)\VMware\VMware Remote Console\vmrc.exe vmrc://clone:*protected email*/?moid=vm-37

With the new URI handler, you can automatically associate it with the standalone VMRC application which means you can type this into a browser or into a Windows explorer and it will automatically launch VMRC. The other nice thing about the new standalone VMRC is if you would like to reduce the complexity of getting a regular use connected to their desktop, you can easily use the standalone VMRC and dynamically generating a link for your end users to access their VMs without ever exposing them to the underlying vSphere infrastructure. I suspect there will be some really interesting use cases for the new standalone VMRC and the VMRC team will continue to iterate to make it better based on customer feedback.