Using workarounds for applications with drivers
Network Monitor 3.4 is also a good example of an application that could be sequenced with a few tweaks, even if the software requires a driver to work properly.
Once we sequence the application and apply the workaround reviewed before editing the App-V Sequencer Exclusion Items, we will see our application running apparently normally; but, as soon as we try to capture it from the network, we will see the None of the network adapters are bound to the netmon driver message:
If we are working with an application and we don't know the exact driver that it is using, we can use Process Monitor again, to find the particular driver used. In this case, the network driver, used as a filter in communications, is named nm3.sys.
You can also easily find the latest driver installed by accessing C:\Windows\system32\drivers and looking for the latest files added.
In order to get this application working as virtual, we must do the following:
Sequence the application...
