{"id":2240,"date":"2015-01-06T09:56:17","date_gmt":"2015-01-06T14:56:17","guid":{"rendered":"https:\/\/www.tmurgent.com\/TMBlog\/?p=2240"},"modified":"2015-09-30T15:29:32","modified_gmt":"2015-09-30T19:29:32","slug":"app-v-internet-explorer-add-on-conflict-watch-those-registry-keys","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=2240","title":{"rendered":"App-V Internet Explorer Add-on Conflict: Watch those Registry Keys"},"content":{"rendered":"

Students\u00a0run into this problem in our App-V training classes<\/a> every time.<\/p>\n

The Problem<\/strong><\/p>\n

In one of the labs we deal with creating and deploying a handful of browser plugins in a connection group.\u00a0 And everyone runs into an issue of some of them seemingly not working.\u00a0\u00a0The lab specifies a set of plug-ins to use, but I usually encourage students to work off-script and sequence from a bigger set I have available or download something they use at work.\u00a0 Typically, they sequence a bunch of add-ons, running a smoke test on each to verify operation.\u00a0 Then, when they place them in a connection group, some don’t appear in the browser.<\/p>\n

The Cause<\/strong><\/p>\n

The problem happens due to created registry keys.\u00a0 Add-ons to the Internet Explorer are registered via one of several registry keys, by adding in a subkey with the appropriate information.\u00a0 But out of the box, the naked OS does not have the base keys that you register under.\u00a0 Thus, when you install the plug-in it creates the base key along with its subkey, both of which are then marked as “Override Local” keys.<\/p>\n

In particular, I have noticed the following keys (under HKLM or HKCU):<\/p>\n