Vsphere web client linux

vSphere Client on the Linux Desktop

A lot of linux users are looking for a way to run .Net applications on their desktop, too. Since Wine does not provide the ability to do so and running an entire VM to use the complete Windows Desktop is an annoying option, these users are looking for a better solution. For Example the VMware vSphere Client, which requires .Net Framework and does not come as a Linux Version, forces Users and Admins to step back to Windows. But using Seamless RDP by Cendio, there is a way around this.

This Howto applies to Windows VMs running in background in any
virtualization product or physical systems alike. Also, this is of
course not limited to the VMware vSphere Client and can be used to run
any Windows application.

• On the Windows System (e.g. a VM or the VMware vCenter Server) download the GPL licensed SeamlessRDP Tool and extract it into a folder, e.g. C:\RDP

• Also, install the application you wish to use on your Linux Desktop

• Enable the Remote Desktop in System Settings — Remote tab — «Allow users to connect remotely to this computer.». You might want to create an extra user for the remote access and enable it to connect via RDP.

• Within the SemalessRDP folder, create a .bat file that runs your needed application, followed by the logoff command to make sure the session gets closed after usage. E.g: vsphere.bat:

«C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe»
logoff

• Install rdesktop on your Linux system, using the appropriate way for your distribution or sources from www.rdesktop.org. Make sure you are using at least rdesktop version 1.5.

• On your Linux Desktop, create a shourtcut for your Application, e.g. vSphere Client and call the following command from this shourtcut:

You can of course create an extra user for the remote access and need
to insert the appropriate IP Address and Batch file to call. In my
vSphere example this looks like:

rdesktop -A -s «C:\RDP\seamlessrdpshell.exe C:\RDP\sphere.bat» 192.168.1.23 -u remote -p remoteP@55

• On running the shourtcut from your Linux desktop, rdesktop will initialize a seamless session to the Windows system, start the batchfile to open the vSphere Client, and present only the application Window to our Linux Desktop.

So far this is probably the best solution we have to bring the VMware vSphere Client to the Linux Desktop. Enjoy.

Источник

Is there a vSphere Client for Linux and Mac?

If you are using a Linux-based pc or Mac OS X and want to manage a vSphere-environment then you might ask yourself the question if there is a native OS-version of the vSphere Client available for your platform.

The short answer is: no.

The longer answer is: do you need one? And is there an alternative? For most day to day operations you should move to the vSphere Web Client. And you can access that from your Linux system and Mac OS X. The only problem with that is that it only works with vCenter. So what do you do when your vCenter server is down or what to do if you only have one ESXi server?

There are a few tools that you can use to make administration for your environment simpler. But you would always need the vSphere Client on Windows at least once after installation of ESXi to for example import the vCenter Virtual Appliance (explained here) Or to create a virtual machine.

It is also possible to import the appliance from the command line with VMware’s OVF Tool, which is available for Linux and Windows. How to do this is explained in this article.

Run a Windows VM in Player, Workstation or Fusion

To work with the full vSphere Client on Windows you can run it in a Windows virtual machine or from a physical Windows computer to configure the ESXi-host and create virtual machines. I personally run openSUSE and work with Linux for the largest part of the day. But from time to time there are Windows-based applications for which there really is no alternative and for those cases I have a Windows VM on my laptop.

Access your VM-console from Linux or Mac OS X with a VMware Player-console

Once your ESXi-host is up and running and you have multiple virtual machines running and maybe also vCenter deployed as a virtual appliance then you can access the console of those virtual machines with VMware Player. This tool is available as a download for Windows and Linux (www.vmware.com/go/downloadplayer) and it’s included with Mac OS X.

With VMware Player installed you can run it from the command line and connect to an ESXi-host:

This will open a VMware Player window and requests login to the host. You can provide the host’s IP-address with the -h parameter but if you leave it out you can enter it with the user credentials.

