{"id":423,"date":"2010-12-21T21:31:32","date_gmt":"2010-12-21T21:31:32","guid":{"rendered":"http:\/\/www.stevenwhiting.com\/blog\/?p=423"},"modified":"2011-01-06T14:40:37","modified_gmt":"2011-01-06T14:40:37","slug":"installing-the-vmware-vsphere-client-in-windows-7","status":"publish","type":"post","link":"https:\/\/stevenwhiting.com\/blog\/?p=423","title":{"rendered":"Installing the VMware vSphere Client in Windows 7"},"content":{"rendered":"<p>This is fixed in vSphere in 4.1 I think but I can&#8217;t get hold of it.<\/p>\n<p>So<\/p>\n<p><a href=\"http:\/\/www.youtube.com\/watch?v=-ys__7ga41E&#038;playnext=1&#038;list=PLEFC103E97FE8182C&#038;index=20\">http:\/\/www.youtube.com\/watch?v=-ys__7ga41E&#038;playnext=1&#038;list=PLEFC103E97FE8182C&#038;index=20<\/a><\/p>\n<p><a href=\"www.vmwarevideos.com\/vsphere-client-win7-system-dll.zip\">www.vmwarevideos.com\/vsphere-client-win7-system-dll.zip<\/a><\/p>\n<p>Copy .dll to <\/p>\n<p>C:\\Program Files (x86)\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\\Lib<\/p>\n<p>or <\/p>\n<p>C:\\Program Files\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\\Lib<\/p>\n<p>If Lib don&#8217;t exist, then create it.<br \/>\n<a href=\"http:\/\/www.techhead.co.uk\/running-vmware-vsphere-client-on-windows-7\"><br \/>\nhttp:\/\/www.techhead.co.uk\/running-vmware-vsphere-client-on-windows-7<\/a><\/p>\n<blockquote><p>Many of you, like myself, have started running Windows 7 as their primary desktop OS and find it to be a massive improvement over Windows Vista on so many levels.<\/p>\n<p>One of the very few inconveniences I have found with it, and this is not an bug or problem with Windows 7 itself, is the inability to run the VMware vSphere Client.<\/p>\n<p>UPDATE: Good News \u2013 This issue has now been resolved in VMware ESX\/ESXi 4.0 Update 1 (U1).<\/p>\n<p>When attempting to run the client the following errors are received and you are unable to proceed any further:<\/p>\n<p>\u201cError parsing the server \u201c<server name\u201d \u201cclients.xml\u201d file.\u201d\n\n \n\nError parsing the server \u201c<server name\u201d \u201cclients.xml\u201d file\n\n\u201cThe type initializer for \u2018VirtualInfrastructure.Utils.HttpWebRequestProxy\u2019 threw an exception.\u201d\n\nThe type initializer for \u2018VirtualInfrastructure.Utils.HttpWebRequestProxy\u2019 threw an exception\n\n \n\nLuckily there have been a few good VMware forum posts such as this one by ftubio which outlines how to successfully run the vSphere Client under Windows 7.  I thought I\u2019d put together this brief post with a few screenshots to outline the required steps.\n\nI am running the x64 version of Windows 7 so you will notice that any reference to the \u2018Program Files\u2019 will have an \u2018(x86)\u2019 at the end of it.  If you are running the x86 version of Windows 7 then ignore the \u2018(x86)\u2019 portion of the directory path (ie: C:\\Program Files (x86) \u2013> C:\\Program Files).<\/p>\n<p>Follow these 4 basic steps and you\u2019ll be up and running in no time!<br \/>\nStep 1.<\/p>\n<p>imageDownload this DLL called system.dll<\/p>\n<p>*Note:  This DLL is usually found in the  %SystemRoot%\\Microsoft.NET\\Framework\\v2.0.50727\\  directory of a non Windows 7 PC with  .NET v3.5 SP1 installed.<\/p>\n<p>Step 2.<\/p>\n<p>Once downloaded install it in the \u201cC:\\Program Files (x86)\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\\Lib\u201d directory.  If the \u2018lib\u2019 directory doesn\u2019t exist then create it and drop the dll file into it.<\/p>\n<p>VMware vSphere Client Windows 7<br \/>\nStep 3.<\/p>\n<p>Next edit the \u201cVpxClient.exe.config\u201d file which can be found in the \u201cC:\\Program Files (x86)\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\u201d directory and add the following three lines to it in the location specified in the screenshot below.  Then save the changes.<\/p>\n<p><runtime><br \/>\n<developmentMode developerInstallation=\"true\"\/><br \/>\n<\/runtime><\/p>\n<p>VMware vSphere Client Windows 7<\/p>\n<p>Step 4. <\/p>\n<p>From the Windows 7 \u2018System Properties\u2019 click the \u2018Advanced\u2019 tab and then the \u2018Environment Variables\u2019 button as we want to add a new \u2018System\u2019 variable.<\/p>\n<p>VMware vSphere Client Windows 7<\/p>\n<p>Create a new \u2018System\u2019 variable called \u2018DEVPATH\u2019 and assign the following variable value:<\/p>\n<p>C:\\Program Files (x86)\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\\Lib<\/p>\n<p>VMware vSphere Client Windows 7<\/p>\n<p>You are now ready to start using the VMware vSphere Client on your Windows 7 machine!  Some people have reported having to run the client as an \u2018Administrator\u2019 so if you are having difficulties it may pay to try this \u2013 I luckily didn\u2019t experience this problem. Also you will likely have to reboot your machine (or restart the explorer.exe process) for your new path information to come into effect.<\/p>\n<p>VMware vSphere Client Windows 7<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>This is fixed in vSphere in 4.1 I think but I can&#8217;t get hold of it. So http:\/\/www.youtube.com\/watch?v=-ys__7ga41E&#038;playnext=1&#038;list=PLEFC103E97FE8182C&#038;index=20 www.vmwarevideos.com\/vsphere-client-win7-system-dll.zip Copy .dll to C:\\Program Files (x86)\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\\Lib or C:\\Program Files\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Launcher\\Lib If Lib don&#8217;t exist, then create it. http:\/\/www.techhead.co.uk\/running-vmware-vsphere-client-on-windows-7 &hellip; <a href=\"https:\/\/stevenwhiting.com\/blog\/?p=423\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[86],"class_list":["post-423","post","type-post","status-publish","format-standard","hentry","category-it-notes","tag-vsphere"],"_links":{"self":[{"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=423"}],"version-history":[{"count":6,"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/423\/revisions"}],"predecessor-version":[{"id":456,"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/423\/revisions\/456"}],"wp:attachment":[{"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stevenwhiting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}