Yammer Download link

https://about.yammer.com/product/desktop-application/

Adobe Reader XI - App-V 5.0 SP2

This is treated in a very similar way to the recent previous versions.
Briefly
Download the enterprise version
Extract the MSI, create an admin point and patch the admin point.
Download and install the Adobe Customisation Wizard and use that to create a transform.

The above is necessary for a normal package.

The main problem with creating an App-V 5.0 SP2 version is that the App-V client redirects some keys through to the native registry

[HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\AppV\Subsystem\VirtualRegistry]
PassThroughPaths = REG_MULTI_SZ :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Application
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
HKEY_LOCAL_MACHINE\SOFTWARE\Policies
HKEY_CURRENT_USER\SOFTWARE\Policies

See this link for more information
http://packageology.com/2014/02/overriding-group-policy-settings-app-v/


The result is that unless the HKLM\Software\Policies value is removed from the above key, the desired settings for Adobe Reader XI cannot be available in the bubble.  An example is Updating.  If [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown]
"bUpdater"=dword:00000000
Is not a setting that can be seen then the updater item in the preferences menu will still be visible.

For an App-V version of Adobe Reader XI
HKEY_LOCAL_MACHINE\SOFTWARE\Policies
This value either needs be removed from the above registry key OR the HKLM\SOFTWARE\Policies\Adobe and below must be managed by Group Policy.

While sequencing it is very important to turn off Protected Mode and then re launching Reader and closing.  This causes important user settings to be captured in the sequence.  Also with out this mode set, launching Reader on a client results in:

This is related to the file %AppData%\LocalLow\Adobe\Acrobat\11.0\ReaderMessages which is not properly managed by a virtualised reader running in protected mode.

Keywords: passthough pass through



Windows 7 Virtual Store (redirection)

Where applications attempt to write to inappropriate locations at runtime such as C:\Programdata\Apple Computer\QuickTime\QuickTime.qtp   Windows 7 may redirect the activity to the Virtual Store which is located %LOCALAPPDATA%\VirtualStore\ProgramData\Apple Computer\QuickTime

This automatic redirection will obviously cause issues in certain situations.

App-v 5.0 SP2 Client download

App-v 5.0 SP2 Client UI Application download.

app-Client_ui_setup.msi
appv_clientUI_package.msi - this is app-v version.

http://www.microsoft.com/en-au/download/details.aspx?id=41186

Windows Application Compatibility Site

see as I can never find this quickly on search engines- here it is
http://www.microsoft.com/en-gb/windows/compatibility/CompatCenter/Home
http://technet.microsoft.com/en-us/windows/application-compatibility.aspx


Online compat search
http://www.microsoft.com/en-gb/windows/compatibility/win7/CompatCenter/Home?Language=en-US

Fluke Networks Linkware 8.1

Fluke Networks Linkware 8.1 is an MSI install in an InstallAware execuatable wrapper.

The MSI extracts out into the temp folder when the exe is run and the exe launches the MSI with a partiular command line.

The MSI is totally non-standard, probably due to the InstallAware type of generation.

The exe does support the /s switch which makes the installation silent with defaults however the driver installation part of the install which is DPINST driven prompts to user to trust drivers from the Fluke Networks vendor.  This prompt can be worked around by obtaining the registry key which is written when the "Always Trust drivers from this vendor" tick box is clicked.  It is a binary registry entry created here
HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\97A2CBA2763CAD7B8B214B4BE53ABE56380747FB

If this value is written into the registry before the exe /s is launched the installation will be fully silent.

Finally the exe is not SCCM compatible because it fails to run properly under the system account.

It is possible to use psexec.exe to remotely run the install under an admin account on the target machine.  Copy the install files to the target first then run

psexec.exe \\machinename <path to batch file>

A batch file can manage the installation of the regkey (reg.exe import of a reg file), launch the exe /s and then delete unwanted shortcuts (uninstall)

The uninstall procedure can be silent with the following batch file

C:\ProgramData\{AF40D181-8A8C-4CE5-99C4-8E2EF44E493F}\setup.exe /s REMOVE=TRUE
rd /s /q "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Fluke Networks"

IBM Websphere MQ Explorer 7.5.0.2 - install MSI special command line requirements.

The websphere MQ Explorer 7.5.0.2 MSI installation requires some parameters to be supplied via an ini file.  This ini file is specified on the command line using the USEINI parameter.

msiexec /i "IBM Websphere MQ.msi" transforms=<name> USEINI=<path> /qn

/qn or /q must be used so that the MSI is run with no user interface at all.

important: the USEINI path must be a full and absolute and not relative.  Putting the ini file in the same folder as the MSI/MST and using USEINI=myfile.ini will NOT work.

UNC paths will work.

http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.ins.doc/q009040_.htm