I discovered that apparently App-V ignores the HKEY_LOCAL_MACHINE\SOFTWARE\Policies and
HKEY_CURRENT_USER\SOFTWARE\Policies Registry keys by design. I was able to overcome this issue with the info provided here:
After utilizing the tool and successfully surpassing that issue, I'm finding a new problem in play.
I've been tasked with creating an App-V version of Chrome (81) with an extremely locked down configuration. Namely, my InfoSec team wants this instance of Chrome to be accessible only to specific URLs. I have tried two methods of applying the necessary settings to the Chrome install during sequencing and both result in the same behavior when packaged and deployed.
1. Scenario one is using Group Policy to configure the required settings, create a backup of that group policy and apply the backup to local group policy on the (non-domain joined) sequencer through LGPO. This successfully applies the required policy and after sequencing Chrome behaves as intended. i.e. All URLs are blocked except the ones listed in the URLWhitelist provided. However, once I deploy this AppV package to an end point (using SCCM CB), Chrome installs successfully but the settings are no longer effective.
2. Scenario two is using Chrome's Master Preference file to configure (most of) the settings. The setting for Blacklist/Whitelist of URLs is not available in the master preference file, so I applied it using a registry command after the Chrome installer completes. Again, this method succeeds on the sequencer, but when deployed these settings are not effective.
In both cases when I view the the .appv file through TMEdit I can see the registry changes and GPO policies being flagged by the tool. I am intentionally leaving them and only "fixing" unrelated items (namely the ShortName fix) but to no avail.
I've been using AppV on and off for years with success, but have never been tasked with a package of this complexity. Are there some best practices that I should be following here? Perhaps there's another tool I'm missing on the site that would aide me?
Is there a way to ensure these policy/settings configurations are retained in the resulting .appv?