AppV 4.6 SP3 registry injection behavior changed from SP1

Question

Hello,
We are testing and preparing to rollout SP3 for AppV 4.6 and I came across this issue which is fairly major for us. It works 100% fine on 4.6 sp1.
We have several packages that point to c:\program files\Internet explorer\iexplore.exe (IE11) with a parameter of the URL. In addition we use the environment block to inject the proxy server settings into the registry which sets the correct proxy server.
I have tested that on SP1 this works without issue, as soon as I upgrade to SP3 with no other changes this fails to work anymore. I have tried both injecting at the environment block and in the script block as a reg add and a reg file. Nothing seems to change
the proxy. I also tried turning on and off local interaction.
In the script section I loaded the registry after adding the setting and can validate it does exist, which is even odder.
If anyone has any ideas it would be much appreciated. Below is the reg key
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"AutoConfigURL"="http://"my.proxy.com"
Thanks
Life moves pretty fast. If you don't stop and look around once in a while, you could miss it.

Answer 1

Ok, I have some more information. With additional tested outlined above I have proved out that this is not solely an APPV issue rather an APPV+IE11 issue.
Here were my results (All tests running Win7 64bit w/AppV 4.6 SP3 HF1):
1. APPV w/IE8
--- I am able to update the proxy from within the OSD using any of the standard methods (script, environment, and calling a cmd that updated instead of iexplore.exe) and everything works as expected.
--- If I put a script in the OSD and call regedit then change the proxy setting it is reflected as expected.
2. APPV w/IE11
--- I am able to update the registry from within the OSD using any of the standard methods however the update is NOT reflected when IE launches
--- If I run regedit on launch and change the proxy manually it also is NOT reflected when IE launches. I searched the entire registry and the bad proxy string does not exist anywhere. So where is IE getting this from?
3. Local IE11
-- The thought was that there are more or different registry settings needed so I modified the single key and launched local IE and the new proxy was reflected. So confirmed I am looking at the correct key and it is the only key required.
4. Set the Global HKLM setting Locally
-- This worked as expected however if I changed it on the local machine the local IE changed but the packaged IE stuck to the previous setting. I cleared everything and I even invalidated the cache and it still stuck. This is probably not a huge issue.
5. Set the Global Proxy within the package
-- For some reason this was not sticking. I need to look into this option further.
==============
RESULT: Option 4 or 5 will probably be the solution. 4 can be set in a GPO, 5 in the package if I can get that working.
==============
Note: I did contact Microsoft and they verified there are issues with APPV 4.6 and IE11 and were not able to resolve my issue. Their recommendation was to repackage. As this is a valid method it would just be too time consuming based on the total number
of packages we have in this state. IE11 should honor the registry setting as IE8 does.
==============
In case anyone's interested on how to set the Internet Explorer proxy for all users in HKLM:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings]
"ProxySettingsPerUser"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
"AutoConfigURL"=http://my.proxy.com
Life moves pretty fast. If you don't stop and look around once in a while, you could miss it.