WilliamLam.com

Embedded Host Client Fling v3 released!

by // 8 Comments

I just wanted to give everyone a quick heads up that version 3 of the awesome Embedded Host Client Fling has just been released! In addition to all the new features and bug fixes which you can find more details below, there is now also an offline bundle for ESXi 5.x as well as ESXi 6.x which can then be used to distribute to your vSphere environment using vSphere Update Manager. One of my favorite features in this new release is the ability to edit or delete existing disk partitions which is super handy when repurposing existing disk devices for use with VSAN. You can find the download on the Embedded Host Client Fling page here.

Screen Shot 2015-10-23 at 10.03.53 AM
If you have v1 or v2 installed, you can perform an "update" by simply running the following ESXCLI command:

[root@mini:~] esxcli software vib update -v /esxui-signed.vib
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_bootbank_esx-ui_0.0.2-0.1.3172496
VIBs Removed: VMware_bootbank_esx-ui_0.0.2-0.1.3015331
VIBs Skipped:

What's new in v3 - 

  • VM
    • Answer question support
    • Upgrade virtual hardware to the latest supported by the host
    • Hot edit VM settings
    • VM table column configuration (show/hide columns), remembered across browser refresh
    • VM startup/shutdown priority (simple increase/decrease)
  • Host
    • Change host power management policy, advanced power configuration
    • Generate IP/FQDN certificate signing request and import new certificate
    • Join a host to an active directory domain controller
  • Storage
    • Disk device partition editor
    • Adapter rescan for new LUNs
    • Disk device rescan for new VMFS volumes
    • Clear a disk's partition table
    • Disk device partition diagram
    • Increase datastore size onto disk that already contains a partition table
  • Performance charts
    • Ability to change performance chart colors (two choices: default VMware colors and high contrast colors)
    • Added Network and Disk charts to Host performance UI
    • Improve VM performance UI, still missing some charts
    • Improved performance UI on tablets
      • Always hide the top legend in the chart
      • Hide the focus widget to increase vertical space
  • General
    • In-app update tool: provide a URL to a new version of the VIB, refresh the browser, et voila!
    • For tabbed UIs, the selected tab is remembered as you navigate around the UI to avoid un-necessary clicks
    • Better scrolling performance on tablets (tested on iPad)
    • Hide-able navigator allowing more space on tablets
    • Shortcut buttons to Host, Host Manage, Host Monitor, VMs, Storage, Networking when navigator is collapsed
    • Improved Actions menu behavior on tablets:
      • Menu navigation no longer hides the actions menu
      • Added an explicit close button on actions menus
      • A second press on the Actions button will close the menu
  • Bugfixes
    • VM table sizing with small number of VMs
    • In-browser consoles:
      • Will now attempt to reconnect when losing a connection to a powered on VM
      • Reverting to a powered-on snapshot while a console is open to that VM will reconnect the console

Handy tidbits & workarounds for the VCS to VCSA Migration Fling

by //

The VCS (Windows VC) to VCSA Migration Fling has been out for a little over 6 months and the response from customers thus far has simply been phenomenal. We have also received some great feedback (200+ comments) from customers who have tried out the Fling in either a Dev/Test environment and some even in their production environment for those that are a bit more on the adventurous side. I have also had the pleasure in talking to some of these customers who have been successful in migrating off of their Windows vCenter Server (both large and small) and onto the vCenter Server Appliance (VCSA) and sharing additional feedback they may have about the Fling and how we can further improve.

Given the popularity of this topic, I thought it would be useful to aggregate some of the learning's, tidbits and workarounds that have been discovered in the past 6months to help any new or even existing users who might be interested in trying out the Fling. We really do appreciate all the feedback that everyone has given in the various forms and in fact, several of the workarounds were ones provided by our customers. As you know, the Fling today is not currently officially supported, however the feedback has really helped our PM/Engineering team. In fact, you can even get a sneak peak at an early Tech Preview we did at VMworld here to give you an idea on how some of your feedback has influenced a feature that may or may not be out in the near future 😉

