Windows 7下不能使用VMware vSphere Client的处理办法

Windows 7下不能使用VMware vSphere Client的处理办法
案例1：
ESXi4安装好后(ESXi服务器的IP 192.168.15.101)，通过https://191.168.15.101进去下载了VMWare vSphere Client，安装后连接ESXi服务器的IP 192.168.15.101，居然连不通，系统提示“分析服务器"192.168.15.101"的"clients.xml"文件时出错。登录将继续，请联系系统管理员。”，点出确定之后继续报错“"VirtualInfrastructure.Utils.HttpWebRequestProxy”的类型初始值设定项引发异常。”，进而无法田连接到ESXi4。

经过多方努力，这一问题终得解决。原来是Win7下的Dotnet是3.5版本，而VMWARE的vShpere用的是Dotnet 2.0。解决方法如下：
1. 打开文件夹: C:\Program Files(X86)\Vmware\Infrastructure\Virtual Infrastructure Client\Launcher

2. 编辑文件 VpxClient.exe.config 增加如下内容（红色显示）：
















3. 创建一个文件夹，放dotnet2.0的 System.dll 放到新建的文件夹中。
C:\Program Files(x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib\
注意一下，这个里面说到的System.dll文件可以在XP等之类的装了.net 2.0的机器上复制到，具体位置位于
%SystemRoot%\https://www.sodocs.net/doc/848063690.html,\Framework\v2.0.50727\System.dll，Win7自带的就是.net 3.5了。

4. 编辑系统的环境变量，新增一个叫DEVPATH环境变量，值就是你放dotnet2.0的System.dll的目录，比如我的:
C:\Program Files(x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
现在，vSphere client 应该可以工作了。

5. 但是Host Update Utility 仍然不工作, 所以这里还需要附加的步骤来解决:
从C:\Program Files(x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\下拷贝VpxClient.exe.config file到如下位置, 并改名为VIUApp.exe.config:
C:\Program Files (x86)\VMware\Infrastructure\VIUpdate 4.0\
问题解决了。

另外，2010年6月这几天才出现这个问题的朋友请留意,造成问题的原因是安装了微软六月份
发布的补丁 .NET Framework (980773)。

将vSphere Client升级到4.0u1以上版本或则移除这个补丁后可以解决。
当然，把.net全部卸载了，重新安装2.0的也可以解决问题。

--------------------------------------------
vSphere Client on Win7
http://www.virtuallifestyle.nl/vsphere-client-on-win7/

Update: This page is outdated. On the 19th of November, 2009, VMware released VMware vSphere 4 Update 1. This release included an update to the vSphere Client, which makes it co

mpatible with Windows 7 and Server 2008 R2. You can download the client here.

Note that I left the original instructions, needed to get the pre-Update-1 version of the Client working below. They are not needed for the Update 1 version.

Update: The VMware KB team has released KB1011329, “Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2″, which basically explains the exact same workaround as I do below.

The best read blog post on Virtual Lifestyle is definitely VMware vSphere Client on Microsoft Windows 7!. Along with VMware vSphere Host Update Utility 4.0 on Microsoft Windows 7!, I explain how to get the VMware vSphere Client running on Microsoft Windows 7. To make it easy on everyone, I created a separate page from these posts. Now you don’t have to wade through the rest of my content to get to this post.

Running the VMware vSphere Client on Microsoft Windows 7
Automated with a PowerShell script
First off, I’ve attempted to automate this with my first ever PowerShell script. Download the script that does it all for you here. Please run this script with administrative rights (i.e. ‘Run as Administrator’). This script will work for x64 (64-bit) versions of Windows 7.


The manual steps are:
Copy System.dll (%SystemRoot%\https://www.sodocs.net/doc/848063690.html,\Framework\v2.0.50727\) from a non-Windows 7 system with Microsoft .NET 3.5 SP1 installed to the Windows 7 system (or download it here).
Place the file in C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib\.
Edit the VpxClient.exe.config file (C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\). You’ll need to do this as an administrator. Alternatively, you can download the edited file here. Add the red bit like this:














Make sure that the quotation marks are the correct ones (i.e. (“), not any of these (′) (″) (”) (“) (’) (‘) (′)), and that the … bit is in between the … part.

Add the DEVPATH variable via Control Panel → System → Advanced System Settings → Environment Variables to the User Variables. My layout prevents me from displaying the text in a single line. Please copy the text below to notepad, make a single line of it, and add is as a variable:
DEVPATH=C:\Program Files (x86)\VMware\Infrastructure\
Virtual Infrastructure Client\Launcher\LibReboot.
Running the VMware vSphere Host Update Utility on Microsoft Windows 7
Automated with a PowerShell script
With the script mentioned above, you’re all set. This script will also do the steps described below.

The manual steps are:
Copy VpxClient.exe.config to C:\Program Files (x86)\VMware\Infrastructure\VIUpdate 4.0\.
Rename VpxClient.exe.config to VIUApp.exe.config