We will continue delivering this Fling on a regular basis even with the released supported version of the vSphere Client, so we hope that most of you will continue to use the Fling and update it weekly so that we can get your feedback about our direction.
You can find a summary of changes in all the clients available in vSphere 6.5 in this blog post – What’s new in vSphere 6.5: vCenter management clients. In the blog, you can also find a link to all the features that are not available in the GA version of the vSphere Client and link to frequently asked questions on all the vSphere Clients.
We would also like to thank all of you that have tried the Fling and have provided us feedback, we would not have achieved the progress we have without your engagement.
For partners who want to extend the HTML Client, this Fling also includes a new HTML SDK. Please see the HTML Client SDK Fling Overview.pdf and download the html-client-sdk.zip.
- Linux will show a warning on the login page about being unsupported, but the Fling should still work after login
- Bug: Unpatched versions of IE can fail to login and end up at URL “vmware-csd://csd”: This is a known vCenter 6.0 bug that we cannot patch with this appliance. The KB and fix are located here: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2109554
- Bug: If the client page is visited before the server has fully started, sometimes the strings do not load and you will see things like “summaryView.guestFullName” in views or in action menus. Refreshing the page may fix this, but restarting the appliance server with: “/etc/init.d/vsphere-client restart” should definitely fix it.
- This client is designed for managing vCenter. If you are looking for the Host Client you can find it as “ESXi Embedded Host Client” (https://labs.vmware.com/flings/esxi-embedded-host-client).
- The new visual theme is called “Clarity”, and is also still in development. We will be fixing UI bugs and subtly changing the look and feel to fit the new Clarity standard.
- The appliance requirements are recommended settings. It should still work at lower settings, but performance may be impacted.
- The root password on the appliance is ‘demova’ (without quotes). If you enter the wrong password too many times you will get locked out. The easiest way to fix this is to redeploy the appliance from the OVA.
- HTML Client SDK Fling Overview and Release Notes-5097204.pdf.
- Create a new certificate for a HTML5 client fling v3.pdf.
- H5 Client Deployment Instructions and Helpful Tips_v27.pdf.
VMware Fling page
Download h5ngcVA-18.104.22.168-5130996_OVF10.ova from vSphere HTML5 Web Client Fling page.
See previous HTML5 Web Client v2.5
Any customer who would like to see the complete picture of all the products installed in their deployment or get specific product information like version, IP address, VM name etc., can use this tool. The tool persists all the discovery results so that the user can see what has changed in their deployment over a period of time. Users can also toggle between ‘VC view’ which shows what products are managed by what product and ‘Host view’, which shows which host each of the products is running on.
- The PSC’s hosted in the environment are discovered but the vCenter Server and PSC relationship is not computed hence the relationships of VC <-> PSC might not be accurate.
- The tool doesn’t consume vCenter Server Extension APIs hence it doesn’t detect any 3rd Party solutions managed by the vCenter Server.
- Any standard system running Windows, Mac OS or Linux.
- Any modern web browser (tested with Chrome and Firefox). NOTE: minimum browser window size of 1024 X 768 is recommended.
- Access to a vCenter server 5.0 or above to initiate discovery.
- 1. Download the appropriate Windows, Mac OS or Linux sddc_discovery_1.0.zip deliverable.
2. Extract the contents by unzipping the package.
3. Start the app server as below:
– Double click the sddc_discovery.exe executable file in the extracted folder to start the server
Linux and Mac:
– Navigate to the extracted directory and execute the command “./install.run” to start the server
4. At this point the server is started and the application should be accessible on 127.0.0.1:XXXX (typically 1024). The Windows machine should directly launch the application on the browser whereas Mac and Linux users may have to manually navigate to 127.0.0.1:XXXX to launch the application. NOTE: The terminal where the server was started should output the url where the application is accessible.
5. Once EULA is accepted, users will be navigated to the dashboard page. Typically the table is empty as no discoveries have been performed yet.
6. Navigate to the discovery page and trigger discovery by providing VC credentials that need to be probed.
7. Upon successful discovery, the user is navigated to summary page where all the discovery results are presented.
8. All the successful and failed discoveries are persisted and are shown on the dashboard page.
Download SDDC Discovery Tool VMware FLINGS.
Using a supported storage controller and firmware is important in a VSAN deployment to ensure normal operations, optimal performance, and to reduce the chances of hardware/firmware issues. This tool can be useful to ensure that a storage device and its firmware went through certification testing supported by VMware and its partners.
Some scenarios where the tool can be useful:
- Verify if new server and storage adapter are supported for a VSAN deployment
- Verify if re-purposed server, storage adapter are supported for a VSAN deployment
For a full VSAN system check, please install the VSAN Health Check Plugin after a VSAN deployment.
- Windows: XP, 7, 8, 10, Server 2008, 2012
- Browser: IE 8 and above
- HTTPS/443 access to ESXi hosts (interacting with hostd)
- TCP/5989 access to ESXi hosts (CIM service secure)
- Internet HTTP/80 access to http://partnerweb.vmware.com/service/vsan/all.json (optional)
ESXi Host Requirements
- ESXi 5.1.x, 5.5.x, 6.x are supported
- Direct access to the hostd service with username and password
- CIM service (secure) running on port 5989
- CIM provider for HP or LSI controller
- Extract the contents and double-click on hclCheck.exe
hclCheck [-h] [–hostname hostname [hostname …]] [–username USERNAME]
[–password PASSWORD] [–hcl-url HCL_URL]
Check ESXi host against VSAN HCL
-h, –help show this help message and exit
–hostname hostname [hostname …]
Hostname/IP of ESXi host
–username USERNAME Username (default: root)
–password PASSWORD Password
–hcl-url HCL_URL URL to VSAN HCL DB (http://path/to/hcl.db or file:///C:/path/to/hcl.db)
Download VSAN Hardware Compatibility List Checker v7 VMware FLINGS.
First things first– this Fling is not fully complete. We wanted to get it in front of our customers as soon as possible, and so we are only offering the following features for the time being (we feel that these are the most commonly used actions/views):
- 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)
This Fling has been designed to work with your existing vSphere 6.0 environments. The new client is deployed as a new VM from the downloadable OVA. Currently the installation instructions are command line-based, but we are working on a GUI installation and plan to release it as an update to this Fling once it is ready.
We intend to regularly update this Fling to both provide new features and address reported issues, based on feedback. When providing feedback, please provide as much detail as possible to help us understand and fix any issues.
- Firefox and Chrome are most compatible with this Fling. IE11 should also work with no issues. We have tested with Safari and Edge as well.
- Linux will show a warning on the login page about being unsupported, but the Fling should still work after login
- Bug: Unpatched versions of IE can fail to login and end up at URL “vmware-csd://csd”: This is a known vCenter 6.0 bug that we cannot patch with this appliance. The KB and fix are located here
System requirements – 2 vCPU, 4 GB RAM, 14 GB
- 2 vCPU, 4 GB RAM, 14 GB
- An existing VC6.0 installation (VCSA or Windows). The H5 client appliance will need 4 GB RAM, 2 vCPUs and the hard disk will grow up to 14 GB.
- Recommended browsers: Chrome, Firefox, IE11. Others may work, with some functional or layout issues.
- Windows vCenter: Was tested with a vCenter on Windows Server 2012 R2, but should work with other versions as well. Please report any issues.
- HTML Client SDK Fling Overview.pdf.
- HTML Client SDK Fling Overview and Release Notes.pdf.
- H5 Client Deployment Instructions and Helpful Tips_v22.pdf.
This guide provides the necessary information for optimizing a Windows virtual desktop or server master image for use in View in Horizon 6 or Horizon 7, or in Horizon Air Cloud-Hosted. The document is a companion to the VMware OSOT Fling (Operating System Optimization Tool version b1057). The document describes optimizations for Windows 7, Windows 8, Windows 10, Windows Server 2008, and Windows Server 2012. These recommended optimizations enhance the overall scalability and performance within a View virtual desktop infrastructure or Horizon Air cloud tenant environment.
VMware Operating System Optimization Tool
The free OSOT makes it easy to apply configuration settings to desktops and servers. It includes settings to optimize the following Windows operating systems for both desktops and servers that reside in the data center and in the cloud:
- Windows 7
- Windows 10
- Windows Server 2008 (including R2)
- Windows Server 2012 (including R2)
- The OSOT does not support optimizing Windows Server 2008 or 2012 when those operating systems are used as single-session desktops.
- The optimization information in this guide does not pertain to Windows XP, which Microsoft no longer
supports. For more information, see the Windows XP Deployment Guide.
This guide is written for data center administrators and IT personnel who want to optimize Windows operating systems. The guide assists you in working with the OSOT, and provides an ongoing reference as you become a more proficient OSOT user. VMware will periodically update this document to reflect continuing enhancements to the OSOT and future releases of the Windows operating system.
Windows was designed for physical hardware, specifically desktops, and for that hardware to be accessed by just one user at a time. Windows uses many resources to present a responsive desktop, but many of its settings are unnecessary or even detrimental when applied to a virtual environment. These actions include, for example, animating windows as the user opens them. Performing this animation takes significant CPU resources, which decreases the number of desktops that you can host per VMware VSphere® server. Consequently, this nonessential function in a virtual machine (VM) environment increases the amount of system hardware that you need. Even if hardware is plentiful, Windows animations do not perform well when accessed remotely, especially when connecting over a slow WAN or Internet connection. As a result, keeping animations enabled (in addition to other features unnecessary for VMs) impairs the end-user experience.
Another example of desktop optimization in a virtual machine environment is to disable Windows Update so that control of the service is isolated to administrators. Administrators can run Windows Update in batch mode for the VMs as opposed to users performing this task.
Download a full VMware Windows Operating System Optimization Tool Guide Technical White Paper.
These recommended optimizations enhance the overall scalability and performance within a View virtual desktop infrastructure or Horizon Air cloud tenant environment.
You can perform the following actions using the VMware OS Optimization Tool:
- Local Analyze/Optimize
- Remote Analyze
- Optimization History and Rollback
- Managing Templates
- Windows 7, Window 8, Windows Server 2008 R2, Windows Server 2012, Windows 10(Beta)
- NET Framework 3.5, SP1.
Note: .NET 4.0 does not cover .NET 3.5 SP1. If you have only .NET 4.0 or 4.5 installed, you still need to install .NET 3.5 SP1. By default .NET 3.5 is installed on Windows 7. For Windows Server 2008 r2, it’s a Windows feature and you can enable it without additional download.
Download VMware OS Optimization Tool.
- Download file from Download button
- Double-click to install. Follow instructions from there
For more information, please see the VMware Optimization Guide(PDF).
This video describes how to use Auto Deploy reference hosts to provision all target hosts with the same networking, storage, and other settings using host profiles.
About This Book
The VMware Auto Deploy Administrator’s Guide explains how to prepare your environment for VMware® Auto Deploy, and how to use VMware Auto Deploy for ESXi deployment. The VMware Auto Deploy Administrator’s Guide also includes a reference to deploy-cmd management commands and troubleshooting information.
This book is for experienced system administrators who are familiar with vSphere administration tasks and
datacenter operations and know how to use commands in scripts. A solid understanding of DHCP is essential.
Introduction to VMware Auto Deploy
VMware Auto Deploy supports automatic PXE boot (network boot using PXE) and customization of large numbers of ESXi systems. This chapter introduces Auto Deploy, discusses benefits and limitations, and gives an overview of the Auto Deploy architecture and the deployment process.
Auto Deploy Components
Auto Deploy allows rapid deployment and configuration of a large number of ESXi hosts. After a DHCP server has been set up, Auto Deploy PXE boots machines that are turned on with an ESXi image. Auto Deploy then customizes the ESXi systems using host profiles and other information stored on the managing vCenter Server system. You can set up the environment to use different images and different host profiles for different hosts.
ESXi systems booted through Auto Deploy have the same capabilities as other ESXi systems. However, because these systems depend on the Auto Deploy appliance and the vCenter Server system, some vSphere features might work differently than they work with stateful ESXi systems. See the VMware Auto Deploy Release Notes.
The Auto Deploy virtual appliance is based on the vSphere Management Assistant (vMA). vMA includes prepackaged software such as a Linux distribution, the vSphere command‐line interface (vCLI), and the vSphere SDK for Perl. Administrators can use the software to run scripts and agents to manage ESX/ESXi and vCenter Server systems. See the vSphere Management Assistant Guide.
In addition, Auto Deploy includes these components:
- The services required for performing the PXE boot and the auto‐configuration of the ESXi systems (DHCP, TFTP, NFS, HTTP, and so on)
- The deploy‐cmd command‐line interface for configuration and control (see “VMware Auto Deploy
Interfaces” on page 23 The deploy‐cmd database
- The image repository.
After an ESXi system has booted, the system contacts Auto Deploy. Auto Deploy manages configuration of the system by adding it to the vCenter Server specified in the boot profile and applying the specified host profile.
Auto Deploy Architecture
Figure 1‐1 is a static illustration of the components of the Auto Deploy virtual appliance and the vSphere
components Auto Deploy interacts with.
The Auto Deploy virtual appliance runs on a physical server (ESX/ESXi system) and includes components that support Auto Deploy. The physical servers are booted over the network. Auto Deploy first applies configuration stored on Auto Deploy through a boot profile and then applies configuration stored on the vCenter Server system.
Download out the full VMware Auto Deploy Administrator’s Guide.
This video explains the use of a management cluster to host infrastructure and Auto Deploy services to create a highly available Auto Deploy environment. You learn how to architect a management cluster and key benefits of setting up Auto Deploy in this way.
This video gives an overview of Auto Deploy, the new vSphere network boot infrastructure that allows rapid provisioning and configuration of ESXi hosts. It describes how Auto Deploy allows you to manage stateless hosts using centralized configuration.