Dragon Naturally Speaking 10.1 App-V package - activation

Question

I've packaged Dragon Naturally Speaking 10.1 using App-V 4.6 SP3, & all functions that I have tested are working normally.
However, the one problem I can't seem to get past is that every time my Dragon user logs a different VDI (virtual desktop), Dragon asks to activate again, and it only has a limited number of activations before the license code is locked out. As our users
are connected at random to one of a large pool of VDI's when they log in, this is a problem.
I have been in contact with Nuance directly and with our software supplier, who are partnered with Nuance, and have been given a lot of conflicting information, but have not been able to resolve matters. This has been going for several weeks. 
As I can see several topics that would indicate others have successfully sequenced Dragon NS before, I would like to ask how product activation was dealt with?
To clarify: I am NOT asking for anything illegal (keys, cracks, etc), and I already have a paid-for licence. I just need to get this running as it is a health & safety requirement for my user, and until I can resolve the activation problem, I'm stuck.

Answer 1

How very odd that you post on a product that was developed by one of the original SoftGrid (previous name for App-V) QA Managers!
Any way, I don't know the specifics of Dragon, but the general approach is as follows:
Install the product without activation, start procmon and figure out what files/registries get modified.
Often, we just remove whatever that is and then activation happens the first time the user launches the app.  Then, those changes are saved for that user and when he/she launches a new VDI session it just layers in.
In App-V 4.* this worked great as EVERYTHING followed the user.  In App-V 5 some things do not.  So what you want to do in procmon the client when you activate it the first time.  Given what you've said, chances are, unless the user is also
an admin, that we are talking about a file that is written to a normally non-roaming area.  In App-V 4.* this would be redirected correctly, but in App-V 5 it is redirected to the user's AppData/Local folder.  So to fix this you create two scripts,
one for start of virtual environment and one for end of virtual environment.   End of environment copies the file into the user's home drive/roaming folder.  Start of VE restores the file (if present).  TMurgent has a free tool AppV_Remediation
to use in the script that will do this for all files in the package by just providing the package GUID.
If the changes are registry based AND user is admin, then it could end up in HKLM for the package with a user SID.  You can similarly back this up and restore it.
Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "The Client Book" and "OSD Reference Book" (http://www.tmurgent.com/Books )