I suggest you ...

App-V 5.x allow pathpassthru be optional per package and not global

App-V v4.6 has the ability to leverage native registry access, but the App-V virtual registry bubble writing takes precedence (http://support.microsoft.com/kb/2750869/en-us). With App-v 5.x, there is a change in how App-V handles writing to native registry. The change is a global workstation change that if you modify the global settings to specify a registry path to be written to in the native registry, it will apply to all App-V packages and will take precedence in any App-V package virtual registry bubble edits (https://www.vmadmin.co.uk/microsoft/88-app-v/418-app-v-5-x-write-to-the-native-registry).

Would be nice if App-V 5 allows the similar capabilities at a per package level as was there from v4.x or at least give the option per package to either to writ to the virtual or native registry, but not force all to have one or the other.

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jeff Ranta shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base