VMware Horizon Community
john1234w
Contributor
Contributor

let thinapped application access a network file

I'm having trouble with ThinApp accessing a network file....

I have an application that is actually two applications and I've thinapped them into one (because they share runtimes), one of them however installs on a server via UNC path, those files don't get copied into the application, nor do I want them to.

What I want is the shortcut that appears on the desktop that says run
servername\share\program.exe to work. The shortcut just says it can't find it. I want the shortcut to be part of the thinapp so that it has access to those shared runtimes, so simply making my own shortcut outside of thinapp won't help.

I made an AUTOIT script that calls that program.exe as well and stuck it in the package, but it too cannot find the file...i know there must be some setting somewhere that is not letting the script and shortcut in the thinapp bubble talk to the network share, but i'm not sure where/how/what to do.

Reply
0 Kudos
3 Replies
Squidly_Man
VMware Employee
VMware Employee

Forgive me here...but I'm not quite certain I understand what you are attempting to have occur. Could you explain a bit more? Did you want the ThinApp package to register to the workstation even though it is sitting on a UNC path (and create a shortcut to itself)? Or was there something else I missed?

As for running a scripted process, ThinApp will support VBS scripting - so anything you script will fire up within a ThinApp. See the ThinApp blog articles on scripting at .

-Dean F.

-Dean F. https://www.vmware.com/support/pubs/identitymanager-pubs.html
Reply
0 Kudos
john1234w
Contributor
Contributor

The client executable file is on a UNC path, however the runtime components are local to the workstation, therefore I need the shortcut that opens the UNC file to be in the same thinapp as the runtime files...problem is the shortcut can never open a unc path for some reason if it's in the thinapp package.

Reply
0 Kudos
Squidly_Man
VMware Employee
VMware Employee

It appears this may be broken in this version of ThinApp.

There are two ways to work around this:

  1. Create a drive mapping, either in a login script for the users needing this drive mapping, or within the ThinApp package (see the ThinApp Blog Article, "How to Map a Drive within a ThinApp Packaged App"). You'll need to reconfigure the entry point for the app within your ThinApp project's PACKAGE.INI file to use this drive mapping as well. Oh...and before you actually run BUILD.BAT, the drive needs to be mapped for ThinApp to see this file as the proper "Source".

  2. Use a Shell Wrapper such as ShellExecute.exe (download and use at your own risk) or a custom ThinApp Wrapper (not officially supported by VMware).

-Dean F.

-Dean F. https://www.vmware.com/support/pubs/identitymanager-pubs.html
Reply
0 Kudos