App-V: On Current Recommended Practices And How They Evolve ...
Maybe your like
App-V: On Current Recommended Practices and how they Evolve . . . (a.k.a. – about that PVAD)
February 16, 2016 madvirtualizer Leave a comment Go to commentsThis morning, I was on a joint webinar with Flexera (http://learn.flexerasoftware.com/AR-WBNR-Microsoft-AppV-Best-Practices) on App-V best practices and I reminded many on the call why I always prefer to use the term "current recommended practices" as opposed to "best practices." Today I explained that I know longer insist on avoiding the use of the PVAD (Primary Virtual Application Directory) and sticking to strictly VFS sequences. True, I did make this recommendation nearly a year and a half ago (http://blogs.technet.com/b/gladiatormsft/archive/2014/08/25/app-v-5-installing-to-the-pvad-don-t-do-it-yes-i-said-it.aspx ) however, at the time, App-V 5.0 Service Pack 2 required VFS sequencing to ensure connection group convergence as well as a few others mentioned in the blog post. With the addition of the merged roots feature as well as the correction of issues with the convergence of environment variables, there is no longer any major reason to force packages to VFS sequences for the purposes of making connection groups work.
Some Applications Need the PVAD for Proper Functionality
As App-V 5.0 SP3 was released over a year ago and App-V 5.1 was released a few months back, it has become known that due to issues with pathing limits and other issues related to the App-V VFS subsystem and its native NTFS integration, there are some applications which still require the use of the PVAD. By this, I mean to actually expose the Primary Virtual Application Directory (PVAD) within the App-V sequencer and selecting that same directory during the installation of the application during the monitoring phase of the sequencer. You will find many examples of applications within the App-V community. While the number of applications requiring the use of the PVAD is a relatively small percentage, the applications that are affected represent a significant footprint that involve nearly every major enterprise organization's application library. For example, Office 2010 is one of those applications. In fact, if you were to look at the virtual file system structure of the App-V package generated by the ODT (Office Deployment Tool) you would also find that the flattened Office 2013 and Office 2016 packages are actually PVAD sequences.
Share this:
- X
Related
Categories: Uncategorized Tags: app-v, AppV, Flexera, Office, pvad, vfs Comments (2) Leave a comment-
Roy Essers February 17, 2016 at 8:01 am Reply
Thanks for pointing this out, Tim keeps track of packages which need PVAD. Have a look here: http://www.tmurgent.com/TmBlog/?p=2264
-
Vigneshwaran (MCTS) February 18, 2016 at 7:51 am Reply
Well said "current recommended practices".
- No trackbacks yet.
Leave a comment Cancel reply
On Debugging Virtual Applications: Part 1: Overview (or Let’s Start at the Beginning) App-V: Current Recommended Practices for using App-V with Azure RemoteApp RSS feed- Youdao
- Xian Guo
- Zhua Xia
- My Yahoo!
- newsgator
- Bloglines
- iNezha
Author
-
madvirtualizer
Twitter Feed
Tweets by madvirtualizerTop Posts & Pages
- App-V: Error Running Virtualized SAS Client: "Could not Load SAS font"
- SCVMM: Service Principal Names (SPNs) Required for Proper SCVMM 2008 Functionality
- App-V 5: On Dynamic Configuration
- App-V 5 Scripting: Change
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 |
Archives
- November 2024
- September 2016
- February 2016
- January 2016
- November 2015
- October 2015
- June 2015
- April 2015
- March 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- April 2012
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- September 2010
- June 2010
- April 2010
- March 2010
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- April 2009
MadVirtualizer
MadVirtualizerFollow The Mad Virtualizer at Microsoft on WordPress.com Top Blog at WordPress.com. Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. To find out more, including how to control cookies, see here: Cookie Policy
- Comment
- Reblog
- Subscribe Subscribed
-
The Mad Virtualizer at Microsoft Join 36 other subscribers Sign me up - Already have a WordPress.com account? Log in now.
-
-
-
The Mad Virtualizer at Microsoft - Subscribe Subscribed
- Sign up
- Log in
- Copy shortlink
- Report this content
- View post in Reader
- Manage subscriptions
- Collapse this bar
-
Tag » App-v 5 Pvad
-
What I Do: App-V 5 And The “Primary Virtual Application Directory”
-
About App-V 5.0 SP3 - Microsoft Desktop Optimization Pack
-
How To Sequence A New Application With App-V 5.0 - Microsoft Docs
-
Understanding The PVAD - Virtual Vibes - Algiz Technology
-
Permissions In The PVAD And VFS With App-V 5.0 - Virtual Vibes
-
App V PVAD - YouTube
-
How To Turn On Hidden Primary Virtual Application Directory (PVAD) In ...
-
All About Microsoft's Recently Launched App-V 5.0 SP3 - ISHIR
-
Demystifying The PVAD - Packageology
-
[PDF] How To Troubleshoot App-V 5 (like A Ninja)
-
App-V Deployment: Acrobat — Acrobat Desktop Virtualization Guide
-
Virtualizing The IBM Data Server Driver On Windows Platforms
-
App-V 5.x Tab - Advanced Installer
-
App-V 5 PVAD / VFS Layering Bug - Packageology