NeilP's Posts

Re: Cannot type (using keyboard) on vSphere Web Client

by Contributor in VMware vCenter™ Discussions
‎10-17-2017 04:10 AM
1 Kudo
‎10-17-2017 04:10 AM
1 Kudo
Same here..  Typed text does not show up until I click on the window I am typing in.. Using firefox (only just fixed an issue with the most recent version of Flash). I fear these ridiculous w... See more...
Same here..  Typed text does not show up until I click on the window I am typing in.. Using firefox (only just fixed an issue with the most recent version of Flash). I fear these ridiculous web client issues are going to continue - too many browsers (Firefox, IE/Edge, Chrome etc), Operating systems and problems with the many updates to these browsers that VMware has no oversight of.. Add Flash/HTML5 to the mix and you wonder who on earth made the decision to move to a web client..

Re: vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!

by Contributor in ESXi Discussions
‎10-17-2017 12:46 AM
‎10-17-2017 12:46 AM
I've always disliked the web client. I've been using VMware products since ESX 3.5 and I've found the thick client to be reliable and stable. However, the web client is an unmitigated disaster. ... See more...
I've always disliked the web client. I've been using VMware products since ESX 3.5 and I've found the thick client to be reliable and stable. However, the web client is an unmitigated disaster. It's slow and frequently suffers from graphical corruption where sometimes you can't see what you're meant to be clicking until you force a refresh. This is bloody dangerous! Please listen to your customers AND especially the techies that keep recommending your products; which is becoming more and more difficult!

Re: Unable to run Freesco within ESXi4

by Contributor in Virtual Machine, Guest OS and VM Tools Discussions
‎10-21-2011 01:18 PM
‎10-21-2011 01:18 PM
It does actually work in ESXi4.x ...However you cant configure it. I have built my Freesco 4.3 (and previously 4.2) in VMWare workstation using the floppy image. When it was completed and ... See more...
It does actually work in ESXi4.x ...However you cant configure it. I have built my Freesco 4.3 (and previously 4.2) in VMWare workstation using the floppy image. When it was completed and I was happy with it, I simply uploaded the floppy image to the ESXI datastores and created a new VM from there. It works fine (from a routing perspective anyway) however I cant configure it (which is a bit of a pain). I can simply configure it on VMWWorkstation and copy the file over again (if I wanted to make any changes, and I dont need to.. hardly ever). NP

Re: vsphere client 4.1 white console screen

by Contributor in ESXi Discussions
‎10-06-2010 02:11 AM
‎10-06-2010 02:11 AM
No problem.. Glad to hear its worked for more than just me.. :smileygrin: The issue was a royal pain in a$$ I also had white screen issues both with 3.5 AND 3.5i. As its easil... See more...
No problem.. Glad to hear its worked for more than just me.. :smileygrin: The issue was a royal pain in a$$ I also had white screen issues both with 3.5 AND 3.5i. As its easily sorted out with client software (Launcher directories), I would say that the problem is with the 4.1 Infrastructure client's failure to provide backward console compatibility with the 3.5/i servers, not the other way around. ....Mainly as I'd rather patch my Windows 7 box than my live, stable ESX/ESXi environments! Cheers, Neil

Re: vsphere client 4.1 white console screen

by Contributor in ESXi Discussions
‎08-18-2010 07:07 AM
‎08-18-2010 07:07 AM
Hmm.. Both clients work fine with me.. I installed 2.5 Update 6 client. Then 4.0 Update 2 client (Build 253290) - I had to install 4.0 into VMWare workstation then update to ... See more...
Hmm.. Both clients work fine with me.. I installed 2.5 Update 6 client. Then 4.0 Update 2 client (Build 253290) - I had to install 4.0 into VMWare workstation then update to update 2 with host update utility in order to download the 4.0 Update 2 client. Then 4.1 (Build 258902) I did not remove 4.0. FYI My client version numbers VMWare Infrastructure client 2.5.0 Build 227637 (VMware VirtualCenter 227637) VMWare VSphere client 4.1.0 Build 258902 (VMWare ESXi Build 260247) Cheers, NP

Re: vsphere client 4.1 white console screen

by Contributor in ESXi Discussions
‎08-18-2010 05:54 AM
‎08-18-2010 05:54 AM
Hi there Yes, I've tested ISO images with both 'parallel' clients and the dialog box opens up to select the ISO image. Are you getting an error when trying to map to an ISO image? N... See more...
Hi there Yes, I've tested ISO images with both 'parallel' clients and the dialog box opens up to select the ISO image. Are you getting an error when trying to map to an ISO image? NP

Re: vsphere client 4.1 white console screen

by Contributor in ESXi Discussions
‎08-18-2010 04:00 AM
‎08-18-2010 04:00 AM
Even after cleaning and reinstalling in the way specified, it didnt work for me. However, I have a workaround if you cant get this method to work. :smileydevil: Before you install ... See more...
Even after cleaning and reinstalling in the way specified, it didnt work for me. However, I have a workaround if you cant get this method to work. :smileydevil: Before you install 4.1 Client, take a copy of the Launcher directory in the Virtual Infrastructure Client directory. Copy it somewhere else and rename it to Launcher OLD (or whatever). Install the 4.1 Client Put your Launcher OLD directory back to the Virtual Infrastructure Client directory, so you should now have a Launcher directory and Launcher OLD directory.. When connecting to 3.5 Clients, use the VPXClient.exe file in the Launcher OLD directory (356kb) When connecting to 4.1 Clients, use the VPXClient.exe file in the Launcher directory (367kb) You can create separate shortcuts to both and run them depending on the ESX/ESXi servers you are connecting to. The console works for me in both instances.. Cheers, NP

