Hello,
As someone who has been using the Add-On Management feature of SP2 via Group Policy (and struggling with it due to lack of information in some respects), I'd like to point out some additions to this article which might be useful.
I'd be interested in seeing more on the use of 'Add-On Management' through the use of Group Policy. In a corporate environment for example, it is unlikely that you would want end users being able to enable/disable ActiveX controls on an 'as needs' basis - IMHO this is asking for trouble - therefore, being able to use the 'only allow ActiveX controls in this list' policy setting (which acts like a whitelist) is a good move as this then allows the IT admin to control what can and can't be used.
The problem here is that no where (or at least not so far as I have found) is there a list of standard controls and their Class IDs. Microsoft themselves do not have this information (and I know as I have been through this with PSS!)
Therefore, in order to make use of Add-On Management via Group Policy properly, a lot of donkey work is required with SysInternals 'RegMon' and other tools to try and determine which controls IE is calling when it tries to use certain functionality. Also, some of this info can be found out through looking at the source code of web pages which call such controls (for example, pages which use Flash etc.) This is easiest done by searching for 'CLSID' in the web page source code.
The additional problem here is that so much of IE's core functionality (for example, being able to use VBScript, Javascript, integrated MSN search etc.) is all delivered via ActiveX controls. Thus, enabling 'Add-On Management' and the whitelist via Group Policy immediately means that the vast majority of IE functionality ceases to work!! Hence, the need then for Regmon etc. to work out what is being accessed.
I have thus far put together a list of required ClassIDs which are needed when using Add-On Management and the whitelist via Group Policy, but I firmly believe that Microsoft should have produced this info prior to making SP2 (or at least this feature) more widely available. At the moment, it is very difficult to use properly.
A further comment about the article - the article states that enabling or 'trusting' the control of one manufacturer automatically trusts all other controls from the manufacturer.
This is certainly NOT the case if using the 'Add-On Management' whitelist via Group Policy. All specific ClassIDs have to be added. For example, if I enable Macromedia Flash by adding its ClassID to the whitelist, this does NOT automatically make Shockwave also work (and thank goodness for that, I say!!)
With Add-On Management enabled, there are some additional columns which can be turned 'on' in the 'Add-On Management' window which can be useful, especially when determining what ActiveX control ClassID to add to the whitelist (of using Group Policy to control ActiveX etc.) By right-clicking on any of the column headings in the Add-On Management window, a number of other columns can also be added. These include 'Class ID' and last accessed time as well as statistics as to how often a control has been used - these can all be very useful.
Finally, a number of core Microsoft controls do not show up in Add-On Management when blocked (although the 'ActiveX blocked' icon in the IE status bar or the Information Bar does appear.) This makes troubleshooting very difficult. Such controls which do this are those that enable VBScript and Javascript functionality for example.
Nice to see a non-MS article on use of the 'Add-On Management' feature, but I'd like to see more detail (i.e. lists of ClassIDs and use of this via Group Policy) in a later article if possible.
Regards,
Mark.