I have felt like i have written the same email about applications that are not suitable candidates for virtualization in App-V more than a dozen times over the past week. And I wanted to throw up a table that i tend to use to help highlight some of these.
I often use the MSIT case study as a great example of what to look for an how to identify and set up a process/strategy and how to evaluate the software catalog.
To help minimize the costs associated with application management, an organization should follow a specific sequencing process to help reduce the costs of packaging applications.
The process can be categorized into several distinct phases that begin with evaluating the current software catalog, continue with building the sequencing workstation, and then finish with performing the sequencing tasks. The following sections discuss considerations for each phase.
Phase 1: Evaluate the Current Software Catalog
When determining which applications are suitable virtualization candidates, Microsoft evaluates the potential candidate and places the application into one of three categories:
- Ideal Candidate. Applications meet all of the possible candidate criteria and have no identifiable roadblocks to success.
- Possible Candidate. Applications do not meet disqualifying criteria but may require additional research or validation.
- Not a Candidate. Applications are more expensive to virtualize than the benefits achieved from virtualization. This category also includes applications that technically cannot be virtualized because of current limitations.
To assist with identifying applications that are not a suitable candidate for virtualization,
Table. Provides information to consider.