During the last Dutch Citrix User Group I had the honour to present a 15 minutes ‘pitch’ on Citrix AppDisks which is a newly introduced feature in XenDesktop 7.8. It’s Citrix’s implementation of the popular layering solutions for application distribution.
Archive for APP-V
Today I ran into an application issue with an application, when a normal user would start the application the application would prompt for a file. When browsing to the file and opening the file the application would throw an error message: ‘unnamed file contains an invalid path’
At the moment I’m bulding a new PVS/XA based environment with RES AM and RES WM in combination with APP-V 4.6 SP1 but when the App-V team sequenced the first application they received:App-V error 0A-0000E01E: An Unexpected error has occured. So I googled and found a support article but after changing the reg key on the client it still gave this error.
I was creating an unattended installation of the App-V 4.6 x64 for RDS using RES Automation Manager, I used an installation script from somebody else as source for this installation and the installation went without any problems. I accessed the server via a published desktop managed by RES Workspace Manager to test an application that was delivered via App-V but I couldn’t launch the application and it came up with the following errors in the eventviewer:
I recently helped building a PoC containing Citrix XenDesktop and XenApp with RES Workspace Manager and Microsoft APP-V, while testing the applications on the different platforms we discovered that a certain application had some strange looking artifacts and display errors when started on XenDesktop. These artifacts didn’t show up when started on XenApp or when using the VMware Console and start this specific application. After some research I found the following posts on the Citrix Forums:
One of my customers asked for a ‘self service tool’ for their users to remove Microsoft APP-V pkg files from their profiles. Because there’s no direct relation between the registry values and the location of the pkg files I had to be creative with a search within this script: