Home » appv

Tag: appv

App-V 5 local publishing of an App-V client package

Here is a quick tip for App-V 5 local publishing of an App-V client package

After packaging an application recently, we wanted to test it locally first before adding to the App-V shared content store, or distributing it via the App-V infrastructure mode servers etc.

You may however come across some errors when trying to add and publish the appv package similar to the below.

add-appvclientpackage : Application Virtualization Service failed to complete requested operation.
Operation attempted: Retrieve Package and Version IDs From Package URL.
AppV Error Code: 0C80070002.
Error module: Streaming Manager. Internal error detail: 74F00F0C80070002.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ add-appvclientpackage “C:\admin\G&G IP v4.3.2015.49 OSL\G&G IP v4.3.2015.49 OSL. …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (:) [Add-AppvClientPackage], ClientException
+ FullyQualifiedErrorId : RetrieveGuidsFromPackageURL,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage

Some things to keep in mind when publishing from a local source.

  • Run the powershell console as an administrator
  • Ensure your content is pointing to a UNC share path not a direct path (even though direct is apparently supported?)
  • Ensure the Network Service account has permission to access this local folder or path

So, instead of: add-appvclientpackage “C:\folder\ApplicationName\ApplicationName.appv”

Share it and try: add-appvclientpackage “\\server\folder\\ApplicationName\ApplicationName.appv


Full command to add a package locally, publish it and mount it:

Add-AppvClientPackage -Path ” \\server\folder\\ApplicationName\ApplicationName.appv ” | Publish-AppvClientPackage -Global | Mount-AppvClientPackage


AppV 5 Publishing Error 0x74F00F0C


Added a new list of Computers to begin accessing our App-V 5 Infrastructure.

The access to the servers and share are driven by AD Group “App-V Citrix Computers” and “App-V LT or DT Computers” etc


AppV 5 Publishing Error 0x74F00F0C

Event ID: 1008, Error, Logname Microsoft-AppV-Client/Admin

With creating the new group for desktops and laptops to start accessing the AppV infrastructure we started getting

Package {b10fe46f-1d9e-449e-94dc-b6f3e1b0bf47} version {c8df57be-6ed3-49f6-8611-bb7e1c896a3a} failed configuration in folder ” with error 0x74F00F0C-0x80070043


Ensure the above groups (that App-V is publishing too) have read access to the App-V content store. Otherwise they will get the publication from App-V Infrastructure mode – but have none of the rights to access the packages and files it contains.


Citrix PVS vdiskdif.vhdx cache file filling up and servers crashing after reboot.


We had a number of production VMs running a Citrix desktop workload on Citrix Xenapp 6.5 via Citrix PVS 7.1 (SP3) with cache to RAM with overflow to hard drive, set at 2048Mb. VMware Hypervisor 5.5 and Appv 5 SP2 with HRP4 running in full infrastructure mode (no Microsoft SCCM) and 30GB of packages running in Shared content store mode from a network file share \\server\appvshare$

Servers have 12GB Ram, with 4 vCPU’s and Windows 2008 R2 SP1

C: Drive is 40GB (with 35GB utilised)

D: Drive is 20 GB (typically 12GB utilised at any one time) with a 6.1GB Page file redirected here, an the vdiskdif.vhdx at 4mb

We have a daily reboot for the entire Citrix desktop estate estate at 3am.

Appv GPO Settings are to use Shared content mode, use the local path of c:\programdata\appv (not app-v), autoload = ALL, user and computer refresh on logon = true



After an IE11 upgrade on the Citrix vDisk, every 2-3 days some of the citrix servers would reboot (as per policy) and quickly fill up the D drive, finally crashing the server and rendering it unusable. Hoorah for PVS cache to disk.

As the machine had crashed there was little way to troubleshoot it after the fact, so we needed to capture it during.

Steps to resolve:

Increase C: Drive to 60GB using the process listed in the first section of this article – NO FIX

Increase D: Drive to 40GB to resolve. The server stopped crashing as the server didnt run out of D drive space, we then noticed that the vdiskdif.vhds was sitting at 13.6GB and growing (vs unaffected servers sitting at 4Mb) When checking the system processes, nothing was obviously running or processing. This was a nice workaround but not a final solution or fix.

We rebooted and remotely monitored the system with PSTools (sysinternals) executable “pslist -s \\servername”. During the reboot the appvclient.exe was siting 25% CPU, whilst the GPO to do a full client sync was ‘called’ and run (powershell: get-appvpublishingserver | sync-appvpublishingserver)

Our crashing was finally narrowed to the AppV client that was sporadically somehow crashing and filling the D drive. When the AppV client was stopped or the server removed from any ‘global’ publishing – the server never crashed. As soon as the production APPV packages were republished to the device, and after every 2 or 3 reboots the appvclient.exe would run, start caching files, and start filling up the D drive as it was ‘copying / caching’ the packages.

This felt very much like the AppV client was ignoring the shared content mode, and trying to cache everything locally.

Final Resolution:

The ‘gut feeling’ on this problem was that the AppV client wasnt getting the correct settings from GPO in time. The local AppV Client settings (registry) were reviewed and it seemed there were some improvements to be made.





Turns out the Appv Client settings were set to disable Shared content mode, and to autoload all apps which we are assuming its doing sometimes before it gets its required settings from GPO.






After creating a new vDisk version with the ‘New Setting’ registry keys listed above tattooed in the vDisk image  the servers haven’t crashed since.

Also we were using a GPO powershell script that tells the client to go and ‘autoload’ all the apps. So the autoload registry option was just confusing things, hence we disabled it.

Launch Internet Explorer in APP-V 5 environment & passthrough the URL

We have a package that needs to be installed and run inside the APP-V 5.0 ‘virtual environment’ or ‘bubble’.

The following command ran Internet Explorer inside the APP-V package / environment then passed Internet explorer the URL

Its a powershell script we have housed on a network share for all such XenApp scripts and specific application launching etc

Powershell Script

$AppVName = Get-AppvClientPackage “Published AppV Name”
Start-AppvVirtualProcess -AppvClientObject $AppVName iexplore.exe “http://website/page”


Citrix Published App Path:

“C:WindowsSystem32WindowsPowerShellv1.0powershell.exe” -windowstyle hidden “\serversharescript.ps1”