Tidbit 1 Microsoft Windows 2012 is currently not supported.
Additional Info There is a known winexe bug which is affects migrating from this specific OS platform.
Workaround Engineering has a fix for this and is currently in the process of testing the fix along with legal review. There is not an ETA due to the review but we hope to release an update to Fling that includes this fix very soon. Stay tuned!This has been resolved with v0.9.1 of the Migration Appliance and for more details please take a look here.
Tidbit 2 Use of non-default (custom) ports on Microsoft SQL Server Database is not supported
Additional Info The Fling currently assumes the SQL Server Database is running on port 1433
Workaround Engineering has a fix for this and is currently in the process of testing the fix along with legal review. There is not an ETA due to the review but we hope to release an update to Fling that includes this fix very soon. Stay tuned!
Tidbit 3 Use of an Embedded Microsoft SQL Server or Microsoft SQL Express Database on the vCenter Server is not supported
Additional Info Since the source Windows vCenter Server must be powered off during the database migration; running the database on the same source vCenter Server is not possible.
Workaround One option is to re-ip the source Windows vCenter Server and ensuring the vCenter Server service is completely disable which would allow the Migration Appliance to communicate with the database. This is not ideal as you are modifying the source Windows vCenter Server but has worked in our testing. Second option that several other customers have recommended instead is to export the vCenter Server Database to a single instance of a Microsoft SQL Server or Microsoft SQL Express and that has worked really well.
Tidbit 4 Clustered database such as Microsoft Clustering Services (MSCS) is not supported
Additional Info There have been issues from some customers when trying to connect to an instance of the vCenter Server Database behind an MSCS Cluster.
Workaround Exporting the vCenter Server Database to a single instance of a Microsoft SQL Server or Microsoft SQL Express and then using the Fling has worked for several customers.
Tidbit 5 Issues connecting to a non-default named instance (e.g. SERVERNAME\VCENTER) of the vCenter Server Database.
Additional Info Some customers have had issues with the connection string to a non-default named instance of the vCenter Server Database during the database migration portion of the Fling.
Workaround A solution that was identified by a customer used the following: http://stackoverflow.com/a/11921896/2668394
Tidbit 6 Upgrade to VCSA 6.0 after migrating from Windows vCenter Server 5.5 to VCSA 5.5 fails
Additional Info You see the following error "Extra sequences: vpx_host_cnx_seq;" in /var/log/vmware/upgrade/vcdb_req.err during the upgrade to VCSA 6.0. These sequences are only found and valid in a Microsoft SQL Server Database and are not relevant in an vPostgres Database and just simply need to be dropped as they are not used at all.
Workaround Login to the VCSA 6.0 appliance as root and run the following command: /opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB -c "drop sequence if exists vpx_host_cnx_seq cascade"

If you are running into issues while through the the migration, one thing you can do is login to the Migration Appliance and go to another virtual console (ALT+F2) and view the Migration logs  under /var/log/migrate.log SSH is currently not installed by default. If you wish to pull out the logs for additional support, you can install which will require internet access and you can do so by running the following commands:

sudo apt-get -y update
sudo apt-get -y install openssh-server
sudo /etc/init.d/ssh start

The credentials to the Migration Appliance is vmware/vmware

Lastly, if there are other tidbits or workarounds that you would like to share, feel free to leave a comment and I will get it added to the list.

ESXi Embedded Host Client Fling updated to v2

by // 13 Comments

The response and feedback from our customers on the recently released HTML5 Embedded Host Client for ESXi Fling has just been absolutely phenomenal. Having only been released for a little less than two weeks ago, it has also become the #1 Fling on the VMware Labs which is an amazing accomplishment in it itself as well as to the awesome work from both the Engineers: Etienne and George. 

Having said that, both Etienne and George have not stopped and have been quite busy in the last couple of weeks. They have been working adding new features based on feedback from our customers as well as any bug fixes that have been reported. Today, I am please to announce that they have just released version2 of the Embedded Host Client for ESXi which you can find here. If you have v1 installed, you can perform an "update" by running the following ESXCLI command:

[root@mini:~] esxcli software vib update -v /esxui-3015331.vib
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_bootbank_esx-ui_0.0.2-0.1.3015331
VIBs Removed: VMware_bootbank_esx-ui_0.0.2-0.1.2976804
VIBs Skipped:

In addition to the new features listed below in v2, I would also like to mention we now have both an installable VIB as well as an offline bundle as some of you have been asking for which will allow you to use vSphere Update Manager (VUM) to automate the deployment of the Embedded Host Client across your ESXi hosts.

What's new in v2:

  • Host
    •  Improved host performance monitoring UI
    • Composite CPU/memory figure
  • Virtual Machines
    • VM Snapshot support.
    • In-browser VM console full screen support.
    • In-browser VM console 'shrink’ support.
    • Create Wizard: Mac OS guest creation has been enabled.
  • Storage
    • Completed file browser (copy/move/delete/create directory/upload/download)
    • Right click on VMX file in browser to register VM
    • Mount/create NFS datastores
    • Create VMFS datastore (currently only on disks that don't have a partition table)
    • Extend VMFS datastore (currently only onto disks that don't have a partition table)
    • Mount/Unmount VMFS datastore
  • Networking
    • Firewall ruleset listing (currently read-only)
  • General Features
    • Double click title bar to enlarge dialogs and wizards
    • Alt + drag in a dialog or wizard to resize
    • Locale override (we still only support en-US at this stage)
    • Customizable session timeout.

I have already deployed the latest version in my lab and I have to say, the new features rock. One tiny little feature which I really like is a session timeout count down which appears on your browser tab of the Embedded Host Client when left idle.

Screen_Shot_2015-08-24_at_9.23.29_AM_stream
In my opinion, the attention to details both big and small is what really differentiates this UI from any other that I have used and really provides for a fantastic user experience. Keep up the great work guys!

If you have any feedback, please leave a comment either on my blog or on the Fling site and who knows, your request might just make it into the next release 🙂