new1234.jpg

Archive

Posts Tagged ‘vSphere Client’

VMware: VMware Remote MKS has stopped working

November 3rd, 2016 No comments

Running vSphere Client 6.0.0 build 2741530. Sometimes when opening the remote console, during boot virtual machine the resolution is swapping from small to a bigger resolution.

App crash with details:

vmware-remotemks.exe version 8.0.0.33578

 

Solution

Update the VMware vSphere cliënt, in my case to version: 6.0.0-3562874

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Installing VMware vSphere Client 4.1 or 5.0 on Windows 8.1

January 15th, 2015 4 comments

Today I tried installing VMware vSphere Client 4.1 on my Windows 8.1 update 1 workstation and I received this error message:

This product can only be installed on Windows XP SP2 and above.

 

image

 

Solution

1. Download the vSphere ClientCLient installer

2. Properties > Compatibility > Run this program in compatibility mode for: Windows XP SP2

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Alias value is empty when attempting to log in to VMware vCenter Server 5.5

January 12th, 2015 No comments

image

 

A general system error occurred: alias value should not be empty

 

Cause

This issue occurs when the Active Directory Identity Sources are not available.
This issue may also occur while SSO is starting up, or for a period of time after start-up. This occurs when the number of domains in the Active Directory forest is large.

Resolution

This is a known issue affecting:

  • VMware vCenter Server 5.5.0b (Build 1476327)
  • VMware vCenter Server 5.5.0 Update 1 (Build 1623101)
  • VMware vCenter Server Appliance 5.5.0b (Build 1476327)
  • VMware vCenter Server Appliance 5.5.0 Update 1 (Build 1623101)

This issue is resolved in vCenter Server 5.5 Update 2, available at VMware Downloads. For more information, see the Resolved Issues section in the vCenter Server 5.5 Update 2 Release Notes.

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

XP can’t connect via vSphere 5.5 client

December 16th, 2013 9 comments

Last week I added some new vSphere 5.5 host in a new configured cluster, the customer is still using Windows XP SP3 32-bit, he received this error message:

 

image

An unknown connection error occurred. (The Client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.

 

Reason:

This issue occurs due to increased security of the cipher strengths which are, by default, used by the VMware Management Web Services components. Due to this change that was introduced in vSphere 5.1, the host operating system is required to support a higher cipher strength to be able to connect to these components.

In Windows Vista and Windows Server 2008, the proper cipher strengths are built into the operating system. However, for older Windows operating systems, a Microsoft hotfix must be applied to add the supported cipher strengths.

For more information on the cipher strengths that get added with the hotfix, see the Microsoft Knowledge Base article 948963.

 

 

Solution:

Windows 2003 (32-bit and 64-bit Edition)

For Windows Server 2003 (32-bit and 64-bit), apply the appropriate hotfix to the machine on which the vSphere Client is installed.

Note: If the vSphere Client is installed on the Windows Server where vCenter Server is installed, you must also apply the patch to that Windows Server.
To download the hotfix for your system, see the Microsoft Knowledge Base article 948963.

Notes:

  • You must reboot the machine after applying the hotfix.
  • Non-English versions of the hotfixes are also available on the Microsoft site. Click the Show hotfixes for all platforms and languageslink on the Hotfix Request page to view the available versions.

Windows XP (32-bit)

There is no hotfix available for Windows XP (32-bit). Microsoft currently only provides limited support for Windows XP, and as a result the hotfix has not been released for it. To resolve this issue, you must upgrade your host operating system to Windows Vista or later, which support the use of high cipher strengths.

If you are unable to upgrade your environment, you may try adding less secure cipher strengths back to the configuration, which allows communication to proceed successfully.

To add less secure cipher strengths back to the configuration:

Caution: This is not a recommended configuration and is provided for backward compatibility purposes only. This is not extensively tested and is supported on a best effort basis only.

  1. Log in as an administrator to the server where vCenter Server 5.1 is installed.
  2. Navigate to the tomcat configuration directory.
    Note: By default, this directory is located at C:\Program Files\VMware\Infrastructure\tomcat\conf\. In vCenter Server Appliance, the file is located at /ur/lib.vmware-vpx/tomcat/conf.
  3. Open the server.xml file using a text editor.
  4. Change the Connector text to add support for weaker ciphers by changing it from:
    <Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"></Connector>
    To:
    <Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA ,SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"></Connector>
    Note: Add only the red text as indicated and do not change any other options. This adds back support for less secure cipher strengths for backward compatibility purposes.
  5. Restart the VMware VirtualCenter Management Web Services service. For more information, see  Stopping, starting, or restarting vCenter services (1003895).

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2 (1011329)

November 13th, 2009 No comments

We already posted a solution. This is the official unofficial unsupported VMware KB

  • You cannot launch the vSphere Client
  • If you install the vSphere Client in Windows 7 or Windows 2008 R2 and try to connect to the vSphere server, you see the errors:
    • Error parsing the server "<servername>" "clients.xml" file.
    • The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.

The vSphere Client is not currently supported in Windows 7 or Windows 2008 R2 and it does not run in Compatibility Mode.

This issue may occur because of the .NET loading mechanism change in Windows 2008 R2 and Windows 7.

There are 2 possible workarounds. Perform one of these options:

  • Install a Windows XP virtual machine in Windows 7 or Windows 2008 R2 using Windows XP Mode.
  • Bypass the normal .NET Framework loading mechanism.
    Warning: This workaround is unsupported.
    To bypass the normal .NET Framework loading mechanism:

1. Download the file system.dll. This file is typically located in  %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non-Windows 7 or Windows 2008 R2 machine with .NET v3.5 SP1 installed.

2. Copy the file to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib.
Note: If the lib directory does not exist, create it.

3. Open VpxClient.exe.config in a text editor. The file is located at C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher.

4. Add the following three lines to VpxClient.exe.config, just before </configuration>:
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>

5. From Windows 2008 R2 or Windows 7 System Properties, click the Advanced tab > Environment Variables.

6. Create a new System variable called DEVPATH and assign the value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Note: For 32bit operating systems, replace Program Files (x86)with Program Files.
You can now launch vSphere Client from a Windows 7 or Windows 2008 R2 machine. You may have to right-click on the vSphere Client icon and choose Run as administrator.

VMware: Get a vSphere Client working on a Windows 7 machine

November 5th, 2009 No comments

It’s very easy..

Install the VMware vSphere Client by default from CD or from your ESX host.

Download viclient_fix.zip

Move and replace the content in “C:\Program Files (x86)\VMware\Infrastructure\”

Open the “VMware vSphere Client” from the directory

image

It’s working great! 🙂

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: The requested operation is not implemented by the server

September 9th, 2009 No comments

By connecting a single host or VC with VI Client I receive this error: “The requested operation is not implemented by the server”

image

My Virtual Infrastructure Client is configured with PassThroughAuth parameter set for Auto SignOn capabilities. With parameters: "D:\APPS\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" -passthroughauth -s localhost

 

Solution: Use the Shortcut in your Menu Start > VMware > “VMware Infrastructure Client” of delete the passthroughauth parameter in the shortcut/target field.

Now I can connect my VC/Host with the VI Client without problems.

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn