none
App-v 5.1 and SCCM 2012 Error RRS feed

  • Question

  • Hello, seeing this error on some of our clients trying to pull down a new application:

    CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290)

    The only way to fix this seems to be removing app-v client, deleting the left behind registry keys and reinstalling the client. I've had this happen on over 200 clients out of 2000. I need to know what is causing this to break.

    This is app-v 5.1 using SCCM 2012 to distribute its applications. This is in the app discovery log.

    <![LOG[AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [4e5461d9-c0e0-4ce6-986a-2d0967ba8bbb]. (0x87d01290)]LOG]!><time="07:45:19.945-60" date="09-14-2016" component="AppVHandler" context="" type="3" thread="3020" file="appvpackagequery5x.cpp:199">
    <![LOG[CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290)]LOG]!><time="07:45:19.945-60" date="09-14-2016" component="AppVHandler" context="" type="3" thread="3020" file="appv5xhandler.cpp:261">
    <![LOG[+++ Discovery of application [AppDT Id: ScopeId_F0F4A6E5-92F5-4175-8E12-FE0EAB530EA5/DeploymentType_e4f106b5-f6e0-41ac-8143-5ea5db2edfc7, Revision: 2] returned an error (0x87d01290).]LOG]!><time="07:45:19.945-60" date="09-14-2016" component="AppVHandler" context="" type="2" thread="3020" file="appv5xhandler.cpp:1011">


    • Edited by IanC97 Wednesday, September 14, 2016 6:52 AM
    Wednesday, September 14, 2016 6:51 AM

