Over Christmas break my mind was flowing with great ideas for what I was going to do in 2014. I was fired up to do podcasts, video blogs, debate panels, then I got back to work and got a lot of extra stuff put on my plate (not pointing fingers but this is completely Chris Wolf’s fault). So alas all my great ideas went to the way side, luckily I had already shot my first video blog and after about a month of a delay I finally got around to finishing the edits on it. So without further ado I give you my first video blog on why we struggle with Windows application management.
After watching the blog I want to point out something I didn’t say: What I’m suggesting here isn’t a new idea, I talked to some of our analysts and they shared with me that they suggested this in 2007! Also, I think its interesting to that if you look at how mobile OSs are designed, they follow this model.
I really want to talk about the Framehawk acquisition in this blog but I don’t feel I can write a blog this week without at least addressing these announcements. To all the new appointments I say “congratulations”, its the beginning of the year, so changing jobs is fairly typical this time of the year. These are all great fun announcements that I could write a whole separate blog about but lets get into the one announcement that is related to a tangible EUC technology: Framehawk.
I have heard over the past few years that this is the “year of VDI” I think we’ve all come to realize there will never be a “year of VDI” but I do think 2013 was the year VDI became simple. The tech nerd inside of me doesn’t want this. I got into VDI because it was extremely challenging, I got to be a storage/networking/hypervisor expert. You’re good at server virt? Ha! Try virtualizing a desktop; bet you never tried to get a DVD to burn using a remote protocol over a sat link with 1000ms latency. VDI was my tech nerd utopia, no matter where you looked there was something difficult that had to be fixed. I get bored if I’m not challenged, VDI was a perfect challenge that constantly kept me on my feet. [Read more →]
I just got off a vendor briefing with Amazon Web Services on their Workspaces product and I compiled a list of frequently asked questions that I thought I’d post in my blog. I hope it helps those of you that are looking for answers. If there are any I didn’t ask please let me know in the comments or on twitter. [Read more →]
Amazon announced this week that they are offering their own Desktop as a Service (DaaS) offering. Before I dig into this let’s set the record straight: technically speaking there was absolutely nothing new in this announcement. [Read more →]
It’s time for me to admit something; while I have been sharing quite a bit in blogs and research lately around high end graphic technologies with virtual desktops, I’ve been quiet on some fronts, specifically shared graphics technologies. The reason I haven’t said much is that I haven’t been impressed by most of the technology that’s been out there. I have known for the past two years that better technology is coming so I decided to focus on the good news (typically GPU pass through technologies) as it became public and not blog or tweet, or just rant about what I really want, because up until now what I want didn’t exist. [Read more →]
At the stroke of midnight last night Desktone was acquired by VMware. I realize this is a smaller vendor that many people don’t have much knowledge of so I’ll share with you the high level value this acquisition gives VMware, then I’ll do my typical thing and talk about what I’m excited about. [Read more →]
I take a lot of heat about my view of virtual desktops. I don’t think a week goes by that I’m not involved in some public debate about which should I use RDS or VDI. In fact a large part of my job is in helping our clients make that decision. The long and the short of it is (and this is a fact most people will agree with) you use either of these depending on your needs and use case. The devil is in the details which is why I do a lot of research about this. There is one detail that I don’t talk about too much and that’s my view on RDS over the long haul verse VDI over the long haul. [Read more →]
Further, with Windows Server 2012 R2 Microsoft is introducing the Microsoft Remote Desktop app, available for download in application stores later this month, to provide easy access to PCs and virtual desktops on a variety of devices and platforms, including Windows, Windows RT, iOS, OS X and Android.
As some of you may recall one of the big mistakes I’ve called Microsoft out on is that its RemoteApp platform lacks good clients (see: Wanted: Client Development for Microsoft VDI). In fact in that blog I called out three paths I foresaw Microsoft taking, the third potential path for Microsoft was for them to get in the game and not lean on others to build upon the RemoteApp “framework” and instead turn RemoteApp into a “product”. Last night’s press release from Microsoft sends a very clear signal: they are in the game.
I hope this makes a lot of organizations start to ask the question: Can Windows Server 2012′s RemoteApp Replace Citrix XenApp? after all if you ask the question you’ll want to see my research . In all seriousness, I think its a very important question to ask and that’s why I wrote the research about it early this year. I do plan on updating that paper next year as Microsoft continues to build out its RemoteApp strategy so Gartner clients stay tuned to that. The fact is if RemoteApp is “good enough” this has the potential to displace a lot of Citrix XenApp (now XenDesktop) licenses.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.