As outlined by Ben’s article in Citrix blogs (see: https://www.citrix.com/blogs/2018/06/15/using-app-v-dynamic-deployment-user-configuration-files-with-xenapp-7-18/ )
a key new feature that has been added and long sought after was the ability to alter the dynamic configuration files that came with your app-v package. Delighted this piece is in now as a million and one use cases for it and just wish it was part of the LTSR release which would make it even better.
Essentially in tandem with the app-v sequencing feature for install capture in AppDNA (see: https://docs.citrix.com/en-us/dna/current-release/configure/install-capture/dna-execution-profiles/dna-execution-profile-appv-51.html) this helps speed up packaging times, also provides more flexibility in the testing cycle as most times will be looking to amend the deployment files rather than that binaries within the app-v package itself.
Been getting instances of this recently with our BYOD environment relating specifically with windows 10 devices. Seems the default behavior for the later version of receivers is reverting to the light version which cuts off some functionality required to make user’s be heard on skype calls – they can hear but cannot be heard. Enclosed are steps to resolve this.
Troubleshooting Windows 10 iFlex Skype audio issues_update
Further to an earlier post i did relating to a similar error message I did come across this issue again in 2 separate environments. Oddly v.uneven in how often it would happen but it would only occur with the app-v published applications we had.
Summary of environments
Both Xenapp 7.13
VDA’s running 7.15
Published to VDA’s running MCS and PVS images respectively.
Band-aid fix was to reset the profile in Director. Did see instances of “bad” profiles having files in their AppData\local\Microsoft\Credentials folder but a removal didn’t do anything.
Ultimately came down to controller version. Upgrading environments to the 7.15 LTSR resolved the issue. If you review the readme for 7.15 it details the fix specifically:
When launching an App-v package using the Microsoft App-V 5.0 infrastructure integrated with XenDesktop, the App-V package might fail to synchronize and the following exception occurs:
“Cannot start <applicationname>” [#LC5483]
Shout out to Wendell who posted some great recommendations regarding the above setup – will definitely save some time for folks in the long run particularly relating to UPM configuration piece and getting that right, details enclosed:
Recently came across this question on the citrix discussions and must say Martin has come up with a novel approach to what could of required a more complicated solution – see thread below:
From time to time might encounter issues relating to your WMI provider service. This service interacts directly with the SCCM client so is an important one as would affect in a lot of cases to patch your systems. Have seen this pop-up moreso in pre-2012 r2 environments but still does.
Regards automating fixes for this issue there is an auto-recover facility that comes with Window server OSes 2008 r2 or later.
on how to enable.
Recently setup a pool of Citrix VDA’s (7.16) to house app-v packages for publication using SMB/Single Admin mode.
On setting up (thought I) followed all the steps outlined in:
but missed a key action on first pass, when launching my app in citrix i would get the “cannot Start <App-name>” message (pretty common and not terribly informational 🙂
Anyways said the key action i did miss was as per above eDoc:
“Tip: After you install the App-V client, with Administrator permissions, run the PowerShell Get-AppvClientConfiguration cmdlet, and ensure that EnablePackageScripts is set to 1. If it is not set to 1, run Set-AppvClientConfiguration -EnablePackageScripts $true.“
Once implemented was all good to go.