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.
Bite size application compatibility testing
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.
For example, rather than conducting compatibility assessment for all applications used in a particular region or country (e.g. US-based apps), you're likely to ensure a higher success rate if you analyze blocks of up to a 1,000 users who are categorized by job function or department (e.g. finance). That allows IT to identify and migrate users in small groups, making the project more manageable and minimally disruptive. Getting migration right the first time must be a key goal for IT departments embarking on VDI projects.
The ultimate end point for the majority of enterprises today is the cloud. To successfully achieve this, a measured, best practice approach that puts users' needs at the heart of the virtualization initiative is imperative. This requires: