locked
Why isn't my Chrome Package Using the Virtual Directory? RRS feed

  • Question

  • I sequenced an installation of Google Chrome, and as part of the installation I imported a set of registry keys meant to set Chrome policies (per our IA guidance.)

    I checked the package afterwards, the registry keys and values are all there (HKLM\Software\Policies\Google\Chrome.)  However, after publishing the package, the policies I attempted to set are not.  As a test, I added one of the values at the referenced key in the real registry, and the policy immediately took hold.

    So the question is, "Why is the Chrome package referencing the real registry instead of the virtual?"

    I know I can set these values via GPO, but I have non-technical (political) reasons for not wanting to do that.

    I imagine if I created the registry keys and then set them in the package to merge, that would probably work, but I don't want to develop yet another solution to setup a place for App-V to put the values....might as well just create the keys and values then.

    Any ideas on the question?


    d

    Wednesday, April 1, 2015 11:45 AM

Answers

All replies