We even had a PFE on site who was unable to determine the cause. Eventually, I did a clean, generic, click-click install of the AppV client on a non-domain system (to exclude GPO's). I manually copied the .appv and .xml over and added/mounted/published the package via powershell with the dynamicconfiguration.xml and I saw my missing registry keys! hurray!

I then took the registry values from our non-working system and compared them to the working system. Adding in keys from the non-working system to the working system until it failed I came across the following culprit:NoBackgroundRegistryStaging REG_DWORD 0x1
When that value was set to 0x1 the registry keys from the dynamic xml file would not apply. If it was deleted or set to 0x0 then the keys applied without issue. I had originally added this key from this article:

But it appears that article didn't specify the full impact of adding this key. Steve noticed that CPU utilization was lower when publishing applications with this key set, but it appears that could be because XML processing on the dynamicconfig.xml isn't happening. Because of this removal of this great feature to add keys after package creation I would recommend removing the NoBackgroundRegistryStaging key.

Notice the Foo and EmptyKey. Those keys are set via the dynamic.xml fle.

Tuesday, June 10, 2014

We are looking to utilize AppV 5's shared content store and one of the things I was interested in was knowing what kind of overhead network performance may vs. local disk. What I have is a physical server with 3x300GB 10,000 RPM SAS drives in a RAID-5 vs. a CIFS share on SSD. The catch about the CIFS share is it is 300 kilometers (200 miles) away in another city. I used this share as I don't have another share local to the physical box and this brings the performance of the share down, but it's still faster than the disk. The IOMETER readings for the Shared Content Store and the local disk hosting the PackageInstallationRoot are:

The CIFS share is 2x faster on average, pulling 2803 IOPS vs 1324. Bandwidth of the CIFS share is faster as well, 11.48MB/s vs. 5.43MB/s for the local disk.

To test the performance I did the following, I loaded an AppV 5 application to disk, I then wrote a AutoIT script to get the start time, launch the program, wait for the login screen, once the login screen is visible get the finish time. I then stopped and started the appvclient as this ensures nothing is cached in RAM and ran the AutoIT script again. I did this thirty times. I then turned on Shared Content Store (SCS) and loaded the package in that manner and retested. The results are (average of all 30 runs):

Local Disk: 9.6s
SCS: 9.7s

For the 30 runs the Local Disk deviated +/- 0.2s from average so the range was from 9.4s to 9.8s.

For the SCS the deviation was much bigger, probably to be expected when you're pulling from a file share 6ms away across a shared pipe. Deviation on the network was:
+/- 1.85s with a range from 8.2s to 11.9s. Amazingly, there were numerous runs where the network bested the local disk under 9.4s for launch time. I'm sure if the SCS was local we'd get even more consistent performance and probably even faster performance. A local server to the share gets about 8x better IOMeter numbers.

Now, how about when the application has already been launched so files are cached? Results (average of all 30 runs):

Tuesday, June 03, 2014

With AppV 5 and connection groups, a lesson I learned today is if you want to utilize connection groups you cannot use a valid PVAD path as the PVAD will not merge with VFS or another package's PVAD. So for any application you plan on using Add-on's or Middleware you MUST set the PVAD to something that is not used and install to the VFS for both the base package and the Add-on/middleware. If you use a PVAD what ends up happening is one of the packages in the connection group will "win" and be the only thing you see when you browse the PVAD path.

In the instance of this error I found, we sequenced VMWare and I wanted to add the VMware Update Manager as a add-on/plugin to the package. I used the same PVAD for both packages initially, "C:\Program Files (x86)\VMware" and when I published each seperately to a server I saw the proper file structure for each, when I made a connection group and published both to a single server and browsed to that PVAD I only saw the contents of one of the package, not the combination of both. I then resequenced the Add-on with a VFS path and it usurped the PVAD as it was not accessible nor the file systems merge.

I found one little blurb about this on WCA-8139.pptx on slide 38: PVAD is not merged in Connection Groups.
http://video.ch9.ms/sessions/teched/na/2013/WCA-B319.pptx

Only VFS Folders and tokenized paths merge. Pure and simple. If you suspect you will use an application or a plug-in within a connection group, you will need to sequence your application a specific way when it comes to selecting a PVAD (Primary Virtual Application Directory) and an installation directory. Unlike the former DSC (Dynamic Suite Composition) where the opposite was true, non-VFS folders do NOT merge. You will need to fully VFS the packages, that is, provide incorrect ‘Primary Virtual Application Path’ (PVAD) while sequencing the packages. This puts all the files of the package under VFS folder and nothing ends up in the root folder. For example, use C:\ as the PVAD and install to its regular tokenized path (i.e. C:\Program Files, etc.) If the application does not normally install to a tokenized path, make sure you install to a different folder then the PVAD."

It's also important to note that registry keys will merge even if the underlying filesystem does not. This can make for some interesting customizations in applications that can be changed by registry only. You could publish the application to a generic group of users and then have two connection groups with two different packages and the difference between the packages is some registry keys that does something like change the server depending on the groups user location. This way a single package can serve multiple roles.