You can use thinapp and then provision the thinapp packages with appvolumes if you wanted to. You need something that would isolate them and thin app is really the only option outside of separate desktop pools and/or rdsh farms serving published apps.
"The problem is, we have some clinicians that roam from facilities in one LOB to facilities in the other LOB, and they need to be able to use the appropriate dictation software when they're in the appropriate facility."
Have you tried just user based assignments and only install the separate apps?
Appstacks are assigned to users today, but the roaming clinicians need the appstacks from both lines of business because they visit sites in each. The dictation software in each appstack breaks the functionality of the dictation software in the other. Dictation-software-only stacks wouldn't help here since both are needed by the same person.
What kind of dication software are you using if I may ask? We tried doing this with Dragon but because you can also control the machine itself with it this did not really work all to well because it needs to be there before the machine starts.
That being said. I'm trying to figure out what you are trying to do. Do you have the use case where 1 users needs both applications but just on a different machine? If so couldn't you create 2 groups, and when assigning the appstacks make sure to do a machine prefix assignment? Computers on both parts do need to be in a different pool for that off course and the prefix of the machines do need to be different.
Yeah I was kinda thinking of what Ray is mentioning something along the lines
1.)An appstack for most of your applications
2.)An appstack with the dication software its self
and then a mix of user groups and limiting the app stacks to machine prefixes to limit it as you need.
Not sure if the screenshot will come inso the TEXT reads:
Normally, all assigned appstacks are attached during a computer startup or user login. However, some use cases may call for a selective assignment that is only attached to a specific set of computers.
The Limit Attachment option enables you to specify the prefix of a computer name. When provided, the assigned appstack will only be attached to computers whose name that begins with that prefix.
Consider a user named Bob. He is assigned two appstacks, one is a standard assignment and one is one limited to "Win7-Dev". When he logs into the computer named "Win7-Dev-021", both AppStacks are attached. When he logs into "Win7-Test123", only the standard assignment is attached.
This is perfect! We're on AV 2.17, which doesn't have the Limit attachment of these assignments to specific computers option. But an upgrade to v2.18.4 is in the offing, and after that we'll be able to limit the attachment of the two appstacks to only the Desktop Pools that apply to each LOB. This will solve our problem nicely. Thanks for the tip!