Once you are logged in you will see a list of available virtual machine. If the VM is not powered on and you open a console to the VM it will be powered on. If it’s already running you can connect directly to the virtual machine. In the image below you see a VM running Windows. It also has the vSphere Client to allow you to manage the ESXi-host.

Host management with SSH and vCLI

You can also perform some management tasks from an SSH-connection to your host. You must enable your SSH-server on the ESXi-server before you can do this. You can enable this from the vSphere Client or from the Direct Console User Interface (DCUI) on the server’s console. Once you have access with SSH and you want to use the DCUI for configuration purposes you can type this command:

And it will open the menu-based console in your SSH-session. To close it press ctrl-c.

Источник

VSphere Web Client

This page is NOT an official VMware document. It is intended for vSphere Web Client users to share tips. Feel free share this page with anyone who could use or contribute to it. Please attribute where applicable.

Change lists should be added to the discussion list.
Highly Recommended tips are marked with *

This page can also be accessed by going to

VMworld 2015 — INF5093 — vSphere Web Client — Yesterday, Today and Tomorrow

Video also accessible through shortlink

Contents

Learning Web Client — Where things have moved to in Web Client relative to the Desktop Client [ edit | edit source ]

This is a list of items that have moved (or may be hard to find in Web Client) from where they used to be in the Desktop client.
Here, Home refers to the main Web Client login page. These things are accessible under the vSphere 6 Home menu.
[vCenter] means when you’ve selected a specific vCenter, and you can access its ‘Summary/Manage/Monitor’ tabs in the center workspace.
[VM] means the same thing for a VM (also for a cluster, host, any object).

• Licensing: Home -> Administration -> Licensing
• Sessions (logged in users) — [vCenter] -> Manage -> Sessions
• VMs belonging to a host — [Host] -> Related Objects -> Virtual Machines
  • This is generally true for all objects, they’re under Related Objects
