Just a quick note on the blog that I’ve put together a new VMware fling, the first of many (hopefully!).
The VMware Horizon HelpDesk Agent is built on the Horizon HelpDesk API to be a more natural and fluid experience for windows administrators of Horizon. I’ve ensured that this application is as responsive and intuitive as possible by leveraging asynchronous calls where possible to ensure the user is rarely left waiting for responses.
With the HelpDesk Agent, you connect once and maintain your session throughout the day to the subscribed service, once you need it, you simply pull it up via keystroke and begin to search for the user you wish to assist or observe. I’ve optimised the search experience to remove some unnecessary steps and allowed quick access to the users data. You can maintain multiple open windows, access everything with simple key strokes, etc.
So here’s an ask I’ve had for well over a year, which i duly neglected until the mind of the brilliant Sean Massey decided to send me a PM on the vExpert EUC slack channel.
VMware Horizon’s API has been published for well over a year at this point over on code.vmware.com but there’s two challenges with this API in my humble opinion:
A: it’s WAAAAY too developer orientated for a regular PowerShell consumer*
B: while it’s a fully fledged API it seems a bit shortsighted to only document how to use it from Powershell given that the full API is documented.
* oh don’t have such a high opinion of yourself, everyone complained, i have the emails to prove it!
I had attempted this a few times before, but my usual source of help, Remko was too busy to help me or I duly hit a problem and inevitably toddled off to do something else. Not this time! and with no Remko help! *pats self on the back*
The VMware Unified Access Gateway really is a wonderful device. With a quick deployment of an OVF you’re up and running with free remote access to your VMware Horizon environment. The device is so simple in fact, that it’s often a case of set and forget, it does the hard work freeing you up to do more important things.
A request came in from a customer last year to be able to view more about what this little magic appliance is doing, how healthy it is and how many users it is currently servicing.
For VMware vRealize Operations for Horizon customers, this data is all available directly in the VROPS portal, but what if you don’t have VMware vRealize Operations for Horizon? or want to query this in an automated fashion?
So VMware Horizon 6.2 was announced at VMworld just a week ago and the one feature I sorely wanted to see was automated provisioning (golden image management) of a Microsoft Remote Desktop Services farm.
The provisioning process is fairly straight forward, so in this blog post I’ll walk you through the steps to avoid any issues.
Download the Agent, Connection Server and Composer software.
Upgrade your Connection Servers to 6.2.
Upgrade your Security Servers to 6.2 (remember you’ll need to repair with the connection servers).
two years ago at an E2EVC event, the concept behind ThinIO was born with just a mad scientist idea amongst peers.
If you are lucky enough to be attending E2EVC this weekend, David and I will be there presenting ThinIO and maybe, just maybe there will be an announcement. Our session is on Saturday at 15:30 so pop by, you won’t be disappointed.
Back on topic:
So here’s a really interesting blog post. Remote Desktop Services (XenApp / XenDesktop hosted shared) or whatever you like to call it. RDS really presents a fun caching platform for us, as it allows us to deal with a much higher IO volume and achieve deeper savings.
We’ve really tested the heck out of this platform for how we perform on Microsoft RDS, Horizon View RDS integration and Citrix XenSplitPersonality with Machine Creation Services.
The figures we are sharing today are based on the following configuration and load test:
Citrix XenDesktop 7.6
Windows Server 2012 r2
Citrix User Profile Manager.
16gb of Ram.
LoginVSI 4.1 medium workload 1 hour test.
VMFS 5 volume.
Diving straight in, lets start by looking at the volume of savings across three cache types.