Global File State Changes in App-V 5.0

This post has moved here

Comments (4)

  1. Anonymous says:

    Hi Mark, in most instances I would lean towards no. Users shouldn’t typically be changing global assets and if they are it should maybe be addressed in the sequencing of the package. Windows best practices would be to roam only the user specific roaming location in AppData. If there is important user personalisation going elsewhere this needs to get addressed on the package level.

  2. Mark C says:

    Hi Thamim. Is there a case for roaming this folder to retain these state changes in a Win 7 hot-desking environment or RDS platform?

  3. Anonymous says:

    We have come a long way from the good ol’ .pkg files we had back in days on 4.x. I have discussed

  4. Anonymous says:

    CoW stands for Copy on Write and it’s a concept discussed in depth in our App-V 5 SP2 Application

Skip to main content