Firstly just don't. But if you have to...
This post relates to issues encountered when attempting to publish and launch App-V 5 applications which are on network locations.
This article
https://packnowledge.wordpress.com/2013/03/20/launching-a-network-executable-inside-an-app-v-5-virtual-environment-2/ discusses a situation where providing the machine account with access to the network resources can resolve an error which appears when attempting to launch the application:
TargetFileName.exe - Application Error
The application was unable to start correctly (0xc0000142). Click OK to
close the application.
However in a recent scenario a resolution was not found. Here the application exe target had been moved from an actual Windows 2000 server share where launching worked fine, to a share on an enterprise storage system which used isilon OneFS. Unsuccessful attempts to resolve it included creating a test share on the isilon OneFS system with completely open permissions and also restricting the network protocol to SMB (not SMB2 or 3). More info here
https://support.microsoft.com/en-us/kb/2696547
Before it was even possible to carry out a launch, the application would only publish IF the drive mapping to the share was disconnected or deleted. If the drive mapping was connected to the share then publishing would fail with the following responses (errors).
publish-appvclientpackage : Application Virtualisation Service failed to complete requested operation.
Operation attempted: Publish AppV Package.
Windows Error: 0x3A - The specified server cannot perform the requested operation
Error Module: Share Component. Internal error detail: 8DC022250000003A.
This was observed in 5.0 SP2 HF4, 5.0 SP3 and 5.1
The App-V package was simple in that it consisted of only a shortcut to the exe file on a drive mapping and an ini file in the windows folder. Appsense Environment Manager was used instead to deliver a shortcut and copy the ini file to the users Windows 7 virtual store.
