Forum Discussion
Publishing an exe that resides on a file share
Christian_Montoya Yes it is a click-to-run exe. It's always reliable when launching the exe from a full desktop session. I have not tried to run it from a command based session. I was under the impression that I could not do this through PowerShell as the file share is mounted as a mapped drive.
The current app design requires that it is installed centrally and then the users run the exe by clicking a shortcut from their desktop which points at the central location, i.e. file share which is mounted as a mapped drive.
Christian_Montoyaa little bit more info on our app...
when the exe is run for the first time from the file share/network location, it installs files into the appdata directory. The application then runs from there.
On the WVD environment, it would appear that there is a file share mapping problem when the load balancer launches a session to one of the virtual desktops. As I said previously, this is only an issue after a previous session has been disconnected. It always works first time in the morning!
tadhgclifford hello publishing a remote app from a network share has not been evaluated and its not a scenario we recommend (or the AppFoundation team recommends). In general for RDS/VDI apps must be present on the machine prior to user logged in or installed by the user after session is established. With click-to-run apps there are set of internal procedure/micro-services that do certain cleanup upon user logoff. Not all do it … it really depends how the app was written (if app was written not to put setting in the user profile should not be a problem...I tested this scenario a while back).
Click-to-run apps to run from network share but there are challenges (like those that you are experiencing) (additionally click-to-run apps do some weird stuff with user data unless coded for such scenario).
Logs: Try looking here %LocalAppData%\Temp
Also check converting Click-to-run to MSIX (repackage it there is a tool in the store). MSIX has the procedure/capabilities to clean itself quite nicely upon session disconnect.
