If you are using the primary user attribute to define some of your software installations in CM2012 it can be useful to audit the deployed devices in your environment to help troubleshoot issues with application deployment. I use primary user to help define software delivery such as having FAT packages only install on primary devices or have App-V applications only fully cache on a primary device. I quickly put together a query you can use to check Windows 7 machines to see if they have a primary user assigned or build a collection of machines the helpdesk can look at when trying to troubleshoot application delivery issues.
Last year in London I did a presentation on advanced sequencing scenarios with App-V. Basically I broke the session into using application compatibility shims, device drivers and finally how to use Procmon with App-V to do some basic troubleshooting. The presentation video can be found here http://www.brianmadden.com/blogs/videos/archive/2013/04/24/briforum-london-2012-advanced-sequencing-for-app-v.aspx and the deck has been uploaded over here. http://sdrv.ms/1cJz91m
This year at Briforum Chicago 2013 Nicke Kallen and myself were selected to deliver a presentation titled Application Packaging Smackdown. What we attempted to do is bring some sort of clarity as to the tooling options that are available to packagers since much has changed recently. These changes include features such as application compatibility analysis, automated application repackaging and support for virtual application packaging.
This presentation has been an interesting journey for both of us as we have discovered some surprises along the way as we took a close look at what is currently available for application packaging. One notable surprise was the inclusion of MSI Studio with ChangeBASE. The significance of this discovery has us wondering if this is the new competition to AdminStudio since there isn't much that supports Windows Installer editing, application compatibility, automated repackaging, and virtual application support into one suite.
We also take a look at more niche tools that could be used to complement other tools and make them more comparable to a suite. Unfortunately I am not going to go into deep detail at this time as we are wrapping up a whitepaper to better describe our findings. What we are doing as a bit of a teaser is to publish the slide deck used at Briforum. We've decided to release this deck on Nicke's blog which you can find over here:
Please let us know what you think, we are always open to suggestion and having our own views challenged. Here is our email alias you can use to provide feedback firstname.lastname@example.org.
Sometimes a MSI will install with error 1909. The error message would suggest there is a missing directory in the installation. Check the shortcut target. If it is a command line shortcut check that the target file in fact exists on the system. If the file does not exist the MSI will generate the 1909 error.