1. Sequencing Applications That Cannot Install to Q:

At some point while sequencing applications you will most likely run across an application that will not let you install to Q:. This by itself does not present a problem when sequencing the application. In fact only one minor modification will need to be made.

• When you hit the “Start Monitoring” button you will browse to the root of Q:.

• Make a directory for your application using the 8.3 naming convention and select this directory as the asset directory

• Select Ok and continue sequencing as normal.

There are pro’s and con’s when sequencing with this method.

2. Sequencing Web Based Applications

Internet Explorer is NOT supported in a sequenced application. However you can sequence plug-ins or ActiveX controls for Internet Explorer.

This pulls the locally installed application into the virtual environment with the additions you have specified. In this case it was a web plug-in. This lets you have a clean and secure Internet Explorer that you can lock down on a users machine and then allow them to use the plug-ins that you define.

3.Sequencing applications that require access to local devices and or resources

In many ways you sequence these applications no different than you would any other. The applications inside the virtual environment can see the local resources on the OS and can access them. Devices are another matter. App-V cannot virtualize drivers. If you can install the driver separately from the application then the application will fall through to the OS to look for the driver and see that it is installed.