I have following problem
- As a standard installation (not as a ThinApp), AWD creates what is "AWD login" as a shortcut on the desktop.
- Once you start shortcut AWD login and authenticate through it, this creates additional shortcuts, depending on the user's security level access to the images.
The problem I find when this application virtualization is encapsulating executable works as expected, and achieves the ability to use sign-AWD, but the shortcuts created by the AWD system will have an objective that aims to C: \, not to a virtualized path. for the reason that the destination path is not establish, make shortcuts to failure. Again, these additional shortcuts cannot be encapsulated as part of the ThinApp package, in view of the fact that these shortcuts are generated when the user logs into the application.