I hate to keep flogging this, but this "webclient" implementation and rollout was and is so wrong in so many ways. VMware needs to understand this loud and clear and with no mistake or PR or rat...
See more...
I hate to keep flogging this, but this "webclient" implementation and rollout was and is so wrong in so many ways. VMware needs to understand this loud and clear and with no mistake or PR or rationalization. We run a secure airgapped environment. Among many other things this means 'no flash'. Among many other things this means that stuff needs to Just Work. As one poster above said (paraphrased with apologies) "I don't pay a lot of money to have to do the google-this-try-that-maybe-ff-around-to-make-it-work-sometimes thing". If I was ok with that we'd be doing some kvm derivative. And then by requiring flash, well did I mention that running a secure airgapped environment means 'no flash'? This effectively killed the virtualization effort that I have been pushing (uphill, I might add) for two years. Arguably I should have stopped pushing and just let it go when you guys insisted on flash for v5.5, but I said 'surely flash is interim temporary, and by V6 they'll have done it right'. I see now I was naive and wrong. "Fortunately", if that's the right word, the vm's I'm running I can work with via the viclient. They are all are for convenience, not production. And it looks like that's the way it will stay. I mean seriously, anyone could have told vmware (and probably did numerous times ) that this was the Wrong Direction. I'm not sympathetic with the argument that "well, we were so far along that we had to keep going". A clearly wrong headed way forward is simply throwing good money after bad, not to mention destroying customer confidence and good will ('Goodwill" is a balance sheet term, btw) when it's shoved down their throat.