How to get applications that use as USB hardware to run inside streaming isolation App

How to get applications that use as USB hardware to run inside streaming isolation App

- Applications that talk directly to USB drives for examples Signature Pad etc .. may have challenges to work, if they are executed within the isolation environment. Imagine a situation where :.

1. An application "X" that is installed and speaks to a USB drive or some equipment directly on site
2. App "X" to work with a program that is broadcast on the desktop or the server (or) app is streaming needs to talk to / run the application locally installed "X".
3. In both situations app "X" installed outside insulation must run inside insulation work with Streamed application.

When the application that needs to talk directly to the USB drivers or any other materials, Insulation works inside they may fail, especially if App "X" makes use of NamedPipes talk with USB drive (which is the most commonly used method). Failure is because, by default, all NamedPipes created by any application within the isolation are isolated means that these namedpipes created by the application within isolation are not understandable to the external environment.

We can make use of Rules long streaming App in solve this problem , let me explain how. There may be two solutions:

If you're not an expert on working with the rules App Feature streaming Why read the rules and how the rules

Solution 1: Add a rule to Ignore all namedpipes for the profiled application that needs executed with / launch app "X".

This solution is no better way to do things, but the simplest way to get App "X" executed in isolation successfully. But it can have side effects if the App NamedPipes profile is created, in which case these NamedPipes created by Streamed App will be visible outside isolation, which can break multi-user scenarios ..

Alternative 2: Discover specific needed NamedPipes / App created by "X", and Ignore the latter.

We can not ignore that NamedPipes that are created by App "X" so that the side effects we discussed in Solution 1 can be avoided. We can find out all that namedpipes App "X" using Process Explorer

1. App Launch "X" locally (not in isolation), and Explorer tool tool. open process (procexp.exe)
2. List down all NamedPipes used by App "X" process explorer, given a preview below for an example of the application :.
   

   NamedPipe List: ranking on the path name

3. now change the target Profile streamed App, add NamedPipes Ignore rule for these specific NamedPipes

Distribution profile added Regulations and the launch of the App "X" that needs to talk to the USB hardware based, works fine .

a consultant put me in contact with a similar problem, the problem of the above solution has been resolved, and one of my superiors asked to write a message, so that it can be helpful to others with similar problem also, credits for this position will both.

Tweet