KB: A Microsoft Application Virtualization MSI run from a mapped drive fails to install the virtual package
Here’s a new Knowledge Base article we published. This one talks about an issue where a Microsoft Application Virtualization MSI run from a mapped drive fails to install the virtual package.
=====
Symptoms
Consider the following scenario:
- You have created a Microsoft Application Virtualization (App-V) Virtual Package and placed the package contents on a network share.
- You have mapped a drive to this network share.
- You attempt to install this Virtual Package by double clicking on the .MSI file located on the mapped drive.
In this scenario, the package fails to install. No on screen errors are seen and the virtual package does not show in the list of virtual packages.
Additionally, in the Application Event logs you see the following MsiInstaller Event:
Log Name: ApplicationSource: MsiInstallerDate: Event ID: 1033Task Category: NoneLevel: InformationKeywords: ClassicUser: User1Computer: Computer1Description: Windows Installer installed the product. Product Name: My Virtual Package. Product Version: 1.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
Cause
The mapped drive that holds the .MSI and the .APPV files is only available for access in the Users' own context, however the MSI Installation is done using the System context. The System context does not have the appropriate privileges to access the mapped drive.
Resolution
Run the MSI directly from a network share (e.g. \\server\share\MyVirtualPackage.MSI) or copy the package to a local drive on the client computer.
Also ensure that the computer account (the computer you are logged into) also has access to the network share.
=====
For the most current version of this article please see the following:
J.C. Hornbeck | Knowledge Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter :
App-V Team blog: https://blogs.technet.com/appv/
ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/< /a>
DPM Team blog: https://blogs.technet.com/dpm/
MED-V Team blog: https://blogs.technet.com/medv/
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: https://blogs.technet.com/momteam/
SCVMM Team blog: https://blogs.technet.com/scvmm
Server App-V Team blog: https://blogs.technet.com/b/serverappv
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: https://blogs.technet.com/b/systemcen teressentials
WSUS Support Team blog: https://blogs.technet.com/sus/
The Forefront Server Protection blog: https://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : https://blogs.technet.com/b/clientsecurity/< /a>
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/< /a>