Library Pack Header

Migrating to a VDI (Virtual Desktop Infrastructure) is no easy feat, especially without the right pre-deployment intelligence. In fact, the most common failures in large-scale VDI projects stem from organization setting themselves lofty deployment goals without actually undergoing proper investigations '''to understand their end-users' work habits''', service consumptions, and data requirements. In addition, they too often follow a \"build it and they will come\" mentality by investing significant capital and labor resources only to create a service they are not even sure people will migrate to or adopt. Even worse is that IT teams rarely—if ever—engage with employees using strategic communication plans to understand what they truly need and expect. These types of operational failures can have a significant impact on the business and will not only hinder productivity and raise business costs, but also harm the trust users have in IT.\nFor many, a common alternative to the on-premise VDI has been DaaS (Desktop as a Service), which has a different dynamic. Notably is how it encourages testing with reduced barriers to entry – provided you can find a service with a minimum monthly commitment and no minimum contract duration. However, while the capital and capacity risks are quite distinct to those of the on-premise VDI, the DEX (Digital Employee Experience) considerations are of equal importance. Indeed, it is not uncommon for post-migration surveys to reveal severe employee dissatisfaction which, even though the infrastructure is in place and resources committed, is still considered a failure. Beyond the budgetary consequences this may have, this creates significant reputational damage making the next deployment that much harder for IT staff.\nFor these reasons, having pre-deployment visibility and '''continuous actionable''' insight across the entire landscape throughout the migration process is a must in any on-premise VDI or DaaS project. In the early stages, this also enables IT to define realistic objectives and commit the right amount of resources based on '''their respective drivers'''. For instance,  if your business is losing millions of dollars for each hour of application unavailability, the business case for VDI is simple and the infrastructure can be organized accordingly. Today, the management of VDI is not as resource-intensive as it was seven years ago. This doesn't mean that it's a cheap solution, but it does facilitate the consolidation of a business case based on the financial situation. In addition, a good evaluation of hardware usage and the physical infrastructure can also go a long way to make significant savings on the overall hardware costs. 

Virtualization - Project

Description

Screenshots

Versions

Content

Required Products

Platforms

Compatibility