- Top 10 Recession-Proof IT Jobs
- 7 Hot IT Jobs That Will Land You a Higher Salary
- Link Building Strategies and Tips for 2014
- Top 10 Accessories for Your iPad Air
Network World - This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter's approach.
Although virtual desktop infrastructure (VDI) is well recognized, up until now, the technology has over-promised and under-delivered. Many IT departments, lured by better resource utilization and cost savings, have had their fingers burnt as a consequence of adopting a 'lock stock and barrel' approach to VDI projects. For many companies, the project has actually negatively affected users' ability to do their jobs, in turn resulting in outright rejection of the implementation.
The error has lied in taking an IT-centric approach to VDI. Evidence suggests that a user-led approach to VDI implementation is more successful. This requires a deeper analysis of how users do their jobs and the impact of the virtualized app on the users' day-to-day activities.
Compatibility testing can measure which applications can be moved to the virtual environment, and usually IT departments will focus on this. However, as part of this, user compatibility testing is overlooked. In order to truly deliver value from VDI, only those applications that will either perform better or will enhance user experience should be migrated to a virtual environment.
User compatibility testing involves a comprehension of which applications are used most by users, how they use them, from which devices, how often and for what purposes. Some applications (e.g. Microsoft Office) are more suited to VDI as they can be encapsulated easily, they are platform independent and multiple versions can run on the same box without compromising performance.
Other applications that carry a heavier data load (e.g. SAP) lose performance and are more dependent on resources outside of the discreet device accessing the data. Corresponding usage behavior of its users and an understanding of the application are essential to identifying the best candidates for VDI.
For instance, one of the behaviors that should be monitored prior to virtualization is the time required to initiate the session or begin working. If the time to log in is minimal, then it is often assumed that the user would be a good candidate for VDI or application virtualization. However, you must still look at the after state to determine if there has been an impact due to unknown issues such as network latency, shared license check-out, etc.
If this test reveals that a user will experience noticeable delays launching an app in a virtualized environment, it will likely create a negative impression and contribute to user rejection of the virtualized app. It is precisely this type of analysis and understanding that can make the difference between a successful or failed virtualization initiative.
IT departments commonly commit a one-off virtualization compatibility test before a VDI project, whereas compatibility evaluation is best conducted on an on-going basis.