Share via

Global File State Changes in App-V 5.0

  • Article

This post has moved here

Comments

  • Anonymous
    January 01, 2003
    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.
  • Anonymous
    December 17, 2013
    The comment has been removed
  • Anonymous
    February 05, 2014
    We have come a long way from the good ol’ .pkg files we had back in days on 4.x. I have discussed
  • Anonymous
    April 01, 2014
    CoW stands for Copy on Write and it’s a concept discussed in depth in our App-V 5 SP2 Application