While I am not one to normally care about vendor spam. I received what I thought was a really odd email from Citrix regarding their XenDesktop capabilities versus VMwares offering.
Whether they are right or wrong… the marketing attempt is quite silly. Check the Subject of the email !
Why call out 6 things, and then only identify 4 ?
I can’t identify where the 6 things were ? Turns out it isn’t me who can’t count.
A lot of customers that are evaluating VDI are probably looking at the Wyse (WTOS) V10L series of Thin Client. Wyse have a kick-ass little unit in these devices, and I am sure their sales are ticking along, as the ease of management for these puppies is well…. easy!
Getting back on point, The V10L does have the odd limitation, and one is that it’s not using a full VMware View client, its their port / interpretation of what features they think customers will want the most. And thus, there was only an option for a single broker VDIBroker= <set in your WNOS.INI>.
While this is fine for most customers, its not for those planning mass VDI deployments with multiple brokers internally. Brokers might be segregated by region, business unit, etc etc… and previously this would have put the poor lil V10L out of a large sale. Customers needed to use a VMware View client (Win32 or Linux variants) to get a multi-broker capable client.
But…. Wyse are listening to their customers and partners ! and just a few weeks back after sending in a Feature Request for a multi-broker supported firmware, they sent me a working beta of exactly what is needed. While it was only limited to 5 brokers initially, this should get upped shortly, and hopefully permanent baked into new V10L firmware releases. This is another tick in the box for the V10L, where it previously had an X.
There are a few more features coming to the V10L firmware that I’m happy about, but I’ll talk about them another day. But I guess what really pleases me is that Wyse take their feature requests seriously, and their turn around times from request to private beta has been outstanding, sometimes in less than 48hrs!
Lets hope Wyse keep up the development for these little units !
This is a quick FYI for those running VMware View Connection Servers(Brokers/Managers). Regardless of whether you are using ‘Direct’ or ‘Tunnelled’ connections you may see these messages in your logs similar to the ones below with sequential request numbers.
(Request112) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe
(Request111) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe
The error messages are generally caused by an ADC or Load Balancer that is polling the Connection Servers web server, and forcing a close of the client connection. This is not something that the View Connection server is expecting to handle, so it dumps this message to the logs.
Essentially, its a false-positive in most cases, and I have heard on good authority that the VMware developers will change the log messages to something a little more friendly in future (~View 4.0).
If you’re seeing loads of these errors and your not using a Load Balancer, then you could have some clients out there that are pushing load generator scripts at your brokers, or potentially some idiot trying out his new script kiddie util. Check out vAudit from Richard Garsthagens site here — http://www.run-virtual.com/?dl_id=1 if you want more detail around successful and unsuccessful user logins. Its a great utility for those running View 3.x environments.
Welcome to the 1st post from the Cloud Pimps…
Initially I’d like to start by covering off what we’re all about… and that is T&T. Tits & Technology… yeah it may be a bit sexist, but that was our mantra over a decade ago… and while it still has some element of truth, we lean more towards the technology side these days.
Going back in time, the two of us created a very successful site (girl4ruste.com) about the former topic I mention above which has now gone by the wayside – if you’re interested to see our efforts, check it out via the waybackmachine, most of the links are probably broken now, but anyway — that was the past. This site will be about the later topic, but you might hear about both intermixed in our posts depending on our mood.
We aim to cover many topics, but we are primarily focussed on Cloud computing, Virtualisation and all those sticky grey matter areas in between.
If you’re keen to follow us, you can catch us both on twitter: @cloudpimps & @cloudjunky !
Like a rhino…..