All replies

  • Which Version of ConfigMgr are you running? Are you using the latest Hotfix for the App-V 5.1 Client?

    Simon Dettling | msitproblog.com | @SimonDettling

    Wednesday, September 14, 2016 7:35 AM
    Moderator
  • Probably a WMI issue. Try to reinitialize the wmi namespace:

    mofcomp "C:\Program Files\Microsoft Application Virtualization\Client\AppvClientWmiProvider\Microsoft.Appv.AppvClientWmi.mof" and reboot.

    Otherwise, repair wmi.


    Roy Essers

    Wednesday, September 14, 2016 7:43 AM
  • Hello, thanks for the response. We are running SCMM version 1602. I've tried installing hotfix 4 for app-v 5.1 but same result. I've tried the mofcomp command and rebooting same result.

    What I have found is if I delete the registry key

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Packages]

    Run a resync and it seems to fix the problem.

    Wednesday, September 14, 2016 8:41 AM
  • In that case there is a corrupted package, which you need to identify.

    Roy Essers

    Wednesday, September 14, 2016 12:12 PM
  • Hello, what I don't get though is if I rebuild the client or remove app-v and install it back on it resolves the issue. If I had a corrupt package in sccm wouldn't the problem reoccur and effect all clients?
    Wednesday, September 14, 2016 12:56 PM
  • Did you ever get anywhere with this problem? We are seeing exactly the same issue on lots of machines.

    It fails on a different random package, so we agree not a specific package corruption. It then sticks on that one package and refuses to download\install any others.

    Particularly annoying now that the app-v client is baked into windows 10 as you cant remove and reinstall.

    Deleting the registry key does work and we are looking at a script to work out which package was responsible for the bloackage and remove just that entry but it would be nice to get to the bottom of why it is happening at all.

    Andy

    Tuesday, October 10, 2017 10:16 AM
  • Interesting, so you say random packages are causing this issue? How are your apps deployed? Machine or user targeted? Are they available or required.

    Roy Essers

    Tuesday, October 10, 2017 10:24 PM
  • Hi, thanks for giving it some thought.

    We are deploying via SCCM 1706 to the windows 10 1703 baked in app-v 5 client (both fully patched).

    We normally target machines with a required deployment and the applications are generally set to stream from the DP.

    However we do have some of the larger apps set to download and run. And we also target a user group with one limited licence app (this never really works nicely but that's another story). :-)

    Most machines just work ok but a fair number get stuck and will not do anything until the packages reg key is deleted.

    Once stuck on an app the app-v client will not do anything else. hundreds of these in admin event log:

    Content required by an application could not be retrieved from the network. A request for file C:\ProgramData\App-V\221D5064-4A6C-459F-87BB-D2B132E6303C\ED8AD61A-41F5-4F03-9C05-B33ED0C4B0CF\Root\VFS\Common AppData\CambridgeSoft\ChemOffice2015\ChemScript\Examples\Demo\Demo.exe from package version {ed8ad61a-41f5-4f03-9c05-b33ed0c4b0cf} failed with error The parameter is incorrect..  Check your network connection and try again.

    AND

    Content required by an application could not be retrieved from the network. A request for file C:\ProgramData\Microsoft\AppV\Client\Catalog\Packages\{62CC2DD2-2A8F-458A-BCEE-DCE67BF591AF}\{843F4930-FA90-48FF-903A-F97284B46328}\Manifest.xml from package version {00000000-0000-0000-0000-000000000000} failed with error There was no match for the specified key in the index..  Check your network connection and try again.

    operational:

    A request for the file C:\ProgramData\App-V\221D5064-4A6C-459F-87BB-D2B132E6303C\ED8AD61A-41F5-4F03-9C05-B33ED0C4B0CF\Root\VFS\Common AppData\CambridgeSoft\ChemOffice2015\ChemScript\Examples\Demo\Demo.exe from process 0xdcc is being processed as SYSTEM since no suitable user token could be found.

    In SCCM logs we see as original poster plus:

    appdiscovery.log The stuck app plus all the ones behind it in the queue get errors like:

    +++ Application not discovered. [AppDT Id: ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_47f8f6b7-5cce-4922-b90d-1756f802c3e0, Revision: 17] AppDiscovery 10/10/2017 23:10:33 3192 (0x0C78)
    +++ Local Handler found 6 applications, encountered 0 failures. (Elasped time = 0 seconds), Handler CLSID = {8B1B4B43-7CDE-4113-BDF5-3A02EAEA9B16} AppDiscovery 10/10/2017 23:10:33 3192 (0x0C78)
    +++ Enumerating all applications which use AppX detection, on WMI namespace: root\CCM\CIModels AppDiscovery 10/10/2017 23:10:33 3192 (0x0C78)
    System Context Installs are not supported with the Windows8App Apps AppDiscovery 10/10/2017 23:10:33 3192 (0x0C78)
    +++ Windows8App Handler found 0 applications, encountered 0 failures. (Elasped time = 0 seconds), Handler CLSID = {B23C3FE9-AAEE-40D9-A749-D593011AF2C0} AppDiscovery 10/10/2017 23:10:33 3192 (0x0C78)
    +++ Enumerating all App-V 5X applications. AppVHandler 10/10/2017 23:10:33 3192 (0x0C78)
    AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [5cf3ee73-986c-4441-8cfa-3288d961839b]. (0x87d01290) AppVHandler 10/10/2017 23:10:35 3192 (0x0C78)
    CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290) AppVHandler 10/10/2017 23:10:35 3192 (0x0C78)
    +++ Discovery of application [AppDT Id: ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_9c16aa50-9cb0-49c8-87e9-f6b66d727841, Revision: 8] returned an error (0x87d01290). AppVHandler 10/10/2017 23:10:35 3192 (0x0C78)
    AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [09e19e3a-b7c9-40c7-b42c-95a338044620]. (0x87d01290) AppVHandler 10/10/2017 23:10:35 3192 (0x0C78)
    CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290) AppVHandler 10/10/2017 23:10:35 3192 (0x0C78)
    +++ Discovery of application [AppDT Id: ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_5f05223b-aa9c-4b9f-baa2-66f0ff1f58db, Revision: 3] returned an error (0x87d01290). AppVHandler 10/10/2017 23:10:35 3192 (0x0C78)

    Then lots of these:

    AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [62cc2dd2-2a8f-458a-bcee-dce67bf591af]. (0x87d01290)

    CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290)

    +++ Discovery of application [AppDT Id: ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_ebb71b45-a046-4d6b-ae54-00305c8c3629, Revision: 9] returned an error (0x87d01290). AppVHandler 11/10/2017 05:23:45 5696 (0x1640)

    appintenteval.log does not mention the stuck app but does have lots of others like: ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/RequiredApplication_aeade956-2239-46ce-bb32-144dd7568784/4 :- Current State = Error, Applicability = Unknown, ResolvedState = None, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy AppIntentEval 11/10/2017 05:23:58 2756 (0x0AC4)

    cas.log is almost inactive, suspiciously quiet. appenforce.log the same, info for the last successful app install (weeks ago), and nothing since.

    Thanks for any ideas.

    Andy


    • Edited by AndyFriday Wednesday, October 11, 2017 10:12 AM
    Wednesday, October 11, 2017 10:08 AM
  • Here's the moment in the appenforce.log that it dies:

    +++ Starting Install enforcement for App DT "Pharmacology_VFS - Microsoft Application Virtualization 5" ApplicationDeliveryType - ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_69d088ed-f885-40fb-84a5-a4cc7fdf986e, Revision - 9, ContentPath - C:\windows\ccmcache\1l, Execution Context - Any AppEnforce 11/10/2017 05:11:22 2104 (0x0838)
        A user is not logged on to the system. AppEnforce 11/10/2017 05:11:24 2104 (0x0838)
    The package with GUID ec7e9133-3954-449d-883f-d098e05e6010 is not installed on this machine yet AppEnforce 11/10/2017 05:11:49 1172 (0x0494)
        Installing App-V 5.X package Pharmacology_VFS (DTId = ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_69d088ed-f885-40fb-84a5-a4cc7fdf986e, Revision = 9) AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
    The AppV 5X client is configured for use with ConfigMgr. AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
    The package with GUID ec7e9133-3954-449d-883f-d098e05e6010 is not installed on this machine yet AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
    Package: Pharmacology_VFS with version GUID 07a4a508-019b-4c8e-9065-2379264e22d6 is not installed. Will install it AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
    Configure the package Pharmacology_VFS as streaming. Use content ID Content_d21d3ab8-e421-421f-a102-490dbb62d86e and content version 1 AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
    Using content path http://sccm-blah:80/SMS_DP_SMSPKG$/Content_d21d3ab8-e421-421f-a102-490dbb62d86e.1/Pharmacology_VFS_2.appv AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
    Running App-V command ["C:\\windows\\system32\\WindowsPowerShell\\v1.0\\PowerShell.exe" -ExecutionPolicy Bypass if((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\AppV\Client' 'Enabled' -ErrorAction SilentlyContinue) -eq $null) {import-module 'C:\Windows\System32\AppvClient\AppvClient.psd1'};  Add-AppvClientPackage -Path 'http://sccm-can-dp1.ad.blah:80/SMS_DP_SMSPKG$/Content_d21d3ab8-e421-421f-a102-490dbb62d86e.1/Pharmacology_VFS_2.appv'  -DynamicDeploymentConfiguration 'C:\windows\ccmcache\1l\Pharmacology_VFS_2_DeploymentConfig.xml'] for the  machine AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
        Executing Command line: "C:\\windows\\system32\\WindowsPowerShell\\v1.0\\PowerShell.exe" -ExecutionPolicy Bypass if((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\AppV\Client' 'Enabled' -ErrorAction SilentlyContinue) -eq $null) {import-module 'C:\Windows\System32\AppvClient\AppvClient.psd1'};  Add-AppvClientPackage -Path 'http://sccm-can-dp1.ad.blah:80/SMS_DP_SMSPKG$/Content_d21d3ab8-e421-421f-a102-490dbb62d86e.1/Pharmacology_VFS_2.appv'  -DynamicDeploymentConfiguration 'C:\windows\ccmcache\1l\Pharmacology_VFS_2_DeploymentConfig.xml' with system context AppEnforce 11/10/2017 05:11:49 2104 (0x0838)
        Process 5264 terminated with exitcode: 0 AppEnforce 11/10/2017 05:11:52 2104 (0x0838)
       Opened config file C:\windows\ccmcache\1l\Pharmacology_VFS_2_DeploymentConfig.xml for package [Id = ec7e9133-3954-449d-883f-d098e05e6010] [Xml namespace=http://schemas.microsoft.com/appv/2010/deploymentconfiguration]. AppEnforce 11/10/2017 05:11:52 2104 (0x0838)
    Running App-V command ["C:\\windows\\system32\\WindowsPowerShell\\v1.0\\PowerShell.exe" -ExecutionPolicy Bypass if((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\AppV\Client' 'Enabled' -ErrorAction SilentlyContinue) -eq $null) {import-module 'C:\Windows\System32\AppvClient\AppvClient.psd1'};  Set-AppvClientPackage -PackageID ec7e9133-3954-449d-883f-d098e05e6010 -VersionID 07a4a508-019b-4c8e-9065-2379264e22d6  -DynamicDeploymentConfiguration 'C:\windows\CCM\SystemTemp\AppVTempData\ec7e9133-3954-449d-883f-d098e05e6010_DeployConfig.xml'] for the  machine AppEnforce 11/10/2017 05:11:52 2104 (0x0838)
        Executing Command line: "C:\\windows\\system32\\WindowsPowerShell\\v1.0\\PowerShell.exe" -ExecutionPolicy Bypass if((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\AppV\Client' 'Enabled' -ErrorAction SilentlyContinue) -eq $null) {import-module 'C:\Windows\System32\AppvClient\AppvClient.psd1'};  Set-AppvClientPackage -PackageID ec7e9133-3954-449d-883f-d098e05e6010 -VersionID 07a4a508-019b-4c8e-9065-2379264e22d6  -DynamicDeploymentConfiguration 'C:\windows\CCM\SystemTemp\AppVTempData\ec7e9133-3954-449d-883f-d098e05e6010_DeployConfig.xml' with system context AppEnforce 11/10/2017 05:11:52 2104 (0x0838)
        Process 4632 terminated with exitcode: 0 AppEnforce 11/10/2017 05:11:53 2104 (0x0838)
    Running App-V command ["C:\\windows\\system32\\WindowsPowerShell\\v1.0\\PowerShell.exe" -ExecutionPolicy Bypass if((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\AppV\Client' 'Enabled' -ErrorAction SilentlyContinue) -eq $null) {import-module 'C:\Windows\System32\AppvClient\AppvClient.psd1'};  Publish-AppvClientPackage -PackageID ec7e9133-3954-449d-883f-d098e05e6010 -VersionID 07a4a508-019b-4c8e-9065-2379264e22d6 -Global -ev err; if(($err -ne $null) -and ($error[0].Exception.AppvWarningCode -eq 8589935887)) {$host.SetShouldExit(4736)}] for the  machine AppEnforce 11/10/2017 05:11:53 2104 (0x0838)
        Executing Command line: "C:\\windows\\system32\\WindowsPowerShell\\v1.0\\PowerShell.exe" -ExecutionPolicy Bypass if((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\AppV\Client' 'Enabled' -ErrorAction SilentlyContinue) -eq $null) {import-module 'C:\Windows\System32\AppvClient\AppvClient.psd1'};  Publish-AppvClientPackage -PackageID ec7e9133-3954-449d-883f-d098e05e6010 -VersionID 07a4a508-019b-4c8e-9065-2379264e22d6 -Global -ev err; if(($err -ne $null) -and ($error[0].Exception.AppvWarningCode -eq 8589935887)) {$host.SetShouldExit(4736)} with system context AppEnforce 11/10/2017 05:11:53 2104 (0x0838)
        Process 5532 terminated with exitcode: 0 AppEnforce 11/10/2017 05:11:54 2104 (0x0838)
    Successfully Published 3 component(s) [[{AppVPackageRoot}]\G-Proteins\Znewgp.exe,[{AppVPackageRoot}]\Ion Channels\znewic.exe,[{AppVPackageRoot}]\Synaptic Transmission\znewcns.exe,] in package [Pharmacology_VFS] for Machine AppEnforce 11/10/2017 05:11:54 2104 (0x0838)
        CAppV5XHandler::InstallApp() completed successfully. AppEnforce 11/10/2017 05:11:54 2104 (0x0838)
    ++++++ App enforcement completed (31 seconds) for App DT "Pharmacology_VFS - Microsoft Application Virtualization 5" [ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_69d088ed-f885-40fb-84a5-a4cc7fdf986e], Revision: 9, User SID: ] ++++++ AppEnforce 11/10/2017 05:11:54 2104 (0x0838)
    +++ Starting Install enforcement for App DT "IlogCplex - Microsoft Application Virtualization 5" ApplicationDeliveryType - ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_2858278f-c821-4650-8d63-9a390656b381, Revision - 6, ContentPath - C:\windows\ccmcache\1m, Execution Context - Any AppEnforce 11/10/2017 05:16:13 7140 (0x1BE4)
        A user is not logged on to the system. AppEnforce 11/10/2017 05:16:14 7140 (0x1BE4)
    AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [ea863aba-cff1-41ca-8d91-fbe96f049851]. (0x87d01290) AppEnforce 11/10/2017 05:16:35 7136 (0x1BE0)
    CAppV5XHandler::GetExcludedFileList() failed. (0x87d01290) AppEnforce 11/10/2017 05:16:35 7136 (0x1BE0)
        Installing App-V 5.X package IlogCplex (DTId = ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_2858278f-c821-4650-8d63-9a390656b381, Revision = 6) AppEnforce 11/10/2017 05:16:35 7140 (0x1BE4)
    The AppV 5X client is configured for use with ConfigMgr. AppEnforce 11/10/2017 05:16:35 7140 (0x1BE4)
    AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [ea863aba-cff1-41ca-8d91-fbe96f049851]. (0x87d01290) AppEnforce 11/10/2017 05:16:35 7140 (0x1BE4)
        CAppV5XHandler::InstallApp() failed. (0x87d01290) AppEnforce 11/10/2017 05:16:35 7140 (0x1BE4)
    ++++++ App enforcement completed (22 seconds) for App DT "IlogCplex - Microsoft Application Virtualization 5" [ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_2858278f-c821-4650-8d63-9a390656b381], Revision: 6, User SID: ] ++++++ AppEnforce 11/10/2017 05:16:35 7140 (0x1BE4)
    +++ Starting Install enforcement for App DT "HLM-2017 - Microsoft Application Virtualization 5" ApplicationDeliveryType - ScopeId_3296E61C-2534-4B63-B809-34ADCFBDA15E/DeploymentType_0c03e878-7329-49c9-babf-8ca464178498, Revision - 3, ContentPath - C:\windows\ccmcache\1n, Execution Context - Any AppEnforce 11/10/2017 05:16:35 7140 (0x1BE4)
        A user is not logged on to the system. AppEnforce 11/10/2017 05:16:37 7140 (0x1BE4)
    AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [4f5bf112-7e0d-4dfd-a498-1eb3d4c7c9c7]. (0x87d01290) AppEnforce 11/10/2017 05:16:52 7136 (0x1BE0)
    CAppV5XHandler::GetExcludedFileList() failed. (0x87d01290) AppEnforce 11/10/2017 05:16:52 7136 (0x1BE0)

    Wednesday, October 11, 2017 10:49 AM
  • app-v client via powershell is also nicely broken:

    get-appvclientpackage
    get-appvclientpackage : Application Virtualization Service failed to complete requested operation.
    Operation attempted: Get Packages.
    Windows Error: 0x800703E7 - Error performing inpage operation
    Error module: Manifest Library. Internal error detail: 43E01234800703E7.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + get-appvclientpackage
    + ~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Get-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : GetPackagesError,Microsoft.AppV.AppvClientPowerShell.GetAppvPackage

    matching event log: A request for the file C:\ProgramData\Microsoft\AppV\Client\Catalog\Packages\{62CC2DD2-2A8F-458A-BCEE-DCE67BF591AF}\{843F4930-FA90-48FF-903A-F97284B46328}\Manifest.xml from process 0xd28 is being processed as SYSTEM since no suitable user token could be found.

    Looking at that file in explorer it is greyed out presumably as a sparse file.

    Wednesday, October 11, 2017 11:07 AM
  • I have seen a similar issue, where 2 versions of a package use the same PackageURI. This can happen if your sequencer-guy is sloppy ;-). What happens is if you create an upgrade from an other package, keep the same name, and overwrite the old version on the contentstore.
    I use the following script to determine if thats the case:
    $Catalog = "C:\Programdata\Microsoft\AppV\Client\Catalog\Packages"
    Foreach($Package in (Get-ChildItem $Packages)){ 
        Foreach($Version in (Get-ChildItem (Join-Path $Catalog $Package.Name))){
            $VersionID = $($Version.Name).Trim("{","}")
            $Manifest = "$Catalog\$($Package.Name)\$($Version.Name)\Manifest.xml"
    
            [xml]$Content = Get-Content $Manifest
    
            if((($Content.Package.Identity.VersionId).toUpper()) -ne $VersionID){
                Write-Warning "Name: $($Content.Package.Properties.DisplayName)"
                Write-Warning "PackageID: $(($Package.Name).Trim("{","}"))"
                Write-Warning "VersionID: $VersionID"
                Remove-AppvClientPackage -PackageId $(($Package.Name).Trim("{","}")) -VersionId $VersionID
            }
        }
    }
    Give it a try.
    I actualy have a CI running to detect this and a remediation script to fix the issue.  

    Roy Essers


    • Edited by Roy Essers Wednesday, October 11, 2017 8:37 PM
    Wednesday, October 11, 2017 8:14 PM
  • Thanks for the suggestion but the script is coming up clean. No duplicates, so it must be something else.

    cheers

    Andy

    Thursday, October 12, 2017 1:59 PM
  • Andy,

    It's hard to tell the cause for this, but it smells like an issue in the App-V client getting access to the "source".  You have two possible cases of this:

    1) In http streaming, it is the client getting access to the files on the DP via Http/s.  It is the App-V client service (system account of the local system) that requires this access.

    2) (More likely?)In the case of BITS, the App-V client doesn't kick in until after the package is fully in the CM cache folder of the client machine.  But if there isn't room for the full AppV file there, or you have some nefarious cleanup activity happening to manage the CM cache size, you could run into problems there.  To reduce this possibility, packages that will be targeted for BITS/Download&Run should be sequenced to force 100% of the package contents into the Primary block (the checkbox on the streaming page of the sequencer).  With this set, when the App-V client is notified about the package, it will immediately stream everything into the App-V cache and whatever cleanup happens to the CM cache won't matter.


    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "PowerShell with App-V 5 (5.1 Edition)", "The Client Book (4.x)" and "OSD Reference Book" (http://www.tmurgent.com/Books )

    Thursday, October 19, 2017 4:14 PM
    Moderator