Re: vsphere client 4.1 white console screen

by Contributor in ESXi Discussions
‎08-17-2010 08:11 AM
‎08-17-2010 08:11 AM
Is there actually anywhere you can download those specific VMWare Infrastructure clients. Whether on VMWare.com or whatever? Before anyone says "connect to the browser on your ESX/ESXi se... See more...
Is there actually anywhere you can download those specific VMWare Infrastructure clients. Whether on VMWare.com or whatever? Before anyone says "connect to the browser on your ESX/ESXi servers"; we dont have those particular versions installed in our environment and dont particularly want to install those specific versions just to be able to download the clients. Specifically vCenter Client 2.5 Update 5 and vCenter Client 4.0 Update 2 I need to be able to download these from the Internet.. Many thanks, NP

Re: vsphere client 4.1 white console screen

by Contributor in ESXi Discussions
‎07-27-2010 02:39 AM
‎07-27-2010 02:39 AM
Same issue here.. VI 2.5 and 4.0 clients work fine to a ESX 3.5 server farm When I install 4.1 VSphere client (to connect to our test ESXi 4.1 hosts) and try to connect to our ESX 3.5... See more...
Same issue here.. VI 2.5 and 4.0 clients work fine to a ESX 3.5 server farm When I install 4.1 VSphere client (to connect to our test ESXi 4.1 hosts) and try to connect to our ESX 3.5 I get this White Screen issue when using the console to the VM's. Connecting to our our ESXi 4.1 VM's, the console works fine. I am running Windows 7 x64. NP

Re: ESX 3.5u3, Vmotion and isolation - help please.

by Contributor in vCenter™ Server Discussions
‎02-17-2009 04:06 AM
‎02-17-2009 04:06 AM
Thanks for you help, all.. I am still a bit hazy on a couple of points, but the changes I have made seem to have allowed me to separate my Vmotion and iSCSI. It works manually. ... See more...
Thanks for you help, all.. I am still a bit hazy on a couple of points, but the changes I have made seem to have allowed me to separate my Vmotion and iSCSI. It works manually. Now onto the isolation failover problems.. NP

Re: ESX 3.5u3, Vmotion and isolation - help please.

by Contributor in vCenter™ Server Discussions
‎02-17-2009 02:48 AM
‎02-17-2009 02:48 AM
Thanks Yattong. The iSCSI/VMotion side of the ESX Server network is isolated from the rest of our network and is not accessible from my or most machines. If I removed the service cons... See more...
Thanks Yattong. The iSCSI/VMotion side of the ESX Server network is isolated from the rest of our network and is not accessible from my or most machines. If I removed the service console from the Virtual Machine network (on your vSwitch2), would I lose connectivity to the VM's? I know I would not be able to access the ESX servers directly from my machine. Cheers, NP

Re: ESX 3.5u3, Vmotion and isolation - help please.

by Contributor in vCenter™ Server Discussions
‎02-17-2009 02:38 AM
‎02-17-2009 02:38 AM
Thanks for the reply.. Just to clarify a few points before I award - hope you dont mind. 1) If vMotion is placed on a separate network, does it need to be able to access the iSCSI Fi... See more...
Thanks for the reply.. Just to clarify a few points before I award - hope you dont mind. 1) If vMotion is placed on a separate network, does it need to be able to access the iSCSI Filer directly? 2) The 6 NIC design you listed has the iSCSI and Vmotion on the same network is that correct? 3) Is it a good idea to have a second service console (I have seen documents stating that it is useful to have 2)? If so, do you have any pointers to ensure a failover takes place when either of the service consoles lose connectivity? Many thanks again, NP

ESX 3.5u3, Vmotion and isolation - help please.

by Contributor in vCenter™ Server Discussions
‎02-17-2009 01:50 AM
‎02-17-2009 01:50 AM
Hi all, We are quite new to Vmware (Well, to ESX and Vcenter anyway) and would appreciate it if you could help with a couple of issues we are having. After our ESX/Vcenter trial and s... See more...
Hi all, We are quite new to Vmware (Well, to ESX and Vcenter anyway) and would appreciate it if you could help with a couple of issues we are having. After our ESX/Vcenter trial and successful test environment we bought the Enterprise ESX package with 2 new servers (plus one for Vcenter). Manual Vmotion is working fine however I have a couple of questions and would appreciate it if you could point me in the right direction. Config.. 2x ESX3.5u3 servers and 1 VCenter2.5u3 server. 6 nics in each (not all used). VSwitch0 - 2 NICs active in team..... VM port group (VM Network), Virtual machines (3 test machines so far), Service console port (Service Console). Connected to our main L3 switch stack. VSwitch1 - 1 NIC active...... Service console port (Service console 2), VMKernel Port (iSCSI). Connected to a switch with connectivity to our NETAPP Filer via iSCSI. No router here. Questions. 1) I would like to optimise the configuration to add a separate VMKernel port to move Vmotion to a new VSwitch2. At present, the iSCSI port has been set up for VMotion on vSwitch1. Does this sound ok and is it worth doing for performance reasons? My question is whether the new Nic needs to be able to see the iSCSI datastore "directly" on the same subnet (No router here)? Can someone provide an optimum design using between 4-6 NIC's please? 2) I have been doing some isolation testing, unplugging the 2 nics on Vswitch0 for the active host (with the 3 vms on it). I was expecting the host to power down the machines and move them across, but they stay running and dont move. Am I missing a few steps? I have set the HA on the cluster to "Shut down VM" in the host isolation response settings. Many thanks in advance. NP