It is very important to understand App-V 5.0. General tips Familiarize Yourself With App-V 5.0 The next article will help you assess your infrastructure and give you a migration workflow.
Considerations and Limitations of Client Co-existence/Package Conversion in the Migration ProcessĪfter reading and following all instructions in this article, you should be ready to pilot a migration.This blog provides you the resources to familiarize yourself with App-V 5.0 as well as highlight the considerations & limitations of the migration process. Assess, prepare, and execute a migration from 4.x to App-V 5.0.Learn about App-V 5.0, the new changes, and how it impacts your current environment.Therefore, if you're a 4.x customer, you should be prepared to invest time into the following: Since releasing App-V 5.0, we have noticed that there is a learning curve for the new architecture for App-V 4.x customers. Right-click), and simpler VC-runtime packaging. Some of the new SP2 features include shell extension support for virtual applications (ex. Since App-V 5.0 was announced in November last year, it has garnered lots of excitement from customers. In order to provide those benefits, App-V was designed from ground up to provide the foundation upon which we could continue to improve App-V in the future and add scenarios that were not feasible previously, such as shell extension support in virtual applications.Īnd now that App-V 5.0 SP2 Beta is announced, even more scenarios are enabled, giving more reason to migrate to App-V 5.0.
This is the first post in a series of posts around migration of App-V from 4.x to 5.0.
0 kommentar(er)
