@ Eric ..thanks for the reply :-)
FOR THE RECORD .. did you read my message correctly ?
Believe you me I've been all over this like a bad rash ..
CTRL+ALT ... been there done that .. it only releases the NON-EXISTENT MOUSE ... did you read the problem I described ?
(OLD TRICK .. teach this dog some new ones ..)
I have now verified this issue .. it is prevalent in both vcenter 6.5 as well as when connected to a stand-alone host ! \
![rdp web console bugs.JPG]()
It is insanely frustrating and hurtful that vmware insist on either not testing this stuff or releasing semi-tested software continuously .. these basic things are NOT difficult to test at all !
I have TESTED this and while testing realized there is a new update released about two weeks ago now.
The updates are for both vsphere and esxi 6.5 (yip that's right .. update b ..mmm are we going from alpha to beta in a GA ? )
So I thought I'll just set the whole lab up again , this time using 6.5b
Well I have spent a full 24 hours setting it all up again .. and finally 6.5b is up and running.
I anxiously created a new virtual machine ( first windows 2012) and after MUCH STRUGGLE just assigning a hard disk .. yes another bug it seems .... imagine that ..
the issue is that the default disk is set for THIN provision but if the datastore is less capacity than the thin provisioned disk the wizard generates and error , which is fine but unless you actually double click the THIN provision option OR click a THICK option, and assume that THIN is the default once you click finish an error appears saying the disk space is not enough ...AAAARGH ~!!!!
Then to add insult to injury you have the ISO selection ... OMG what a JOKE ! Sometimes you can select and click the datastore option and sometimes you can click it stupid and it doesn't select.
then you may have to refresh the window or log out and then back in again and then it may work.
If you did actually manage to select the datastore browser and it worked you are taken to a window to select your ISO from a list of files .....
GUESS WHAT . ?
NO FILES ARE DISPLAYED ...WOOOHOOO .....WHAT FUN AND GAMES ............NOT !!
Ok so off or refresh the browser window (whichever works for you ..maybe try a combo if it doesn't and you may be successful).
then you can maybe see the files to select your installation ISO .. at last ..yaaay!
Now what I've also noticed is that sometimes the connect at power on is not there or gets deselected somehow (UN-DEVINE INTERVENTION).
So after all of this the result is .... : THE MOUSE NOW WORKS ! ...YES sort of like it used pre-vsphere 6.5
BUT WAIT THERE'S MORE (OR LESS .. more is less and less is more right ?) ......
Now that the mouse works (a revelation perhaps for some like me).. you now are presented a kind of newer console with ...WAIT ...STOP ... I can't see it now because there's an UNHANDLED EXCEPTION(1) ERROR ... HAHA try google this one baby !
Now if this isn't a sign of BAD CODE then what is ??????
Ok the UNHANDLED EXCEPTION (1) (non-hyphenated of course because that would be proper English right ? And we code , to hell with english right ?) says to refresh the browser because ' we recommend refreshing and submitting a bug report' ...
And this is possible of course if you're in a datacenter which is CANNED and non-internet facing ... Security in a datacenter ?? HUH what's that ?
Yes of course all client datacenters are internet facing ...and no NONE of them are in remote locations or off-site ..right ?
An no-one out there really uses RDP connections much right .. ? I mean RDP tunnels in RDP tunnels and then a vmware console inside that .. gee who even does that ... ?
Because if for example I happened to hear that I should maybe try the VMRC (an option that is available as you you launch the client) ... you try it by making the selection from the console which isn't really working to well (yip it sort of works but hey who cares if it doesn't fully work right , I mean we've tested it in our local dev environment and not in the most obvious places or situations like real client remote connections ..right ? That of course is fine right ? I mean we can always figure it out in the updates and if clients really want to they will eventually hear about it right ? )
So on with the program (well a sort of program which sort of works after sort of programming, after all , code is code ..good or bad right ?)
Ok so now I'm back and finally have the ISO mounted and this after a few refreshes of the web browser and one or two log off and log on's ..... take a deep breath buddy production and business can wait.
Ok so I have the console now and BE CAREFUL ... DO NOT DOUBLE-CLICK .. that brings up a window sizing frame that looks like something one might find when you paste a picture in mspaint or you're cutting and pasting in mspaint (A far more superior program I think).
So once you've figured out that this is some sort of resolution or screen sizing/setting tool then pat yourself on the back ... and make sure you have something hard to bite on because you have a little work ahead trying to figure out how to get it out of your way... (click the tiny cross with the arrows on top left of transparent frame)
and if you happen to try set the size by dragging the dotted frame around then you will probably end up with a lovely blank screen (color is chosen automatically) but where is the Windows desktop now ....AAAARGH !
So close the console and open a new one and don't double click !!
Move slowly , too fast and you are out of the frame or playing with a drunk mouse !
OK .. now that we have a SORT OF WORKING CONSOLE it's time for VMWARE TOOLS (praying this helps ...eeeek!)
So once you've figured out where the option is (top right of new console , along with options for virtual keyboard ..heheh some devs also probably had issues .. GOOD ..feel my pain or at least part of it ...the best is yet to soome when I realize how much time and money I've lost battling with this flaky management product PUI (pooey, in fact stinky pooey and oh so clunky)
Now back to business (maybe) ....
Ok so I fired up vmware tools install , procedure is to find where to select guest and then select it and select install vmware tools.
and wait ....
dude just wait ...
and wait ...
it's not working ...SIGH
So into the OS I go hi-ho hi-ho .. the vmware tools ISO is mounted but not launched .. click it don't double-click it ..I said don't double-click dammit!
AAAAH at last some responsiveness from the mouse wooohoo !
I can sort of work now in a console screen that sort of responds but isn't very intuitive (Did anyone actually do any end user testing and actually ask people what they might like in terms of layout and user-friendliness .. I think NOT !)
Now go easy please... you have a locked windows screen where you need to login right ?
So normally (based on legacy operations through years gone by with vmware product) one would click in the console (not double-click!) and press CTRL+ALT+INSERT (used to be a local login right ?) well good luck with that one :-) ... you need to select the ACTIONS (link/button/option) on t the top right of the console windows and then select GUEST OS , SEND KEYS and select CTRL+ALT+DELETE via a mouse click ...always easy in these remote in remote in console sessions that hardly anyone in the world uses ..right ?)
and then ....right click the desktop .. and ooh that lovely transparent frame is back ...YAY.....
OH WELL IT SORT OF WORKS DOESN"T IT ??
Three words come to mind here ...STOP THE MADNESS !
C'mon guys ... you're taking us back in time to early ILO java sessions ...do you actually think clients are loving this ?
This is seriously testing our patience.
You say the c# client is DEAD .. but how the hell do you manage these vm's now ..this has become something BEYOND A JOKE !!!!!!!!
PS . I certainly hope the moderators here have the gumption(assertiveness) to actually post this.
And i sincerely hope this helps others to at least get to manage their vm's too.
OH and the final straw was this post ... trying to just upload an image here freezes good old firefox and you end up with a browser not responding but thank goodness firefox retained all of my post after the re-load.
OH AND FOR THE RECORD .. let's not even mention the VMRC ... but if you really want to entertain that thought, by all means try it .. first battle around with the plug-in a little (otherwise you miss the fun stuff) and then open it up to find the missing mouse , if you can of course, assumming you don't have a blank screen and hopefully you've had a littrle more fun checking out the KB that points to checking the firewall and ports etc etc.
this of course with you knowing full well that all used to work pre-vsphere 6.5