This is part five of the "Making VDI Work" blog series by Leostream CEO Karen Gondoly. Click here to read part four "How to Mobilize Your Workforce with VDI and Hosted Resources", part three "Choosing A Display Protocol", part two "Things to Consider About Client Devices", or part one "How to Design the Ideal VDI or Hosted Desktop Solution".
GPUs, CPUs, and VDI, oh my! GPUs get all the credit for rendering stunning displays for fancy graphics-intense applications. However, CPUs are the true unsung heroes of the high-performance computing (HPC) that solves some of the biggest, most complex problems of our time. By maximizing CPU usage using cloud-hosted or on-prem VDI, you can deliver a virtual HPC machine, anywhere, anytime, for a fraction of the cost.
The answer? It depends. Leostream CEO Karen Gondoly discusses when that expensive, high-performance display protocol really does matter, and when free will work just fine.
Last night, Microsoft announced that it would discontinue shipping Microsoft Paint in the newest Windows 10 upgrade, scheduled for release this September. The internet outrage was swift and fierce, as millions mourned the death of an application that, for many, was the first application we ever used on a PC. From cropping screenshots, to low-quality memes, to recreating a masterpiece, MS Paint simplicity and flexibility has made it a technology staple for simple image editing for 32 years.
As enterprises move away from traditional full-stack VDI and trend towards deconstructed VDI, IT professionals are faced with new challenges when designing a solution that fits all their users’ needs and workflows.
Today, Leostream is celebrating 15 years in the VDI space. In tech years, that is nearly a lifetime of watching new technologies come and go. 15 years ago, VDI was barely more than a proof of concept, and many thought the tech would never go mainstream. Our founders thought differently, and here we are, 15 years later, still managing thousands of VDI and DaaS implementations in both the private datacenter and in the cloud, with a wealth of knowledge of just about every VDI or DaaS use case you can dream up. In honor of those 15 years of VDI greatness, here are the top 15 things to consider when deploying a new VDI or DaaS solution.
This blog is part four of the "Making VDI Work" blog series. If you'd like to learn more about how to make VDI work for your organization, check out our previous installments How to Design the Ideal VDI or Hosted Desktop Solution, Things to Consider about Client Devices, and Choosing A Display Protocol
Earlier this month, OpenStack Summit was conveniently held in Leostream’s back yard of Boston. I took the opportunity to avoid my Waltham commute, attend a particularly interesting session, and participate in some great follow-up conversations centered on OpenStack VDI. Here’s what I learned.
VDI was supposed to save us money. By virtualizing desktops, we mobilized the workforce, maximized resource utilization, and reduced hardware costs. So, the cost-savings had to follow naturally, right? Well, once those pesky licensing fees started to add up, suddenly that big money-saving VDI initiative became just as pricey, if not more so, than dedicated hardware. So, does that mean that the VDI Revolution was a flop?
The other week, while giving a demonstration of our VDI management platform, I tossed out the word “orchestration”. It’s a term you often hear from organizations that are moving resources into the cloud. Invoking the orchestration card, however, brought on the question of how, exactly, our platform was different from all of the other cloud orchestration tools on the market.