Often, the first VDI use case at an organization will be clearly persistent or nonpersistent; as the VDI adoption increases, so does the amount of use cases that need to be supported.

For example, an organization can initially implement a View solution to support their 250-seat classroom environment. This is likely a nonpersistent solution. However, after seeing the benefits of View for its classroom, the organization may decide to roll out VDI on a larger scale. Now, instead of just supporting classrooms, the executive team has decided to adopt VDI to support its mobile lifestyle. In addition, the CEO has demanded that he needs to be able to use VDI from his Apple iPad.

In these types of situations, persistent vDesktops can make life a bit easier. There aren't any user profiles to worry about, per se, and the application distribution is conceptually the same as it is in the physical world. It may also be the easiest way to troubleshoot...