As you may have seen, we announced that App-V 5.0 SP1 is now available as part of MDOP 2013. In our many conversations at MMS a few weeks ago, we heard a lot of excitement around 5.0 SP1 as many of you are evaluating 5.0 alongside your 4.6 deployments. We also heard at MMS and over the past few years that one of the most popular applications to sequence on App-V 4.6 is Adobe Reader. With this in mind, the App-V team has partnered with Adobe to see how we can make Sequencing Adobe Reader even easier. That partnership has produced its first result and we are happy to announce that you can now get a Package Accelerator for Acrobat Reader 11 that is officially supported by Adobe in the App-V TechNet gallery.
The 11.0.01 update of Adobe Reader includes two tools to help virtualize the application on the Microsoft App-V platform. These tools include a Package Accelerator and an App-V Reader MSI, which installs a few DLLs and creates some registry entries to support shell extensions, browser integration, and PDF ownership.
For deployment details, refer to the App-V documentation in the Acrobat Enterprise Toolkit at http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/appv.html.
This is great for those still using 4.6, but are there plans or any documentation for App-V 5?
The link references to instruction for App-V 4.6, where is it for App-V 5?
Seriously, get Adobe reader working with app-v 5.0. I would go with app-v in a heartbeat if it were supported (along with Office 2013 KMS, not just the office365 click-to-run package).
As everyone else has said, this is for 4.6 not 5.0. Why do Microsoft push their customers towards latest and greatest and then develop solutions/tools for older products?!!
I do not understand where the benefit is in virtualizing Adobe Reader if I have to deploy an MSI along with it in order to get it to work! That's practically twice the work. Am I missing something here?
@Dustin W. In the case an legacy programs needs an older version locally. In this case you can sequence the new version to be used next to the old one. When the legacy program is compatible with the new version you can update the local one.