Appv sequencing limitations

When we are sequencing the applications, we need to be mindful of which one we can sequence and which one we cannot. Also there are certain limitations when using App-V.
Here is a list of application functions and limitations of App-V sequencing;

Limitation	Description
Applications that start services at boot time	•          App-V requires a logged in user to initiate the launch of an application.
Applications that require device drivers	•          App-V cannot virtualize drivers. It is possible to bypass this issue and install the driver locally on the target computer. •          Some user-mode device drivers can be virtualized.
Applications that are required by several applications for information or access	•          For example, a program that will initiate a command and launch another program. Normally both programs would be included in the same suite.  However if this application launches or initiates commands in several applications it may not be feasible to include all of the applications in the same suite. •          This is especially true if one of the reasons for deploying App-V is to avoid application conflicts.  Always remember that the virtual “bubble” can see the OS and what’s installed on it but the OS cannot see the “bubble” and interact with it.  On the same note, remember that one “bubble” cannot see another unless they are brought into the same virtual environment using Connection Groups.
Applications that are a part of the OS	•          Such as Internet Explorer
Applications that use COM+	•          Because COM+ is dynamic and happens at runtime, there’s no way for the Sequencer to capture this information.
COM DLL surrogate virtualization	•          For example, DLLs that run in Dllhost.exe