Internet Explorer 11 Download Manager will not start when virtualized with AppV 4.6 SP3 1

Internet Explorer 11 Download Manager will not start when virtualized with AppV 4.6 SP3
A co-worker recently ran into this problem at one of his projects. An Internet Explorer 11 add-on was virtualized using AppV 4.6 SP3 and the add-on uses the Internet Explorer Download Manager to serve up documents from a back-end. On the AppV client however pressing CTRL+J or going to the menu to start Download Manager ...

Parameter -EnablePVADControl will sometimes not work on a 64-bit machine 3

Parameter -EnablePVADControl will sometimes not work on a 64-bit machine
Bringing back the PVAD debate for one last time. Reminder: These are the three methods of bringing back the PVAD as discussed in several blog posts and the Microsoft TechNet site. Microsoft should fix this page though as they spell Compatibility right once and then spell it as Compatability in the Note. 1. Launch the Sequencer ...

Sequencing and Publishing MProof Clientele ITSM

This is a fast recipe to sequence and publish MProof’s Clientele ITSM in conjunction with App-V. The reason to blog about it is that the application popped up at several of my projects.  At my last project the solution to get Clientele ITSM to work with App-V was unknown. So here goes. The installation is ...

AppV 5.0 SP3 and the “hidden” PVAD

AppV 5.0 SP3 and the
I just downloaded the bits and bytes for the AppV 5.0 SP3 and started to play around with the PVAD that is now “hidden”. This is because a Merged roots principle was introduced. First let me take you back to version 4.x of AppV. One thing I didn’t like about AppV 4.6 and using a ...

Don’t use an UNC path as a dummy PVAD in AppV 5.x

Don't use an UNC path as a dummy PVAD in AppV 5.x
From the beta from AppV 5.x onwards I always used a dummy folder as Primary Virtual Application Directory (PVAD from now on). By doing this I always ensured that all files ended up in the virtual file system. I want all files to end up in the virtual file system because only virtual file systems ...

Sequencing Google Chrome 38.0 in AppV 5.0

It has been a while since my last blog post but I found something that’s hasn’t been blogged about or is specific enough to blog about. As far as I know… Last week I was asked to see if I could sequence Google Chrome 38.0 using AppV 5.0 with hotfix 4 applied. For the same ...

Failed to generate MSI error in AppV 5.0

Failed to generate MSI error in AppV 5.0
Yesterday I spent most of my day finding the cause of strange characters in the xml configuration files. You can find my blog about it here. While I was trying out saving the sequence in different localized sequencers (dutch and english) I came across the following error: I initially thought I broke the Windows Installer service ...

Strange characters in AppV 5.0 xml configuration files 1

Strange characters in AppV 5.0 xml configuration files
In AppV 5.0 you can overwrite the default configuration (Appxmanifest.xml in the .appv file) with two external files called DeploymentConfig.xml and UserConfig.xml. At times I would observe strange characters in these two files. See the picture below for an example of a file containing these strange characters: The files should look like this: Today I ...

Fixing WinZip MSI error when sequencing with AppV 5.x 2

Fixing WinZip MSI error when sequencing with AppV 5.x
In AppV 5.x I have been sequencing applications pointing the primary virtual application directory (PVAD) to a dummy folder like C:\apps. The primary virtual application directory is the location where the virtual file system (VFS) will be created during sequencing. The reason for using a dummy folder is the inability of AppV connection groups to ...

Unexpected behaviour when upgrading AppV 5.0 SP1 sequences

Unexpected behaviour when upgrading AppV 5.0 SP1 sequences
One of my students noticed some unexpected behaviour when upgrading an AppV 5.0 sequence for the second time. I haven’t run into this unexpected behaviour earlier because normally I make a new sequence every single time. In AppV 4.x the standard behaviour was to append the internal version number associated with the sequence to the .sft output file. ...