• Batch Actions — If you select multiple objects (using Ctrl+ or Shift+ in a list (Related Objects -> VMs for example), you can then right click and perform some simple batch actions, like Power On VM
• webclient.properties on Server Appliance (VCSA) has moved — on vSphere 6 it is at: /etc/vmware/vsphere-client/webclient.properties
• Enable/Disable Services (including SSH) on a Host — This is now located in [Host] -> Manage -> Settings -> System -> Security Profile -> Services -> [Edit]. You can also set the service startup policy here.

TBD — please feel free to add entries for these features, and remove them from this list [ edit | edit source ]

Live refresh of Recent Tasks in 6.0U1 [ edit | edit source ]

Adding this setting into the webclient.properties file will allow tasks to be refreshed immediately and automatically across different Web Client instances. [1]

Working on a small screen [ edit | edit source ]

If you’re working on a small screen, such as a laptop with a pretty standard 1366×768 resolution, things can be kind of cramped, both vertically and horizontally. Browser zoom seems to work pretty well! 90% or 75% seem pretty legible, and provide quite a bit more room.

I tried it on Chrome, and IE11 and they seemed to work fine, though zoom shortcut keys may not work due to Flash capturing the events, you’ll probably have to go to the menu to change the zoom percentage. Firefox didn’t seem to work at all.

Re-enable NPAPI on some Chrome versions (used for vSphere 5.5 Client Integration Plugin) [ edit | edit source ]

Chrome disabled NPAPI by default on the newest versions of Chrome. This affects the Client Integration Plugin (CIP), which adds in functionality such as OVF deploy, Windows authentication logon, and others. It used to contain VMware Remote Console (VMRC), but that now is a separate downloadable for Windows and OSX.

You can re-enable NPAPI by typing: chrome://flags/#enable-npapi into the URL bar and clicking «Enable».

This is not necessary for vSphere 6 as the CIP for vSphere 6 has no NPAPI dependency.

Collect CIP Logs for debugging required by VMware [ edit | edit source ]

Sometimes during discussion with folks from VMware they might ask for CIP logs, here is how to provide them. Enable trivia logging for CIP operations in vSphere Web Client: https:// /vsphere-client/?csp&logLevel=trivia&debug=true

Mac: /Applications/VMware Client Integration Plug-in.app/Contents/Library/data/

Customize vSphere 6.0 Web Client login UI [ edit | edit source ]

Allows you to customize the background and text of the Web Client login page [2]

Maximize a wizard by double-clicking the titlebar/header [ edit | edit source ]

Hierarchy button, located on top right of the workspace (central panel) [ edit | edit source ]

Allows you to see full hierarchy of an object (screenshot needed).

Accessing vSphere Web Client no longer requires adding the port number «:9443» [ edit | edit source ]

So just go straight to https:// /vsphere-client/, but it still works with «:9443», so feel free to leave it in (and not have to update your shortcuts/bookmarks).

Aggregation Threshold — Annoyed by the Client collapsing lists into single lines? [ edit | edit source ]

In vSphere 5.5 this limit was 20. In vSphere 6 this is (default for VMs) 100 and configurable in the webclient.properties file, search for «aggregationThreshold»

Collapse portlets to improve load time and save space [ edit | edit source ]

To improve load times and save space (at the cost of displaying information without additional clicks), you can set it so that all of the collapsable portlets in the workspace area are closed by default. go to webclient.properties and find «portlets.collapsed». This only works on vSphere 6.

Configuring a vSphere 6 VCSA/vCenter Server Appliance as a Web Client Appliance [ edit | edit source ]

If you don’t want to unnecessarily dedicate resources to the vCenter 6 installation in a Mixed Version environment, William Lam has created some instructions for thinning this vCenter down on resources, and de-registering it so it doesn’t show up in the interface. This still leaves the Web Client instance working. COMPLETELY UNSUPPORTED: http://www.virtuallyghetto.com/2015/04/configuring-vcsa-6-0-as-vsphere-web-client-server-for-vsphere-5-5.html

Block Desktop/C# client from vCenter Server [ edit | edit source ]

These instructions are probably for vSphere 5.5, but the file locations should be similar.
Go to:

• Windows: C:\ProgramData\VMware\VMware VirtualCenter\docRoot\client
• VCSA: /etc/vmware-vpx/docRoot/client

And edit the «version.txt» file so that the «exactVersion» number is something unrealistically high (like 9.0.0 as suggested in the post). This will force any Desktop/C# client installation to be recognized as an «incorrect version», prompt the user for download, but the new install will also fail to connect.
http://www.virtuallyghetto.com/2012/12/blocking-vsphere-c-client-logins.html

Increase refresh rate of Recent Tasks independently of global-auto refresh [ edit | edit source ]

In the webclient.properties file there is a line

Where the time is the number of seconds between Recent Tasks automatically refreshing. Lowering this to 10 (minimum) will get it refreshing as often as possible. This may have a significant performance effect on your environment though, especially with large number of users and tasks

Work in Progress — Save Wizards progress for later (vSphere 5.5) [ edit | edit source ]

The double arrow on the top right of most wizards allows you to minimize the wizard, saving your work. You can then recall the wizard at a later time, and this state is saved after you log out.

vSphere Web Client 6 [ edit | edit source ]

Fastest way to get Web Client 6 — Mixed Version Transitional Environment* [ edit | edit source ]

Since upgrading vCenter infrastructure is a long and scary process, the fastest way to get the new Web Client is to (this only works with external SSO):

1. (optional) Create a new vCenter 5.5 with no inventory, and point it to your existing external SSO
2. Upgrade your external SSO to vSphere 6 PSC
3. Upgrade a vCenter 5.5 (the one in the first step, preferably) to vCenter 6

Connect to the new vCenter 6 and you should see the inventory from your old vCenter 5.5 instances (this is called «Enhanced Linked Mode» by VMware).

This environment would be called a «Mixed-Version Transitional Environment» [3]

William Lam detailed this on a blog post, with additional (unsupported) instructions for minimizing the footprint of the new/empty vCenter 6:
http://www.virtuallyghetto.com/2015/04/configuring-vcsa-6-0-as-vsphere-web-client-server-for-vsphere-5-5.html

Enhanced Linked Mode / Single Pane of Glass [ edit | edit source ]

vSphere 6 has a new version of linked mode that allows you to see all of your inventory from a single view, as long as all the vCenters are joined to the same Platform Services Controller (PSC). This should be automatic once you’ve joined the vCenters to the same PSC, and logged into Web Client. This is not available to the vSphere Client for Windows. Some documentation available here: [4]

Access a Virtual Machine’s HTML5 console [ edit | edit source ]

Previous versions of vCenter Web Client presented the two available console technologies (VMware Remote Console/VMRC, or HTML5/webmks) differently than in vSphere 6.
BONUS: the links generated by either can be shared with end users! (pending credentials)

For clarity, here is how the two consoles are accessed from a VM’s summary tab.

Access the HTML5 console by clicking the VM thumbnail — this should work directly on any platform with any modern browser.

Access the VMRC console by clicking the «Launch Remote Console» link — this will only work if you have the VMRC plugin, or VMware Workstation (maybe Fusion?) installed.

Unofficial list of what’s new in Web Client 6 [ edit | edit source ]

• Customizable UI – Allows users to customize their interface by moving various elements around (navigation, tasks and alarms, recent tasks) and resizing them
• Configurable tasks refresh – Allows users to tweak their Recent Tasks refresh timer so that they can control the balance between performance of vCenter and live-ness of tasks (in webclient.properties)
• Configurable object “roll-ups” – previous to vSphere 6, more than 20 objects would not be listed in the lefthand navigation pane. This has become a configurable setting, allowing users to further customize their experience. Also default at 100 now (in webclient.properties, set to 0 for never «roll-up»)
• Improved Action Menus/Right click Menus – These menus were changed to improve both usability and familiarity, which should ease the transition from Windows Client/C# to Web Client.
• Improved navigation at top level – the common views of “Hosts and Clusters”, “VMs and Templates”, “Storage”, and “Networking” have been brought to the top level of the Navigator, making the much easier to find
• Home button navigation – Users can now go from anywhere in the UI straight to one of the standard views with 1 click.
• Persistent settings – the UI now remembers on the server many of the UI customizations you have made (such as columns selected, and column widths)

vSphere Web Client 5.5 [ edit | edit source ]

Many of these tips should work for releases after 5.5 as well.

Global [ edit | edit source ]

Recommended Browser [ edit | edit source ]

VMware recommends Chrome and Internet Explorer over Firefox for performance [5]
With the release of vSphere 6, retesting shows that this may no longer be true. All browsers seem to have similar performance numbers.

Linux — Using vSphere Web Client on Linux through Chrome [ edit | edit source ]

VMware doesn’t currently support any browser for vSphere Web Client on Linux, but Chrome (with its built-in Pepper Flash plugin) should work out of the box! [6]

Configure/Increase Web Client Session Timeout [ edit | edit source ]

Step 1 — Locate the webclient.properties file:

vCenter Server Appliance (VCSA v5.x) vCenter Server Appliance (VCSA v6.x) Windows vCenter Server

Step 2 — Un-comment and change session.timeout value to desired value:

Step 3 — Restart the vSphere Web Client Service:

You will need to restart the vSphere Web Client service for the changes to go into effect. For the Windows vCenter Server, just restart the vSphere Web Client service (either from Task Manager or services.msc) and for the VCSA, run the above command. [7]

Monitoring [ edit | edit source ]

All Users’ Tasks (Recent Tasks) [ edit | edit source ]

You can view tasks from All Users in the «Recent Tasks» pane by changing the view. Click on the drop-down and select which one you want. [8]

Navigation [ edit | edit source ]

History * [ edit | edit source ]

Access your navigation history, like the browser back button. [9]

Recently Visited & Created Objects (Recent Objects) * [ edit | edit source ]

View (and jump to) recent objects [10]

Related Objects: Finding Datastores connected to your VM * [ edit | edit source ]

Have you ever had trouble finding all of the datastores connected to a particular VM, the VMs that are in a cluster, or any sort of list of objects that have any relation to the object you’re looking at?
They’re all under «Related Objects», a great way to find all of the connected to a particular object.

Bookmarks * [ edit | edit source ]

You can bookmark things on vSphere Web Client so that you can return to them quickly, or share them with others. This should work with almost every view, and even with specific objects! Take this one step further, and you can set one of these bookmarks/URLs as your homepage or the link you click to get to vSphere Web Client, if there is a common view or object you work with frequently. [11]

Shortcuts [ edit | edit source ]

Saved Searches [ edit | edit source ]

Access your saved searches by clicking the arrow on the right side of the search bar [12]

Quickly Schedule Tasks [ edit | edit source ]

Hold down «Ctrl» in the action menus (right click menu) in the vSphere Web Client to quickly schedule tasks [13]

Quick Filters [ edit | edit source ]

On many lists of objects you will see the icon below, which after clicking you will see the menu of items called «Quick Filters».
Using these filters makes it easy for you to reduce your list and find the object(s) you are looking for. [14]

Shortcut Keys * [ edit | edit source ]

Access various inventory pages using shortcut keys: [15]

Keyboard Combination	Action
Ctrl+Alt+s	Quick Search
Ctrl+Alt+Home OR Ctrl+Alt+1	Home Screen
Ctrl+Alt+2	Virtual Infrastructure Inventory
Ctrl+Alt+3	Hosts and Clusters Inventory
Ctrl+Alt+4	VMs and Templates Inventory
Ctrl+Alt+5	Datastores and Datastore Clusters Inventory
Ctrl+Alt+6	Networking Inventory

Peformance Impacting Tweaks [ edit | edit source ]

Some of these changes may impact your Web Client and/or vCenter Server performance. This is likely to be worse with:

• larger inventory of objects
• more simultaneously logged in users
• higher frequency of tasks executed

Configure Auto-Refresh & Disable Inventory Navigator Animation [ edit | edit source ]

Enable and tweak Web Client autorefresh time. [16]

To enable auto-refresh, you will need to locate the webclient.properties configuration file:
/var/lib/vmware/vsphere-client/webclient.properties on the vCenter Server Appliance
C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\webclient.properties on vCenter Server on Windows

By default the auto-refresh is disabled, to enable it, you will need to un-comment the following configuration parameter and set the number of seconds to auto-refresh:

Performance Improving Tweaks [ edit | edit source ]

Java heap sizes for Tomcat server [ edit | edit source ]

Adobe Flash Player Local Storage Settings * [ edit | edit source ]

Occasionally you may run into this warning:

The easiest way to fix this is to go to this website:
Macromedia Website Storage Settings panel
And increase your storage settings for the appropriate site/domain name/IP address for your vCenter Server by selecting it from the list, and sliding the setting all the way to the right. [17]

Troubleshooting [ edit | edit source ]

Error #1009 [ edit | edit source ]

The fairly cryptic «Error #1009» is actually not a vSphere Web Client-specific error code, but a general ActionScript (Flash-related) error, caused by some kind of problem in the Web Client. Because of that, just the error code itself isn’t nearly enough for root causing the problem that you are seeing, because it’s not really telling anything specific about the related Web Client problem. The stack trace shown after clicking «Show error stack. » in the error dialog in the vSphere Web Client should be present in the Web Client’s Flash-related, browser-captured logs which are gathered like: VMware KB: Troubleshooting the vSphere 5.x Web Client [18]

Источник